Bassdude, yep, I tried it with wavelab and still got the same problem. The 24bit ALT setting minimised the issue..but even so it still occurred but less severely. Still no where near good enough for proffesional application.
I've got a busy day, but I will get a "distortion" sample up for you later on.
Greetz from, can you believe it, SUNNY, Uk.
Wave Destination Module problems
Bassdude, heres an example of the noise...this is just a straightforward recording at 24bit 44.1. No signal input, just hit record in soundforge and this is what comes back! Right side LED clips whilst recording whereas left stays low. Standard routing from scope, ie, mix outs to 24bit wave dest and 24bit wave source routed to a couple of input channels on the mixer.
Let me know your thoughts.
Let me know your thoughts.
Hi Gary, thats exactly what I thought originally, see my first post on this subject.
Scope is master....no slaves attached, though I feel a bit like a slave to the scope right now
The noise mp3 is also quite revealing in that it simply sounds like white noise..but 1 channel only??? How weird can it get.[/code]
Scope is master....no slaves attached, though I feel a bit like a slave to the scope right now
The noise mp3 is also quite revealing in that it simply sounds like white noise..but 1 channel only??? How weird can it get.[/code]Hi Gary, Pwr supply is fine, and card is new. The problem is identical to Pulsar 1 card which Ralph kindly replaced with this scope pro.... Problem is same regardless of machine, pci slot, intel/amd etc etc, check all my posts for the whole picture. Its possible I shorted a contact or damaged the slot, but I have to say its unlikely in this instance, though I may have been an ass and missed something really obvious Someone else on this thread reported the exact same problem when they upgraded kit to dual core, I'm starting to think that maybe the good folks at Soniccore may have missed something in new mb/chip architecture which is as yet unaccounted for?? Who knows, frankly, I'm just about out of ideas. I take it your systems don't exhibit this problem which in turn makes me inclined to agree that it is the card. But 2 cards, a pulsar 1 and then a scope pro with exactly the same problem regardless of machine its fitted in seems more than coincidental to me. My Machine consists of the following:
Asus P5WDH Deluxe i975X socket 775, Pentium D805 2.66GHz, 2GB Hyperx Memory, Sapphire Radeon X1900XT, Hiper type R 580W pwr supp, Western Digital 250GB 7200rpm, Zalman CNPS9700 LED cooler, Thermaltake case with wind tunnel fans (average chip temp upper 20's to lower 30's max) If you can see any issues please let me know.
Regards from an amazingly still sunny UK.
Someone else on this thread reported the exact same problem when they upgraded kit to dual core, I'm starting to think that maybe the good folks at Soniccore may have missed something in new mb/chip architecture which is as yet unaccounted for?? Who knows, frankly, I'm just about out of ideas. I take it your systems don't exhibit this problem which in turn makes me inclined to agree that it is the card. But 2 cards, a pulsar 1 and then a scope pro with exactly the same problem regardless of machine its fitted in seems more than coincidental to me. My Machine consists of the following:Asus P5WDH Deluxe i975X socket 775, Pentium D805 2.66GHz, 2GB Hyperx Memory, Sapphire Radeon X1900XT, Hiper type R 580W pwr supp, Western Digital 250GB 7200rpm, Zalman CNPS9700 LED cooler, Thermaltake case with wind tunnel fans
(average chip temp upper 20's to lower 30's max) If you can see any issues please let me know.Regards from an amazingly still sunny UK.
That actually does sound like loss of clock, especially the burst of white noise in the former clip.
I've had issues with the wav driver myself in the past and it was usually resolved by increasing the 'output preload' slider buried in the Creamware properties in the device manager or sounds & audio devices hardware tab. However what I heard with that particular issue was obviously buffer underrun issues where the audio would simply 'glitch' from one value to the next as a chuck of data went missing.
In this case the former is outright mismatched clock, and the later sounds like a two clocks running in the same samplerate but without sync, where values occasionally 'drift' between sample frames causing clicks measured in a sample or two but with the overall tone intact across time.
I've had issues with the wav driver myself in the past and it was usually resolved by increasing the 'output preload' slider buried in the Creamware properties in the device manager or sounds & audio devices hardware tab. However what I heard with that particular issue was obviously buffer underrun issues where the audio would simply 'glitch' from one value to the next as a chuck of data went missing.
In this case the former is outright mismatched clock, and the later sounds like a two clocks running in the same samplerate but without sync, where values occasionally 'drift' between sample frames causing clicks measured in a sample or two but with the overall tone intact across time.
Thanks Valis, interesting post.
So how would u go about fixing it ?
I ve tried increasing the output preload , no change....
And I cant' understand how there can be a loss of sync between Scope and Soundforge...can u elaborate further. It would be much appreciated.
Greetz from a more typically overcast UK
So how would u go about fixing it ?
I ve tried increasing the output preload , no change....
And I cant' understand how there can be a loss of sync between Scope and Soundforge...can u elaborate further. It would be much appreciated.
Greetz from a more typically overcast UK
don't know about what the sync issue could be, but there are buffer settings in wavelab(edit:excuse me, soundforge) as well. playing with those in a systematic way should fix the clicks...
Last edited by garyb on Fri Sep 14, 2007 6:04 pm, edited 1 time in total.
Valis, its soundforge version 5, sorry but what do you mean "what driver am I using?" Could u please elaborate on your point about digital sync from your last post..it sounds interesting but I was not aware that there was any way to alter sync between forge and scope..at least I cant find any settings that relate to it and have never heard it mentioned before.
Bassdude, no I havent checked in the other system with the scope pro. And no I didnt do a full os re install. I did however completely remove all references to the previous Scope software (4.0) and install 4.5 with mix n master pack.
I would prefer to not move this new card around any more than is essential......but if all else fails I may just try it.
Whats your theory regarding the full reinstall of XP? I have regcleaned the system, and there were defintely no drivers, dlls, registry entries or other associated bits form the old install left.
Bassdude, no I havent checked in the other system with the scope pro. And no I didnt do a full os re install. I did however completely remove all references to the previous Scope software (4.0) and install 4.5 with mix n master pack.
I would prefer to not move this new card around any more than is essential......but if all else fails I may just try it.
Whats your theory regarding the full reinstall of XP? I have regcleaned the system, and there were defintely no drivers, dlls, registry entries or other associated bits form the old install left.
My theory is possible corrupted system files. And it's what I would do. While registry cleaners do some of the work, the only real way to cleanup the registry is to re-install.
I would download a free disk imaging utility like Driveimage XML, image what you have currently got, wipe the c: drive and then re-install and configure the OS, make a disk image of that, then install the scope pro and soundforge (or in my case CoolEditPro as I know it works) and nothing else. If that doesn't work, then I would do the same thing on the other machine as another test. Time consuming yes, but when troubleshooting, I always try to work with a clean slate. Using a disk image tool just makes re-installing the OS etc a whole lot quicker and less painful.
I would download a free disk imaging utility like Driveimage XML, image what you have currently got, wipe the c: drive and then re-install and configure the OS, make a disk image of that, then install the scope pro and soundforge (or in my case CoolEditPro as I know it works) and nothing else. If that doesn't work, then I would do the same thing on the other machine as another test. Time consuming yes, but when troubleshooting, I always try to work with a clean slate. Using a disk image tool just makes re-installing the OS etc a whole lot quicker and less painful.
Stuart.