Jump to content


  • Content Count

  • Joined

  • Last visited

About kxkvi

  • Rank
    ISF Newbie

Profile Information

  • Gender
  • Location
    Wisconsin, USA
  1. kxkvi

    Direct Show Filter

    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
  2. 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
  3. 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 ImgBurn.log
  4. kxkvi

    Farewell Winamp

    From winamp.com:
  5. 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.
  6. kxkvi

    Read speed and related issues

    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.
  7. 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.
  8. 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
  9. kxkvi

    Shelf Life of a burned CD/DVD

    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
  10. kxkvi

    Shelf Life of a burned CD/DVD

    Very cool. I'm definitely interested. Judging by the Wiki article, the technology made its debut several years ago. I'm surprised it hasn't become more widely known by now. 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. kxkvi

    Session count not equal?

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

    Are all ISOs created equal?

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

    Are all ISOs created equal?

    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

Important Information

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