Update:
I tried read ahead optimization set to almost full, instead of off.
No change - still got the crackles, even on a nearly empty edit, when I mouse over any 'resize' track width/height, filter width/height, or when automation curves are in a transition period.
I will try to do the PCI latency thing to re-set the video card latency, if I can.
-Scott
Willadding more system memory fix this in T?
-
- KVRAF
- Topic Starter
- 4908 posts since 10 Aug, 2004 from Colorado Springs
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Also, just switching around the cards (physically) inside your computer sometimes helps. If it's an AGP card, you don't have much choice, but move the sound card to a different PCI slot to see if that helps.
Greg
Greg
-
- KVRAF
- 5851 posts since 9 Jul, 2002 from Helsinki
My friend's primed audio machine got introduced to crackly life after he installed a cordless IR mouse.or even when I move the mouse.
-
- KVRAF
- Topic Starter
- 4908 posts since 10 Aug, 2004 from Colorado Springs
Well, it's an AGP card - so that shoots a couple of things:Lunch Money wrote:Also, just switching around the cards (physically) inside your computer sometimes helps. If it's an AGP card, you don't have much choice, but move the sound card to a different PCI slot to see if that helps.
Greg
1. The whole PCI latency possibility seems moot; though I did download and install the powerstrip application mentioned in another post (this app did not have a way to change PCI latency, by the way).
2. I moved the SBLive to a different slot - same problem.
3. Someone else mentioned disabling CD audio output - done, same problem.
One thing that the powerstrip program did have was a CPU monitor that seemed to indicate many more spikes than the CPU gauge built into T. It was hitting 100% at the times when I get the crackles, whereas the meter in T didn't show more than 50-60%. Any clues what this discrepancy might be?
-Scott
-
- KVRian
- 779 posts since 3 Apr, 2003 from UK
Actually having an AGP doesn't make it moot - although it is essentially a separate bus, it does still interact with the PCI bus and the latencies of an AGP card can affect PCI cards and vice versa.rockstar_not wrote:Well, it's an AGP card - so that shoots a couple of things:
1. The whole PCI latency possibility seems moot; though I did download and install the powerstrip application mentioned in another post (this app did not have a way to change PCI latency, by the way).
I did discover a program for 98 which will allow you to set the latency of your AGP card - humour me and try it!
http://www.overclockers.com/articles529/
-
- KVRAF
- Topic Starter
- 4908 posts since 10 Aug, 2004 from Colorado Springs
OK Rich, I appreciate your tenacity. I've downloaded it and will be trying it tonight.I did discover a program for 98 which will allow you to set the latency of your AGP card - humour me and try it!
http://www.overclockers.com/articles529/
-Scott
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
What I was referring to is unrelated to latency-- it's more about resource-sharing. Switch the card to another slot. 
Greg
Greg
-
- KVRAF
- Topic Starter
- 4908 posts since 10 Aug, 2004 from Colorado Springs
Greg,Lunch Money wrote:What I was referring to is unrelated to latency-- it's more about resource-sharing. Switch the card to another slot.
Greg
I tried this as well (I spent about 2 hours trying everything in the list I put above and still ended up with crackles galore.
-Scott
-
- KVRer
- 20 posts since 14 Jun, 2004 from Bristol, UK
Tried different drivers for your sound/graphics card and mobo? Get the latest ones, and if that doesn't help, try older ones.
That's fixed my problems occasionally. Though my latest audio bug (which didn't affect Tracktion, just everything else) was only solved by a complete Windows reinstall.
Blame Windows, then. (I'm building myself a Linux system, though I doubt Rosegarden will completely replace Tracktion.)
That's fixed my problems occasionally. Though my latest audio bug (which didn't affect Tracktion, just everything else) was only solved by a complete Windows reinstall.
Blame Windows, then. (I'm building myself a Linux system, though I doubt Rosegarden will completely replace Tracktion.)
-
- KVRian
- 779 posts since 3 Apr, 2003 from UK
rockstar_not wrote:OK Rich, I appreciate your tenacity. I've downloaded it and will be trying it tonight.I did discover a program for 98 which will allow you to set the latency of your AGP card - humour me and try it!
http://www.overclockers.com/articles529/
-Scott
I can get a bit obsessive! It's just that your problem sounds very typical of a PCI latency issue.-
- KVRAF
- Topic Starter
- 4908 posts since 10 Aug, 2004 from Colorado Springs
OK,
Powerstrip DOES let you change the AGP latency. My first time through the program didn't point me to it. I only found it through some right clicking.
Anyhow, my AGP ATI Rage Fury Pro was set to 248 for latency. I used Powerstrip to bring this all the way down to 64 and then 48, and I still had the crackling issue.
So, then I thought, perhaps the ASIO latency is just too short for my system. I had it set to the minimum value of 5.33 mS, which seemed to work fine at my first uses of Tracktion and worked great for the example projects that come loaded with Tracktion.
I tried the next higher latency setting, 10.6 mS- and nearly every crackle is now gone - even with unfreezing almost every track in the edit.
So, my question now to other Tracktioneers: is 10mS a reasonable latency setting? Would I put this offset into each audio track in the 'time adjust' (actually would it be -10 mS) field?
Sorry, I'm just learning, and the manual doesn't have too much description on this.
-Scott
Powerstrip DOES let you change the AGP latency. My first time through the program didn't point me to it. I only found it through some right clicking.
Anyhow, my AGP ATI Rage Fury Pro was set to 248 for latency. I used Powerstrip to bring this all the way down to 64 and then 48, and I still had the crackling issue.
So, then I thought, perhaps the ASIO latency is just too short for my system. I had it set to the minimum value of 5.33 mS, which seemed to work fine at my first uses of Tracktion and worked great for the example projects that come loaded with Tracktion.
I tried the next higher latency setting, 10.6 mS- and nearly every crackle is now gone - even with unfreezing almost every track in the edit.
So, my question now to other Tracktioneers: is 10mS a reasonable latency setting? Would I put this offset into each audio track in the 'time adjust' (actually would it be -10 mS) field?
Sorry, I'm just learning, and the manual doesn't have too much description on this.
-Scott
-
- KVRAF
- 2009 posts since 9 Apr, 2003 from Cornwall, UK
10ms is alright, not great but you can get away with recording at this setting. I try to record at 3ms. If the system can't handle it I try muting tracks till the cpu load is less, then try again.
If your not recording latency is irrelavent, choose whatever setting doesn't give you crackles.
If your not recording latency is irrelavent, choose whatever setting doesn't give you crackles.
-
- KVRian
- 779 posts since 3 Apr, 2003 from UK
I concur, 10ms is okay. It's the equivalent of playing an electric guitar standing several feet away from the amp.tingle wrote:10ms is alright, not great but you can get away with recording at this setting. I try to record at 3ms. If the system can't handle it I try muting tracks till the cpu load is less, then try again.