Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: "Quick Convert" naming strategy fails, if... (Read 1732 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

"Quick Convert" naming strategy fails, if...

Hi,

thanks Peter for Fb2k 1.2. Just installed the 1.2b1 and it seems the new Quick Conversion simply names the new output files after the input files. But in my case where I have an image-File with embedded CUESHEET, this strategy fails, because then of course fb2k wants to name all output files the same - and therefore it comes up with the overwrite dialog

Michael

"Quick Convert" naming strategy fails, if...

Reply #1 –
Thought I was the last person using image+cue when I gave up using these last year. I'll see if I can help with it.
Microsoft Windows: We can't script here, this is bat country.

"Quick Convert" naming strategy fails, if...

Reply #2 –
Peter,

I suspect that there are still many of using CUE+WAV - or even CUE+IMAGE. In my case, I am a recording engineer who records live concerts and has to make CDs for radio broadcast. I never render a CD project in my DAW to a CD - I always render to CUE+WAV. Once this has been done, I may burn a CD, split the CUE/WAV to individual tracks - or just play the CUE/WAV in fb2k. Burning in a DAW is so unreliable compared with a program such as ImgBurn. Please keep all CUE/WAV support in your great program ;-)

Mike

"Quick Convert" naming strategy fails, if...

Reply #3 –
Quote from: Peter on
Thought I was the last person using image+cue when I gave up using these last year.

You think so? In my library I consistently use FLAC plus embedded CUE and see no disadvantage. But I must say for security reasons (file metadata corruption), I auto export cuesheet/alltags with tag.exe into 2 text files; OTOH all text files make up a good database about all my library, which I use at a different place.
For some reason I don't like the "1 file per track" strategy, not sure why.

"Quick Convert" naming strategy fails, if...

Reply #4 –
I'm also on the "one file per disc" (WavPack with embedded cuesheet) camp and according to this poll about 22% of HA members are still using this strategy...
Sergio
M-Audio Delta AP + Revox B150 + (JBL 4301B | Sennheiser Amperior | Sennheiser HD598)
 

"Quick Convert" naming strategy fails, if...

Reply #5 –
I see you have resolved this in the latest Beta by adding an enumerator [n] to the filename; thanks for that.