LIGHTNING UK!

I figured you’d be using the same versions on both machines, so anything that may or may not feature in the changelog for 2.5.8.0 wouldn’t come into it. Obviously I do not remember what I did when, it was years ago!

LRA is last recorded address. If you’ve got the track size, it isn’t overly required. Some drives don’t bother returning that info. The addition of ADIP info might be down to the date of the firmware in the LG drive. The adip info doesn’t change, even once you’ve burnt the disc. So the book type field will show the real type of disc. The last recorded info can be changed as a result of burning, and that’s where you’d then see a disc have its book type changed to dvdrom for compatibility reasons. As for the commas, that’s down to your regional settings. The program uses what your OS is configured for.

Are you able to try your Samsung drive in that other machine? It's quite a specific error and seems weird a drive would return it when reading a normal DVD-RW disc. Maybe you've some software on your PC that's messing with the error codes? There's nothing that can be done software wise to work around this issue. If that's really what the drive thinks the problem is, you just have to live with it. The firmware update might fix it, but you'd have to try and find a changelog for SB01 somewhere. FirmwareHQ is fine, we helped collect all the firmware and build it.

As it’s quite rare these days, are you doing this for someone with no internet connectivity? If they do have the internet, just email them the 3 urls to the YouTube videos.

First things first, have you actually downloaded them as files from YouTube? I'm pretty sure they come down as MP4 or AVI files... but I believe 3rd party tools are required for that job. If that's still the case, you'll need to find out how to download from YouTube before you can begin to do anything with ImgBurn.

It sounds like your I/O is getting hung up. That's why ImgBurn can't be closed and you're having to reboot. When it gets stuck, try just unplugging the drive and see if anything returns to normal - and 'normal' in this situation would mean you get an error message. As to why it's running into issues... who knows. It could be a bad usb cable, outdated drivers, bad usb chipset/drive enclosure chipset combo etc.

Hmmm... weird! Can you try the disc in another drive and see how it gets on with it?

https://www.google.co.uk/search?q=record+screen+windows+10 'Windows Key + G' looks like it'll do the job on Windows 10.

You could try a different write speed if 'max' keeps failing. Check the list of 'supported write speeds' in the log you provided or refer to the info box on the right of the main screen when you're in Write mode with one of those discs in the drive.

So what is the reply windows doing exactly? Does it expand when you click it....even if only for a second? But then it goes back to the one line version? Any chance you can take a screenshot (or a video) of it doing it? There must be something funny going on.

As mentioned in your other thread, when you run into the situation where you can't get the 'reply' box to come up properly, try pressing F12 and see if anything is written in the 'console' tab of the developer tools. Other things to try... Close your browser down and reopen it. Log out and log in again Clear your browser's cache / cookies. Best option is to log out, clear cache, close browser, reopen browser, log in again.

If it happens again, you'll know what to do. Well, that and press CTRL+F5 to force a refresh before trying to click in the reply box again.

Please post the log so we can see what's actually happening.

I use Chrome exclusively and have never had a problem replying to posts. Looking at that thread, nobody said they had problems with Chrome on these forums. dbminter said he'd had problems with Chrome on the Macrium Reflect forums. You may need to open up the developer tools (press F12) and see if you're running into errors when you click your mouse in the reply box. If you have something running that's blocking the forum software from working as expected (the little 1 line reply box turns into a bigger box with more features once clicked), that could be why you're running into issues.

There no ‘mode’ for it. It would basically be an image conversion mode.

4x and 8x aren’t supported speeds. It would have burnt both of those at 10x.

You can’t use that initial cue to build a backup image. It can only be used to burn a disc. If you want to save that stuff so you can burn another copy some time, either keep a copy of the audio files alongside the cue or use Read mode on the burnt disc to get a new bin/cue set.

This is something related to DirectShow, not ImgBurn itself. What sort of files are you trying to add? It looks like you have some iffy filters installed or something. That specific log doesn’t mention the filter dll being used as part of the ‘connect’ process, but maybe it’s visible in another one of the crash logs?

It's probably easier if you just google for the various sector formats/structures possible on a CD. There's Mode 1, Mode 2 Form 1, Mode 2 Form 2 and CD-DA. If you look at the TOC info, you'll see if it has multiple tracks or a non Mode 1 track. If it isn't single session/track/mode 1, use BIN. That's what the program defaults to anyway, so just go with what it suggests. If you want to faithfully reproduce (or emulate) the disc, you should keep its sectors in the format they're supposed to be in.

M4a seems to have 2 codecs associated with it. AAC and ALAC. So even if something says it supports M4A, it doesn’t meant it’ll support both codecs. As your OS install can’t decode the files you’re feeding it (well, feeding into ImgBurn), that tells us you need another codec installed on the system. It sounds like you’ve got it working ok now having installed that DirectShow filter, so that’s good. [emoji1303]

None of these packages are from Microsoft. Anything not supported ‘out of the box’ requires 3rd party DirectShow filters. Having Googled a bit for ‘alac DirectShow filter’, this one got mentioned a lot. http://dsp-worx.de/?n=15

What type of audio files are you actually trying to use? File extension / codec please.

That disc only has a single, mode 1 track on it, so ISO would be the default extension / format. Iso is mode 1 / ‘user data’ of a sector - 2048 bytes per sector. Bin is for raw sectors - 2352 bytes per sector. That’s why the bin is bigger.

There’s overhead of the file system(s) you decide to use on the disc.

Were you using the same drive you're having issues with in one of your threads? Beyond that, I've no idea.