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 to ensure file integrity when splitting a FLAC file with cue sheet (Read 3830 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

How to ensure file integrity when splitting a FLAC file with cue sheet

Research:

http://www.hydrogenaudio.org/forums/index....showtopic=84209
http://www.hydrogenaudio.org/forums/index....showtopic=91689
http://www.hydrogenaudio.org/forums/index....showtopic=91702
http://www.hydrogenaudio.org/forums/index....showtopic=91648
http://www.hydrogenaudio.org/forums/index....showtopic=89792

Problem: How to split a large FLAC file into tracks with the use of the cue sheet

Possible Solutions:

(a) Decode to a WAV, edit into tracks using Cooledit/Audition, and recode back to FLAC

(b) Use either Medieval, shntool, Foobar in order to automate the process

Concerns:

I am pretty sure option (a) is a sure shot.  But I rather can save time by automating the process.  Although Medieval will be able to do the job and properly label the tracks, I have read a lot of negative feedback warning not to use this application because it does not do a crc check and it also changes the audio.  Do the same problems exist with shntool and foobar?  My main concern is about file integrity.

How to ensure file integrity when splitting a FLAC file with cue sheet

Reply #1 –
Please use the search function:
http://www.hydrogenaudio.org/forums/index.php?act=Search

Since I posted this, I see that you've shown a link indicating that you've done some research.  I urge you to do some more.  This is asked on almost a weekly basis (often by those who have downloaded copyrighted material that has been illegally distributed).

How to ensure file integrity when splitting a FLAC file with cue sheet

Reply #2 –
Quote from: greynol on
Please use the search function:
http://www.hydrogenaudio.org/forums/index.php?act=Search

Since I posted this, I see that you've shown a link indicating that you've done some research.  I urge you to do some more.  This is asked on almost a weekly basis.



The heart of my question is about file integrity.  It seems that you know the answer but are not willing to share your knowledge.  Please don't turn this is into a flame/troll session.  This is not the purpose of my thread.

How to ensure file integrity when splitting a FLAC file with cue sheet

Reply #3 –
I've already shared the knowledge which is why I pointed you to our search function.

Medieval does not split properly on CD frame boundaries.  Shntool is command-line based, names your files generically and does not write metadata.  Use CUETools or foobar2000.

HTH.

PS: Accusing me of trolling isn't going to get you very far.

How to ensure file integrity when splitting a FLAC file with cue sheet

Reply #4 –
Thank you.  I was going to change the topic header to include the words "file integrity" but for some reason I cannot edit my OP.  Not sure if it is a time sensitive issue.  But I will try again later.
 

How to ensure file integrity when splitting a FLAC file with cue sheet

Reply #6 –
Here is a PM response from board member Takla (Thanks Takla):

If you run Windows then I suggest you use foobar2000 or cuetools to do the splitting, they will do it properly. If you use GNU/Linux or BSD or Mac OS X then I'd suggest split2flac.

Any of the tools I've mentioned will split a lossless+cue without causing any problems, audible or otherwise. You will find people are familiar with the tools and can offer advice. Medieval cue splitter should be avoided. I have used it and it causes audible artefacts such as nasty clicks. If you use my script or someone else's personal script and it doesn't do what you want, or it causes a problem, there is zero support.