[SOLVED] Console mode creates _orig_12345678 file
Posted: Tue Apr 18, 2023 1:37 pm
Hi
Did not use Console mode for a while but always keep up to date. I did a PowerShell script to automate things and the result of that script was fine up until today. For some reason, a backup file ending with _orig_12345678 (random 8 digits numbers) is created and i didn't had that behavior before.
Command line is:
xrecode3cx64.exe -i "AlbumPath\*.flac" -q /fileexists 2 /createinsrc /dest flac /compression 4 /pt /n /na /nafa /nsaa /nebl "-180"
The files are normalized correctly but the backup is left over and i do not want that (and did not had that before). Another tools rans after that creates an EBU report file. This report trigger if the folder (album) should be normalized or not. As the report also contains backup files that are not compliant with EBU, the folder will be normalized again and again...
Of course, i can put an action before running the EBU report and delete manually the _orig_11111111 but....
Regards
JF
Did not use Console mode for a while but always keep up to date. I did a PowerShell script to automate things and the result of that script was fine up until today. For some reason, a backup file ending with _orig_12345678 (random 8 digits numbers) is created and i didn't had that behavior before.
Command line is:
xrecode3cx64.exe -i "AlbumPath\*.flac" -q /fileexists 2 /createinsrc /dest flac /compression 4 /pt /n /na /nafa /nsaa /nebl "-180"
The files are normalized correctly but the backup is left over and i do not want that (and did not had that before). Another tools rans after that creates an EBU report file. This report trigger if the folder (album) should be normalized or not. As the report also contains backup files that are not compliant with EBU, the folder will be normalized again and again...
Of course, i can put an action before running the EBU report and delete manually the _orig_11111111 but....
Regards
JF