RE: Winamp Version 5.092 is now Available
The other thing they fix but don't tell you about I believe is the ability to use programs like Total Recorder to record streams from Winamp - in other words they've foiled it for copyright reasons. I haven't tested this myself, but I read about it a few weeks ago and have not upgraded for this reason. John Gurd -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Steve Pattison Sent: 28 May 2005 00:28 To: PC Audio Subject: Winamp Version 5.092 is now Available Winamp version 5.092 is now available and one place where you can download it from is at www.whitestick.co.uk/download.html. Here are the changes in this version: * Fixed: Long delay and high cpu on exit with many items in playlist Regards Steve, Email: [EMAIL PROTECTED] MSN Messenger: [EMAIL PROTECTED] Skype: steve1963 ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED]
Real Player blocking the desktop
Is there a way of preventing Real Player from obscuring part of the desktop and other applications while something is playing? There is an option called on top while playing, but clicking this with JAWS doesn't seem to change anything. What I want is a way to minimise Real Player even when something is playing. Any help would be appreciated. Thanks, Barry Chapman ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED]
Re: Real Player blocking the desktop
Hi, Barry, have you tried pressing enter on this option to see if it is a check box that toggles or not? I know in the old versions of real player in 2000, it was that way, but I can understand if things have changed. On Sat, 28 May 2005 18:02:15 +1000, Barry Chapman wrote: Is there a way of preventing Real Player from obscuring part of the desktop and other applications while something is playing? There is an option called on top while playing, but clicking this with JAWS doesn't seem to change anything. What I want is a way to minimise Real Player even when something is playing. Any help would be appreciated. Thanks, Barry Chapman ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] Marty ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED]
Re: Reusing an RW CD?
Hi Dana. To erase your rewritable using nero, just insert your discand use alt + R to open the recorder menu. Arrow down to erase rewritable disc and press enter. Choose whether you wish to perform a quick eraise or a full erase and then tab to the erase button to start the process. The quick erase takes about a minute and will just flag all files on the disc as obsolete. A full erase will actually wipe the complete contents of the disc and will take about 30 mins. A quick erase is usually all you'll need to do. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Dana S. Leslie [EMAIL PROTECTED] To: PC-Audio pc-audio@pc-audio.org Sent: Thursday, May 26, 2005 10:04 PM Subject: Reusing an RW CD? Can anyone explain to me how to re-format an RW CD, so that it can be re-used? I paid extra for RW CDs, because I understood that one could do this with them. But I haven't been able to figure out how. After burning some music tracks to a CD, when I want to re-use it, I can't find any icon in the context menu of my CD drive for re-formatting the disc, or anything else that looks promising. Perhaps, there some way to do this in the Nero software? But I don't know my way around that package; so far, I've burned all my CDs using either Easy CD Extractor or RealPlayer 10. Is there any way to reformat an RW CD using either of these packages? Thanks. Dana ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED]
Re: converting text to audio
I personally use textsound. www.bytecool.com It's more simple to use than textaloud and it have a nice command line interface to use it with batch files. Well, no many persons have this particular need, but On Sat, 21 May 2005 15:00:09 -0400, you wrote: Thanks Daniel. Actually, I *am* using Openbook to do the conversions now, I'm just searching for a better alternative. Text Aloud has been suggested by one list member, and I intend to give it a try. Good luck, Scott - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 21, 2005 5:18 PM Subject: Re: converting text to audio Scott, So far as I'm aware, there *is* in the current version of Open Book (version 7x) the ability to do just this, though I haven't learned yet how to do it, myself. There is a mailing list specifically for Open Book Users, and if you write to me privately, I'll find the subscription information and give it to you. Daniel - Original Message - From: Scott Blanks [EMAIL PROTECTED] To: pc-audio@pc-audio.org Sent: Saturday, May 21, 2005 6:56 AM Subject: converting text to audio Hi everybody, I'm new to this topic, so I hope I ask the correct questions. Basically, what I am looking for is an accessible and effective way to convert text or MS Word files into mp3 or wav. I use Open Book currently, but I imagine there is something out there which would more adequately meet my needs. Any ideas? Scott mailto:[EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.14 - Release Date: 5/20/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.14 - Release Date: 5/20/2005 ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED]
Re: On the fly ripping and burning
Hi Daniel. I think it was myself that you'd probably referred to below as recommending that one should rip with on the fly unchecked. You've asked a few questions below so I'll try to answer them as best I can. Firstly, the speed at which you rip can be changed in the CDEX settings so it may be worth trying this first before you decide to do anything differently. The thread priority setting has 5 or 6 values that vary from below normal to fastest. There's a balance to be had here as if you rip at the fastest speed you may find that you can't use your computer effectively while ripping because it's taken so much resource. With regards to using on the fly in general, this really refers to processing a direct data stream right from your CD-ROM rather than extracting data first and then processing it when it's been safely read and stored on your hard drive. When ripping on the fly, it is possible that you will find slight imperfections with the finished product usually manifesting itself in pops and crackles. This is generally as a result of jitter but could be just down to the process of extractign and converting a direct data stream. If you've used CDEX you may have seen on the list of tracks that there's a right hand column called status. This can have 3 different values: dash meaning that the track has not yet been ripped. OK meaning that the track was ripped with no jitter errors. X followed by a number meaning that there were a number of jitter errors found; the number representing the number of errors in the track in total. These values are retained by CDEX so even if you haven't noticed them before, you can put in a CD that you've ripped previously and see the status results. The reason why I mention this is that I too take great care of my CD's but I have been surprised by jitter errors when ripping my CD's. Some I've been able to remove by cleaning the CD with a special CD cleaning cloth but others I've been unable to remove. The number of jitter errors generally dictate how noticeable the errors will be to you. A standalone CD player usually is far better built than a CD-ROM and in general have far better error correction capabilities. So, if you put your CD in your standard player you might not notice jitter errors because of this error correction and the quality of the transport build. With regards to burning on the fly, well, the same applies in terms of the possible impact on the final product but there is another danger here. If you're burning on the fly, again you're taking a direct data stream from your CD-ROM and passing it straight to your rewriter. If there is a read error on the source CD and you're burning, the burn could actually fail and then you are going to end up with a CD that cannot be played and is good only for using as a coaster or tying together with other ruined CD's and Robbie Williams CD's to scare birds from your vegetable plot in the garden. Like most things, personal preferences dictate whether you will use on the fly or not but I see it as a guarantee that is worth a little extra time on that rip or burn. Hope this helps. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC-Audio Pc-audio@pc-audio.org Sent: Friday, May 27, 2005 11:36 PM Subject: On the fly ripping and burning Lately, I've been downloading and exploring a number of programs for ripping, burning and copying music. And one thing I've noticed while reading the documentation for these applications. That's that they don't all agree with, who was it, I think Keith, who in the course of describing how to best configure the ripping settings in CDex, said that on the fly ripping was to be avoided in favor of the slower method of writing a file (or image, or whatever is right to say; I've seen it put both ways now). as I understand it, this is so that if there's some sort of flaw in the material being ripped, then the program will catch it and somehow rectify the error prior to writing the track to disk. I think that's the idea, right? Well, in at least one of the programs I've been trying-- I think it's the Easy CD-DA Extractor that everyone's been speaking highly of, the developer himself, in the instructions, recommends the on-the-fly method, explicitly, as he explains how to set everything for optimal ripping quality. A moment ago, I used CDex to rip all the tracks from a CD to disk, and was reminded as I waited, and waited, and waited, just how much extra time the slower method required. I could enjoy having this procedure go faster. What I'd like to know is, just what sorts of errors are supposed to be avoided by using the slower method, and where in the sequence are those errors expected to come from? I mean, if it's in case your CD is faulty in some way, then I'm going to just set it for on the fly. Because I know the condition of most of my music CDs, and have little reason to suspect that
Re: On the fly ripping and burning
Kevin, Yes, of course it was you who enabled me to fine tune my CDex settings, for which help I thank you again. And thanks for your clear and informative explanations here, as well. that said, I understand better now your preference for being cautious with ripping. But in order to get a sample of what had happened with a disc I ripped to .mp3 just yesterday, after setting CDex back to its default on the fly mode, I stuck that CD into the drive again, launched CDex and used the Jaws cursor to read the full length of the information beside each track. And every track of the 16 said Okay at the end of the line (I know it isn't a line, but that's how I'm perceiving the layout with Jaws). So that one went okay, for instance. and when I used to rip on the fly before taking the precaution you recommended, I never produced .mp3 tracks with any pops or clicks or other audible faults. On the other hand, maybe you can explain this: As I listen to Jaws read the info that tracks the ripping process, after it reaches 100 per cent of a track, I always hear, as the last utterance before I hear 5 per cent as the ripping of the next track gets underway, jitter. It says this every track, at the end of ripping it. I've always wondered what that meant, but now that you say it indicates a flaw in the disc or maybe in the recording process, I don't get it. My ripping turns out faultless, as I've said. So why am I hearingjitter reported at the end of each track while ripping it? I have one more question, this time about burning as opposed to ripping. You wrote: With regards to burning on the fly, well, the same applies in terms of the possible impact on the final product but there is another danger here. If you're burning on the fly, again you're taking a direct data stream from your CD-ROM and passing it straight to your rewriter. If there is a read error on the source CD and you're burning, the burn could actually fail and then you are going to end up with a CD that cannot be played and is good only for using as a coaster or tying together with other ruined CD's and Robbie Williams CD's to scare birds from your vegetable plot in the garden. I'm not sure what you mean, here. When I say burning, I'm talking about creating a CD from .mp3 files that are on my computer, and which I usually know to be playable and listenable. So I don't understand why you again cite the critical importance of considering both the condition of the original CD and the error correction capabilities of the CD ROM drive. Maybe you thought that when I spoke of burning, I was talking about copying a CD? I wasn't, in this case. Hope that's more clear. And thanks again for your explanation. I may experiment a little with returning to your cautious method and jacking up the priority level a bit, to see if that would make it less frustrating to use the imaging method. But mainly, I appreciate your giving me such a clear idea of the things to be watchful for, and the alternatives for ripping. Daniel - Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 6:52 AM Subject: Re: On the fly ripping and burning Hi Daniel. I think it was myself that you'd probably referred to below as recommending that one should rip with on the fly unchecked. You've asked a few questions below so I'll try to answer them as best I can. Firstly, the speed at which you rip can be changed in the CDEX settings so it may be worth trying this first before you decide to do anything differently. The thread priority setting has 5 or 6 values that vary from below normal to fastest. There's a balance to be had here as if you rip at the fastest speed you may find that you can't use your computer effectively while ripping because it's taken so much resource. With regards to using on the fly in general, this really refers to processing a direct data stream right from your CD-ROM rather than extracting data first and then processing it when it's been safely read and stored on your hard drive. When ripping on the fly, it is possible that you will find slight imperfections with the finished product usually manifesting itself in pops and crackles. This is generally as a result of jitter but could be just down to the process of extractign and converting a direct data stream. If you've used CDEX you may have seen on the list of tracks that there's a right hand column called status. This can have 3 different values: dash meaning that the track has not yet been ripped. OK meaning that the track was ripped with no jitter errors. X followed by a number meaning that there were a number of jitter errors found; the number representing the number of errors in the track in total. These values are retained by CDEX so even if you haven't noticed them before, you can put in a CD that you've ripped previously and see the status results. The reason why I
Re: Kevin: On the fly, another question
But don't most extraction process actually separate those processes anyway? I really don't know the answer to this one, but I would have thought that a program like Easy CD-DA Extractor would first rip the file off the disk, then compress it, even if the user doesn't actually have to perform both of these steps. Am I wrong? Bruce -- Bruce Toews E-mail and MSN/Windows Messenger: [EMAIL PROTECTED] Web Site (including info on my weekly commentaries): http://www.ogts.net Info on the Best TV Show of All Time: http://www.cornergas.com On Sat, 28 May 2005, Kevin Lloyd wrote: Hi Daniel. It's not that flaws at source can be fixed just because you've unchecked the on the fly checkbox. If there are flaws on the CD then they will cause issues whether you rip on the fly or not. The point I'm not making very well is that by breaking down a complex process involving the extraction and conversion of data from a spinning disc, there are less chances of issues arising if the process is instead broken down into a number of discreet steps. Specifically, separating the process of reading the disc to extract all audio information before any conversion to MP3 is done using an encoder that is applying complex algorithms to the data to assess what it thinks can be disregarded and what it thinks needs to be retained to fulfil high quality sound reproduction. Hope that's clearer. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 5:26 PM Subject: Re: Kevin: On the fly, another question kevin, I don't quite understand. If you aren't offered the opportunity to correct an error yourself, then are you implying that somehow, during this two step process, errors from a damanged or flawed CD nonetheless do get corrected for before they're written to .mp3 from the image? Only without your intercession? Is that it? Otherwise,I don't understand how the two-step process ensures that flaws in the audio CD source don't get written to .mp3. Is my question clearer now? Thanks. elps m isk e3tween - Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 8:40 AM Subject: Re: Kevin: On the fly, another question No, it won't detect potential errors and allow you to stop, continue or fix in situ. By creating the image you are breaking down the tasks associated with ripping so that you extract in one step to your hard drive and then convert from there. When on the fly you extract and convert in a single step. It is for this reason alone that you are likely to have less risk of imperfections when ripping to an image first. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC-Audio Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 4:31 PM Subject: Kevin: On the fly, another question Kevin, Let's say I use the method of ripping that involves writing a file or image to disk and then ripping from that, the method you prefer for its prudence. Okay. So what if a CD I'm ripping tracks from turns out to have the kinds of flaws that elicit this jitter error report and mean that you'll wind up with a messed-up .mp3 copy? In what way does this method actually provide protection? Does it stop the process at some point, notify you that there's a flaw, and offer the option to correct it by clicking on something? Or if not that, what? Thanks. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.1.0 - Release Date: 5/27/2005 ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.1.0 - Release Date: 5/27/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.1.0 - Release Date: 5/27/2005 ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to:
Re: Kevin: On the fly, another question
Kevin, You mean that when you have flaws on an audio CD, once they get written to an image file on disc, the encoding process is less likely to pick up the flaws, somehow, as it creates the compressed file? appy- Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 10:05 AM Subject: Re: Kevin: On the fly, another question Hi Daniel. It's not that flaws at source can be fixed just because you've unchecked the on the fly checkbox. If there are flaws on the CD then they will cause issues whether you rip on the fly or not. The point I'm not making very well is that by breaking down a complex process involving the extraction and conversion of data from a spinning disc, there are less chances of issues arising if the process is instead broken down into a number of discreet steps. Specifically, separating the process of reading the disc to extract all audio information before any conversion to MP3 is done using an encoder that is applying complex algorithms to the data to assess what it thinks can be disregarded and what it thinks needs to be retained to fulfil high quality sound reproduction. Hope that's clearer. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 5:26 PM Subject: Re: Kevin: On the fly, another question kevin, I don't quite understand. If you aren't offered the opportunity to correct an error yourself, then are you implying that somehow, during this two step process, errors from a damanged or flawed CD nonetheless do get corrected for before they're written to .mp3 from the image? Only without your intercession? Is that it? Otherwise,I don't understand how the two-step process ensures that flaws in the audio CD source don't get written to .mp3. Is my question clearer now? Thanks. elps m isk e3tween - Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 8:40 AM Subject: Re: Kevin: On the fly, another question No, it won't detect potential errors and allow you to stop, continue or fix in situ. By creating the image you are breaking down the tasks associated with ripping so that you extract in one step to your hard drive and then convert from there. When on the fly you extract and convert in a single step. It is for this reason alone that you are likely to have less risk of imperfections when ripping to an image first. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC-Audio Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 4:31 PM Subject: Kevin: On the fly, another question Kevin, Let's say I use the method of ripping that involves writing a file or image to disk and then ripping from that, the method you prefer for its prudence. Okay. So what if a CD I'm ripping tracks from turns out to have the kinds of flaws that elicit this jitter error report and mean that you'll wind up with a messed-up .mp3 copy? In what way does this method actually provide protection? Does it stop the process at some point, notify you that there's a flaw, and offer the option to correct it by clicking on something? Or if not that, what? Thanks. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.1.0 - Release Date: 5/27/2005 ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.1.0 - Release Date: 5/27/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.1.0 - Release Date: 5/27/2005 ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.2.0 - Release Date: 5/27/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.2.0 - Release Date:
Re: On the fly ripping and burning
Hi Daniel. A buffer under run is where your computer can't pass enough data quickly enough to the rewriter to enable the write to continue successfully. The burn therefore fails and you can end up with a coaster. The underrun protection somehow smooths out the data transfer between the computer and the rewriter so that this doesn't happen, effectively maintaining a constant flow of data between the two. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 4:15 PM Subject: Re: On the fly ripping and burning Kevin, All points taken. While you're on the subject of copying, could you explain to me what the option in most programs for checking a box to enable something I think is called underrun protection or something like that means, and what's best to do with that setting? Sorry if I'm not remembering the expression just right. thnk - Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 8:04 AM Subject: Re: On the fly ripping and burning Hi Daniel. Yes, those OK values would suggest that those tracks have ripped just fine. Don't worry about JAWS saying jitter in that situation, it's just a JAWS thing rather than anything to do with the rip itself. You will know when there truly are jitter errors there when you hear JAWS announcing jitter during the actual extract as he talks through the percentage completed so far. You can also review the screen with your JAWS cursor during the extract step and you'll see there's a box at the bottom of the screen with a running total of jitter errors for that particular track. You're quite right that I was talking more specifically about copying audio CD's when I wrote those words rather than burning acompilation from your hard drive. Sorry for any confusion caused. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 3:55 PM Subject: Re: On the fly ripping and burning Kevin, Yes, of course it was you who enabled me to fine tune my CDex settings, for which help I thank you again. And thanks for your clear and informative explanations here, as well. that said, I understand better now your preference for being cautious with ripping. But in order to get a sample of what had happened with a disc I ripped to .mp3 just yesterday, after setting CDex back to its default on the fly mode, I stuck that CD into the drive again, launched CDex and used the Jaws cursor to read the full length of the information beside each track. And every track of the 16 said Okay at the end of the line (I know it isn't a line, but that's how I'm perceiving the layout with Jaws). So that one went okay, for instance. and when I used to rip on the fly before taking the precaution you recommended, I never produced .mp3 tracks with any pops or clicks or other audible faults. On the other hand, maybe you can explain this: As I listen to Jaws read the info that tracks the ripping process, after it reaches 100 per cent of a track, I always hear, as the last utterance before I hear 5 per cent as the ripping of the next track gets underway, jitter. It says this every track, at the end of ripping it. I've always wondered what that meant, but now that you say it indicates a flaw in the disc or maybe in the recording process, I don't get it. My ripping turns out faultless, as I've said. So why am I hearingjitter reported at the end of each track while ripping it? I have one more question, this time about burning as opposed to ripping. You wrote: With regards to burning on the fly, well, the same applies in terms of the possible impact on the final product but there is another danger here. If you're burning on the fly, again you're taking a direct data stream from your CD-ROM and passing it straight to your rewriter. If there is a read error on the source CD and you're burning, the burn could actually fail and then you are going to end up with a CD that cannot be played and is good only for using as a coaster or tying together with other ruined CD's and Robbie Williams CD's to scare birds from your vegetable plot in the garden. I'm not sure what you mean, here. When I say burning, I'm talking about creating a CD from .mp3 files that are on my computer, and which I usually know to be playable and listenable. So I don't understand why you again cite the critical importance of considering both the condition of the original CD and the error correction capabilities of the CD ROM drive. Maybe you thought that when I spoke of burning, I was talking about copying a CD? I wasn't, in this case. Hope
Re: On the fly ripping and burning
thanks. That's a nice feature, it would seem. Is it the best idea to enable it every time you're offered the choice in the settings of a CD burning program? - Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 10:15 AM Subject: Re: On the fly ripping and burning Hi Daniel. A buffer under run is where your computer can't pass enough data quickly enough to the rewriter to enable the write to continue successfully. The burn therefore fails and you can end up with a coaster. The underrun protection somehow smooths out the data transfer between the computer and the rewriter so that this doesn't happen, effectively maintaining a constant flow of data between the two. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 4:15 PM Subject: Re: On the fly ripping and burning Kevin, All points taken. While you're on the subject of copying, could you explain to me what the option in most programs for checking a box to enable something I think is called underrun protection or something like that means, and what's best to do with that setting? Sorry if I'm not remembering the expression just right. thnk - Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 8:04 AM Subject: Re: On the fly ripping and burning Hi Daniel. Yes, those OK values would suggest that those tracks have ripped just fine. Don't worry about JAWS saying jitter in that situation, it's just a JAWS thing rather than anything to do with the rip itself. You will know when there truly are jitter errors there when you hear JAWS announcing jitter during the actual extract as he talks through the percentage completed so far. You can also review the screen with your JAWS cursor during the extract step and you'll see there's a box at the bottom of the screen with a running total of jitter errors for that particular track. You're quite right that I was talking more specifically about copying audio CD's when I wrote those words rather than burning acompilation from your hard drive. Sorry for any confusion caused. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 3:55 PM Subject: Re: On the fly ripping and burning Kevin, Yes, of course it was you who enabled me to fine tune my CDex settings, for which help I thank you again. And thanks for your clear and informative explanations here, as well. that said, I understand better now your preference for being cautious with ripping. But in order to get a sample of what had happened with a disc I ripped to .mp3 just yesterday, after setting CDex back to its default on the fly mode, I stuck that CD into the drive again, launched CDex and used the Jaws cursor to read the full length of the information beside each track. And every track of the 16 said Okay at the end of the line (I know it isn't a line, but that's how I'm perceiving the layout with Jaws). So that one went okay, for instance. and when I used to rip on the fly before taking the precaution you recommended, I never produced .mp3 tracks with any pops or clicks or other audible faults. On the other hand, maybe you can explain this: As I listen to Jaws read the info that tracks the ripping process, after it reaches 100 per cent of a track, I always hear, as the last utterance before I hear 5 per cent as the ripping of the next track gets underway, jitter. It says this every track, at the end of ripping it. I've always wondered what that meant, but now that you say it indicates a flaw in the disc or maybe in the recording process, I don't get it. My ripping turns out faultless, as I've said. So why am I hearingjitter reported at the end of each track while ripping it? I have one more question, this time about burning as opposed to ripping. You wrote: With regards to burning on the fly, well, the same applies in terms of the possible impact on the final product but there is another danger here. If you're burning on the fly, again you're taking a direct data stream from your CD-ROM and passing it straight to your rewriter. If there is a read error on the source CD and you're burning, the burn could actually fail and then you are going to end up with a CD that cannot be played and is good only for using as a coaster or tying together with other ruined CD's and Robbie Williams CD's to scare birds from your vegetable plot in the garden. I'm not sure what you mean, here. When I say burning, I'm talking about creating a CD from .mp3 files that are on my
RE: Winamp Version 5.092 is now Available
Hi Bruce, And let me say most respectfully, that I don't think that it is either fair, or even legal for one to allege that one is in violation of the law just because one wants to make a recording for one's own personal use. I know, many people abuse their privileges, but in this country, one is presumed innocent until proven guilty. This kind of action is not really a matter of legality, because recording devices per se aren't considered illegal, only the use of these devices in an act of piracy. One is also free to own a gun in this country, but that doesn't mean that any act engaged in by the user by that right is legal. Of course, it isn't legal to shoot your neighbor. At least at this point in time, I can't be arrested for having a recording device on my computer, but if I were to be found to be engaged in illegal activities through the use of that product, I would be charged with said illegal activity, not with the possession of an illegal device. At 11:02 AM 5/28/2005, you wrote: I'm sorry, but in my personal opinion, attempting to comply with the law is hardly a malfunction. Bruce -- Bruce Toews E-mail and MSN/Windows Messenger: [EMAIL PROTECTED] Web Site (including info on my weekly commentaries): http://www.ogts.net Info on the Best TV Show of All Time: http://www.cornergas.com On Sat, 28 May 2005, Larry Higgins wrote: John, I just tried recording with V5089.1 with Total Recorder, and had no problem using the software driver to do so. Again, are you specifically referring to this latest upgrade, or was this malfunction supposed to be introduced into this latest incarnation of the program? At 03:00 AM 5/28/2005, you wrote: The other thing they fix but don't tell you about I believe is the ability to use programs like Total Recorder to record streams from Winamp - in other words they've foiled it for copyright reasons. I haven't tested this myself, but I read about it a few weeks ago and have not upgraded for this reason. John Gurd -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Steve Pattison Sent: 28 May 2005 00:28 To: PC Audio Subject: Winamp Version 5.092 is now Available Winamp version 5.092 is now available and one place where you can download it from is at www.whitestick.co.uk/download.html. Here are the changes in this version: * Fixed: Long delay and high cpu on exit with many items in playlist Regards Steve, Email: [EMAIL PROTECTED] MSN Messenger: [EMAIL PROTECTED] Skype: steve1963 ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED]
Re: Apology Re. Editorializing
Sorry Buddy Bruce g. I know better also, but I let your post get the best of me, and that rarely happens with me. Guess It was the coffee g. At 11:06 AM 5/28/2005, you wrote: I apologize about my editorializing in my previous post about Winamp. I know better than to do this, and I don't want to start a big debate on copyrights and the rightness or wrongness thereof. Please, pretend I didn't post that last message. Bruce -- Bruce Toews E-mail and MSN/Windows Messenger: [EMAIL PROTECTED] Web Site (including info on my weekly commentaries): http://www.ogts.net Info on the Best TV Show of All Time: http://www.cornergas.com ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED]
Burning with RealPlayer
For a few days now, I've been downloading tracks from the RealPlayer 10 Music Store, burning them to CD - which has to be done in RealPlayer Premium - , and ripping them off as .wav files. It's been working well, and the quality of the tracks is excellent! But I have one major problem (aside from the cost grin). When the tracks I want to burn are loaded in RealPlayer and ready to be burned, the burn your Tracks button has to be click with the JAWS cursor, and it's rather hard to find in JAWS cursor mode. Does anyone know of an easier way to start a burn in RealPlayer 10? Is there a key stroke, or something else I don't know about? Thanks. Blessed Be, Dana D. S. Leslie, ne C. R. Guttman [EMAIL PROTECTED] E OL' PHILOSOPHIE SHOPPE Your Source for Discounted Ideas http://members.cox.net/dsleslie2/ ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED]
Re: Sound Forge, GoldWave, and WMA files.
Jim! .wma shows up in the Open dialogue of Sound Forge so I assume it can open them. Chirp|Chirp|Chirp: It's the Bat, Chirping Bat .Com ! New DEC-TALK USB: $650.00, www.chirpingbat.com/dectalkusb.shtml ! Gyration RF Wireless 100 foot range keyboard: $199.00, www.chirpingbat.com/rfkeyboard.shtml ! J-Say without Naturally Speaking: Standard $345.00, Professional $575.00, www.chirpingbat.com/j-say.shtml ! Window Eyes 5.0: $700, includes delivery in the USA, www.ChirpingBat.Com/windoweyes.shtml ! Triple Talk: USB $450, PCI $350, includes delivery in the USA, add $30 outside, www.ChirpingBat.Com/tripletalk.shtml ! Sound Forge 8.0 with CD Architect 5.2: $250, includes delivery in the USA, www.ChirpingBat.Com/soundforge.shtml ! We accept PayPal Visa, Mastercard, money orders, checks, wire transfers, etc. We ship Internationally. Click to convert our prices into your currency at: www.xe.com/ucc/full.shtml Reach BA Software in the United States at: Phone: 1-518-572-6092 weekdays, 1-518-359-8538 other, Email: [EMAIL PROTECTED], Skype name adirondackbat, WWW: www.ChirpingBat.Com ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED]
Re: On the fly ripping and burning
yes Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 6:22 PM Subject: Re: On the fly ripping and burning thanks. That's a nice feature, it would seem. Is it the best idea to enable it every time you're offered the choice in the settings of a CD burning program? - Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 10:15 AM Subject: Re: On the fly ripping and burning Hi Daniel. A buffer under run is where your computer can't pass enough data quickly enough to the rewriter to enable the write to continue successfully. The burn therefore fails and you can end up with a coaster. The underrun protection somehow smooths out the data transfer between the computer and the rewriter so that this doesn't happen, effectively maintaining a constant flow of data between the two. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 4:15 PM Subject: Re: On the fly ripping and burning Kevin, All points taken. While you're on the subject of copying, could you explain to me what the option in most programs for checking a box to enable something I think is called underrun protection or something like that means, and what's best to do with that setting? Sorry if I'm not remembering the expression just right. thnk - Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 8:04 AM Subject: Re: On the fly ripping and burning Hi Daniel. Yes, those OK values would suggest that those tracks have ripped just fine. Don't worry about JAWS saying jitter in that situation, it's just a JAWS thing rather than anything to do with the rip itself. You will know when there truly are jitter errors there when you hear JAWS announcing jitter during the actual extract as he talks through the percentage completed so far. You can also review the screen with your JAWS cursor during the extract step and you'll see there's a box at the bottom of the screen with a running total of jitter errors for that particular track. You're quite right that I was talking more specifically about copying audio CD's when I wrote those words rather than burning acompilation from your hard drive. Sorry for any confusion caused. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 3:55 PM Subject: Re: On the fly ripping and burning Kevin, Yes, of course it was you who enabled me to fine tune my CDex settings, for which help I thank you again. And thanks for your clear and informative explanations here, as well. that said, I understand better now your preference for being cautious with ripping. But in order to get a sample of what had happened with a disc I ripped to .mp3 just yesterday, after setting CDex back to its default on the fly mode, I stuck that CD into the drive again, launched CDex and used the Jaws cursor to read the full length of the information beside each track. And every track of the 16 said Okay at the end of the line (I know it isn't a line, but that's how I'm perceiving the layout with Jaws). So that one went okay, for instance. and when I used to rip on the fly before taking the precaution you recommended, I never produced .mp3 tracks with any pops or clicks or other audible faults. On the other hand, maybe you can explain this: As I listen to Jaws read the info that tracks the ripping process, after it reaches 100 per cent of a track, I always hear, as the last utterance before I hear 5 per cent as the ripping of the next track gets underway, jitter. It says this every track, at the end of ripping it. I've always wondered what that meant, but now that you say it indicates a flaw in the disc or maybe in the recording process, I don't get it. My ripping turns out faultless, as I've said. So why am I hearingjitter reported at the end of each track while ripping it? I have one more question, this time about burning as opposed to ripping. You wrote: With regards to burning on the fly, well, the same applies in terms of the possible impact on the final product but there is another danger here. If you're burning on the fly, again you're taking a direct data stream from your CD-ROM and passing it straight to your rewriter. If there is a read error on the source CD and you're burning, the burn could actually fail and
Re: Kevin: On the fly, another question
No Joel. Once an image is created it's not going to be able to go back and clean up any imperfections. My point is that the creation of the image itself allows the ripper to separate the processes. If you're ripping on the fly you won't get an image file at all because the encoding is being done on the data stream as it leaves the CD-ROM. You really only need ask yourself a very simple question as to whether you want to use on the fly or not. Do you think that developers put this flag in just to slow you down when ripping or burning? The developer obviously wants their program to rip and burn at the maximum speed and quality so why would they build in a feature who's only purpose would be to slow you down? It's pretty obvious I think that the trade off is that you forgo some quality for speed and so it's really a personal choice. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 6:17 PM Subject: Re: Kevin: On the fly, another question Kevin, You mean that when you have flaws on an audio CD, once they get written to an image file on disc, the encoding process is less likely to pick up the flaws, somehow, as it creates the compressed file? appy- Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 10:05 AM Subject: Re: Kevin: On the fly, another question Hi Daniel. It's not that flaws at source can be fixed just because you've unchecked the on the fly checkbox. If there are flaws on the CD then they will cause issues whether you rip on the fly or not. The point I'm not making very well is that by breaking down a complex process involving the extraction and conversion of data from a spinning disc, there are less chances of issues arising if the process is instead broken down into a number of discreet steps. Specifically, separating the process of reading the disc to extract all audio information before any conversion to MP3 is done using an encoder that is applying complex algorithms to the data to assess what it thinks can be disregarded and what it thinks needs to be retained to fulfil high quality sound reproduction. Hope that's clearer. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 5:26 PM Subject: Re: Kevin: On the fly, another question kevin, I don't quite understand. If you aren't offered the opportunity to correct an error yourself, then are you implying that somehow, during this two step process, errors from a damanged or flawed CD nonetheless do get corrected for before they're written to .mp3 from the image? Only without your intercession? Is that it? Otherwise,I don't understand how the two-step process ensures that flaws in the audio CD source don't get written to .mp3. Is my question clearer now? Thanks. elps m isk e3tween - Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 8:40 AM Subject: Re: Kevin: On the fly, another question No, it won't detect potential errors and allow you to stop, continue or fix in situ. By creating the image you are breaking down the tasks associated with ripping so that you extract in one step to your hard drive and then convert from there. When on the fly you extract and convert in a single step. It is for this reason alone that you are likely to have less risk of imperfections when ripping to an image first. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC-Audio Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 4:31 PM Subject: Kevin: On the fly, another question Kevin, Let's say I use the method of ripping that involves writing a file or image to disk and then ripping from that, the method you prefer for its prudence. Okay. So what if a CD I'm ripping tracks from turns out to have the kinds of flaws that elicit this jitter error report and mean that you'll wind up with a messed-up .mp3 copy? In what way does this method actually provide protection? Does it stop the process at some point, notify you that there's a flaw, and offer the option to correct it by clicking on something? Or if not that, what? Thanks. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.1.0 - Release Date: 5/27/2005 ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL
Re: Kevin: On the fly, another question
Hi Bruce. Can't speak for that program specifically but I would think the process is standard for all rippers and encoders. As I mentioned in a previous post, it's really a trade off of quality against speed. What else would that feature be there fore? The following is an explanation from the CDEX manual, not the most clear granted but I think you'll get the gist of it. On-the-fly MP3 encoding (default value: on): When enabled, tracks are recorded directly into the desired compressed format (e.g. MP2/MP3) without having to store the entire file first to a WAV file. However, with some configuration people have heard strange clicks in the output file. Therefore, if this option is on, the file is first record as a WAV file, which can be converted to the desired output format. The WAV file is automatically deleted when the conversion has been completed. DISABLE THIS OPTION IF YOU EXPERIENCE STRANGE CLICKS IN YOUR MP3 FILES. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Bruce Toews [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 6:09 PM Subject: Re: Kevin: On the fly, another question But don't most extraction process actually separate those processes anyway? I really don't know the answer to this one, but I would have thought that a program like Easy CD-DA Extractor would first rip the file off the disk, then compress it, even if the user doesn't actually have to perform both of these steps. Am I wrong? Bruce -- Bruce Toews E-mail and MSN/Windows Messenger: [EMAIL PROTECTED] Web Site (including info on my weekly commentaries): http://www.ogts.net Info on the Best TV Show of All Time: http://www.cornergas.com On Sat, 28 May 2005, Kevin Lloyd wrote: Hi Daniel. It's not that flaws at source can be fixed just because you've unchecked the on the fly checkbox. If there are flaws on the CD then they will cause issues whether you rip on the fly or not. The point I'm not making very well is that by breaking down a complex process involving the extraction and conversion of data from a spinning disc, there are less chances of issues arising if the process is instead broken down into a number of discreet steps. Specifically, separating the process of reading the disc to extract all audio information before any conversion to MP3 is done using an encoder that is applying complex algorithms to the data to assess what it thinks can be disregarded and what it thinks needs to be retained to fulfil high quality sound reproduction. Hope that's clearer. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 5:26 PM Subject: Re: Kevin: On the fly, another question kevin, I don't quite understand. If you aren't offered the opportunity to correct an error yourself, then are you implying that somehow, during this two step process, errors from a damanged or flawed CD nonetheless do get corrected for before they're written to .mp3 from the image? Only without your intercession? Is that it? Otherwise,I don't understand how the two-step process ensures that flaws in the audio CD source don't get written to .mp3. Is my question clearer now? Thanks. elps m isk e3tween - Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 8:40 AM Subject: Re: Kevin: On the fly, another question No, it won't detect potential errors and allow you to stop, continue or fix in situ. By creating the image you are breaking down the tasks associated with ripping so that you extract in one step to your hard drive and then convert from there. When on the fly you extract and convert in a single step. It is for this reason alone that you are likely to have less risk of imperfections when ripping to an image first. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC-Audio Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 4:31 PM Subject: Kevin: On the fly, another question Kevin, Let's say I use the method of ripping that involves writing a file or image to disk and then ripping from that, the method you prefer for its prudence. Okay. So what if a CD I'm ripping tracks from turns out to have the kinds of flaws that elicit this jitter error report and mean that you'll wind up with a messed-up .mp3 copy? In what way does this method actually provide protection? Does it stop the process at some point, notify you that there's a flaw, and offer the option to correct it by clicking on something? Or if not that, what? Thanks. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version:
Re: Kevin: On the fly, another question
Ah, got it. I prefer doing my compressing in Gold Wave anyway, so I can maximize teh volume or whatever else I want to do. Bruce -- Bruce Toews E-mail and MSN/Windows Messenger: [EMAIL PROTECTED] Web Site (including info on my weekly commentaries): http://www.ogts.net Info on the Best TV Show of All Time: http://www.cornergas.com On Sat, 28 May 2005, Kevin Lloyd wrote: Hi Bruce. Can't speak for that program specifically but I would think the process is standard for all rippers and encoders. As I mentioned in a previous post, it's really a trade off of quality against speed. What else would that feature be there fore? The following is an explanation from the CDEX manual, not the most clear granted but I think you'll get the gist of it. On-the-fly MP3 encoding (default value: on): When enabled, tracks are recorded directly into the desired compressed format (e.g. MP2/MP3) without having to store the entire file first to a WAV file. However, with some configuration people have heard strange clicks in the output file. Therefore, if this option is on, the file is first record as a WAV file, which can be converted to the desired output format. The WAV file is automatically deleted when the conversion has been completed. DISABLE THIS OPTION IF YOU EXPERIENCE STRANGE CLICKS IN YOUR MP3 FILES. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Bruce Toews [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 6:09 PM Subject: Re: Kevin: On the fly, another question But don't most extraction process actually separate those processes anyway? I really don't know the answer to this one, but I would have thought that a program like Easy CD-DA Extractor would first rip the file off the disk, then compress it, even if the user doesn't actually have to perform both of these steps. Am I wrong? Bruce -- Bruce Toews E-mail and MSN/Windows Messenger: [EMAIL PROTECTED] Web Site (including info on my weekly commentaries): http://www.ogts.net Info on the Best TV Show of All Time: http://www.cornergas.com On Sat, 28 May 2005, Kevin Lloyd wrote: Hi Daniel. It's not that flaws at source can be fixed just because you've unchecked the on the fly checkbox. If there are flaws on the CD then they will cause issues whether you rip on the fly or not. The point I'm not making very well is that by breaking down a complex process involving the extraction and conversion of data from a spinning disc, there are less chances of issues arising if the process is instead broken down into a number of discreet steps. Specifically, separating the process of reading the disc to extract all audio information before any conversion to MP3 is done using an encoder that is applying complex algorithms to the data to assess what it thinks can be disregarded and what it thinks needs to be retained to fulfil high quality sound reproduction. Hope that's clearer. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 5:26 PM Subject: Re: Kevin: On the fly, another question kevin, I don't quite understand. If you aren't offered the opportunity to correct an error yourself, then are you implying that somehow, during this two step process, errors from a damanged or flawed CD nonetheless do get corrected for before they're written to .mp3 from the image? Only without your intercession? Is that it? Otherwise,I don't understand how the two-step process ensures that flaws in the audio CD source don't get written to .mp3. Is my question clearer now? Thanks. elps m isk e3tween - Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 8:40 AM Subject: Re: Kevin: On the fly, another question No, it won't detect potential errors and allow you to stop, continue or fix in situ. By creating the image you are breaking down the tasks associated with ripping so that you extract in one step to your hard drive and then convert from there. When on the fly you extract and convert in a single step. It is for this reason alone that you are likely to have less risk of imperfections when ripping to an image first. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC-Audio Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 4:31 PM Subject: Kevin: On the fly, another question Kevin, Let's say I use the method of ripping that involves writing a file or image to disk and then ripping from that, the method you prefer for its prudence. Okay. So what if a CD I'm ripping tracks from turns out to have the kinds of flaws that elicit this jitter error report and mean that you'll wind up with a messed-up .mp3 copy? In what way does this method actually provide protection? Does
mp3 direct cut
Who is the official maker of mp3 direct cut program? Web site please. What is the most addessible mp3 direct cut version? Any help is appreciated. If the lame.dll file is already on my hard drive do I still need to place this file or a copy of it to the program's plugins\ folder. Please explain this. Thank you ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED]
Re: On the fly ripping and burning
Hi Kevin. Well since you posted about on the fly, I have it unchecked. I remember you saying that this method controls pops and crackles, but I find that I still have some noise. This is probably because some of the tracks were recorded from vinal. Now I do use the Soundforge Noise Reduction to try and eliminate those, and it works. I did notice with the noise-reduction plug-in, that when I play the file in Winamp, the file size is smaller. The bit rate is lower. Like has been stated, there are trade-offs that have to be made, with regards to file size and quality. Maybe some songs can do with a little tweaking. - Original Message - From: Kevin Lloyd [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 9:52 AM Subject: Re: On the fly ripping and burning Hi Daniel. I think it was myself that you'd probably referred to below as recommending that one should rip with on the fly unchecked. You've asked a few questions below so I'll try to answer them as best I can. Firstly, the speed at which you rip can be changed in the CDEX settings so it may be worth trying this first before you decide to do anything differently. The thread priority setting has 5 or 6 values that vary from below normal to fastest. There's a balance to be had here as if you rip at the fastest speed you may find that you can't use your computer effectively while ripping because it's taken so much resource. With regards to using on the fly in general, this really refers to processing a direct data stream right from your CD-ROM rather than extracting data first and then processing it when it's been safely read and stored on your hard drive. When ripping on the fly, it is possible that you will find slight imperfections with the finished product usually manifesting itself in pops and crackles. This is generally as a result of jitter but could be just down to the process of extractign and converting a direct data stream. If you've used CDEX you may have seen on the list of tracks that there's a right hand column called status. This can have 3 different values: dash meaning that the track has not yet been ripped. OK meaning that the track was ripped with no jitter errors. X followed by a number meaning that there were a number of jitter errors found; the number representing the number of errors in the track in total. These values are retained by CDEX so even if you haven't noticed them before, you can put in a CD that you've ripped previously and see the status results. The reason why I mention this is that I too take great care of my CD's but I have been surprised by jitter errors when ripping my CD's. Some I've been able to remove by cleaning the CD with a special CD cleaning cloth but others I've been unable to remove. The number of jitter errors generally dictate how noticeable the errors will be to you. A standalone CD player usually is far better built than a CD-ROM and in general have far better error correction capabilities. So, if you put your CD in your standard player you might not notice jitter errors because of this error correction and the quality of the transport build. With regards to burning on the fly, well, the same applies in terms of the possible impact on the final product but there is another danger here. If you're burning on the fly, again you're taking a direct data stream from your CD-ROM and passing it straight to your rewriter. If there is a read error on the source CD and you're burning, the burn could actually fail and then you are going to end up with a CD that cannot be played and is good only for using as a coaster or tying together with other ruined CD's and Robbie Williams CD's to scare birds from your vegetable plot in the garden. Like most things, personal preferences dictate whether you will use on the fly or not but I see it as a guarantee that is worth a little extra time on that rip or burn. Hope this helps. Regards. Kevin E-mail: [EMAIL PROTECTED] - Original Message - From: Yardbird [EMAIL PROTECTED] To: PC-Audio Pc-audio@pc-audio.org Sent: Friday, May 27, 2005 11:36 PM Subject: On the fly ripping and burning Lately, I've been downloading and exploring a number of programs for ripping, burning and copying music. And one thing I've noticed while reading the documentation for these applications. That's that they don't all agree with, who was it, I think Keith, who in the course of describing how to best configure the ripping settings in CDex, said that on the fly ripping was to be avoided in favor of the slower method of writing a file (or image, or whatever is right to say; I've seen it put both ways now). as I understand it, this is so that if there's some sort of flaw in the material being ripped, then the program will catch it and somehow rectify the error prior to writing the track to disk. I think that's the idea, right? Well, in at least one of the programs I've
Skype and Total Recorder 5.2 pro
I've installed the latest version of Total Recorder and now Skype doesn't load correctly. skype loads to the point of saying sk splash and showing a copyright message. I've installed Total recorder on tow machines and get the same error. I've tried uninstalling and reinstalling Skype but it won't load. The JAWS scripts are loading however. Has anyone experienced the same problem. regards Paul ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED]
recording Streams from the latest Winamp
Hi. After it was reported here that the latest version of Winamp blocked recordings when made from a Winamp generated stream, I decided to give it a try for myself. I recorded using the latest Winamp with Replay Radio, as I prefer Replay to Total Recorder for that purpose. For what it's worth to anyone here on the list, my recording played back just as it should have. No tones, no hits, no errors. Peace, Larry - Original Message - From: bt internet [EMAIL PROTECTED] To: PC audio discussion list. Pc-audio@pc-audio.org Sent: Saturday, May 28, 2005 7:20 PM Subject: Skype and Total Recorder 5.2 pro I've installed the latest version of Total Recorder and now Skype doesn't load correctly. skype loads to the point of saying sk splash and showing a copyright message. I've installed Total recorder on tow machines and get the same error. I've tried uninstalling and reinstalling Skype but it won't load. The JAWS scripts are loading however. Has anyone experienced the same problem. regards Paul ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED] ___ PC-Audio List Help, Guidelines, Archives and more... http://www.pc-audio.org To unsubscribe from this list, send a blank email to: [EMAIL PROTECTED]
