Now I wonder which options (e.g. compression level) are used to create the flacs. There is any strategy to pass flac parameters to shnsplit?

I hope somebody can help.

There are two ways to do this. You could write a script in BASH that does it automatically (which might take some time)

Try using a combination of wavunpack and flac in a script combination or a separate script to rencode them to flac.

or you go into synaptic package manager and look for a program called "SoundKonverter". Make sure it has all of the necessary dependencies installed before you use it! It will tell you what's required. I think it handles CUE sheets and I know it handles ReplayGain tags. It's a KDE frontend that allows you externally specify various binary encoders x86 or 64-bit based ones.

You can use the GUI program flacon (you can find it at www.kde.org, it is a QT4 program), to break up a wavpack (ape, flac ...) + cue into separate files.It preserves the tags within the cue sheet (with the exception of the comment tag).

You can use the GUI program flacon (you can find it at www.kde.org, it is a QT4 program), to break up a wavpack (ape, flac ...) + cue into separate files.It preserves the tags within the cue sheet (with the exception of the comment tag).

./splitshnsplit: warning: none of the builtin format modules handle input file: [file.wv]shnsplit: error: cannot continue due to error(s) shown aboverm: cannot remove `split-track00.flac': No such file or directoryls: cannot access split-track*.flac: No such file or directorywarning: number of files does not match number of tracksls: cannot access split-track*.flac: No such file or directory

cust Custom output format module (output only, useful for encoding to a format that shntool does not yet support)

term sends output to the terminal

null sends output to /dev/null (output only, useful for dry‐runs in several modes, such as fix mode or strip mode)

shnsplit (part of shntool) definitely supports wavpack if you have wavpack installed (wvunpack is included in wavpack).

I suggest you make sure you have installed cuetools, flac and wavpack. I'm using these tools in Debian and that script decodes and splits cue+wavpack|ape|wav|flac just fine. I think it's reasonable to assume the equivalent packages in Ubuntu are identical except for the version names (this is true of about 70% of Ubuntu packages).

You can check the status of these packages in Synaptic or you can run

CODE

$ apt-cache policy wavpack

CODE

$ apt-cache policy flac

CODE

$ apt-cache policy cuetools

This will show you what is installed and what is available in each case.

I've got them all installed. Yesterday I tried manually convert file.wv into wav using wvunpack and it worked fine. I have split then the wav file. Probably it is a problem with integration of wavpack into shntool?

I've got them all installed. Yesterday I tried manually convert file.wv into wav using wvunpack and it worked fine. I have split then the wav file. Probably it is a problem with integration of wavpack into shntool?

That shouldn't be a problem. If wavpack is in your PATH, then shntool should see it and use it. No special version of wavpack is needed.

I've got them all installed. Yesterday I tried manually convert file.wv into wav using wvunpack and it worked fine. I have split then the wav file. Probably it is a problem with integration of wavpack into shntool?

There is another possibility. The way shntool works is by examining the first few bytes of the input file to determine the type, and in your case it looks like it's not working (I assume there is a different message if shntool recognizes the format but can't find the decoder). This could happen for several reasons. A self-extracting WavPack file has the self-extraction header on the beginning which would cause the test to fail. Also, those .iso.wv files have stuff before the first WavPack block.

The command-line wvunpack program works fine with these files because it searches up to 1 MB for a valid WavPack block. Unfortunately, I was not able to find a shntool option to override the format test (there is no "-i cust ...").

David

edit: if you try the -DD option as shnutils suggests, it will show the bytes at the beginning of the file that are causing the identification failure (I just tried it on Ubuntu)

The command-line wvunpack program works fine with these files because it searches up to 1 MB for a valid WavPack block. Unfortunately, I was not able to find a shntool option to override the format test (there is no "-i cust ...").

Funny, I had just tried that exact command and it still failed, but my shntool is old (3.0.3). Is this something fairly recent? If so it should definitely fix the OP's issue.

BTW, thanks for keeping WavPack support in shntools!

No problem, as I recall you made it easy for me by providing detection code.

"shntool -a" is simply a helpful command added in 3.0.8; the functionality it describes (modifying encoder/decoder parameters) has existed since 3.0.0. So your version should support the -i decoder modifications. That said, I don't think it's going to make a difference here, since the issue centers around shntool's WavPack detection code itself (which is run prior to calling the decoder).

Version 3.0.8 is also the version that added support for self-extracting WavPack files, which I believe is the 1MB check. So my current suspicion is either a) TA123's shntool version is earlier than 3.0.8, or b) I have a bug in my 1MB scanning code. I will know more when TA123 responds with his results.

BTW, I had to chuckle when I saw this in my code:

CODE

/* like WavPack, we check the first 1 meg of the file for a header. */ /* unlike WavPack, we do it in the most inefficient way possible. */

Thank you. It looks like David's hunch was correct, i.e. you have an outdated version of shntool. Your file has something prepended to it (most likely a self-extraction stub), and your version of shntool can't handle it. If you are able to upgrade to 3.0.8 (or later), then you should be able to use these types of files directly in shntool. Otherwise, you will need to decompress them outside of shntool, and run shntool on the resulting WAVE file.

Sorry for bringing an old thread to live but I have a few questions regarding shntool behavior:

1) Does running the following commandshnsplit -o flac -f cuesheet.cue image.flacresult in re-encoding or just splicing? Is it possible to splitwithout re-encoding at all? It is quite important when lossy formatsare involved or on older PCs where encoding is slow.