LIGHTNING UK!

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.

Your drive is having an issue with the 'MBIPG101-R12-00' discs you're using. Have a read of this - http://forum.imgburn.com/index.php?showtopic=8000

Technically, they don't get done in either of those orders. The order is also subject to verify actually being enabled or not - the code to eject / delete is before the code to start the verify operation... it's just skipped if verify is enabled.

It's not just the Verbatim recommendation (I assume you're referring to this thread? - http://forum.imgburn.com/index.php?showtopic=8000 ), it's the other things in there that you can 'try' too. If a drive fails to burn something, that's pretty much always its own problem. You can change one of the 3 things (drive/firmware/media) in the hope the next combo does a better job. Memorex are just the name stamped on the packaging / disc labels, the important bit is the Manufacturer ID (MID) and those ones are 'MBIPG101-R10-65'. Memorex can (and do) swap between selling different MIDs so you never know what you're getting.

I wouldn't necessarily burn MKM-003-00 at 2.4x, but that still doesn't mean it should fail at that speed. Other than what I mentioned in post #2, I have no other ideas. Your drive should be able to burn those discs but is failing to do so - considering all the discs it's wasting (not to mention your time), it's probably worth just paying out $20 - 30 for a new one!

If it burnt and verified ok, there's nothing more for us to help with really. Did it? Perhaps you could post a log so we can see how the burn went? (as per the pink box up the top )

Try the newer firmware update and see if it add/improves support for the 'CMCMAG-DI6-000' discs you're using. http://www.firmwarehq.com/LG/BH10NS30/files.html As yours is a Buffalo version of LG's BH10NS30, you may need to 'crossflash' the drive using Devilclaw's flasher program. If you want to do that (it's certainly worth a try), ask the nice people in the LG forum over the MyCE forums for help - http://club.myce.com/f91/ The HyperTuning option you tried to access is a feature only found on LiteOn drives, yours is an LG - hence why it failed to work. Oh and you know you're burning next to nothing there yeah? Don't waste a 50GB disc on 2MB of data!

Your DVD burner is ancient and only supports DVD+ format media... so make sure you haven't purchased DVD- (minus) format discs. If the write button isn't enabled, it's probably for a good reason. That reason is normally written in the statusbar at the bottom of the main window.

VLC may just not support (my version of?) Flac files in a CUE file. If the flac files work, the CUE will work

If your drive is reading / verifying slower than it should do, you should remove SPTD from your system (it's normally installed by the likes of DAEMON Tools). If it isn't, you haven't noticed it or you just don't care if it is, leave it be This is the guide you should be following for burning a Blu-ray video disc. http://forum.imgburn.com/index.php?showtopic=9512 Basically, if you don't have an image file (i.e. an ISO file - where you'd use 'Write' mode / the 'Write image file to disc' option to burn it to a disc), you use 'Build' mode ('Write files/folders to disc' or 'Create image file from files/folders').

Ok so here’s what you do... Download madFlac 1.10 from http://madshi.net/madFlac.rar Extract the rar (using something like WinRAR from http://www.rarsoft.com ) to ‘C:\Program Files\madFlac’ (or ‘C:\Program Files (x86)\madFlac’ if you’re using a 64 bit operating system). Now navigate to that folder in Explorer and locate the ‘madFlac.ax’ file. Select it and drag+drop it onto the ‘InstallFilter.exe’ file. You should get a message come up (possibly after a UAC prompt you have to click ‘Yes’ to) saying: “The DirectShow filter "C:\Program Files\madFlac\madFlac.ax" was registered successfully.” Now try loading your Flac files into ImgBurn’s ‘Create CUE File’ window again.

Can you post the log please - as per the pink box up the top

During the burn you mean? It already does that.

It is/does. At one point (version) or another, ImgBurn stopped saving what it was set to when it was closed down. If you happened to have it set to 4 at that time, that's where it will have stayed. Set copies to 1, enable the option to remember the number of copies, close and reopen the program, then tell it not to remember the number of copies again. Or just close the program, locate the correct registry entry (possibly more than 1) and edit it (them) directly in there.

Without knowing more details, it's hard to give you a precise answer. It doesn't normally show that prompt without a good reason though. Please copy + paste all of the disc info from the box on the right. You are using DVD+R DL discs and not DVD-R DL ones yeah? If so, mount the image in a virtual drive program (Virtual CloneDrive etc) and build a new one by pointing 'Build' mode at the virtual drive. Or you could extract the contents of the ISO to a folder on your hdd with something like WinRAR / 7zip and build a new one from that folder.

It must be something you're doing differently because the OS plays no part in it. (Well, ok, it does tell the program the size of the files in question) Maybe the files you're adding within Windows 8 have a much higher bitrate and therefore are much larger in size?

They don't get messed up, it's impossible as nothing gets remembered between calculations. If Calculate fails, it won't ever get to the stage where the disc starts burning - because the exact same code is run again for the real burn (and of course it would fail again). I don't know what you actually did, but it's not what you've shown in that video or what you're telling me you did. Show me the log of the 'coaster' so I can see what happened please. You can access old logs via the Help menu.

Because it ends the 'calculate' operation - notice the log says 'Operation Failed!'. It's not going to calculate the size of the resulting image (or disc) if it can't physically create it in the first place due to an error in what you're trying to do. Calculate it not meant to be used as a running total for how much you're burning to the disc - that's why 'Auto' is disabled by default. If you want a more complex view of what you're burning (as that's not the idea behind 'Standard' input mode), switch to 'Advanced' input mode instead.

I've already explained all this in my previous response.