Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,457
  • Joined

  • Last visited

Posts posted by LIGHTNING UK!

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. '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.

  6. Thank you.

    Well... you can't have a file of total length 02:00:13 and have something starting at 02:00:13... you're already at the end of the file. Looks like a bug in whatever made the cue/wav files.

    Easiest course of action here (assuming it's the same issue with all of the files) is just to remove all of the INDEX 00 entries.

  7. Well, I can't see any 4 second tracks but there are lots of 0 second (and frame) index 00's, which I guess is also a no-no.

    Maybe next track pregaps at the end of the previous track aren't supported at all?

    Could you fire up the 'create cue file' feature in the tools menu and add the first wave file from that set please? If I know exactly how long it it, I'll know if there should be data after the end of track 1 / index 01's supposed end (which would then form index 00 of track 2).

  8. Please don't do the above, it will mess things up.

    Once you've loaded the CUE in Write mode, click the 'Image Information' button and take a screenshot of what it says please. You may need to scroll the window and take a 2nd screenshot so I can see it all.

    Normally a drive will reject a cuesheet because a track is coming out as less than 4 seconds in length. So it could that be the program doesn't really like your CUE (pregaps for the next track at the end of individual track wav files are a bit complex) and a track length is being calculated incorrectly.

  9. For whatever reason, the response to the ‘inquiry’ command is corrupt. That’s where the name of the drive comes from.

    Has it always done that on your system?

    Try turning the machine off and on again.
    Try removing the ide/ata controller from within device manager and rebooting.
    Have a look at which filter drivers are installed ( option on the tools menu), maybe you have one that’s messing with the actual response from the drive.

  10. I don’t even know how that’s possible?!

    It’s not an issue I’ve seen before.

    I’d say to enable I/O debug mode by pressing F8 and then scan for devices again (tools menu). Once the drive has been found and the log window settles down, turn off I/O debug mode again and save + upload the log for me to look at please.

  11. The disc you burnt at 19:04 (according to your log) looks fine to me.

    As you've burnt it at max speed (48x), there's a chance the burn quality won't be quite as good as if you'd burnt it at something like 24x - meaning it might be harder to read and some drives may totally fail. It was totally readable in your burner though, so playback should be possible on your PC.

    If you want names to show up in a standalone player, you need to be looking at adding CD-TEXT to it. You can do that when you create the CUE file based on your MP3 files. ImgBurn can read the ID3 tags (if present) in MP3 files and create CD-TEXT info from them, you just need to instruct the program to do that.

    I think the Audio CD guide in the Guides forum does cover that, so please take a look at it.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.