It's been almost a year and I've heard nothing about the bugs in Z3TA 2, v2.1 being addressed.  Could someone from Cakewalk please respond?
 
Below are only the ones I've noticed, there may be more:
1. USER Waveshaper Waveform Bug - Some Waveshaping controls are applied too agressively to imported waveforms put in USER slots.
 
There is inconsistency with some of the Waveshaper controls between Imported wavs and the oscill.set wavs. Try this:

Dial in a wav on OSC1, e.g. Multi Triangle
Right click in the waveform display and "Reset all shapers".
Right click in the waveform display and "Save Wavetable As".
Set Drive to the halfway mark on OSC1.
Go to OSC2 and import the saved wave in USER1 slot
Copy & paste OSC1 settings to OSC2

You should see that they don't match - you have to back the drive off somewhat on OSC2 to get it to match OSC1. This happens with other waveshaper controls but not all, and the difference can be more extreme depending on the waveform and the number of shapers used.

Doing the side by side comparison as explained above the controls found to be in error were Warp, Twist, Drive, Offset, Wave, and Bit Red. The others seemed to work right.
 
2. Sync issues with Hosts - Any preset that uses sync in any of its parameters (LFO, ARP, etc.) is wonky when used within a project if that project is not stopped or started on the bar grid.  I've also noticed the "stuck note" arp behavior in Cubase, and it happens if the project is stopped at a location off the tempo grid - if you snap the project back to grid the arp behaves normally. I think this is a general sync issue, as weirdness happens too with presets using synced LFOs and the project is stopped or started "off grid"
 
3. Import Preset Naming Bug - Preset names are cutoff when importing names over 26 characters long, this is worsened when using using Original Order since it adds 6 characters.
 
4. Arp Export - If you export (drag) an arp out to save it and then reload it, it loads and plays an octave higher.
Also, if you export at anything other than sync set to 1, the arp pattern is changed (smashed or chopped) when you bring it in again. I realize this can be corrected with the "Autofit Patterns to 1 Measure When Loaded" enabled, but something still feels weird about this behavior...maybe I need to think about it more.

5 Arp Drag - The Manual says "You can also drag a MIDI file to and from the Arpeggiator graph". From works, but To does not. (Least in Cubase 5.5 and Minhost 1.64)

A severe one...

6. It can't be authorized properly on OSX 10.6.8

Maybe a bug? - choosing arp patterns make preset mute -->  
---> OK : it's not bug, You should increase arp velocity. But all this can be very misleading,: by default when you turn ARP on,  velocity is 0, so you can hardly hear anything.
Even in ARP presets, many times arp velocity is 0, and you can hear the preset - so you might think, you dont need to push up arp velocity....
------------------------------------------------------------------------------

environment:  windows7 32bit, 
Reaper 4.261 as host, 
empty project - no other instrument or effect loaded

how to reproduce:
1) Load Factory Content / Percussion / 80s Snare XS
2) play some notes - hear the snare
3) Going to the ARP module and selecting in the pattern: Midi Arp 132
4) play some notes (short or long -  doesn't matter) --> I Don't hear ANYTHING!!!
5) switching pattern OFF in the ARP module , playing some notes -->I hear the snare
6) Going to the ARP module and selecting in the pattern: other midi arp patterns --> none of them produce sound
-----------------------------------------------------------------------------------

After adding the arp pattern you need to increase the value of the arp velocity slider or you will not hear anything.

scook
After adding the arp pattern you need to increase the value of the arp velocity slider or you will not hear anything. 

Thanks for the quick answer :)
I edited my previous "bug" message.
So it's not bug, I should increase arp velocity.
But all this can be very misleading,: by default when you turn ARP on,  velocity is 0, so you can hardly hear anything.
Even in ARP presets, many times arp velocity is 0, and you still can hear the preset - so you might think, you dont need to push up arp velocity....



I don't know if there are any bugs on my platform (win7, reaper),
but I will investigate this.
I only use 6-7 synths that are stable enough and contain almost no serious bugs,
and I want to use  Z3TA+ 2.1 as well.
So thanks for helping me out. I have read the manual too,
but i didn't remember to this detail....

A this is a peer to peer forum mentioning bugs here will not bring them to the attention of Cakewalk . You need to submit a problem report. http://www.cakewalk.com/support/contact/problemreport.aspx

Glad to see that worked for you. FWIW, it works the same way in SONAR on Win7. I have not used z3ta+2 much and it did take a second or two to figure out what was going on after replicating your test plan. Thanks for the clear posting of the issue, it made sorting it out much easier. The Cakewalk staff rarely post on the forum, you can tell them by the [Cakewalk] at the end of their ID.

If you would like to see z3ta+2 function differently or have suggestions how to enhance the documentation there is a feature request form http://forum.cakewalk.com/fb.ashx?m=1594962

Should you wish to contact contact Cakewalk directly here is how http://forum.cakewalk.com/fb.ashx?m=1594962

Thanks for the clarification:
If I really find a bug, I will create a problem report then!

I'm suffering with stuck notes in Cubase 7.5. Was using the arpeggiator, but dragged the notes in to Cubase to try and stop the issue, but it continues.

1 2 Many
It's been almost a year and I've heard nothing about the bugs in Z3TA 2, v2.1 being addressed.  Could someone from Cakewalk please respond?
 
Below are only the ones I've noticed, there may be more:
1. USER Waveshaper Waveform Bug - Some Waveshaping controls are applied too agressively to imported waveforms put in USER slots.
 
There is inconsistency with some of the Waveshaper controls between Imported wavs and the oscill.set wavs. Try this:  [...]

Having just played around with this a bit I can offer a workaround :
 
The waveshaper wants its wavetables normalized to -6db or it won't shape properly.  However, the waveshaper exports the wavetables at 0db.  So, after exporting a waveform, you have to use a wave editor to normalize it to -6db and then it will behave properly once reloaded.