New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discrepancy between DiscImageCreator and redumper in TOC/Cue with DCP #121
Comments
|
So here track flags are different in TOC and in subchannel. As we favor TOC by default, all flags should come from TOC too. |
|
Ok, so what you are essentially saying is unless I need the flags for some reason, I should rather submit the Redumper version of the cue file which is based on the media TOC. Is that an official redump.org stance that the TOC is preferred? I just want to submit the entry which is the most compliant and future-proof. Would it make sense from your point of view, to then file an issue on the DiscImageCreator repository to have it changed there? |
|
http://wiki.redump.org/index.php?title=Redumper |
|
@saramibreak said that he would adjust the behaviour of DiscImageCreator in the next release, so that it will also use the information from the TOC. It seems like the behaviour of the tools converges on using the TOC then, which works for me. |
On this coverdisc there is a discrepancy between the cue generated by DiscImageCreator and the cue generated by redumper. DIC sets the DCP flag on the audio tracks, Redumper does not. All other relevant information matches.
Redumper should probably use the QTOC instead of the TOC to generate the cue file.
Or maybe you can provide an explanation why it would be more desirable to use the TOC and break the DIC compatibility.
Redumper logs: https://archive.org/download/redump.org-logs/TOMBRAIDER2 (Redumper).zip
DiscImageCreator logs: https://archive.org/download/redump.org-logs/TOMBRAIDER2 (DiscImageCreator).zip
DiscImageCreator's
TOMBRAIDER2.cue:Redumper's
TOMBRAIDER2.cue:The text was updated successfully, but these errors were encountered: