I am using cdrtfe to create Enhanced-CDs. In testing 9 CD writers I have found that 4 succeeded and 5 failed using CD-R discs. Amazingly all 9 drives succeeded with CD-RW discs. I am using the updated version of cdrtfe provided by Oliver Valencia linked in the the document noted below, That update provided a 'Multisession' option on the Disc Image tab, streamlining the process.
I have created a test set which provides a 'Large' data set, creating a CD using all but about 10 MiB of the available space as well as a 'Small' data set using about 1/3rd of the CD.
I have posted a link to the above to the cdrtools-support mailing list. It seems most likely that if there is a possible resolution it would be in cdrecord. If you subscribe to that list you may want to see if there is any response there.
Ron Stordahl
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have looked into the logs. There seem to be different problems.
LG HL-DT-ST DVDRAM GP65NB60 Rev PB01:
According to the logs, it seems as if both sessions have been written correctly. Can the CD-ROM session be read, if the disc is ejected and then re-inserted? Can the CD-ROM session be read in another drive?
Samsung TSSTcorp CDDVDW SE-218GNRSBD Rev TS00 USB 2015
The log shows a medium error during fixation of the second session. This may be caused e.g. by a bad disc or incompatibility between disc and drive.
Here the problem is, that after writing the first session, it doesn't seem to be possible to add the second session although the option -multi has been used for the first. The disc doesn't seem to have any remaining writable size.
I have attached the relevant parts of the log files including a short description of the problem.
Sony DVD RW DRU-830A_SS22
I have no idea, what is going on here. There were no errors when writing both sessions. However, cdrecord -minfo shows one track more than expected.
Thanks for the reply. I have been busy on other proejcts and just noticed your response. There doesn't seem to be an option for the forum to notify me by e-mail of a response. So I will have to remember to check more often.
What little I have done is to redo the tests in which I failed to include the '-xa' option for the data session.
Would you consider adding that option to Data Disc\Options\Disc much like you added Multisession to the Write image options?
When I did do so at Extras\Settings\cdrecord\Additional... adding '-xa' it does write CD-ROM XA Mode 2 Form 1 which can be confirmed by looking at the associated sectors and noting at offset decimal 15 the byte is 0x02. A standard CD-ROM would have 0x01 in that position.
I did post my question on the cdrecord forum and Jeorg Schilling replied, but wanted me to pick out the problem segments of the debug log rather than provide the enormous volume of data contained in http://204.221.76.52/cd/Enhanced-CD_Test.7z.
I agree with him, but have not had the time to do so.
The clips you have provided were what I should have provided to him, and I will do so, perhaps this weekend when I get caught up! I am quite sure he will be helpful if I do not overwhelm him with extraneous data.
Surprisingly the Phillips drive successfully wrote the Large Enhanced-CD on CD-R when I ran it again to include the -xa option. I don't think that is the reason it succeeded however. The link to the 7z file above includes that changed result.
I don't think that is is necessary to include the -xa option. The README.cdplus (from the cdrtools source archive) does not mention it. I've tried writing the second (data) session with -xa and without. It made no difference, both times the resulting disc had a readable data session.
Surprisingly the Phillips drive successfully wrote the Large Enhanced-CD on CD-R when I ran it again to include the -xa option. I don't think that is the reason it succeeded however.
I agree. As the -xa option would only affect the second session. However, the previous attempt failed because it wasn't even possible to start writing the second session.
A comparison of both log files shows the differences (cdrecord -minfo after writing the first audio session).
failed attempt:
disk status: incomplete/appendable
session status: incomplete/appendable
[...]
Last session start address: 263164
Last session leadout start address: 1166728
(no info on next writable address and remaining writable size)
successfull attempt:
disk status: incomplete/appendable
session status: empty
[...]
Last session start address: 0
Last session leadout start address: 251764
Next writable address: 263164
Remaining writable size: 96680
You have used different disc types:
failed:
ATIP info from disk:
Indicated writing power: 4
Disk Is unrestricted
Disk Is not erasable
Disk sub type: Medium Type A, low Beta category (A-) (2)
ATIP start of lead in: -11634 (97:26/66)
ATIP start of lead out: 359849 (79:59/74)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
successful:
ATIP info from disk:
Indicated writing power: 5
Disk Is not unrestricted
Disk Is not erasable
Disk sub type: Medium Type A, high Beta category (A+) (3)
ATIP start of lead in: -11634 (97:26/66)
ATIP start of lead out: 359846 (79:59/71)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Regards,
Oliver
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have reduced the number of tests, concentrating on the problem cases. Also I reran the tests using Taiyo Yuden CD-R's so they are all the same. You noted the use of different CD-R's.
In the results folders ...\Succeeded and ..\Failed I have two copies of the debug log, one with the name your program gives it..'cdrtfe_log.txt' and one with a shortened name identifying the drive and test.
That later file is of identical length but I have replaced the timestamp with 00:00.00: to make it easier to compare successrful with unsuccessful runs using a diff program.
With luck tomorrow, probably late in the day, I am going to post there to Joerg. I will study the logs tomorrow and extract from them what appear to be the problems, but probably for just one or two drives, and only what seems to be relevant. Similar to what you have posted above...although it is likely changed with the latest test runs.
That forum is a mailman reflector...I am not sure if it will permit any attachments.
If Joerg comes up with a solution, perhaps a source code change, I would have no way to compile it, but I suspect you do.
Thank you,
Ron
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried to make it clear to Joerg that it is a lot to look at and that I am in no rush. He should deal with it only when time allows.
One interesting discovery I made was that all 9 drives succesfully write the Large E-CD when using a CD-RW disc.
I also found out that using a program ImgBurn one can image the CD-RW disc produced onto a CD-R in one step. Even to drives that fail to write the Large E-CD with cdrecord.
Does cdrtfe have the ability to read a multisession disc to an image and then to write that image to another cd?
Thank you,
Ron Stordahl
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oliver
An issue has arisen with respect to the use of a PREGAP statement in the Cue sheet.
Are you doing some processing on the cue sheet. I am getting in the log this:
00:48.48: > Sending CUE sheet...
00:48.59: > cdrecord: CUE sheet not accepted. Retrying with minimum pregapsize = 1.
Joerg questioned this and so I added:
PREGAP 00:02:00 immediatly before
INDEX 01 00:00:00
The result was exactly the same.
I don't know if cdrecord is not processing PREGAP statements or if cdrtfe is modifying them in some fashion.
All this is occuring over at cdtools-support@lists.sourceforge.net, which is really ackward. He doesn's use the web interface you are using! You can read at https://sourceforge.net/p/cdrtools/mailman/cdrtools-support/ but I can't seem to send anything to it over then via email. Confusing!
But if you can join us over there it would help as I don't know the answers to questions about internals of cdrtfe!
Thanks
Ron Stordahl
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using cdrtfe to create Enhanced-CDs. In testing 9 CD writers I have found that 4 succeeded and 5 failed using CD-R discs. Amazingly all 9 drives succeeded with CD-RW discs. I am using the updated version of cdrtfe provided by Oliver Valencia linked in the the document noted below, That update provided a 'Multisession' option on the Disc Image tab, streamlining the process.
I have created a test set which provides a 'Large' data set, creating a CD using all but about 10 MiB of the available space as well as a 'Small' data set using about 1/3rd of the CD.
A document describing my testing efforts is available: http://204.221.76.52/cd/Enhanced-CD_Test_Procedure.pdf
That document includes links to the test sets and results for each of the 9 drives tested.
Any help resolving the problem will be appreciated.
Ron Stordahl
Oliver
I have posted a link to the above to the cdrtools-support mailing list. It seems most likely that if there is a possible resolution it would be in cdrecord. If you subscribe to that list you may want to see if there is any response there.
Ron Stordahl
I have looked into the logs. There seem to be different problems.
LG HL-DT-ST DVDRAM GP65NB60 Rev PB01:
According to the logs, it seems as if both sessions have been written correctly. Can the CD-ROM session be read, if the disc is ejected and then re-inserted? Can the CD-ROM session be read in another drive?
Samsung TSSTcorp CDDVDW SE-218GNRSBD Rev TS00 USB 2015
The log shows a medium error during fixation of the second session. This may be caused e.g. by a bad disc or incompatibility between disc and drive.
Phillips PLDS DVE+-RW DH-16AAS Rev JD12, Plextor PX-891SAF Rev 1rT2
Here the problem is, that after writing the first session, it doesn't seem to be possible to add the second session although the option -multi has been used for the first. The disc doesn't seem to have any remaining writable size.
I have attached the relevant parts of the log files including a short description of the problem.
Sony DVD RW DRU-830A_SS22
I have no idea, what is going on here. There were no errors when writing both sessions. However, cdrecord -minfo shows one track more than expected.
Oliver
Oliver
Thanks for the reply. I have been busy on other proejcts and just noticed your response. There doesn't seem to be an option for the forum to notify me by e-mail of a response. So I will have to remember to check more often.
What little I have done is to redo the tests in which I failed to include the '-xa' option for the data session.
Would you consider adding that option to Data Disc\Options\Disc much like you added Multisession to the Write image options?
When I did do so at Extras\Settings\cdrecord\Additional... adding '-xa' it does write CD-ROM XA Mode 2 Form 1 which can be confirmed by looking at the associated sectors and noting at offset decimal 15 the byte is 0x02. A standard CD-ROM would have 0x01 in that position.
I did post my question on the cdrecord forum and Jeorg Schilling replied, but wanted me to pick out the problem segments of the debug log rather than provide the enormous volume of data contained in http://204.221.76.52/cd/Enhanced-CD_Test.7z.
I agree with him, but have not had the time to do so.
The clips you have provided were what I should have provided to him, and I will do so, perhaps this weekend when I get caught up! I am quite sure he will be helpful if I do not overwhelm him with extraneous data.
Surprisingly the Phillips drive successfully wrote the Large Enhanced-CD on CD-R when I ran it again to include the -xa option. I don't think that is the reason it succeeded however. The link to the 7z file above includes that changed result.
The PDF document http://204.221.76.52/cd/Enhanced-CD_Test_Procedure.pdf has also been updated.
Thanks for your patience.
Ron Stordahl
Hello,
I don't think that is is necessary to include the -xa option. The README.cdplus (from the cdrtools source archive) does not mention it. I've tried writing the second (data) session with -xa and without. It made no difference, both times the resulting disc had a readable data session.
I agree. As the -xa option would only affect the second session. However, the previous attempt failed because it wasn't even possible to start writing the second session.
A comparison of both log files shows the differences (cdrecord -minfo after writing the first audio session).
failed attempt:
successfull attempt:
You have used different disc types:
failed:
successful:
Regards,
Oliver
Oliver
I have updated the data set: http://204.221.76.52/cd/E-CD_Test.7z
and the document: http://204.221.76.52/cd/E-CD_Test_Procedure.pdf
I have reduced the number of tests, concentrating on the problem cases. Also I reran the tests using Taiyo Yuden CD-R's so they are all the same. You noted the use of different CD-R's.
In the results folders ...\Succeeded and ..\Failed I have two copies of the debug log, one with the name your program gives it..'cdrtfe_log.txt' and one with a shortened name identifying the drive and test.
That later file is of identical length but I have replaced the timestamp with 00:00.00: to make it easier to compare successrful with unsuccessful runs using a diff program.
Hopefully you are subscribed to the cdrtools-support list: https://sourceforge.net/p/cdrtools/mailman/cdrtools-support/. If not perhaps you could join, if only briefly.
With luck tomorrow, probably late in the day, I am going to post there to Joerg. I will study the logs tomorrow and extract from them what appear to be the problems, but probably for just one or two drives, and only what seems to be relevant. Similar to what you have posted above...although it is likely changed with the latest test runs.
That forum is a mailman reflector...I am not sure if it will permit any attachments.
If Joerg comes up with a solution, perhaps a source code change, I would have no way to compile it, but I suspect you do.
Thank you,
Ron
Oliver
I have posted the best analysis of the data I could to the cdrecord-support@list.sourceforge.net for Joerg to review.
I was an enormous e-mail, I hope that list doesn't have a limit that might trip me up.
I have also put it on my server at: http://204.221.76.52/cd/Analysis.7z
The test document has been updated: http://204.221.76.52/cd/E-CD_Test_Procedure.pdf
I tried to make it clear to Joerg that it is a lot to look at and that I am in no rush. He should deal with it only when time allows.
One interesting discovery I made was that all 9 drives succesfully write the Large E-CD when using a CD-RW disc.
I also found out that using a program ImgBurn one can image the CD-RW disc produced onto a CD-R in one step. Even to drives that fail to write the Large E-CD with cdrecord.
Does cdrtfe have the ability to read a multisession disc to an image and then to write that image to another cd?
Thank you,
Ron Stordahl
Oliver
An issue has arisen with respect to the use of a PREGAP statement in the Cue sheet.
Are you doing some processing on the cue sheet. I am getting in the log this:
00:48.48: > Sending CUE sheet...
00:48.59: > cdrecord: CUE sheet not accepted. Retrying with minimum pregapsize = 1.
Joerg questioned this and so I added:
PREGAP 00:02:00 immediatly before
INDEX 01 00:00:00
The result was exactly the same.
I don't know if cdrecord is not processing PREGAP statements or if cdrtfe is modifying them in some fashion.
All this is occuring over at cdtools-support@lists.sourceforge.net, which is really ackward. He doesn's use the web interface you are using! You can read at https://sourceforge.net/p/cdrtools/mailman/cdrtools-support/ but I can't seem to send anything to it over then via email. Confusing!
But if you can join us over there it would help as I don't know the answers to questions about internals of cdrtfe!
Thanks
Ron Stordahl