From T4 to T6 Glitches agogo
-
- KVRist
- 109 posts since 10 Oct, 2005 from St. Louis, MO USA
I'm finding that the 64-bit version runs without glitches and uses less CPU than the 32-bit running the same (32-bit version) plug-ins. Anyone else experiencing this?
MacBook Pro M3, 16GB RAM | UAD Apollo Solo| Tracktion Waveform 14 Pro/Cockos Reaper 7/Ableton Live 12 Standard/Presonus Studio One 7 Pro | A multitude of paid-for and free VST plugs/samples
-
- KVRist
- 238 posts since 24 Sep, 2005
Good points Peter, thanks for sharing.
Your RAM observation is completely relevant , in that before I expanded my laptop's RAM from 2 GB to 4 GB, T4-6 was unusable due to copious audio dropouts and glitches. The expansion was nothing short of miraculous when combined with my setting Windows 7 to prioritize backgrounds tasks. I'd forgotten about that setting, which is hugely important!
The strange thing with my 2 GB configuration is that I always had 1 GB or so open when running T, yet the disk I/O / caching load was way too extreme, thus the poor audio performance. Now with the 4 GB, I have at least 2.5 GB available, thus the glitches should not be RAM related.
I have news to report on the CPU issue I described, which is that I found a service that I'd not disabled which causes T to use much more CPU than called for. It's a cloud backup app named Cubby. Simply disabling it brought my T edit's CPU usage down from and average of 80% to just 25%. This helped with the CPU thrashing I described, in that it takes longer to show up. I think there's still a plugin related issue lurking for his particular problem, yet have not been able to nail that down as of yet.
My main issue now is that I get audio glitches when I first play the edit back, which generally clear up once the edit has played through once. I thought this was a disk I/O load issue, yet using the Windows Resource Monitor reveals little to no disk activity during this glitch phase. Strangeness.
Cjay - interesting that you mention the 32 vs 64-bit observation, in that David of the Tracktion development team just asked me if I'd tried T on a 64-bit system. I hope this insight leads to resolution for us in the 32-bit crowd!
P
Your RAM observation is completely relevant , in that before I expanded my laptop's RAM from 2 GB to 4 GB, T4-6 was unusable due to copious audio dropouts and glitches. The expansion was nothing short of miraculous when combined with my setting Windows 7 to prioritize backgrounds tasks. I'd forgotten about that setting, which is hugely important!
The strange thing with my 2 GB configuration is that I always had 1 GB or so open when running T, yet the disk I/O / caching load was way too extreme, thus the poor audio performance. Now with the 4 GB, I have at least 2.5 GB available, thus the glitches should not be RAM related.
I have news to report on the CPU issue I described, which is that I found a service that I'd not disabled which causes T to use much more CPU than called for. It's a cloud backup app named Cubby. Simply disabling it brought my T edit's CPU usage down from and average of 80% to just 25%. This helped with the CPU thrashing I described, in that it takes longer to show up. I think there's still a plugin related issue lurking for his particular problem, yet have not been able to nail that down as of yet.
My main issue now is that I get audio glitches when I first play the edit back, which generally clear up once the edit has played through once. I thought this was a disk I/O load issue, yet using the Windows Resource Monitor reveals little to no disk activity during this glitch phase. Strangeness.
Cjay - interesting that you mention the 32 vs 64-bit observation, in that David of the Tracktion development team just asked me if I'd tried T on a 64-bit system. I hope this insight leads to resolution for us in the 32-bit crowd!
P