Problems with Samsung playing DVD-R backups?

[SamuriHL]

I'm going to link to the cdfreaks forum on this one just in case people aren't aware of this particular thread. There's just WAY too much information to mirror over here so if this is considered bad(linking to the cdfreaks forum) I apologize in advance. However, this is definitely something everyone wants to keep an eye on. Short version...it would seem DVD-R's burned with CloneDVD and IMGBurn aren't able to play on certain Samsung DVD players. It simply gives a "Playback Prohibited" message. It's being looked into by a myriad of people but I wasn't sure if everyone here was aware of the problem. If you're curious, go ahead and visit this thread:

http://club.cdfreaks.com/showthread.php?t=224544

Thanks!

[Galileo2000]

I'm going to link to the cdfreaks forum on this one just in case people aren't aware of this particular thread. There's just WAY too much information to mirror over here so if this is considered bad(linking to the cdfreaks forum) I apologize in advance. However, this is definitely something everyone wants to keep an eye on. Short version...it would seem DVD-R's burned with CloneDVD and IMGBurn aren't able to play on certain Samsung DVD players. It simply gives a "Playback Prohibited" message. It's being looked into by a myriad of people but I wasn't sure if everyone here was aware of the problem. If you're curious, go ahead and visit this thread:

http://club.cdfreaks.com/showthread.php?t=224544

Thanks!

Samuri,

Thanks for sharing.

However, it looks like an isolated incident to me.

In order to reproduce you need to:

- use DVD-R ;
- burn with CloneDVD2 or Imgburn;
- play on some newer Samsung STB.

The very fact that Nero-burned DVD-Rs are played w/o problems tells me that both CloneDVD2 and Imgburn have the same bug or don't have some sort of hack that Nero has.

I doubt it is some sort of the "newer" copy protection. If that was the case, Nero would be affected too.

[SamuriHL]

I don't necessarily see it as being a new copy protection, either, however, I do see it as being a potential problem depending on what's causing it. I just wanted people to have a heads up on it.

[blutach]

Thread transferred to Gen Discussions - it doesn't seem to have much to do with Decrypting.

And remember, a burning prog simply sends 1s and 0s down the pipe to the hardware device. If it doesn't play, it has to do with burner/media compatibility or poor authoring.

Regards

[SamuriHL]

Actually, it seems like it has more to do with blacklisting application ID's that are burned to the disc. For instance, CodeKing is using the same media for all his burns. If he burns the EXACT same rip with both Nero and IMGBurn, the Nero burned disc will play but the IMGBurn disc will say "Playback Prohibited". The same is true for a CloneDVD burn. Slysoft and LUK have hopefully narrowed this down to the application ID that's being burned to the discs. If they take an ISO created in Nero and burn the ISO with IMGBurn, playback is fine. This isn't as simple an issue as a media issue, unfortunately. As for poor authoring, are you saying that IMGBurn and CloneDVD produce inferior quality authored discs? That is most definitely not my experience...

[setarip_old]

@SamuriHL

Hi!Slysoft and LUK have hopefully narrowed this down to the application ID that's being burned to the discs.But CodeKing indicated that he had the same problem with both DVD-Rs and DVD+Rs (not bitset). If I remember correctly, only one or the other, DVD-R or DVD+R burns an "application ID" to the media...

[blutach]

As for poor authoring, are you saying that IMGBurn and CloneDVD produce inferior quality authored discs?
@SamuriHL

I am saying exactly the opposite - ImgBurn (www.imgburn.com) is simply a burning program - it takes exactly what it is given and sends it down the bus to the device. Nothing more.

As for CloneDvD, I don't use the product and so would not be able to comment on its output being DVD compliant.

Regards

[SamuriHL]

@SamuriHL

Hi!But CodeKing indicated that he had the same problem with both DVD-Rs and DVD+Rs (not bitset). If I remember correctly, only one or the other, DVD-R or DVD+R burns an "application ID" to the media...

Well, according to LUK and Slysoft, it appears that there is an application ID which they've more or less ruled out as the problem and also an implementation ID that they're still looking at. And CodeKing is currently using DVD+RW to test this problem with, so, you're correct that it appears to affect everything that is not bitset. Personally, I'd never buy a piece of equipment that did that, but, I can understand why LUK and Slysoft want to get to the bottom of this mystery so badly.

[SamuriHL]

ImgBurn (www.imgburn.com) is simply a burning program - it takes exactly what it is given and sends it down the bus to the device. Nothing more.

Regards

Unfortunately, that's not entirely accurate. It has to take what it's given and create a burn it to a UDF file system. As a result and part of the UDF spec, there are certain fields that can be filled in such as the application ID and the implementation ID. Nero sets both of those fields, as well. It would seem that when Elby and IMGBurn set them, the disc doesn't play, but, when it's set by Nero, it plays fine. This can be evidenced by the fact that burning an ISO created by Nero with IMGBurn, it plays fine, but, burning an ISO created by IMGBurn with Nero doesn't. There is something in the way that the UDF file structure is being created by CloneDVD and IMGBurn that's causing the Samsung player to display the prohibited playback message. I really hope they figure it out as CodeKing said that when he was searching for answers he found quite a few people suffering from this problem.

[LIGHTNING UK!]

Looking into this has been a great exercise for me actually!

I've already fixed a number of (fairly insignificant) bugs within ImgBurn's file system creation code by comparing the it with the output from all the other utils - but I've also found bugs in their code too, even in Nero's :p

[SamuriHL]

Looking into this has been a great exercise for me actually!

I've already fixed a number of (fairly insignificant) bugs within ImgBurn's file system creation code by comparing the it with the output from all the other utils - but I've also found bugs in their code too, even in Nero's :p

That's truly awesome! :) Any time you can make your code better is definitely a good thing.