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: How can I divide the ape+cue into some tracks? (Read 11450 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

How can I divide the ape+cue into some tracks?

I'm a Chinese,and not good at English,I'm sorry,and I hope You can understand what I said,Thanks.

I have many ape with cue,but now I want to divide them into some single tracks,I know that foobar can finish it,but it cost too much time,it convert ape into wav and then compress wav into a single ape,but is there some software which can divide the ape into some single tracks without converting and compressing.

thanks.And If you can not only tell me how to do it,but also tell me which sentence is wrong and how to correct it,thank you very much.
 

How can I divide the ape+cue into some tracks?

Reply #1 –
I don't see a problem with having to go to WAVE first - it's not as if you have to do it every day.

However, you could try the version here, which has piping support.

Here is a search on HA that supplies numerous threads about splitting APE files - I'm sure at least one will have further information on this subject.
I'm on a horse.

How can I divide the ape+cue into some tracks?

Reply #3 –
Foobar's converter actually can be set up to use tempfiles thus it doesn't need the encoder to support pipe encoding (read a bit around the converter set up window)

How can I divide the ape+cue into some tracks?

Reply #4 –
Quote from: urak on
Quote from: Synthetic Soul on
However, you could try the version here, which has piping support.

if i remember well it doesn't works (unfortunely) with foobar's pipe setting

This is news to me.  I don't use foobar, but I would expect it to work anywhere that piping is used.  Can anyone else substantiate this claim?

How can I divide the ape+cue into some tracks?

Reply #7 –
Thanks to both of you.  That's very interesting.  I'll investigate and see if I can't put out a fixed version that works (hopefully) everywhere.

How can I divide the ape+cue into some tracks?

Reply #8 –
Okay, I tested wav-to-ape conversion and was able to reproduce the error.  So I created a "stdin grabber" encoder to see what foobar was sending.

Turns out that foobar is not setting the WAVE data size to the correct value before feeding data to the encoder (it is set to 0x7fffffd0, meaning foobar isn't even trying to set the right value -- it's relying on the encoder to determine that).

Maybe I can work around this in the encoder, but in my opinion this is a foobar issue.  Are there other encoders that don't work with foobar because of this?

How can I divide the ape+cue into some tracks?

Reply #9 –
Quote from: shnutils on
Turns out that foobar is not setting the WAVE data size to the correct value before feeding data to the encoder (it is set to 0x7fffffd0, meaning foobar isn't even trying to set the right value -- it's relying on the encoder to determine that).

Maybe I can work around this in the encoder, but in my opinion this is a foobar issue.  Are there other encoders that don't work with foobar because of this?

With TAK you have to specify the -ihs (IgnoreHeaderSize) option to make it work. Peter has explained here why foobar doesn't write the correct size value.

How can I divide the ape+cue into some tracks?

Reply #10 –
Quote from: TBeck on
With TAK you have to specify the -ihs (IgnoreHeaderSize) option to make it work. Peter has explained here why foobar doesn't write the correct size value.


Thanks Thomas, I see it from his point of view as well.  So, I have modified MAC to accept WAVE data of unknown length (in fact, it assumes all inputs are unknown, even if they are correct).

The only visible change is a slight increase in the size of .ape files -- this is due to mac.exe assuming that the maximum number of seek tables will be used.  This is not something I can change easily, but I don't see it as a big problem since it only adds a little under 30kb per file.

My rudimentary testing gives me confidence that it works well enough -- the new mac.exe works with shntool, foobar, and directly from the command line.

However, since I don't use other features of APE (such as tagging/seeking), I need others to test this new version and report any problems to me.

Thanks!

http://www.etree.org/shnutils/shntool/