What's wrong??? :o
This happens with .opus too. Image CD is OK.
CUERipper 2.1.6 and 2.1.7
Did you specify the correct path?
There are 3 possible solutions.
1. Define the %PATH% to lame.exe and opusenc.exe in the Windows Environmental Variables
or
2. Copy lame.exe and opusenc.exe to the CUETools program folder
or
3. Define the path to lame.exe and opusenc.exe (e.g. C:\LAME\lame.exe) in the encoder settings (gear icon)
http://cue.tools/wiki/CUERipper_Settings (see #29)
CUERipper rocks!
Thanks a lot,
@korth ! I hadn't noticed the gear icon! :-[ Everything works fine now.
I would just like to ask a question: would you know if CUERipper is an abandoned project? It is a very competent tool!
I don't know the reason for the delay in releasing an updated package but improvements continue on the source code.
https://github.com/gchudov/cuetools.net/
Good to know, thanks!
I don't know the reason for the delay in releasing an updated package but improvements continue on the source code.
https://github.com/gchudov/cuetools.net/
According to GitHub, the main author Grigory Chudov has last committed to the project two years ago. Sadly, there doesn't seem any substantial development to take place any more.
So the 30+ commits made to the official source code by collaborators doesn't count?
There is hope.
So the 30+ commits made to the official source code by collaborators doesn't count?
If the majority of updates related to "Bump copyright year to 2020" makes you happy, good for you.
You're obviously looking in the wrong place (or perhaps just trolling).
https://github.com/gchudov/cuetools.net/commits/master
This is not a trolling attempt. I was referring to the commits listed at the main screen: https://github.com/gchudov/cuetools.net/.
My point is that the main author hasn't been actively committing to the project for ~2 years. My interest in the project lies in the FLAC/FLAKE compression part, which appears to have been touched last in early 2017, including an unstable test release. I did notice, that there is one person regularly committing to the project, which indeed is welcomed. Those additions are minor fixes to the existing code though, the project itself isn't evolving further anymore.
Did you specify the correct path?
There are 3 possible solutions.
1. Define the %PATH% to lame.exe and opusenc.exe in the Windows Environmental Variables
or
2. Copy lame.exe and opusenc.exe to the CUETools program folder
or
3. Define the path to lame.exe and opusenc.exe (e.g. C:\LAME\lame.exe) in the encoder settings (gear icon)
http://cue.tools/wiki/CUERipper_Settings (see #29)
hi, where does one download the ffmpeg for CUERipper ?
ffmpeg.org provides source code only but they have a couple links on their site for third-party pre-compiled windows binaries.
https://www.ffmpeg.org/download.html#build-windows