LIGHTNING UK!

If the discs burn and verify ok, it's really just down to the source files and the playback device's ability to read the disc and play what's on it. There's no layer break stuff to mess with on BD. Can you post a log of you burning and verifying one of your discs please? Do you not get any sort of error from the Oppo 103? Do the discs that work ok in it have the same MID as the ones you're burning now and don't work?

That's correct, as E: didn't match any of the drives, it would have gone with whatever was active last time you used the program.

Both attempts resulted in your drive reporting a 'Write Error', so I'd just say it's unable to burn that media. You should have updated the firmware before making any attempt at burning them... or certainly after the first failure - unless you only found it existed after the second of course. Now it's down to you as to whether or not you update the firmware and try a third time. What do you do if it fails again? Try at 4x? Try some different TL discs? Buy another drive?

Has the drive ever been able to burn those discs? Can it see any other DVDs or is it just CDs that work in it? It might need cleaning or replacing.

I wouldn't hold your breath on that one If you copy and paste the following into a notepad and then save it as something like 'batchbuild.bat', it should do the trick. @for /d %%i in (*.*) do ""%ProgramFiles(x86)%\ImgBurn\ImgBurn.exe" /MODE BUILD /BUILDINPUTMODE STANDARD /BUILDOUTPUTMODE DEVICE /SRC "%%i\" /DEST "E:" /FILESYSTEM "ISO9660 + UDF" /UDFREVISION "1.02" /VOLUMELABEL "%%i" /ROOTFOLDER YES /NOIMAGEDETAILS /START /CLOSESUCCESS /EJECT YES /WAITFORMEDIAYou'll just need to adjust the '/DEST' parameter so it matches the drive letter of your burner. If you aren't burning DVD Video folders, you can adjust the /FILESYSTEM and /UDFREVISION parameters to suit - or leave them out so it uses the GUI defaults / whatever the program thinks it should use. Same goes for the /VOLUMELABEL one. At the moment it'll use the name of the folder. If you want it to use whatever the program generates / suggests, omit that parameter. So if you're happy with your current (pretty much automated) ImgBurn settings, perhaps try the following instead... @for /d %%i in (*.*) do "%ProgramFiles(x86)%\ImgBurn\ImgBurn.exe" /MODE BUILD /BUILDINPUTMODE STANDARD /BUILDOUTPUTMODE DEVICE /SRC "%%i\" /DEST "E:" /START /CLOSESUCCESS /EJECT YES /WAITFORMEDIAYou'd save this batch file in the folder containing your 34 folders to burn (and only those 34 folders) and just run it. It'll eject the disc when it's done and then open another instance waiting for another disc to burn the next one. Just insert the next disc, close the tray and it'll start burning automatically.

The media info button will do that if you go into read mode and press it.

You can't. ImgBurn requires a proper set of DVD Video files if it's to burn a DVD Video disc. If that's the format you want to burn, tell Pinnacle to output to that format. It'll make you a VIDEO_TS folder with the correct IFO/VOB/BUP files and you'll be able to burn that just fine.

Assuming that's burning in DAO mode and not TAO (DAO is the default one), there are no gaps on that disc. If your player appears to be 'playing' one, it's not from the burning phase.

The commands used to communicate with drives are part of a specification (MMC) and don't really change. As such, there's no need to mess with anything if it's working ok... and ImgBurn is working just fine. Nothing new has come out in terms of consumer writable media since the introduction of BDXL and 2.5.8.0 has already been tested / works fine with that. Yes, there are features I could add if I really wanted to, but they aren't ones I'm overly interested in adding. Development hasn't ceased, but I'm also not actively working on it. There will be new versions one day.

Does this help... ? http://forum.imgburn.com/index.php?/topic/22977-Batch-build%2E Just adjust the parameters (as per ImgBurn's ReadMe) to suit what you're trying to achieve.

I'm afraid you can't. You can do it via a batch file where you loop through all the folders, but that's it.

Post the log please.

Not if verify failed, no. If verify fails, your drive can't read everything on the disc. If it can't read everything, chances are that the OS install will fail.

What I'd do is use IsoBuster to examine the disc and just compare the LBA of the files against where the drive failed burning the disc. Anything beyond that point (and probably a bit before it as write errors are deferred) will be useless. "No write current" is nothing to do with electricity Try to avoid using LTH media. The HTL stuff is better / more reliable. I'm pretty sure the order is just alphabetical where ImgBurn is concerned and the folders are traversed in alphabetical order too. IsoBuster will shed more light on that if you dive in and look at the LBA of the files.

The image (files) you're burning will fit on a single layer disc, you don't need to use a double layer disc.

I did.

2.5.8.0 is the current one. I/O errors are not normally related to the program itself, they're simply its way of telling you that your drive failed to do something it was asked to do. So basically, the issue is normally between the drive and the media you're using. You're right, the log didn't attach. You can either try to do it again or copy and paste it.

I could have sworn a firmware update to my old bdp s570 or the newer s580 enabled cinavia detection on the device. Of course if it's hardware based, maybe the hardware was always present (in anticipation) but needed enabling via firmware.

Try cleaning the drive. Failing that, buy a new one.

Yes, standalones detect the signal too and will mute accordingly. It just depends on how new the device is or how new the firmware for the device is. Detecting it is now part of the specs I believe, so all new devices will detect it. Older ones will only detect it if their firmware updates have included it.

Ok well the reason should be fairly obvious. The program told you your image wouldn't fit on the disc, and that's why it's failed. You need to buy some double layer discs. Please refer to the pinned topic at the top of the forum listing - i.e. you want some with the MKM-003-00 dye/MID.

Post the log please - as per the pink box up the top.

Do you have the 'auto' calculate checkbox enabled? That can cause the command line setting to be used once and then reset. Beyond that, the only time number 1 should happen is if the program has already determined what you're burning to be a 'known' type of disc (DVD Video, BD Video etc). Your settings within the program (GUI) itself also need to be taken into account. It's not a CLI application. So if you've adjusted any of the prompts for build mode, they could be causing different things to happen. oh and it's /PRESERVEFULLPATHNAMES... your command line there is missing the 'NAMES' bit off the end. If preservefullpathnames is enabled, rootfolder doesn't apply.

The audio cd guide lists a few for different file types.

If DirectShow can split it apart and just feed the audio stream into something that'll convert it to the correct format, it'll work fine. I have used that feature myself quite a few times in the past with youtube clips.