Ch3vr0n

Yes and no. MTS is primarily linked to AVCHD. Blu-ray is M2TS only, not MTS.

Again not related to burn errors. Why do you keep going further away from the original issue. Different 'questions' : different topic Mode selector - burn folders to disc - done. Imgburn burns exactly what you tell it to burn. If you select a folder it will burn the folder and it's contents. If you only select the folder contents then it only burns that. It's not possible that you select a folder with contents and imgburn only burning the contents and not the folder too. Anyway out for good now. No doubt after this round of questions you'll come up with some more, again not related to the original topic questions. Cya Sent from my Nexus 6P with Tapatalk.

Unless I'm mistaking the DVD standard dictates at least 1gb needs to be written for successful playback. I doubt your few second clip matches the requirements. And then there's the fact that you're using CMC mag am3 cheap crap blanks. Sent from my Nexus 6P with Tapatalk.

No they can't. Disable via task manager, but if you don't know EXACTLY what you're doing you'll cause system instability. You just don't give up do you? More and more questions way beyond op. Sent from my Nexus 6P with Tapatalk.

If you'll look in your logs you'll see a line referring 'SPTI', that's the default one and issued by Microsoft in Windows. Elbycdio is about and sptd yet another. Sent from my Nexus 6P with Tapatalk.

I think what lightning means it's installing something that installs an io controller. Like virtual clone drive from elaborate bytes (free) which installs elbycdio.dll that can then be selected in IMGBurn, or daemon tools (which installs sptd but I nor ImgBurn like that one very much). See if that makes any difference, an io controller is completely different from the physical connection the drive uses. The USB driver is also a different component to the overall equation.

1,2 nor 3 have anything to do with burn errors. Look it up? Using Google is hard yes?

There's a difference between the normal polycarbonate standard discs use and the CARBON layer MDisc uses. *out*

Just because a certain party doesn't talk about a certain thing you immediately jump to the conclusion that there's a problem. Mdisc doesn't use a polycarbonate. The recording layer is made of a glassy carbon. Maybe you should read Wikipedia a little or do more research before jumping to conclusions. The exact properties of Mdisc are classed by millenniata as a 'trade secret'. You're not going to find the exact specs. Now, I have said this once and I'm not going to repeat myself. You keep asking the same thing over and over about pie,pif, PIO on multiple forums and what else but you're never satisfied with the answers lightning UK gives you. Then you jump to a completely different thing such as Mdisc which has nothing to do with your initial 'questions'. You have your answer, or do the research. I'm out. Happy holidays. Sent from my Nexus 6P with Tapatalk.

Mdisc uses an inorganic STONE based surface. On the contrary to standard method where lasers burn into the due, mdisc gets physically etched into it. Data degradation is physically impossible, now obviously that won't protect them from scratches, but when stored right data simply cannot deteriorate unlike standard discs.

It's not the same at all. Not even remotely. The color packaging is slightly different. Dbminter has the good ones, you have LTH type ones which is clearly stated on the packaging. LTH was abandoned years ago and never really took off in the first place. Only a limited number of drives support the organic dye (should be goldish for you on the underside) where the good standard ones use a purple inorganic dye. What you ordered was blank disc leftover stock. LTH was quickly abandoned due to lousy burn results, very limited drive support and being just plain bad. Sent from my Nexus 6P with Tapatalk.

Not really. My topic was about batch burning to disc. He wants to batch convert each dvd folder. So the command line that worked for me will need a small modification to create iso instead of burning to disc.

Just a quick update. Looks like that 2nd one is doing exactly what i wanted. Insert disc, burn, eject, wait for next, burn... Though it looks like that /DEST "E:" paramater is "flexible". I copied it AS IS and forgot it was there and just executed. I've got 3 optical drives, G:\ H:\ and I:\ (C-F are internal harddrives). G:\ and H:\ were empty at the time and only I:\ had a blank disc in it. ImgBurn went straight to the I:\ with a blank disc in it, despite the "/dest E:" parameter and started burning. No error whatsoever for an impossible destination drive. Maybe it's because the last drive ImgBurn had used (through manual burn via GUI, it was still set to I:\)

I'll give it a try. IMGBurn has been setup to if it detects DVD content to auto set the revision to 1.02 without prompting Same for BD content. Don't need to match volume label as it should use the folder name which is exactly what i want So think option 2 is for me

M2ts isn't an image file. That's a video container. Disc images are iso,img,... Sent from my Nexus 6P with Tapatalk.

I have little to no experience with commandline. My imgburn is pretty much configured to no prompts. Just need something simple to burn one folder after another. Deleting source and stuff I'll do that myself. Maybe you can add batch burn folders in the next version. Seems like I'm not the only one that would like that. Sent from my Nexus 6P with Tapatalk.

Can you elaborate how? They all reside in the same folder. I'd love it if you could add that function in the next version (hopefully soon released). Would be kind of redundant to first turn them into iso's and then burn those iso's in batch with imgburn

I have a simple question. I have 34 different DVD folders on my HDD that need to be burned to discs (they each contain a valid full dvd structure that's different). It seems like there's a "batch" mode for burning iso's to disc, but not for burning folders to discs. How do i achieve what i want? Eg: Drag the 34 root folders into IMGburn, when it's done burning the first => eject => Wait for new disc => Burn next folder

The 570 is out of the question, it's even on the net that the latest firmware mr4 or something did not have it. The 580 is a different matter. That's a 2nd quarter of 2012 model, meaning it falls under mandatory detection. If it didn't detect it at first, but did later then the hardware was already present just not enabled. As to the ps3, I did say that above. Sent from my Nexus 6P with Tapatalk.

The first 'fix (software one)' as the name says only applies to PC's, since you can't install anydvd on a standalone. It's the second one that impacts physical players. (whether mkv or disc output). As to the players: ANY licensed Blu-ray player that was licensed on or after February 1st 2012, is required to detect it. That applies to software players as well as standalones. For software based players, i think powerdvd 10's 2nd to last version didn't detect it. It's last update and v11 and beyond do. For standalone's it's their license date that matters, NOT when YOU buy it. Example A licensed player bought on Feb 1st 2012, is not required to detect it. (Model was highly licensed before mandatory detection date) A licensed player that was licensed before Feb 1st 2012, you buy TODAY (if you manage to find one) is NOT required to detect it. It is only NEW players for which the model was located after Feb 1st 2012, that are required to detect it. Why that date? That's the date Cinavia became an official part of the Blu-ray standard, and detection became mandatory. Manufacturers have to implement it or risk losing they're license. It's not just super common on disks because of the high licensing fee for movie studios. ( $ to be allowed to use it, $ per movie title and $ for the amount of copies of said title) There's only a few studios that use it because of that after nearly 5 years of mandatory detection. - Sony (obviously as they were the main backers of it during inventing) - lionsgate - universal @lightning posts older ones older than that date are NOT required to detect it, they couldn't even if they wanted to. Standalone player detection is not firmware based, it's hardware based. Players older than that date simply lack the hardware to do it. The 'exception' was the PlayStation 3. It's Blu-ray player is a software based one, which is why detection wasn't present in 1 firmware and was present the next. They simply pushed a new firmware (4.05 I think), with a new player that detected it. Not surprising since it was Sony.

Yes, it does it in 2 ways. 1) 'prevent Cinavia detection by software player': that AnyDVD setting patches the SOFTWARE player (like PowerDVD) to not detect the signal. That one doesn't remove Cinavia, it just prevents the player from detecting it and thus muting the audio 2) 'remove Cinavia from CloneBD audio copy': that setting is dependant on using CloneBD and in CloneBD downscaling of audio must be selected. When both are enabled, during the cloning process AnyDVD taps into CloneBD without it knowing that and applies the removal fix. (Since removing Cinavia requires audio processing, and that's not something AnyDVD can do on its own). CloneBD doesn't know this is going on and just continues cloning. Sent from my Nexus 6P with Tapatalk.

Blu-ray specification REQUIRES UDF 2.50. https://en.wikipedia.org/wiki/Blu-ray Use 2.1 and it's unreadable on ANY Blu-ray player. Ps3 and standalones alike. You're confusing disc version with the UDF file system. 2 completely separate things

You need specific hardware (drive model) and specific brand of blank discs for that. Overburning is a tricky thing to do right, even with the correct tools.

Cinavia isn't a copy protection, it's an audio drm. Copy protections prevent you from making a copy (like css). Cinavia doesn't do that, if it was a copy protection ImgBurn wouldn't be able to burn cinavia discs. Cinavia is an audio drm, it stops full audio playback. You can still copy it, you just can't properly play the copy. There's a difference.

Whether there is a setting there on the menu is irrelevant. The dvd-r standard simply doesn't have booktype specified and the discs simply don't support it. There's nothing else to say about it. It can't be done, period.