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: Determining source of Flac error (Read 3659 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Determining source of Flac error

Its been awhile since I have had any errors in Flac. I cannot remember where to find the error log so i can determine what is causing my errorwhen I am encoding.

ERROR: Can't Open Input File 5

Thanks

Determining source of Flac error

Reply #1
If you're using the flac frontend app, it's known to choke on 'special' characters in the filename that wouldn't bother the commandline .exe or other encoding frontends.

Determining source of Flac error

Reply #2
I figured it out and it turned out to be in the additional command line I use in EAC.

 

Determining source of Flac error

Reply #3
If you're using the flac frontend app, it's known to choke on 'special' characters in the filename that wouldn't bother the commandline .exe or other encoding frontends.


Yes, I had exactly this experience. I couldn't figure out why FLAC was choking on a couple of my WAVs. When I removed the apostrophe from each file name, they were processed with no problem.