Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,521
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. lol I didn't change anything just upx'd it. Placebo testing is fun, I should do it with ImgBurn
  2. Ahh oops, it seems I rar'd up the non upx'd version. This one is back to ~210k again ImgBurnPreview.rar
  3. CRC errors and failing SMART... I'd deffo run the full set of WD tests on it and see if it passes. If it doesn't, just RMA it.
  4. It does. Help menu -> ImgBurn logs.
  5. I thought the ImgBurn one had always been about 200k?
  6. Try something other than 2x. ie. 8x, 12x or 16x. That's what the media is designed for. RITEKF1 is pretty awful stuff though, I'd wait for your TY's to turn up.
  7. Do some benchmarks using 'HD Tune' or something.
  8. I've done all I can do now, the rest is out of my area of expertise.
  9. The 'Device Not Ready (Cannot Read Medium - Incompatible Format)' message you're getting in the status bar shows the drive doesn't support the discs. You're lucky your drive gives you that much of a clue, normally it'll just say 'Device Not Ready (Medium Not Present)'. You need a new drive if you want to use those discs.
  10. DO NOT use Build mode to burn the image, it's for something totally different. You need Write mode and you also need to get discs that your drive supports properly.
  11. I had a go at speeding up the ' It's quite noticable when previewing from slow media - i.e. direct from an optical drive. The real reason for the delay is that when you press those , >> buttons and the video is playing, the program defaults to playing all the buffered data (note: this is nothing to do with my recently added 64k read buffer - which is now 32k btw). I've told it not to do that now so you should find it's much better. (attachment removed)
  12. If the log window has been closed, open it again via the 'View' menu. You should leave it open really, it contains a lot of important / useful / interesting information.
  13. I think a lot of the sluggishness comes from extra code put in to analyse the stream a bit before playback starts - maybe to find/buffer audio streams, I dunno. The horizontal lines are probably because the source material is interlaced.
  14. Not in ImgBurn you didn't! lol Maybe you just had a 10 second 1st cell on the last disc you really looked at?!
  15. To be honest, I think all the prev/next buttons should have been broken! The 'seek' functions were all using the wrong value for the current sector.
  16. The project doesn't have to include files, you can just have it so it configures all the settings.
  17. What drive is it exactly? Please copy + paste everything from the log window.
  18. There's no way in hell that drive has a proper write strategy for those discs. They're quite new and the drive is ancient.
  19. Ok, try this one... (attachment removed)
  20. You've already got an image there, why aren't you following the 'how to burn an image' guide?!
  21. Check the description of the item you're buying? Get them from www.svp.co.uk The verbatims are
  22. I'm sure I mentioned this before... playing is not the same as decoding to be put on a disc. You can play a 48kHz file as-is, you can't burn anything other than 44kHz. PM me a good email to send you a beta version to and then you can examine the raw output in the same way I did. What you have to understand is that ImgBurn is at the complete mercy of DirectShow. ImgBurn is just telling DS which file to process and then capturing the decoded bytes, there's no clever conversion code in ImgBurn or anything.
  23. Getting an I/O error means it could be something totally different that's making it fail on his pc. Can you post his log?
  24. Cell '1' (cell before the LB) has always been there in full, the previewer just jumps in at the 2nd of the two though. I'll look into the step back issue.
  25. The files shown in SoundForge sound identical (well, to my ears anyway ). So yeah, I cannot reproduce the problem. As ImgBurn lists that the ACM Wrapper filter is being used, it means some *.acm (Audio Codec Manager) file is being added to the mix (rather that just pure DirectShow filters). Assuming your filters are the same as mine, I guess it can only be some difference in the ACM filters that we both have installed. Can you get a screenshot / listing of what yours are? You can use this tool - http://www.nirsoft.net/utils/installed_codec.html Turn off the video/directshow ones in the options (or view?) menu.
×
×
  • Create New...

Important Information

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