LIGHTNING UK!

If the players having trouble with the 3D version will play the 2D version (from the same disc) perfectly, I'd say there's an issue with your source image file. Go back to SlySoft. That is of course assuming the players will play the original disc (both 2D and 3D). Without knowning that info, there's no way to know where the problem lies - original disc or AnyDVD.

Sorry, that was a mistake on my part... Build mode always writes out using buffering. It's Read mode that writes out without buffering. What happens if you run ImgBurn twice? Have 1 reading from NAS and writing to local. Have the other reading local and writing to NAS. Does the throughput then drop on both or do they manage 100mb/s still?

It doesn't know (or care if) things are shares, local drives, 2 different physical drives etc. It just has a couple of paths that it passes to the 'CreateFile' API and that's it. It's then doing ReadFile and WriteFile on the handles obtained by CreateFile as quickly as it's able to. Whilst the reading part has an option of enabling the OS's buffering, the writing part doesn't.

By reading that thread, you've taken the advice of some random person. ISO9660 + UDF is fine for normal data discs. It's potentially only a problem when you're going to attempt to use them in some non-computer device. DVD players are very basic and not exactly flexible in what they do and how they work. You need to check the manual and see exactly what it supports for whatever it is that you want it to read. If your player won't read UDF for anything other than a DVD Video disc, sure, it'll then have to fall back on the rubbish ISO9660 file system. If that's the case (as it appears to be here), you'd want to also include Joliet (so ISO9660 + Joliet + UDF). It can then not read UDF and (hopefully) fall back on Joliet. If that isn't supported either, it'll fall back to ISO9660. A computer will always read UDF over Joliet and ISO9660.

Ah sorry, I missed the bit about you having multiple NAS devices. I don't even have 1, so no, I haven't done any first hand tests at all! What does the 'Buffer' look like when you're reading from one and writing to another? If it's full, it means it can write out the data quickly enough (so source is faster than dest). If it's empty, it can't read the data quickly enough (so source is slower than dest). Using ElbyCDIO won't do anything as it's nothing to do with the API functions used for reading and writing files.

Read the quote again. The disc id is something it generates based on the layout of the disc - number of tracks, length of tracks etc. It's not something you can just read from or write to a disc. Having some sort of ID recorded in the CD-TEXT isn't going to help if the player doesn't attempt to read CD-TEXT in the first place.

Like I said, a lot of players use an internet database for this stuff and NOT CD-TEXT. Your car cd player would rely on CD-TEXT, but the others probably don't. Media Player certainly doesn't read CD-TEXT, you have to install a 3rd party addon to get that functionality. The internet database will only contain info of whole discs. So it might find the disc / track names of a full CD, but it won't find the names of one you've made yourself (which is what you're doing when only burning 1 track).

Consider it done.

You can't burn at 2.4x, it's not a speed the drive (*normally) supports on those discs. That's where the bit I mentioned about modifying the firmware comes in. I'm sure all of this is covered on the xbox forums that actually deal with this stuff. You should probably take a look at some of those instead of this one.

I'm sure yours will also ship with 1.Z7. I expect it'll be Vinpower that release new firmware as it's their drive. Sony Optiarc have basically stopped operating now. The 5280/7280 drives should in theory be the last ones you'll ever see from them.

They already bitset to DVD-ROM on DVD+R and DVD+R DL. You can't change that on the original firmware but I managed to get them to officially add full bitsetting support for the next firmware release So basically, it's like Liggy's one, only official now. From what I can remember of my own testing with the drive, they aren't good with anything other than MKM-001-00 and MKM-003-00 when it comes to overburning. The drive itself is only tested/certified for overburning on those disc - so that would make sense! I have requested a few additional tweaks but I don't know if they'll make it into the next firmware release or not.

To be honest, I haven't even tried to see if the Optiarc can scan.

No, it's for burning optical discs.

Your disc has CD-TEXT on it. If the xbox isn't picking up on it, it probably doesn't look for it in the first place. A lot of these programs rely on an internet database for info - and if it's a CD you've made up yourself, obviously the internet database isn't going to have info for it.

I'm scanning the burnt discs with an iHAS... totally unrelated to the burning drive - obviously

Ah so it's coming direct from the US then? Depending on how desperate you were for one, I was going to suggest one of those US to wherever forwarding companies. Then you could have just got it from Amazon.com.

I'd be interested to hear what they actually said... other people may want to order the same drive

Re-enable Burnproof. Turning it off doesn't do anything and what you've read about it is nonsense. You aren't using the discs recommended when trying to overburn. Others may work with additional firmware tweaks (like swapping the write strategy with MCSE to allow them to be burnt at 2.4x) but they're still very hit and miss... hell, even the recommended ones are hit and miss! btw, service pack 1 for Windows 7 has been out for ages now, you should install it.

You stop it being burnt by it not being in the CUE in the first place.

You just have to select 'Tag'. Your discs may actually have CD-TEXT info stored on them and the problem is the xbox doesn't attempt to read it. Put the disc back in the drive, switch to 'Read' mode in ImgBurn and click the 'View Media Information' button. See if it displays CD-TEXT info in the box that pops up. If it does, you'll know it's present on the disc.

Try contacting info.eu@vinpowerdigital.com and see if they have any details on where you can get one from.

No, it just burns what you give it. Try feeding them into something like MultiAVCHD and have it output a proper BD video disc structure. Then burn that with ImgBurn.

There won't be a problem in ImgBurn causing this. It burnt what you gave it and if it verified ok, the data on the disc matches the source ISO. If you want additional confirmation of that, mount the ISO in a virtual drive program and do a folder compare (using something like Beyond Compare) between the real drive (burnt disc) and the virtual drive (image). If your player is just freezing because it can't read the disc, try some other discs. You could get a decent BD-RE DL for testing purposes, then you don't need to waste discs ever again. I'd still like to see the log file please. You can access old logs via the Help menu.

Because the 'core edition' bit wasn't around at the time. The next release will show it properly.

It's not a specific drive, it's just a DVD burner. The one thing you do need to check is which type of connection (IDE or SATA) your current one has - or at least what's supported by the motherboard. SATA would be better if your motherboard has any/spare SATA ports. Then it's just a case of unplugging the current one and plugging in the new one. If you aren't happy about doing that, take it to someone that is.