Jump to content

kxkvi

Members
  • Posts

    45
  • Joined

  • Last visited

Posts posted by kxkvi

  1. I have a stack of 100 Verbatim DVD+R discs that I bought back in 2012.  I attempted to burn a

    file project to them tonight and ended up with 2 coasters on two different DVD burners.

    (uncorrectable errors on verify)

    Do they go bad over time?  If so, I'll toss them and buy a new spindle.

    Thanks and regards!

     

  2. On 8/13/2019 at 1:37 PM, KBS said:

    That is what I installed was madFlac image-burn doesn't see it even when it says successfully installed.

     

    You didn't happen to delete/move the source files after installation, did you?  By source files, I mean the madflac.ax and libflac.dll.

    Regards,

    Thomas

  3. 1 minute ago, dbminter said:

    I haven't made an audio CD from FLAC files in some time, but last time I did it, I was using madFLAC under Windows 10 x64.

     

    It may sound counterproductive, but try using any of the online free audio file converters to convert one of these FLAC's to a FLAC.  This new FLAC might actually be compliant.  I've had that happen before, actually.  However, it may not actually do any good at all, though.

     

    I just tried creating a CUE file under Windows 10 1903 x64 and it worked with the FLAC I put in.  So, I'd be leaning more towards your input files being the problem.  However, without you actually having a FLAC file you know worked before and trying it again, it's hard to say if it's your input files or your madFLAC installation.

    Hi, thanks for the response.

    I found the problem.  I was trying to install madflac by running the "install.bat" as an administrator from the GUI.

    The solution was to open a command window and use the START command to install it.  All of my FLAC files are

    now recognized successfully.  I'm very pleased and relieved.

    Again, thanks.

    Thomas

  4. I recently needed to burn some FLAC files to an audio CD. My first thought was that I'd need to install

    the madflac v 1.10 filter, so I did.  Nevertheless, my FLAC files still aren't recognized.  I thought it might be

    something peculiar to certain FLAC files, so I tried a variety of them, all with the same result.  I'm running

    Windows 10 x64 v1903.

    Attached is a screenshot and a sample ImgBurn log file.  `Is there any workaround for this?

    Thanks and regards,

    Thomas

     

     

    MadFlac Failure.jpg

    ImgBurn.log

  5. From winamp.com:

     

     

    Winamp.com and associated web services will no longer be available past December 20, 2013. Additionally, Winamp Media players will no longer be available for download. Please download the latest version before that date. See release notes for latest improvements to this last release.
    Thanks for supporting the Winamp community for over 15 years.

     

  6. Is it the economy?  Is it the shift to create apps for mobile devices?  Neither?

     

    On this date in 2012, I could barely keep up with the weekly releases.  It's a
    completely different story this year, as everything seems to be lapsing out of
    development.  Even Mozilla's "rapid release" program appears to have slowed

    to a crawl.  This is not a complaint; merely an observation.  Still, it seems a sad
    day when the most exciting appearance on the scene is the latest update of the
    Java runtime environment.

     

    Enjoy the day.


     

  7. Sectors on a disc are 2352 bytes in size, plus 96 for subchannel. Audio uses all 2352 bytes, data typically uses 2048. So whilst there's room in the 2352 for data to have extra error correction, there isn't any room for CDDA to have it.

     

    Lke you said though, there's some sort of error correction on all discs, even CDDA. You get C1 and C2 error correction and some drives can report back the number of C2 errors to an application - but ImgBurn doesn't enquire about that info.

    Hi Lightning.

     

    Wow.. thanks for sharing that insight. While I don't claim to comprehend it all at this point,

    I think I see what you're getting at. It sounds to me like you're referring to a whole different

    layer involved in the process of moving that data around. Error-correction is there, but not

    accessible or meaningful at the layer that your process needs to deal with. It's embedded within

    the 2352 byte blocks of audio data, and as such, you have no need or way to access it.

    Interesting stuff. We see a lot of similar situations in the telecom/datacom world as well. It'll

    give me something to think about and study over the next few days.

     

    Thanks again.

  8. Hi folks. I'm back to cause yet more trouble.

     

    Yesterday, I was creating some ISO images from various discs. What caught my eye

    at the time was that read speed settings existed on the dialog. In the past, I had

    simply run with the defaults and largely ignored that option.

     

    When I started thinking about the way this option was displayed, it didn't make much

    sense to me. A read spead on the left, then what looks like a division sign (/), then

    another read speed on the right. I just couldn't wrap my mind around it. I started

    poking around in the guides, and finally found the answer.

     

    It seems to me that if the dialog were simply labeled data on the left, and audio on the

    right, it would make the reason for the separate settings more readily apparent.

     

    Also, I read this statement in the guide:

     

    "The reason for the default '8x' for 'Audio' as source, is that there's no error correction

    on Audio tracks, so the slower the better really."

     

    This has me a little bafflled. Is this setting in reference to audio CDs? The way I've

    always understood audio CD theory, as outlined in great detail in Ken Pohlman's

    excellent "Principles of Digital Audio", was that error correction is used extensively

    on audio CDs. Specifically, cross-interleave Reed-Solomon Code, I seem to recall

    that this was part of the Red Book standard as well. As such, I'm left a little mystified

    by this statement, and why ImgBurn would not be unable to access that error-correction

    information.. I suspect that the answer may well be way over my head, but I thought

    I'd throw it on the table nevertheless.

     

    Thanks again for a great app. Enjoy the day.

  9. I'm interested in burner sources here in the U.S. I've been ordering mine from Newegg for the

    past ten years, and have gotten what I consider to be very good deals. The trick seem to be

    to wait until the burners are on special in terms of price and/or free shipping.

     

    What merchant(s) are others using?

     

    Thanks!

     

    Thomas

  10. So, it seems you need a separate drive to write to these discs, but, the media, once written, will apparently read in any DVD+R read capable drive.

     

     

    I had not heard of this technology before, either.

     

    I just received a pair of LG GH24NS90 burners that I ordered. Although the manufacturer does not include any

    specifications regarding burn speeds for this media in their data sheet, they claim that they are M-Disc compatible,

    and the drives have the M-Disc logo silkscreened on the front panel.

     

    Once I install them and receive some M-Discs to burn, I'll post back with the results.

     

    Enjoy the day.

     

    Thomas

  11. What is the useful shelf-life of a typical burned CD or DVD? Is there any

    real research that covers this issue? How long before uncorrectable

    errors appear on the media?

     

    I did a web search on the topic, and the answers I see are all over the map.

     

    I'm sure there are many factors involved, and it's probably not a simple

    question.

     

    Still, it seems to me that the folks who come out with "hundreds of years"

    might be confusing burned CDs/DVDs with conventionally "pressed" media.

     

    As for myself, I'll feel lucky if they perform well after ten years of sitting around

    at room temperature. At the point where things start degrading, if I'm still

    interested in retaining the files, I'll simply burn them to new media, whatever

    form that may take ten years down the road.

     

    On a semi-related note, I'm curious about what type of error-correction is

    currently used on data CDs/DVDs. When I was into digital audio back in

    the 80s, I often read about Reed-Solomon Cross-Interleave Code. However,

    I'm not sure this technology migrated from audio CDs to media holding data.

    I can see from using utilites like Nero CD/DVD speed that errors seem to be

    detectable, and to some degree are correctable, but I'm not sure about

    the algorithm being used.

     

    Regards,

     

    Thomas

  12. When the burner has problems properly recognising the disc it has just burned it's a sign that the burn quality may not be that good.

     

    Try burning at 4x, 6x or 8x and you could end up with better quality burns. Also, what's the brand of the media you're using?

     

    I was burning at the lowest speed supported, which is 3x. Media was Verbatim (Mitsubishi) DVD+R.

     

    Cheers.

     

    Thomas

  13. First time ever for this error.

     

    Situation: Attempting to burn 2 copies of a data DVD from a list of files. Standard

    procedure for me. ImgBurn unexpectedly returns this error, yet asks me to insert a

    2nd DVD to burn another copy.

     

    I aborted.

     

    Although verify failed, DVD seems to read okay. All SHA-256 file hashes are

    good.

     

    Log file attached.

    ImgBurn.log

  14. I just installed UltraISO on my machine. I'm going to give it a whirl this evening and see what I can do with it.

     

    I built ISOs of the aforementioned DVD with both ImgBurn and UltraISO (with "skip bad sectors" and "volume filtering"

    unticked). The files are identical in size. More importantly, the hashes match. I'm impressed!

     

    UltraISO seems a useful tool, just as ImgBurn is.

     

    Regards,

     

    Thomas

  15. When ImgBurn 'builds' an ISO from scratch, it makes them a multiple of 16 (or 32) sectors so this type of thing isn't a problem.

     

    Interesting. So it seems that in the end.. no, they aren't all created equal, even though their intent is the same. Apparently,

    there is room to move around within the standard. This takes me back to the days when I saw heated debates in the forums

    about "such-and-such's ISO app doesn't create a truly compliant image"

     

    I just installed UltraISO on my machine. I'm going to give it a whirl this evening and see what I can do with it.

     

    Regards,

     

    Thomas

  16. What built the ISO in the first place?

     

    I honestly don't know. The image was built by Microsoft, and as far as I know, I have no

    way of determining how they generated the file.

     

    If you burn to a DVD+R, the size could change as the drive will burn a multiple of 16 sectors.

     

    That makes sense, since I did burn it to a DVD+R. Aside from that aspect, is there any

    overhead, padding, or formatting that's applied when the image is built in ImgBurn?

     

    Regards,

     

    Thomas

  17. Earlier this evening, as I do often, I used ImgBurn to burn an ISO image to produce

    a data DVD. As usual, the process was seamless and without incident.

     

    Simply because I had a few extra minutes to devote to the project, I decided to

    try an experiment. Using the same DVD that I had just burned, I used ImgBurn to

    create an ISO image file from it, saving the output file to a different directory. When

    the process finished, I checked the MD5 and SHA1 hahes of the newly created ISO.

    I note that the hashes are different from the original ISO source file.

     

    As such, I need to further my understanding of how ISO files are formatted and written.

    What I need to comprehend is how two different ISO images are able to write identical

    DVDs. I haven't really done a bitwise comparison of the data on two DVDs written

    by the two files yet, but I have the ability to do this, and may add that to my list of things

    to do tomorrow evening. In the meantime, if anyone can point me in the right direction,

    I would be happy to include any information provided as an item for further study.

     

    Enjoy the day.

     

    Thomas

  18. Their 'Search' may be useless but the product pages are still all there.

     

    http://us.liteonit.com/us/dvd-internal/item/dvdinternal/ihas124

     

    You're absolutely right. It was my own fault. I didn't see the horizontal scroll

    arrows on their product page, so neglected to use them.

     

    The 'SmartPack' program handles firmware updates for all of their drives.

     

    Yes, I did see that item, and downloaded it. Do you happen to know if this

    is a standalone utility that contains all of the updated information, or does

    it connect to Lite-On over the Internet to get those?

     

    I've always preferred individual files for each firmware versions, but hey...

    whatever works.

     

    I notice that they also specify using the "Nero Toolkit". I'm unsure of what

    they're referring to, but it may be the Nero Info Tool, which I do have, and

    which displays the product's firmware version, along with a bunch of other

    information.

     

    Thanks much,

     

    Thomas

  19. http://www.liteon.com/index.aspx

     

    Nice web site.. if you happen to be Chinese.

     

    I eventually landed on:

     

    http://us.liteonit.com/us/index.php
    

     

    I was browsing Newegg's burner selection, and noticed that

    they had a Lite-On unit on sale. I pasted the model number

    in the search box of their support section:

     

    com_search.jpg

     

    Search Search Keyword: All words Any words Exact Phrase Ordering:

    Search Only: Download Glossary Articles Web Links Contacts Categories Sections News Feeds

    Search Keyword iHAS124

    Total: 0 results found.

     

     

    I also searched their product section, and got this:

     

    Database Error: Unable to connect to the database:Could not connect to MySQL
    

     

    Okay, so it may be an older drive, but gee whiz, does support really die that

    quickly nowadays? I was unable to find any information whatsoever on their

    web site.

     

    I did find the firmware, but not on their site. Somehow, I don't think I'll be

    purchasing their products anytime soon.

     

    Regards,

     

    Thomas

  20. Run the mp4 through DVD Flick / ConvertXtoDVD etc and then burn the output (a VIDEO_TS folder) with ImgBurn.

     

    Wow, am I ever impressed! DVD Flick does it all! You just tell it what you want, feed it what

    it asks for, then hit the button, sit back, and let it do math for a while. Outstanding! No extra

    codecs to install either. It even calls ImgBurn to write the image file.

     

    The DVD plays great, too!

     

    Thanks again!

     

    Thomas

×
×
  • Create New...

Important Information

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