LIGHTNING UK!

Which version of Bootcamp are you running? I'm afraid this problem won't go away until the OS shows the size as 1080 bytes in the file properties. The 'size on disk' doesn't matter.

You're wasting your time by quick erasing a DVD+RW disc before then burning straight onto it. ImgBurn defaults to formatting discs properly. Nero doesn't and that's why the disc still aren't reported as having been formatted properly in the disc info text on the right. As to why your drive is unable to complete a format on them properly, that's probably some sort of drive/firmware/media combo issue. Post the log please.

That log looks fine to me. With that disc in the drive, copy + paste the disc information text from the box on the right when you're in Read mode please.

Yeah, that disc isn't well. Lay it to rest... in the bin. Try burning on your Pioneer if the Samsung isn't behaving itself.

If you add the mp3 to the CUE window and right click it, see if anything useful comes up when you get the program to show the directshow filter list. It may tell you which filters are being pulled into the conversion 'graph' by the OS.

A mouse click or two is all it takes to opt out of anything OpenCandy happens to offer you within ImgBurn's installation wizard.

Post the log of you burning and verifying the disc please.

Your drive doesn't support the discs ('UMEDISC-DL1-64') you've purchased. http://forum.imgburn.com/index.php?showtopic=8000

I expect so, yes. But ACM would work if the other filters installed on the OP's machine weren't claiming they could decode it ok.

Which 'properties' are you referring to? Within the program? That value you see in the 'Size' column there should match what's shown in the file properties box if you right click the file within the DLE window and select properties. That's not the size of the object on the disc, it should be the actual size of the file... and it saying 4KB is where your problem is coming from.

Can I ask, did it actually give you a value in the 'Time' column for those problem files? My Windows 7 machine can't decode those MP3 files via DirectShow, so you must have additional filters installed that think they can but then fail. Mine then falls back to ACM decoding and that works fine.

I don't know what MultiAVCHD accepts. You might be able to get help with that application at the doom9 forums... we just deal with ImgBurn here really.

That stuff is in my generic signature, it wasn't aimed at you.

Select 'build' in the mode menu at the top, then select 'advanced' in the input menu at the top. You have to use the proper reply method (not the quick box) in order to upload stuff to the forum.

Yes, SetupImgBurn_2.5.8.0.exe is the one you want.

Yes, after that the drives just don't get a letter.

I'm surprised MultiAVCHD doesn't see the .ts file. Maybe tsmuxer or bd rebuilder will work with it? You're correct, ImgBurn won't convert anything, it burns as-is.

It isn't an image file, that's why it isn't showing up in 'Write' mode. Use 'Build' mode - write files / folders to disc.

If you email one of the problem files to 'support' (check the programs about box), I'll take a look at it. What OS are you running?

Did you use Verbatim MKM-003-00 discs? They're what 'everyone' tells you to use, so that's what you should be using. Your drive errored out when trying to burn to the 'CMC MAG-D03-64' ones you've got there... it doesn't like them.

If you use 'advanced' input mode and add that file to the disc layout, what does it list in the size column? Perhaps you could take a screenshot of the disc layout editor window so I can see?

ok and what's the size of the file according to the OS?

All that's happening is the program is unable to read X bytes from a file that's supposed to be X bytes in size... it's as if the file is shrinking between when the OS reports its size and when ImgBurn then tries to read it. The debug info will tell me a bit more about what's going on. I wonder if the problem is coming from Windows 8.1 trying to read that HFS partition or if it's something to do with bootcamp. I've never tried either so I can't comment!

So are you saying that if you repeat that very same build operation (i.e. just click the start/build button again), you won't always get the error on the same file? Press the F8 key before you try again (to enable I/O debug mode) and then post a new log once it has errored out please.

Go into write mode and go through each of your drives (in the 'destination' selection box), right clicking on said box and selecting 'Family Tree'. Close the prompts that come up and just copy + paste everything from the Log window. Make sure you highlight which drives have the problem. I can only assume they're connected differently somehow (a different controller maybe) or have PIO/DMA issues. Try unplugging the slow drives and switch them with one that's working full speed. Are they then ok? If so, that at least rules out the drive itself and then it's just down to your hardware/software configuration.