| Newsgroups |
gmane.comp.audio.eac.user |
| Message-ID |
<[email protected]> |
Again, where do you have flac.exe installed, “M”? Does it match the path show in EAC for it?
Regards,
Fred Maxwell
Moderator, Exact Audio Copy Yahoogroup
> On Jun 1, 2018, at 1:57 AM, Pierre-Yves Thoulon [email protected] [EAC] <[email protected]> wrote:
>
>
> Actually, the & is probably not the problem (it *is* a valid character for a file name under windows), but I *did* have the same problem when there was a strange character in the artist name or any parameter which is used to build the path and yields something that the shell does not like. The only way I found to debug that kind of thing is to rebuild the flac command line that EAC would create by hand and run it manually on the intermediate wav file. This generally gives you a nicer error message than what EAC provides...
>
> Good luck...
>
> Pyt.
>
> On Fri, Jun 1, 2018 at 7:32 AM, Fred Maxwell [email protected] <mailto:[email protected]> [EAC] <[email protected] <mailto:[email protected]>> wrote:
>
>
> Interesting suggestion and something I’d not thought of. But I don’t think that the path is being being passed into flac.exe as an argument (it’s not shown in the “options” listed in the image). I believe that flac.exe command is executed from within the directory where the audio files reside.
>
> Since this is failing on his first track on his first extraction with EAC, and the WAV file is created in that directory, I suspect that the problem is a missing FLAC encoder. If that proves to be wrong, he could test your theory with another CD that has no ampersand in the artist, album, or track titles.
>
> Regards,
> Fred Maxwell
> Moderator, Exact Audio Copy Yahoogroup
>
>> On Jun 1, 2018, at 1:14 AM, Pierre-Yves Thoulon [email protected] <mailto:[email protected]> [EAC] <[email protected] <mailto:[email protected]>> wrote:
>>
>>
>> This typically happens to me when Flac does not like some character in the output file name. In your case, I suspect the & in the wav file path screws up the flac command line (& is a reserved character that has a special meaning in the windows shell).. Try telling EAC to store the intermediate wav file somewhere else, where there are no special characters in the path name.
>>
>>
>> Good luck.
>>
>> Pyt.
>>
>>
>> Le 1 juin 2018 à 03:37, 'M' [email protected] <mailto:[email protected]> [EAC] <[email protected] <mailto:[email protected]>> a écrit :
>>
>>>
>>>
>>> I installed EAC on windows 10 using the defaults and ripped a disc for conversion to FLAC and received the attached message. Wav files were created, but no FLAC. I am not understanding what I am seeing.
>>>
>>>
>>>
>>> <image001.jpg>
>>>
>>>
>>
>>
>
>
>
>
>