24.11.2017, 07:57
24.11.2017, 11:58
(24.11.2017, 07:57)Selur Wrote: [ -> ]Hopefully I fixed it yesterday, but was to sleepy and forgot to attach the new version.Using the previous command example:
-> please try attached version
Cu Selur
Code:
"MediaInfoRenamer.exe" --EncodingSettings="crf %crf%#%ip_ratio%#%pb_ratio%#qcomp%qcomp%" --Separator="#" --Merger="_" test.mkv
Code:
Renaming 'test.mkv' to 'test_crf 28.0_qcomp0.80.mkv'.
With the 'broken example', output is:
Code:
Renaming 'test.mkv' to 'test_qcomp0.80.mkv'.
25.11.2017, 04:57
Sorry uploaded the wrong Version. Will fix once I'm back Home and got some sleep. Friend of mine married today and, so I'm Out of Order atm.
25.11.2017, 14:16
Try the attached version.
Cu Selur
Cu Selur
25.11.2017, 21:48
(25.11.2017, 14:16)Selur Wrote: [ -> ]Try the attached version.Seems to work correctly in all of my tests thus far.
Cu Selur
Sidenotes (for consideration for future versions):
- Using or including a space character in the Merger could improve output readability in some use cases (when the resulting filename is split into multiple lines in a file browser), however currently using a space character as Merger results in: "Error: Missing a 'Merger' parameter" and when used as an additional character, like this: --Merger="; " it gets ignored unless another character is added after it.
- Not sure if placing the standard Merger between the original filename and the first addition is always ideal, but i don't see any significant drawbacks to it either. Replacing it with an optional prefix (and possibly suffix) option(s), would solve any potential issues though.
- When a file includes multiple audio tracks, there is no separation of any kind between their readouts.
26.11.2017, 08:33
Quote:When a file includes multiple audio tracks, there is no separation of any kind between their readouts.How could there? The Renamer doesn't have any concept of the stream count number or anything.
![Big Grin Big Grin](https://forum.selur.net/images/smilies/biggrin.png)
Quote:Not sure if placing the standard Merger between the original filename and the first addition is always ideal, but i don't see any significant drawbacks to it either. Replacing it with an optional prefix (and possibly suffix) option(s), would solve any potential issues though.Not sure either if it's a good idea either.
Quote:Using or including a space character in the Merger could improve output readability in some use cases (when the resulting filename is split into multiple lines in a file browser), however currently using a space character as Merger results in: "Error: Missing a 'Merger' parameter" and when used as an additional character, like this: --Merger="; " it gets ignored unless another character is added after it.I probably added a 'trim' somewhere.
![Smile Smile](https://forum.selur.net/images/smilies/smile.png)
-> Added a new version which:
a. shouldn't 'trim off' spaces.
b. has a new parameter:
Code:
--FileSeparator: Place this text between the file name and the addition, when not used, 'Merger' will be used.
26.11.2017, 13:16
(26.11.2017, 08:33)Selur Wrote: [ -> ]-> Added a new version which:Neither a. nor b. works in this build. Running this:
a. shouldn't 'trim off' spaces.
b. has a new parameter:
Code:--FileSeparator: Place this text between the file name and the addition, when not used, 'Merger' will be used.
Code:
MediaInfoRenamer.exe --Inform="Audio;%StreamSize%bytes#%BitRate/String%#%SamplingRate/String%#%Language%#ch%Channels%" --Separator="#" --Merger=" " --Replacements="kb/s%kbps#:%¦#/%;#\%;#|%;#?%#*%#.000%#.00%#.0%" test.mkv
Code:
Error: Missing a 'Merger' parameter!
I see FileSeparator listed amongst the available parameters, but trying to use it with line:
Code:
MediaInfoRenamer.exe --Inform="Audio;%StreamSize%bytes#%BitRate/String%#%SamplingRate/String%#%Language%#ch%Channels%" --Separator="#" --FileSeparator="_" --Merger="; " --Replacements="kb/s%kbps#:%¦#/%;#\%;#|%;#?%#*%# %#.000%#.00%#.0%" test.mkv
Code:
Error: File 'FileSeparator=_' doesn't exist!
The Code Wrote:test;3371314bytes;296kbps;48kHz;en;ch61250849bytes;110kbps;48kHz;ja;ch2.mkv
(26.11.2017, 08:33)Selur Wrote: [ -> ]How could there? The Renamer doesn't have any concept of the stream count number or anything.I was just expecting to see a standard Merger there by default; see what i mean above... (*=Audio1; *=Audio2)
PS. Also separately checked to make sure that Replacements weren't interfering with the Merger by removing '# %' during testing.
26.11.2017, 13:56
Attached a new version for you.
Cu Selur
Quote:I was just expecting to see a standard Merger there by default; see what i mean above... (*=Audio1; *=Audio2)Don't see how to do that with the output MediaInfo provides for 'Inform'-calls.
Cu Selur
26.11.2017, 17:53
(26.11.2017, 13:56)Selur Wrote: [ -> ]Attached a new version for you.It's working correctly.
(26.11.2017, 13:56)Selur Wrote: [ -> ]Luckily this was fairly easy to work around by padding the Inform call with a copy of the Merger, like so:Quote:I was just expecting to see a standard Merger there by default; see what i mean above... (*=Audio1; *=Audio2)Don't see how to do that with the output MediaInfo provides for 'Inform'-calls.
Code:
MediaInfoRenamer.exe --Inform="Audio;%StreamSize%bytes#%BitRate/String%#%SamplingRate/String%#%Language%#ch%Channels%#; " --Separator="#" --FileSeparator=" - " --Merger="; " --Replacements="kb/s%kbps# %#.000%#.00%#.0%#:%¦#/%;#\%;#|%;#<%;#>%#?%#*%" test.mkv
Code:
test - 3371314bytes; 296kbps; 48kHz; en; ch6; 1250849bytes; 110kbps; 48kHz; ja; ch2.mkv
Sidenode: Ran some additional tests and noticed that --Replacements won't work for --EncodingSettings, however the only usage scenario i can think of where this would ever be useful is in cutting away trailing zeroes after the decimal point; which would cause it's own problems anyhow, with lines like 'scenecut-bias=0.05', at least the way i've used --Replacements in the above example for audio.
PS. Optional trailing zero removal would be another useful feature to consider, the problem with my --Replacements approach above being the lack of outside reference for reliably detecting end of the line.
26.11.2017, 18:56
Okay, didn't apply it to the values of the encoding settings, doing so now.
Cu Selur
Cu Selur