-
BATCH RENAMING. I have been using a simple preset for removing spaces from file names for years now. When used in WL12, the program freezes, stops responding after I hit NEXT on the Operations window. The same preset works fine in WL11.
-
Metadata Origination Date/Time: The new CREATE AUTOMATICALY check box does not seem to have any effect. Whatever is present in the field below is what gets entered when rendering. I was expecting something like @Date11@ to be generated.
Please send me this preset.
Did you read the following, and if yes, do you still say there is an issue?
Here is the Batch Renaming preset which is crashing WL12. Thanks for looking into it.
Remove Spaces.zip (558 Bytes)
Well, it seems my understanding was in error. I thought there was a topic from last year where, in this recent update, the current Date/Time would be entered automatically at time of rendering. That is the reason for my presumption.
As it is, when rendering masters, whatever was previously entered in the Date/time field gets written unless manually changed. So itâs easy to have an incorrect date get written. Even a blank field would be preferable to an incorrect date, but that is not even possible. It would be very welcome not to have to tweak the metadata manually every time I render a new master. I would rather have that simple task be automated. For example, I can use custom variable @DATE11@ in the RIFF chunk to get the exact time of the render. It would be great if that same variable could be entered in the BWF chunk as well. Then they would match exactly.
I assume there must be a reason/benefit for how the CREATE AUTOMATICALLY feature currently functions in this first scenario but Iâm not seeing it.
[/quote]
From a Montage, if I render ALL TITLES IN A GROUP and CREATE AUTOMATICALLY is checked, the time written in the resulting file is still whatever date is in the entry field, not the start of the rendered range. So I must not be clear on how this option works in this second scenario, either.
I could reproduce the problem. This will be fixed in 12.0.30
The problem is not caused by your particular preset, but by the present of ancillary files.
eg. if you have piano.gpk next to piano.wav, then the problem happens. The temporary solution is to erase these temporary files.
1 Like
Concerning the Date/Time and Timeline Reference, I canât reproduce any problem.
I have rendered the titles of an album group (I assume this is what you meant, by âgroupâ), and checked the two options in the montage metadata options, and the audio files were rendered with the correct BWF Date/Time and Timeline references.
If you still think there is a problem, please upload a montage and a more detailed procedure of what you are doing.
I tried it again and now get the results you explained. I guess I just needed some more practice to get it. Thanks for your patience. Seems to work as advertised. This function is not of much use to me, unfortunately. I was hoping that check box would automatically enter the current date. Something like thisâŚ
When rendering REFs or Masters, I recall a format preset with the relative metadata configured as I wish. Except I have to click through a bunch of submenus to manually enter current date/time for the BWF chunk. Every time. We make many masters a day and thinking back on the now decades spent going through this procedure adds up to a lot of time.
It is not a crucial request, but would make life just that little bit nicer. Again, I would be happy if the Origination Date/Time field could accept custom variables.
I donât get it.
- The check box allows to enter the current date/time at the moment the file is being rendered.
- The âclockâ buttons allows to set into the field, the current date/time, at the time when you click.
Therefore, if on one hand, having both the check box and custom date does not make sense, on the other hand, the current options cover âall casesâ. Therefore, I donât understand why you say:
When rendering REFs or Masters, I recall a format preset with the relative metadata configured as I wish. Except I have to click through a bunch of submenus to manually enter current date/time for the BWF chunk. Every time.
I just tried a render again, step by step, and it actually works as I wished. I donât know why I got an erroneous result earlier. Operator error on my part, I guess. Anyway, this is working just as I had hoped. Thank You.
1 Like
In case its helpful to know, if I try the Batch Rename on a folder which contains only .wav files (and no other ancillary files) WL still crashes on my system. Even after a fresh computer reboot which I presume would mean WL does not have its hooks on temporary files yet?
Crash or Freeze?
Freeze. Application not responding.
1 Like
Today I rendered masters with the following render metadata preset:
This was written into the resulting wav file:
The date should have automatically been TODAYâs date.
This inconsistency is very confusing. Sometimes the current date is entered and sometimes whatever was ârestingâ in the date filed is entered. Something is not completely working as it should.
1 Like
What type of render did you do? Titles, clips, whole montage?..
Sorry for interfering the dialogue. But I have observed the same effect, the option âCreate Automaticallyâ doesnât work as expected. Following procedure:
[1] Enter a date manually in the metadata of the montage:
[2] Render montage into an audio file; the date appears correctly in the audio file:
[3] Activate the âCreate Automaticallyâ option in the metadata of the montage:
[4] Render the montage once again; incorrectly, NOT the date at the time of rendering is written into the audio file, instead the manually entered date is written again:
Now, if you look again in the metadata of the montage, the automatic option is NOT activated. Apparently, the activation of the âCreate Automaticallyâ option was NOT applied when the metadata dialog box was closed. Therefore, it did not write the automatic date into the audio file.
Even if there are only wav files in the folder, as soon as you open one of them in WaveLab, a temporary gpk file is created in this (or another designated by option) folder (e.g. âXY.wav.gpkâ for âXY.wavâ). WaveLab by default does not delete this file if you close the wav file. Only if the option âDelete Peak Files When Closing Audio Filesâ is activated and WaveLab is closed once it will be deleted from then on.
The presence of this gpk file leads to the freeze when renaming. Alternatively, you can delete the file in Explorer and renaming will work again.
I have to check this next week (the date thing).
For the renaming, I think the problem has been identified and fixed.
1 Like
Maybe i have lost something from the topic but my Metadata window is not like the one displayed above.
Thereâs no âCreate Automaticallyâ checkbox. Thereâs only the small clock there.
And it seems to be working fine.
When i press the clock it inserts the current time and date that is then embedded in the file as Metadata.
I am using WL 12.0.20 under Windows 10 and running it as Administrator.
Probably because you are opening this dialog from the audio editor.
The check box options are only there when using the dialog from the montage, or when you edit the file format. The later case is when for example, you want to record from WaveLab and have the Origination Date/Time set to the day/time you record.
h
1 Like
Superb! I have learned something new.
And indeed, i was working from the Audio Editor. Thatâs the mode i use WL for, most of the time.
Thankyou!