View Single Post
Old 10-16-2018, 08:12 AM   #1
LuCsa
Human being with feelings
 
Join Date: Aug 2016
Posts: 87
Default Recording Take Counter and Wildcard

Concerning...
*************
... the introduction of a "recording take counter" and a corresponding wildcard.

As a "recording take" I declare the act of recording one or multiple record-armed tracks until this very recording is stopped. (This term is used to avoid confusion with the already existing "takes".)


Request
*******
o) An internal integer counter, whose initial value can be set by the user, which increases by one with every accepted recording action.
o) A corresponding wildcard which contains the current value of said counter in order to use it in the filename of the saved audio files after a recording action.


Benefit
*******
Currently, available wildcards to differentiate recorded takes/files are only those providing date and time information. A counter as proposed would provide short and clear file name/recording take nomenclature.


Reason
******
Especially in classical recording sessions, in which the recording engineer makes important notes about the current take in the score and where quick note taking and quick communication with the tape operator is essential, the described nomenclature is common and of big advantage.
At the beginning of each take its later recording take number is already known, whereas the time/date information under which it will be saved is not (and cumbersome to use for communication and documentation purposes).


Implementation/thoughts
***********************
o) internal integer counter with a user-definable initial value
o) wildcard (e.g.: $rectake) prints current value of counter
o) if one or more recorded items are accepted after record stop, the counter increases (and is used if the wildcard is used in the file name). It remains unmodified otherwise.
o) internal integer variable keeping track of the last used (!) counter value. This can be used to inform the user of potential file name conflicts in case (s)he modified the counter value between two recording actions.

Last edited by LuCsa; 10-16-2018 at 08:44 AM.
LuCsa is offline   Reply With Quote