LIGHTNING UK!

Your drive probably doesn’t support those discs. A firmware update may fix that, but you’d need a patched flasher or whatever due to it being an oem drive. (From a Gateway pc possibly?)

Yes. It would then just be testing the disc is readable.

Yes, it would automatically verify against what has been written - and that applies to both Write mode and Build mode.

If it's a DVD-R, use Read mode to make an image of it and then burn it via Write mode. Is the source disc you're looking at actually a DVD Video disc? As ImgBurn only burn as-is, if you feed it an MP4 file, you'll end up with an MP4 file on the disc. You can probably skip Handbrake entirely.

I don’t know that either. If the model is in the ‘supported’ list I mentioned in my previous reply, it should work. If it isn’t, it won’t. If in doubt, ask Primera.

I've no idea. Going by the guide, mine was/is a Disc Publisher SE. You can get a newer PTRobot from here - https://www.primera.com/developersupport/ Supports Bravo SE,SE-3,II,Pro,Xi,XR,XRP,4100/4200 Series

Try the other filers listed at the bottom of the guide here: https://forum.imgburn.com/index.php?/topic/5555-How-to-write-an-Audio-CD-from-music-files-using-ImgBurn

I haven't done this stuff in like 10+ years, so please don't expect me to remember any of it! Look at an IFO in IfoEdit and you'll see how DVD Video files are broken down. Perhaps you recall the term PGC ? A PGC is a collection of Cells. They're the Cells I'm talking about. It all comes down to the DVD Video specs. A layer break is meant to be put in a certain position (a cell change) and that's the reason for the coloured starts on the layer break selection screen. The more boxes the position ticks, the higher up the star rating chart it goes. Pressed discs will have been designed and authored with a layer break position in mind. Unless of course they're 'seamless' ones and you're relying on the player working with a disc that doesn't really comply with the specs. They too may have some padding within the file system (invisible to you) so that a cell change falls in the correct place for burning to disc. Don't forget that pressed discs can be OTP or PTP. For burning, we only have the option of OTP. Different rules apply for each format in terms of layer sizes.

Once the ogg file has been added to the cue, right click it and you'll see the option on the context menu.

It's meant to split on a cell, but if the disc is quite full, it won't be able to add the required padding to make it work. I'm sure there's a guide for how to deal with such issues.

An hour?! Does it get stuck at 99% or does it count up to 100 really, really, really slowly? Which directshow filter do you have installed for the decoding of OGG files?

That doesn’t change anything. Acrovova have told you you’ve bought a stand-alone unit, not one you connect to a pc.

Nb12 does indeed appear to be a standalone unit. The USB port is probably there for controller updates or something.

If only you hadn’t disabled the ‘verify’ feature The log doesn’t show any errors from during the burn, but the verify operation would have told us if the disc could be read ok.

It means the BD drives don't support the command the older DVD drives used to for bitsetting. If they do it automatically, it's all good

I don’t know. The unit itself shows up ok, so I’d say the driver is ok. Speak to Acronova and see what they say. You didn’t answer my questions about if you can hear or see the drive doing anything when you turn the nimbie on.

The actual drive inside the nimbie should be listed in the cd/dvd devices section within Device Manager. If it can’t see it, ImgBurn won’t be able to either. The ‘elby clonedrive’ device that is listed is a virtual drive from a bit of software loaded on your pc. It has nothing to do with the nimbie unit. So something is wrong with your Nimbie unit or the drive inside it.

It won’t work until Windows displays the drive inside the Nimbie.

What's listed under the Unita DVD/CD-ROM section? The drive inside the Nimbie unit should show up in there. When you power on the Nimbie, can you see / hear the drive doing anything? It could be that something has gone wrong with the unit itself.

Your computer doesn't appear to have found the drive inside the unit. I assume you've tried turning it all off and on again? If so, look in device manager and see if there are any entries with little yellow 'warning' triangles next to them.

It looks like the problem command is this one... I 10:36:26 [0:0:0] HL-DT-ST BD-RE WH16NS40 1.02 (F:) (USB) I 10:36:26 CDB: AD 00 00 00 00 00 00 11 08 04 00 00 I 10:36:26 CDB Interpretation: Read Disc Structure - ADIP Information E 10:36:26 SENSE: 00 00 00 79 00 00 00 00 00 00 00 00 FF FF E 10:36:26 SENSE SK Interpretation: No Sense E 10:36:26 SENSE ASC/ASCQ Interpretation: The semaphore timeout period has expired. Something between the program and the drive is messing that up, because the drive would have no problem handling it. I assume you have no choice but to use the drive via a USB enclosure? Direct SATA connection would always be the better choice.

ImgBurn doesn't have the ability to disconnect your drive, that something your OS and its drivers would do. Press F8 once the program has loaded and enable I/O Debug mode. It'll log more info and then maybe we'll be able to see which command is causing it to get disconnected. Once it's done a cycle or two of finding the drive, the drive disconnecting, the drive being found again etc, press F8 a second time to turn I/O Debug mode off again. Save the log and upload it again for me please.

If you've already got a VIDEO_TS folder with the correct files in it, that's pretty much all that needs to happen. So what you may actually need is an authoring / conversion program that'll give you the complete set of DVD Video files you can then burn to disc.

Take a look at the DVD Video guides in the Guides section. Something like this one will probably do the job.

'Invalid field in parameter list' comes directly from the drive, it isn't an ImgBurn error. ImgBurn doesn't know what it's complaining about... that's where I then diagnose the issue manually. I guess I could have it detect index 00's with no length, but the source program shouldn't have put them in the CUE in the first place.