Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,497
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. An ECC block is 16 sectors on a DVD, not 32. For that reason, the error isn't important. Which UDF version did you use on the disc?
  2. Check (and perhaps replace) the cable / port the drive is attached to. If you're getting CRC errors with the transfer of data to/from the drive, something isn't right somewhere.
  3. It’ll be the same deal as in the other threads. Take control of your AV software and get it to ask you what you want to do rather than just doing it. You also have the option of downloading from one of the other mirror sites.
  4. Australian burner
  5. Sorry, I've never played around with burning those DTS CDs and have no clue how they actually work. Generally speaking, ImgBurn would be trying to convert any audio files fed into it into 44100Hz, 16 bit, stereo.... as that's what CDDA is. The exception to that would be when you feed it a BIN file, as I'm pretty sure that just gets burnt as-is. So, if you're saying it's worked ok in the past, what format were those images / files in? Were they all BIN/CUE? What files do you have for this non-working disc?
  6. What you've said there is the exact opposite of what this person is seeing though. You're essentially saying Build mode works and Write mode doesn't. They're saying Write mode works and Build mode doesn't. Programmatically, the code that does the writing doesn't know or care where it's getting the data from. Data is data and the exact same commands get sent to the drive to ask it to write it to disc.
  7. Speaking from a technical point of view, I'm afraid it doesn't mean anything. There's no difference between Write, Build and Discovery modes where the actual burning of the disc is concerned. There's only 1 chunk of code that does the actual burning and it's used by all 3 modes. Also, there's no way to make a drive more or less capable of burning / reading the disc. That stuff is all controlled by the drive and its firmware.
  8. Your drive can't burn DVDs. It's a CD burner that can *read* DVDs (but not write to them).
  9. Have you switched the output to 'Image File' rather than 'Device' ?
  10. Your INDEX 00 markers do not leave a short time between tracks. That's the point I was making The TRACK commands give you the ability to skip (tracks). You can't do anything with indexes at all - as in, you can't jump between them. They're invisible to software / hardware players. The table of contents on the disc only records where track x / index 01 is and that's considered the start of a track if you skip through them. So really, INDEX 00 of a track actually looks like it belongs to the previous one. The PREGAP command instructs the program to insert digital silence between tracks (that data is not taken from the file).... so if you had a single large file with digital silence in it between tracks, that's where you might choose to use INDEX 00 (for when it starts) and then INDEX 01 for when the music starts again. INDEX's consume data from the file.
  11. You can do without the INDEX 00 entries, there's no point in them being there. INDEX 01 is what players jump to when you skip tracks etc. Plus you'd only made the index 00 1 frame long... which is 1/75th of a second! Well done for figuring it all out though. No idea about the browser thing. Remove the password from your saved password list and try again.
  12. That would have power cycled the drive I guess - something a restart doesn't do.
  13. Why are you using such an old version? Even the latest version is old, so that's the one you should be using. It's not worth anyone's time trying to troubleshoot when you aren't up-to-date with the app in question. Once you've updated (and I suggest you reset back to the default settings), copy and paste everything from the Log window once you've opened the program and left it until it's found the drives - I'm assuming that's the bit yours is taking ages on - going by the screenshot.
  14. Maybe you rebooted your machine? There's no reason for it to get stuck where it did.... it would have been due to something outside of ImgBurn, but a bit more info (in the form of a debug enabled log) would have helped me to help you figure out what it might be. Hopefully it stays working ok for you now.
  15. Please post the log from you burning (with verify enabled) the discs. Either your drive(s) can't burn the discs very well or your playback device can't read them very well. Neither of those are anything to do with ImgBurn really. You could try some different discs.
  16. This is not something ImgBurn can help you with.... but those other CUE tools you mentioned might work? You don't need to split the actual WAV file, if the CUE has tracks defined in it, they'll reference different parts of the file and your disc will come out with multiple tracks rather than just 1. CUE files are actually quite basic, you can edit them in notepad and insert tracks based on rough timings as you fast forward through the file in media player or whatever.
  17. Next time you burn, press the F8 key before the point where it cycles the tray. That'll enable I/O debug mode (confirm it via the Log window) and more will be added to the log. Once it's stuck, save the log and upload it here on the forum please.
  18. That's a Windows thing. Turn off Autoplay or whatever it's called.
  19. It looks like you tried to burn too much to the disc. The program tells you that what you've chosen to burn won't fit, which must mean you acknowledged the message.
  20. If you have an ISO from tsMuxer, use the 'Write image file to disc' option within ImgBurn - as per the guide you were linked to earlier.
  21. Are you trying to burn an Audio CD? If so, follow that guide.
  22. The program detects it's a BD Video based on the presence of the BDMV folder. So.... where's your BDMV folder? Ah, hang on... you mention opening ImgBurn to burn the ISO in your initial post. If you have an ISO, you should be using Write mode to burn it, not Build mode.
  23. Just use UDF (and only UDF) as the file system.
  24. I did a search on the forum.... turns out it's in the FAQ https://forum.imgburn.com/index.php?/topic/59-faq/&tab=comments#comment-8023
  25. Your AV software probably removed it. See if you can get it to actual notify you of what it's doing and not just do it.
×
×
  • Create New...

Important Information

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