Intellectual vs Logical - Revision history

Scpstu32 at 21:22, 4 March 2011

2011-03-04T21:22:14Z

←Older revision		Revision as of 21:22, 4 March 2011
Line 142:		Line 142:
	(updated 2/3/10, Jody DeRidder)		(updated 2/3/10, Jody DeRidder)

-	(updated 9/29/10; 3/4/11, Nitin Arora)	+	(updated 9/29/10, Nitin Arora)
		+
		+	(updated 3/4/11, Nitin Arora)

Scpstu32: /* Audio (reels, etc.) */

2011-03-04T21:21:27Z

Audio (reels, etc.)

←Older revision		Revision as of 21:21, 4 March 2011
Line 142:		Line 142:
	(updated 2/3/10, Jody DeRidder)		(updated 2/3/10, Jody DeRidder)

-	(updated 9/29/10, Nitin Arora)	+	(updated 9/29/10; 3/4/11, Nitin Arora)

Scpstu32 at 21:19, 4 March 2011

2011-03-04T21:19:37Z

←Older revision		Revision as of 21:19, 4 March 2011
Line 116:		Line 116:
	Note: This also applies to situations where multiple performances exist on the same WAV file but may have differing playback requirements in terms of speed and/or direction.		Note: This also applies to situations where multiple performances exist on the same WAV file but may have differing playback requirements in terms of speed and/or direction.
	That is to say, if such a situation exists, the WAV file will be duplicated.		That is to say, if such a situation exists, the WAV file will be duplicated.
-	Then the appropriate adjustments regarding speed and/or direction will be made and such changes documented in the ~~audio decision list~~ to the level required to revert the file back to its original state.	+	Then the appropriate adjustments regarding speed and/or direction will be made and such changes documented in the digitization log to the level required to revert the file back to its original state.

Scpstu32: /* Audio (reels, etc.) */

2010-09-29T15:38:14Z

Audio (reels, etc.)

←Older revision		Revision as of 15:38, 29 September 2010
Line 142:		Line 142:
	(updated 2/3/10, Jody DeRidder)		(updated 2/3/10, Jody DeRidder)

-	(updated 7/01/10, Nitin Arora)	+	(updated 9/29/10, Nitin Arora)

Scpstu32: /* Audio (reels, etc.) */

2010-09-29T15:29:39Z

Audio (reels, etc.)

←Older revision		Revision as of 15:29, 29 September 2010
Line 61:		Line 61:
	Obviously, the file names used for these WAV files may not at all correspond to the web delivery file names of the intellectual item.		Obviously, the file names used for these WAV files may not at all correspond to the web delivery file names of the intellectual item.

-	Presented below are three example scenarios and the file naming methodology that will be employed to address the issues contained within. For the examples below it is assumed that no anomalous situations regarding channel configuration exist - that is to say that per what is outlined above there will be only one WAV file made per side per reel.	+	Presented below are three example scenarios and the file naming methodology that will be employed to address the issues contained within. For the examples below it is assumed that no anomalous situations regarding channel configuration exist - that is to say that per what is outlined above there will be only one WAV file made per side per reel in the examples below.

Scpstu32: /* Audio (reels, etc.) */

2010-09-29T15:28:58Z

Audio (reels, etc.)

←Older revision		Revision as of 15:28, 29 September 2010
Line 57:		Line 57:
	We currently are considering a "performance" to be an intellectual item. That "performance" may simply be a home practice session, a lecture, or some other sensible division of an intellectual whole.		We currently are considering a "performance" to be an intellectual item. That "performance" may simply be a home practice session, a lecture, or some other sensible division of an intellectual whole.

-	Currently we are creating one WAV file per interconnected channels per side per reel. That is to say if there are two monaural sides for a reel, two monaural WAV files will be made. If there are two stereo sides for a reel, two stereo WAV files will be made. If one side consists of a monaural track and the other side is stereo, one monaural WAV file and one stereo WAV file will respectively be made. If a reel consists of a 4-track recording, one stereo WAV file will be made (i.e. each channel of the WAV file will contain a mix of two channels on the reel). If there are two discrete monaural tracks on one side, two monaural WAV files will be made. That is to say only monaural and stereo WAV files will be made, with a WAV file existing to house all interconnected channels per side per reel with the stipulation that stereo WAV files are made by default when more than one analog channel ~~is to be captured onto one WAV file~~.	+	Currently we are creating one WAV file per interconnected channels per side per reel. That is to say if there are two monaural sides for a reel, two monaural WAV files will be made. If there are two stereo sides for a reel, two stereo WAV files will be made. If one side consists of a monaural track and the other side is stereo, one monaural WAV file and one stereo WAV file will respectively be made. If a reel consists of a 4-track recording, one stereo WAV file will be made (i.e. each channel of the WAV file will contain a mix of two channels on the reel). If there are two discrete monaural tracks on one side, two monaural WAV files will be made. That is to say only monaural and stereo WAV files will be made, with a WAV file existing to house all interconnected channels per side per reel with the stipulation that stereo WAV files are made by default when more than one analog channel exists per "performance".

	Obviously, the file names used for these WAV files may not at all correspond to the web delivery file names of the intellectual item.		Obviously, the file names used for these WAV files may not at all correspond to the web delivery file names of the intellectual item.

Scpstu32: /* Audio (reels, etc.) */

2010-08-24T21:33:35Z

Audio (reels, etc.)

←Older revision		Revision as of 21:33, 24 August 2010
Line 74:		Line 74:
	u0008_0000002_0000014.3.wav		u0008_0000002_0000014.3.wav

-	Here we are following the file naming convention used previously for multiple batches of spreadsheets (for large or continuing collections), to indicate that each is only a portion of the whole; to recreate the whole, all these numbered parts would need to be concatenated in the order indicated by the number preceding the extension. Basically, these parts constitute modules ~~- parts of the whole~~.	+	Here we are following the file naming convention used previously for multiple batches of spreadsheets (for large or continuing collections), to indicate that each is only a portion of the whole; to recreate the whole, all these numbered parts would need to be concatenated in the order indicated by the number preceding the extension. Basically, these parts constitute modules.

	This clarifies that all these files are part of the same performance, but they may NOT have a one-to-one correspondence with the intellectual division of this performance into works.		This clarifies that all these files are part of the same performance, but they may NOT have a one-to-one correspondence with the intellectual division of this performance into works.

Scpstu32: /* Audio (reels, etc.) */

2010-08-24T21:32:11Z

Audio (reels, etc.)

←Older revision		Revision as of 21:32, 24 August 2010
Line 74:		Line 74:
	u0008_0000002_0000014.3.wav		u0008_0000002_0000014.3.wav

-	Here we are following the file naming convention used previously for multiple batches of spreadsheets (for large or continuing collections), to indicate that each is only a portion of the whole; to recreate the whole, all these numbered parts would need to be concatenated in the order indicated by the number preceding the extension.	+	Here we are following the file naming convention used previously for multiple batches of spreadsheets (for large or continuing collections), to indicate that each is only a portion of the whole; to recreate the whole, all these numbered parts would need to be concatenated in the order indicated by the number preceding the extension. Basically, these parts constitute modules - parts of the whole.

	This clarifies that all these files are part of the same performance, but they may NOT have a one-to-one correspondence with the intellectual division of this performance into works.		This clarifies that all these files are part of the same performance, but they may NOT have a one-to-one correspondence with the intellectual division of this performance into works.
Line 91:		Line 91:

	Documentation - an XML-based Audio Decision List - in the Admin folder (the Documentation folder of the archive) will contain information spelling out how the separate intellectual items are to be derived from the WAV files.		Documentation - an XML-based Audio Decision List - in the Admin folder (the Documentation folder of the archive) will contain information spelling out how the separate intellectual items are to be derived from the WAV files.
-	For information ~~on the audio decision list used~~, see [[~~AudioRegent~~]].	+
		+	For information, see "SimpleADL" under [[Audio_Specifications_and_Standards#Resources_and_Links]].

	Note: The existence of multiple WAV files per performance mandates the creation of one MP3 file per intellectual division (i.e. the "track") per WAV file.		Note: The existence of multiple WAV files per performance mandates the creation of one MP3 file per intellectual division (i.e. the "track") per WAV file.

Scpstu32: /* Audio (reels, etc.) */

2010-08-24T21:28:52Z

Audio (reels, etc.)

←Older revision		Revision as of 21:28, 24 August 2010
Line 90:		Line 90:
	u0008_0000002_0000014_0005		u0008_0000002_0000014_0005

-	Documentation - an XML-based Audio Decision List - in the Admin folder (the Documentation folder of the archive) will contain information spelling out how the separate intellectual items are to be derived from the WAV files. For information on the audio decision list used, see [~~http://blog.humaneguitarist.org/projects/audioregent/#SimpleADL SimpleADL~~ ].	+	Documentation - an XML-based Audio Decision List - in the Admin folder (the Documentation folder of the archive) will contain information spelling out how the separate intellectual items are to be derived from the WAV files.
		+	For information on the audio decision list used, see [[AudioRegent]].

	Note: The existence of multiple WAV files per performance mandates the creation of one MP3 file per intellectual division (i.e. the "track") per WAV file.		Note: The existence of multiple WAV files per performance mandates the creation of one MP3 file per intellectual division (i.e. the "track") per WAV file.

Scpstu32: /* Audio (reels, etc.) */

2010-07-13T21:10:15Z

Audio (reels, etc.)

←Older revision		Revision as of 21:10, 13 July 2010
Line 53:		Line 53:


-	Audio reels,etc. may or may not correspond to the intellectual object. The capture of the performance may in no way relate to the number of reels used, or where that performance capture began on a reel. That is to say, a performance may span multiple discrete channels on a reel, multiple reels, and a reel may contain multiple performances, and a performance may span only part of one reel and only part of another.	+	Audio reels, etc. may or may not correspond to the intellectual object. The capture of the performance may in no way relate to the number of reels used, or where that performance capture began on a reel. That is to say, a performance may span multiple discrete channels on a reel, multiple reels, and a reel may contain multiple performances, and a performance may span only part of one reel and only part of another.

	We currently are considering a "performance" to be an intellectual item. That "performance" may simply be a home practice session, a lecture, or some other sensible division of an intellectual whole.		We currently are considering a "performance" to be an intellectual item. That "performance" may simply be a home practice session, a lecture, or some other sensible division of an intellectual whole.