Maybe some of you will remember the issues I reported on this forum, first at the beginning of 2011, then in May/June 2012. At the time, I was advised by most of you to address my complaints to Cakewalk Support, which, reluctantly, I eventually did. The problems I reported couldn’t be solved right away, but I was told that people at Cakewalk are looking for solutions. Now, after the release of SONAR X2, I thought it’s only fair to report to you how things changed:

1. In regards to the flash/flicker when loading SONAR nothing changed: it’s still there. It is true, I didn’t expect a solution for this “little problem” since Mr. Munnis told me last spring that he is also experiencing a flash/flicker every time he is loading the program, but that other programs do the same thing and therefore it’s not a big deal…
   
   
2. In regards to the crashing/hanging when trying to use FX2 Amp Sim and FX2 Tape Sim nothing changed: SONAR X2 is crashing/hanging exactly like SONAR X1 every time I try to use any of the two plug-ins.
   
   
3. In regards to z3ta+ fx2 not processing audio when inserted on the FX bin of an Audio Track nothing changed: not only there is no processing, but the Audio Track becomes mute.
   
   

I am sure that some people will immediately assure me that they don’t have any of these problems and that there is something wrong with my system. Don’t bother: my system is fine (if nothing else, it was checked by Cakewalk Support). The problems are caused by SONAR. As I said before, Cakewalk is too busy with trying to make a quick buck (by replacing plugins, for example) and so it doesn’t find time to solve the numerous bugs the program has. To them, the customer is important only if he can be convinced to pay for a new update hoping that finally, this time the bugs will be gone. After paying the “tribute” he’s ignored again and left to struggle with old and new problems. Look around, on the forum, and you’ll see many, many frustrated customers. It is too bad that a product with such great potential is so poorly handled.
 
System:
Intel Core i7-2600K
GIGABYTE GA-Z77X-UD5H
16 GB RAM
Asus Radeon HD 7750-1GD5 Video Card
Windows 7 Pro SP1 64-bit
RME Fireface UFX
MOTU midi express XT
etc.

In regards to z3ta+ fx2 not processing audio when inserted on the FX bin of an Audio Track nothing changed: not only there is no processing, but the Audio Track becomes mute.

Try using the other z3ta vst that's included instead of the one identified as +fx2. The +fx2 does not work for me either. But when I replace it with the simply named "z3ta" in the fx bin - it works great. Not sure what the mixup there was in the naming of these plugs - still, it works fine should I want to use it.


I feel your pain on some of the older plugs we get used to, but now feel long in the tooth and are unsupported with the new platform versions coming out. They are great plugs! It took me a while to pry my hands off of the fxreverb, fxdelay, fxflange and fx chorus. They were my go-to bus plugs. I lobbied hard to have these updated, but that wasn't happening. But I was going to X1/X2 64 bit and had to put some work in to find plugs that sounded similar to what I was used to. The good news is that I did.  You may want to find replacements for your older plugs. In my case I have Valhalla Rm for the reverb (of course now we have brverb which is no slouch). I use sonitus for everything else except the chorus which I tend to like Stillwell's Oligarc. 


TB_reelbus (under $25) is a great replacement for the cake tape sim (I use it on most tracks and the master bus). Cake's TubeLeveler is good and also CamelCrusher (free). 


Voxengo has a great free amp sim. And of course we have the guitar rig and TH2 for amp sims.


The flicker problem, I don't think I have that. I'm not sure what you're seeing but it sounds annoying.




All the best.

when you say flash/flicker, do you mean you  see a white screen  for a second or so after the splash screen pops up then the normal layout after the white screen ?

musicman100


when you say flash/flicker, do you mean you  see a white screen  for a second or so after the splash screen pops up then the normal layout after the white screen ?

Yes, that's an accurate description.

z3ta+_fx2 actually requires a MIDI input.  It's designed for use with Envelope Generators.  So, you can set the filter or volume (or anything) to go through a variety of stages after you hit a note.  The simplest example would be like a trance gating effect.  To do this, insert z3ta+_fx2.  At the top, in the frame, there's a VST dropdown.  Choose "Plug-in Properties" from there.  In the dialog that opens, check "configure as synth."  



Now, remove it.  From now on, the plug-in will be available in the "Instruments" list, rather than in "Audio FX."  But you still insert it in an FX bin.

When you put it in an audio FX bin, set up a MIDI track with its output set to z3ta+_fx2.  Make sure all of the waves in z3ta's oscillators or set to "none" so you don't hear the actual patch.  Add some notes into the MIDI track and you'll hear the effect.  

If you're not looking for this behavior, just use z3ta+_fx, as it's identical outside of this functionality.

Hope this helps.

PapaBear
In regards to z3ta+ fx2 not processing audio when inserted on the FX bin of an Audio Track nothing changed: not only there is no processing, but the Audio Track becomes mute.

A while back a solution was posted. I don't have the reference, but I copied the text:


"In regards to z3ta+ fx2 not processing audio when inserted on the FX bin of an Audio Track, this is completely normal. In order for z3ta+ fx2 to process audio, a few things must happen which differs between hosts. In SONAR:

In the VST Options for z3ta+ fx2, under Plug-in Properties, make sure "Configure as synth" is selected. This will not be selected by default, so you will need to do it from the plug-in itself or from the Cakewalk Plug-in Manager. Afterwards, if the plug-in is already inserted onto the FX Bin of your audio track you will want to remove it and then add it again.
Once configured as synth, place it into the FX Bin of an audio track. It is important to make sure that the audio track actually has some audio material to process
Create a MIDI track and assign the output of that MIDI track to "z3ta+ fx2"
Perform some material live during playback or enter some MIDI data onto the track

At this point, the audio should be filtered through z3ta+ fx2 along with the MIDI performance. If you're unsure, just adjust the filter cutoff. You'll hear it immediately.

Best regards,


Ryan Munnis
Technical Support
Cakewalk"

Bill Jackson [Cakewalk
]

z3ta+_fx2 actually requires a MIDI input.  It's designed for use with Envelope Generators.  So, you can set the filter or volume (or anything) to go through a variety of stages after you hit a note.  The simplest example would be like a trance gating effect.  To do this, insert z3ta+_fx2.  At the top, in the frame, there's a VST dropdown.  Choose "Plug-in Properties" from there.  In the dialog that opens, check "configure as synth."  



Now, remove it.  From now on, the plug-in will be available in the "Instruments" list, rather than in "Audio FX."  But you still insert it in an FX bin.

When you put it in an audio FX bin, set up a MIDI track with its output set to z3ta+_fx2.  Make sure all of the waves in z3ta's oscillators or set to "none" so you don't hear the actual patch.  Add some notes into the MIDI track and you'll hear the effect.  

If you're not looking for this behavior, just use z3ta+_fx, as it's identical outside of this functionality.

Hope this helps.

Thank you for the answer. I have to confess that I still don't understand why z3ta+_fx2 is listed under audio effects, why it's neccessary to move it in the "Instrument" list (couldn't be installed there by default?), why you should set up a MIDI track, and then add some notes into the MIDI track in order to hear the effect (?!)... Oh, and why is z3ta+_fx2 neccessary after all, if z3ta+_fx is identical and can be easily dragged and droped in the FX bin without any problem?

Having "clarified" the z3ta+_fx2 situation, I am, of course, looking forward to your answers to the other issues.

Best regards.

number 2 should be easy to check

In all fairness, I supplied the same solution to the Z3TA FX2 issue twice and was told I was wrong :/. In regards to the flicker, I did contact a developer about it and did open an official report. In no way was I suggesting it wasn't an issue... though I will say it was minor in comparison. :/