![vinylstudio error 32 thr vinylstudio error 32 thr](https://docs.microsoft.com/th-th/office/troubleshoot/client/excel/media/memory-usage-32-bit-edition-of-excel/error-message.jpg)
From this exchange of emails, we have raised some interesting points and issues:.
![vinylstudio error 32 thr vinylstudio error 32 thr](https://content.spiceworksstatic.com/service.community/p/post_attachments/0000180856/5be1528c/attached_file/error.jpg)
Vinylstudio error 32 thr driver#
My SW bud was the SW driver and USB reliability guru.
![vinylstudio error 32 thr vinylstudio error 32 thr](https://biokunststoffe.org/images/654931.jpg)
My work at Texas Instruments involved design and test of USB interfaces. The SW engineer I approached is a colleague that I worked with at Texas Instruments in Aalborg, Denmark. Regarding the USB issue I have sought a second technical opinion. It would help if I could make the issue repeatable but this one is not so easy and, as I said, I have had to stop using Audacity for ripping. S/PDIF and PCI should be extremely robust and reliable.Nevertheless we have an issue and I think I have covered my opinion as to the root cause in one of the previous paragraphs. Time permitting I can try ripping with audio cache enabled/disabled but I suspect this quite unlikely due to time What is startlingly unusual about your problem is that you are not using USB. I could not have missed this distortion hence the reason for my suggesting more than one error. Believe it or not the end of the cut is a drum rap and I was playing air drums, much to the missus' amusement. only sometimes, maybe once or twice a day, do I have the sibilance so this one will not be so easy for me to answer however, having heard the sibilance when in monitor mode I think we can rule out the error being disc writes however, I am still convinced the cut I up-loaded is from a hard drive write data corruption so we could be looking for more than one error. Also, I do not think this error is repeatable, i.e. I could make an educated guess and state the audio cache would not make any difference. Is this problem occurring when you are recording to RAM, or does it also occur when recording direct to disk?As you know, I have continuous, and repeatable, recording freezes whenever I write to RAM so my rip set-up has audio cache off therefore I cannot answer your question. It seems to me Audacity is generating the -55dB noise, in my set-up as stated by Your case is most puzzling. When I play a recording of an LP, captured using Audacity, in Vinyl Studio I see very similar meter levels with both sets of meters so I have no reason to doubt the accuracy of the VS meters. Originally I put this down to my pre-amp not being as good as I had thought (jeez, and ex HW engineer and I blame a very good pre-amp) however, I have run the same test with Vinyl Studio and I do not see anything on the VS meters which go to -100dB (and I do not hear the sibilance either). In Audacity, I see the meters hovering around the -55dB mark with no input, no input means no album playing on the turntable and not an open circuit. Just like Sombunya I am using the meters to monitor the audio amplitude. I think you are far to quick to blame USB whereas I am now pretty certain there is an underlying problem in Audacity. Maybe we have a real problem with the record process in Audacity v2xx. Without stopping the record I stopped the recording process, went to "edit" and undid the recording, hit the record button and it started recording again, with perfect sound.This is EXACTLY the same comment I have just posted re stopping and re-starting the record. My best description would be it sounded like loose connectors on my cartridge, although I've never really experienced that particular problem. Anyway, I was digitizing a vinyl record and I noticed about 3/4 of the way through the record the sound was terrible.