The created disk is compatible with the standard DVD whether or not?

[Nuhim]

With the help IC 7 or DVD95Copy I create a disk. In PowerDVD the disk is perfectly read, and on DVD player Pioner 355 - is not present (can't read disk).
Whether exists such soft DVD player, which strictly would check readable disk on compatibility with By the standard DVD? Or can there is a program, which would do(make) it?
I am sorry for bad English.

[Fmazzanti]

Nuhim,
I'm not sure I understood your question, but I guess you're asking about DVD compliance. Well, all I can tell is that software players are *much* less restrictive than most standalones. In my case, I've been messing around with IFOs recently, and am fed up of creating projects that play smoothly on PowerDVD but that once burned do not play properly on my standalones.

[Oneiroxy]

At the moment tere is no reliable PC software method to ensure that the burned DVD is compiliant with any other stand alone DVD in the market. As it happens the software dvd players read almost everything so it is is recommended to stop your checking there. But be sure that if it is not compatible with your software player it is NOT going to play on the deck...
P.S.: try different brand DVDs this could be the broblem on stand alones. Just for checking try expensive media with the same image!

[MackemX]

just try to load the VTS_TS.IFO into IC and see if it refuses it

If it does then something is wrong and chances are a fussy standalone player will not play it :)

this is the nearest thing you can get to a fussy software player :(

[Imperial Zeppelin]

The Number 1 reason for set top players rejecting burnt DVDs is the use of poor media.

To increase the chances of 100% set top compatibility do the following:

1. Buy only name brand media. I've never had a set top player reject TDK, Memorex, Pioneer, etc. I have had problems with off-brand names.

2. Burn your DVD at 1X! Heck you may have spent hours getting to this step. What's another 25 minutes?

3. In some cases, make sure that you have an AUDIO_TS folder on your disc.

[MackemX]

Originally posted by Imperial Zeppelin
The Number 1 reason for set top players rejecting burnt DVDs is the use of poor media.

To increase the chances of 100% set top compatibility do the following:

1. Buy only name brand media. I've never had a set top player reject TDK, Memorex, Pioneer, etc. I have had problems with off-brand names.

2. Burn your DVD at 1X! Heck you may have spent hours getting to this step. What's another 25 minutes?

3. In some cases, make sure that you have an AUDIO_TS folder on your disc.

well I slightly disagree with the first two but agree with the last

1. Myth! Brand only media has nothing to do with, as does price, it's the actual quality of the media you are burning on you really need to look at as branded/unbranded/cheap/expensive media has nothing to do with the results

2. Myth! Burning at 1x is no different to burning at 4x which I have shown in a test I did using Nero DVD speed, it's more likely to do with the original source/PC spec/user setup/media quality/burner used than it has with burn speed

look at my results after burning at 4X on a Pioneer 105 using Nero (another Myth about it being Nero dispelled) while still using my PC as normal while it was burning away

RESULTS (http://www.deano.dsl.pipex.com/icpic/sam.gif)

this was with cheap unbranded (FWS) Ritek G04 media, so you can see why I disagree to burning at 1X when 4X produces such top quality results. I also got the same results with my old 104 burning at 2X

the majority of settop playback failures are down to people creating non-complaint DVD's and using incorrect methods during the complete process. Add to this the other reasons I have listed and some people will obviously have problems with their standalones as some will not accept the final results

hard but true but I feel the actual Number 1 reason for set top players rejecting burnt DVDs is the user his setup and his methods, so that's why I try to help all people who have problems with DVD's as I feel their methods are more likely behind the problem as I have very few and easily overcome most I come across before I burn :D

p.s. I don't mean to offend anyone as I am entitled to an opinion and obviously some will disagree but then again some may agree :)

[Fmazzanti]

Yes I also disagree here. Well I'll put it in another way: using poor media can certainly produce deffective DVDs, but that's certainly not the only reason for failure. Screwing up IFOs and navigation structure breaks the project too...

[PeteD]

-------------------------------------------
2. Myth! Burning at 1x is no different to burning at 4x which I have shown in a test I did using Nero DVD speed, it's more likely to do with the original source/PC spec/user setup/media quality/burner used than it has with burn speed
-------------------------------------------

Hmmm. I have burnt green top bulk paq disks at 1x which work perfectly, where as when burned at 2x, they screw up - take longer to load and stutter after about 20 mins playing. I would say that burn speed is a factor on some disks. By contrast, burning to a pioneer 4x gives no problems at all.

All this done on the same machine using the same software. XP DVDdecrypter dvd2one pioneer ao5

[MackemX]

are the bulkpaq discs the lighter dye ones?

I reckon these are crap as I had some 2X green bulkpaq ones and luckily managed to sell them on before using more than 2 of them as even those gave me grief during startup by taking ages to load

the ones I use now have a dark dye and I always get great results from the darker dye DVD's (FWS) as I did with the FWS 2X ones, so I'll never go back to bulkpaq and lighter dye DVD's

if a media is supposed to be 2X media and doesn't burn fully working DVD's and your data is 100% fully DVD compliant then chances are its the media quality that cannot handle the 2X burn speed

another higher quality 2X DVD blank will work with a 2X burn with exactly the same data that fails on the 2X bulkpaq so how can burning at 2X be to blame?

the only other factor will be the player that you are playing it in and how fussy it is and the way it's deals with crap media

so as I said previously it's mostly the media quality to blame not the actual burn speed and these 2X bulkpaqs proved that

some people will probably swear by bulkpaqs but I've seen nothing but poor results from them

the simple answer is, if your burning fails at the supposed media max burning speed change your media :). What works for you may not work for someone else but something always will and it's great when you find one that does work

the only time I can think you need to slow down the burn is if you have a really low spec computer and also want to use it at the same time while burning

[russwcj]

You don't indicate if you are using -R or +R media/burner.

If it is +R and you have a Ricoh based burner, then it is important that you run the bitsetting utility against you burner to change the booktype to DVD-ROM on finalization (HP200 does this automatically). On my own tests of a dozen DVD players, this upped compatability from 50% to 100%.
ps. I've used virtually every brand of DVD+R there is and had no problems with any of them.

[MackemX]

Originally posted by russwcj
You don't indicate if you are using -R or +R media/burner. '-' cos I use a Pioneer 105 (mentioned in previous post) and so does PeteD by the looks of his post and Pioneer 105's are '-' :D

great little burner for £180

[mpucoder]

Let's get back to the subject. Is there a software player that can check for compliance? No, and it is unlikely that there ever will be. The reason is standalone's and PCs essentially use different file systems. The standalones use the pointers in VIDEO_TS.IFO to locate everything else, PCs use the OS file system and mostly ignore the ifo pointers. The reason is simple, the pointers are only valid if the files of the DVD are all on HD in exactly the same order as they would be on a DVD, and this virtually never happens.

As for debates on media, we have another forum for that.

Best advice is to get a couple RW discs for testing purposes before you commit.

[MackemX]

what do you reckon about IC to check your DVD mpucoder?

that's damn fussy when it comes to checking a DVD structure, probably too fussy :), but if IC takes it would not play in a fussy standalone?

I reckon it would but then again I only reckon and I cannot prove :( until I come across such a problem

[mpucoder]

It's possible the IC is fussy about the initial pointers enough to be useful as a primitive go/no-go test. This would get some people beyond the "C-1300", "dirty disk", and "no disk" problems, but I doubt it checks the entire DVD for full compliance.

(personal note: I rely on posts here for information about IC, I have not purchased it based on the number of negative reports here, and the fact that its output is a non-standard file.)

Edit: did you just watch a John Wayne movie? That's a lot of reckonin' :)

[Antonio S.]

mpucoder post:Let's get back to the subject. Is there a software player that can check for compliance? No, and it is unlikely that there ever will be. The reason is standalone's and PCs essentially use different file systems. The standalones use the pointers in VIDEO_TS.IFO to locate everything else... Even when there is no "software player" that can check compliance, there are burning programs, like Prassi PrimoDVD, that check your VIDEO_TS folder for 100% compliance. If it is not DVD compliance it abort the process before burning the media. However this compliance test do not work well in burning programs like Nero...

Antonio S.

[red321]

I've always found ifoedit to be the hardest software player to satisfy!

But I have found that ifoedit/powerdvd/Windvd and my standalone seldom agree on whethere a disk is playable or not.

[mpucoder]

There are many levels where compliance can be checked. The burning programs check only the most basic things to make sure the files can be placed on the disk where the pointers say. That alone will help a lot of people, but there is more.
The next level would be to make sure all NAV pack pointers are correct. This is what IfoEdit can check and correct with Get_VTS_Sectors.
The next level would be to ensure that all referenced streams are present and linked properly - no dangling or mis-mapped streams. I know of no readily available software for this.
Another level would be to check all virtual machine commands for correctness, again no dangling references (navigation errors) - buttons don't point off to nowhere, SetSTN doesn't use non-existant audio/subpicture/angle values, no highlighting non-existant buttons, etc.
And finally to check the streams themselves for encoding errors. Check for system clock discontinuities ("layer break") and DTS/PTS errors that cause jerky playback. Check proper stream interleaving and bitrate constraints, etc.

[PeteD]

In answer to MisterX - are they lighter dye ones?

Yes. And I won't be buying them again.

I agree that burning speed is not an issue if the media is good and reliable for the burn speed used. Glad you managed to shift the bulk paqs you had.

Mine are supposed to be 2x, but as I said, they screw up at 2x (old firmware and new in the A05). So for anyone out there having trouble with media, it's worth trying to burn at a lower speed to see if cures the problem. Bottom line, if you can aford more expensive disks, buy them and be happy.

Happy burning.