• SONAR
  • Dropouts and stuttering sounds with X3 only
2014/04/05 16:45:50
Raymond70
Hello forummmembers,
 
[this is about X3 Producer 32-bits]
 
yesterday bought X3 Producer, downloaded it all, including the update patches. Today installed the whole package. No problems encountered. After the initial installation processes/preferences, like setting up audio, midi, asio, Vsti's etc. I loaded an older project with only three midi-input-tracks:
1. solo violin used with VSL Solo Strings under Vienna Ensemble and loaded with Vienna Instruments Pro
2. track for harpsichord, RH
3. track for harpsichord, LH (both calling PianoTeq Harpsichord).
 
In the Audio FX, I am using Altiverb 6 (32 bits). The project played back with dropouts and stuttering sounds.
 
This didn't happen in Sonar 8.5.3. (32bits) or X1 (32bits). I didn't change anything only migrated it from the older Sonar versions to X3. I disabled Altiverb for testing purposes and now no stuttering/dropouts occur. Really strange. I have a strong idea that the stuttering/dropouts occur when the MIDI TEMPO changes. I had the same experience when using Altiverb in Overture notation. Still it is strange that the older SONAR versions had no problem with it at all. What can I do against this?
 
System: Windows 7 / 64 bits, Intel i7, 24 Gb RAM and a couple of HD's and other gear.
 
Thanks in advance,
 
 
Raymond
 
 
2014/04/05 17:04:58
Splat
Hello and welcome...
 
I suggest performing system maintenance first...
 
I assume you are already on X3E.
Please make sure you are on the latest plugin versions and then perform a VST reset and rescan and :
http://www.cakewalk.com/Support/kb/reader.aspx/2007013315
 
And make sure you are up to date with Windows update including Windows optional updates.
You may also want to check you are on the latest drivers and firmware for your interface (what is your interface?).
 
Also check Intel autoupdate:
http://www.intel.com/p/en_US/support/detect
 
Also try turning off Intel Speedstep in your BIOS.
 
Finally if you are using 32 bit Sonar you can only access 4Gb of RAM. So I ask why are you running 32 bit Sonar when you can run 64 bit Sonar and use bitbridge for your 32 bit plugins on your 64 bit OS therefore accessing all available memory (at least for Sonar)?
 
Thanks
 
Alex
2014/04/05 17:42:15
Raymond70
Using Altiverb 32 bits under a 64 bits host doesn't work. Not even with jBridge.
 
I can access max. 4 Gb, but using Vienna Ensemble 64 bits makes it possible using all RAM I have, because the RAM-allocation takes places somewhere outside the realms of the host. As an example: in Overture, which is a 32 bits program/host I can use several instances of Vienna Ensemble with a number of Vienna Instruments up to 10 Gb RAM (actual size of one of my orchestral works). When I do this in SONAR 32 bits the memory usage is far beyond the 4 Gb limit, similar to Overture.
 
I did rescan the VST plugins several times. I am on X3e. Autoupdate for Intel failed, but I will have a look at Intel speedstep in the BIOS.
 
Raymond
2014/04/05 18:32:52
jb101
Raymond70
 
I did rescan the VST plugins several times. I am on X3e. Autoupdate for Intel failed, but I will have a look at Intel speedstep in the BIOS.
 
Raymond




I, personally, would think twice (or more) before preforming this "tweak".  I do not think it is necessary, and should definitely not be performed unless you truly know what/why you are doing it.  Even then, I probably wouldn't do it.
 
What are your Playback I/O Buffer Size set to?
2014/04/06 06:23:17
Raymond70
Don't forget, it is Altiverb 6 - 32 bits (the 64 bits version for Windows is still under construction).
 
The Tweak didn't change anything, so I "enabled" it again.
I experimented with a variety of buffer settings.
I also changed from ASIO to WDM (with its own buffers at various sizes) and set it back to ASIO.
I always rescan the VST plugins, at startup a scan performs in the background.
I tried using Altiverb in X3e 64 bits, no success, not even with jBridged version for a 64-bits host.
I tried using Altiverb in X3e 32 bits, no success.
 
What happened?
I went back to
  • SONAR 8.0 - 32 bits
  • SONAR 8.5.3 - 32 bits
  • SONAR X1 - 32 bits
and in those versions Altiverb worked like sunshine.
What has changed in X3 that Altiverb doesn't work properly?
Unless one of you comes with a solution in the sense of "why didn't I think about that" I will put X3 aside waiting for "better" days.
 
Raymond
2014/04/06 07:36:25
gswitz
 
You might check your Preferences > File > Audio Data > File Bit Depths. Ensure that Record is set to 24 not 32.
2014/04/06 07:48:18
Noel Borthwick [Cakewalk]
From your description it would seem that altiverb has some performance issues. Have you tried contacting their tech support?
One thing you can try is going into preferences and resetting the audio configuration to defaults.  That will set SONAR to the factory settings for audio. Then choose your ASIO driver and retest.
Another thing to try - does VE Pro support hosting normal VST plugins? If so you could load altiverb in a 32 bit instance of the VEPro server,  and reference VEPro from the 64 bit version of SONAR.
 
 
2014/04/06 08:55:40
Raymond70
gswitz
 
You might check your Preferences > File > Audio Data > File Bit Depths. Ensure that Record is set to 24 not 32.


Was set to 16 in all Sonar versions.
 
 
2014/04/06 09:05:00
Raymond70
Noel Borthwick [Cakewalk]
From your description it would seem that altiverb has some performance issues. Have you tried contacting their tech support?
One thing you can try is going into preferences and resetting the audio configuration to defaults.  That will set SONAR to the factory settings for audio. Then choose your ASIO driver and retest.
Another thing to try - does VE Pro support hosting normal VST plugins? If so you could load altiverb in a 32 bit instance of the VEPro server,  and reference VEPro from the 64 bit version of SONAR.
 
 


I don't have VE Pro, I only have VI Pro.
Audio Preferences were set at default... no success. Next I altered them acoording my wishes (as set in other versions of Sonar), no success either.
Performance issues of Altiverb? Maybe, but it is very strange and for me rather incomprehensible that this didn't occur in the previous versions of SONAR. Between X1 and X3e (I skipped X2) some programming must have changed to trigger this.
 
I didn't contact Technical support of Altiverb yet, just because I think it is some issue of SONAR. As everything remained the same with those older versions of SONAR, who/what caused this problem?
 
2014/04/06 09:29:39
robert_e_bone
Well, it is entirely possible that there is a coding problem within Altiverb that is only exposed by slight changes of things within X3.  This has happened before with a small number of other 3rd-party plugins.
 
I also think contacting the Altiverb technical support folks would be a good idea.
 
Can't you swap out Altiverb for some other similar plugin, and run Sonar in x64? 
 
Bob Bone
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account