I use the T Racks Vintage EQ module (Pultec)  as an fx on nearly everything I do (I play acoustic guitar mainly). It's causing X2 to crash though, but only at the end of the project, or if I stop it during play. I just wondered if anyone out there has any instructions or ideas on how to cure this, so I can enjoy using X2. A friend has suggested altering the Aud.ini file, would that help?
Thanks for looking
Martyn

what is it exactly that your frien is suggesting you should alter in the aud.ini file?

Is it the only fx on the track?
Can I assume that you had X1 before this and it wasn't happening?

you haven't exactly given us a lot of info to go on.

Are you on Win 7? 32 or 64 bit?
are you on SONAR 32 or 64 bit?
What sort of PC specs do you have?

When you say crash please describe what you mean? A white screen, blue screen SONAR locks up? what exactly.
Is the transoort active when it "crashes" or after it stops at the end of the project?
There's a lot to know.

Martyn UK


I use the T Racks Vintage EQ module (Pultec)  as an fx on nearly everything I do (I play acoustic guitar mainly). It's causing X2 to crash though, but only at the end of the project, or if I stop it during play. I just wondered if anyone out there has any instructions or ideas on how to cure this, so I can enjoy using X2. A friend has suggested altering the Aud.ini file, would that help?
Thanks for looking
Martyn

When you say "T Racks Vintage EQ module (Pultec)", I assume you mean the Prog EQ 1A.  I just tried a simple test with this on my system, and I did not have any problems with it.  Perhaps there is something system-specific.  I am using the x64 version of SONAR X2 Producer on Win7Pro x64.  The version of T-RackS and this plug-in shows 3.5 (1E31).  It is the 64-bit version of the plug-in (as opposed to the 32-bit version being used via BitBridge or jBridge).
 
If you are running SONAR x64 and the 32-bit version of T-RackS (e.g. from 3.0 or 3.5), I'd suggest updating T-RackS to the latest stuff and using the 64-bit version as it's conceivable there could be an issue in the bridging. 
 
Rick

thanks for your reply, I am using W7 Home Premium 32 bit, Sonar 32 bit, The Pultec worked great on X1. Now in X2, if I press the space bar during a project, or allow it to run to the end and stop, I get a white screen and a dialogue stating the programme has stopped working. If i switch off the Pultec whilst playing the prject, I can press the space bar to stop, or allow the project to run to the end without any problems. Im sorry about the lack of technical details, I am not very technical minded - I have used Cakewalk since Pro Audio 9 for recording my songs and always update when a new version becomes available. My computer is quad core.  A friend suggested altering the 'buffer' in the Aud.ini file - but I dont really understand that. I have been advised to go 64 bit though before.  I considered switching off the Pultec at the end of the project using automation, but that isnt available in the editing list. Thanks for your time
Martyn

It sounds like the issue may be specific to 32-bit.  One thing I can think of on the aud.ini change suggestion is that, if I remember correctly, some of the T-RackS plug-ins, including this one, have a fair bit of latency (I seem to remember a few latency compensation issues a long time back when I was using these more extensively, possibly when I was still on the 32-bit version of SONAR 8).  Perhaps the suggestion your friend made relates to some tradeoff between system timing considerations and giving the plug-in enough time to "do its thing".  I don't see a "buffers" parameter in AUD.INI, but I do see an ExtraPluginBufs, which the manual describes as follows:

    It instructs SONAR to set aside extra audio data buffers, to accommodate plug-ins which do large amount of internal buffering and therefore "keep" data buffers to themselves. Recommended maximum setting of 64 or 128.

Perhaps this is what was intended?  Mine is set to 0, but I'm running 64-bit and my computer is likely much slower than yours (I'm on a Core 2 Duo E6600), and I believe this sort of stuff is specifically for tuning things that may be affected by system performance.   This is totally wild speculation, but perhaps some improvements in the efficiency of SONAR's audio engine from X1 to X2 resulted in your system's just being "too fast" for the internal buffering this plug-in needs to do to keep up.  Can't hurt to try it out, in any case, since the worst that could happen is it makes things worse and then you have to change it back and you're back where you started.

Good luck.

Rick

I run a chain of 4 T-Racks3 64 bit plugs in my mastering chain, and it hasn't caused a problem in x2.