SilverHawk replied to the thread Upcoming changes.
It's 1st Jan 2025 and I'm ready to purchase a perpetual license..... :thumbup: :)
SilverHawk replied to the thread Using the JavaScript Date functions in Filename Override.
Happy New Year everyone. In Pro, if anyone wants an output filename in the format:
original path\original filename-yyyy.mm.dd-hh.mm.ss.original extension
then the following works on Windows 11. Took me ages to get this to work but the secret is to ensure there are no carriage returns etc in the datetime string and no hidden characters before the starting "${" or after the final "}"
${
d = new Date();
p = /^[0-9]$/;
s1 = '-';
s2 = '.';
datetime = d.getFullYear().toString() + s2 +…
SilverHawk replied to the thread Using the JavaScript Date functions in Filename Override.
That's great! :thumbup:
SilverHawk reacted with to Vouk’s post in the thread Using the JavaScript Date functions in Filename Override.
SilverHawk replied to the thread Using the JavaScript Date functions in Filename Override.
Thinking about it some more, may be this should be an enhancement request 8)
OutputFile.Timestamp as YYYYMMDDHHMMSS
SilverHawk replied to the thread Using the JavaScript Date functions in Filename Override.
Many Thanks for your help...all seems to be working now. Some questions related to this:
How much JavaScript can one put in this field? i.e. can I create a single Date instance with "const d = new Date()" and then refer to d.getMonth()?
Does this field have a fixed length?
I'd like to create a mask like <original path><original filename (excl extension)-YYYYMMDDHHMMSS<extension>. I'm almost there with the following, and have worked out that I can add a 1 to getMonth() so that function…
SilverHawk posted the thread Using the JavaScript Date functions in Filename Override.
I'm using Voukoder Pro 2.0.0 (beta) with Vega Pro 22 on Win 11 Pro
I've tried to use most of the displayed JavaScript Date functions to construct an output filename but, whenever one is used, Voukoder is unable to start. Is this a bug or a training issue (!)? ${OutputFile.Absolute} etc work fine, it's just these embedded Date() calls.