re: bug# 3055383
"Please run 'verify' after burning (in UDF VIDEO_TS mode)."
I am testing your beta build as noted in bug # 3055383.
(Since that report has been closed, I cannot re-open it, so I must open this new report.)
The app does go thru a verify step now, but we see no disk (access) activity where the original VIDEO_TS files are stored. (We keep these files on an external FW800 drive, which will blink its LED light when accessed. The light does blink during burning, but does not blink during the new Burn-verify step. FWIW we haven't seen a "bad burn" yet.)
I am wondering if the Burn-verify step is now reading the just-burned optical disc only, perhaps detecting for "bad optical blocks", and not a *REAL* verify against the original files, as Roxio-Toast does?
How we use your app:
We select the 'Video' tab on the main app, set the type drop-down list to 'DVD-Video', do a drag-&-drop of the enclosing folder (to effectively set the title of the disc etc), see that the app will choose the external optical drive, then click the Burn button.
On a terminal, we can see the mkisofs background task, which seems to have the proper CLI options.
But during the verify step, there is no background task, so the main app seems to be doing this phase by itself.
I really appreciate this Burn.app very very much. (I paid for Toast but they will not fix the firewire-attached problems I have registered with them. This Burn.app is otherwise seemingly working very well in this regard. I suppose I still need to use Toast when burning bluray discs, however.)
Thank you again for taking time with any help / explanation.