Hitting another bug in use today with Z3TA+2 made me decide it's high time I start a thread to gather all the bugs I've encountered, and hopefully get some response from Cakewalk guys - as my previous posts have gotten nothing:

1. ARP Changed:
Arp145.cmp IS NOT the arp used in version 1.41, it changed at 1.53 and was carried on into v2. Check the preset A: 063: digi pluck (mw) in 1.4 vs v2. The 1.4 version is obviously how the preset was intended to sound....makes me wonder if there are any other botched arps.

2. ARP Import/Export:
A. If you export (drag) an arp out to save it and then reload it, it loads and plays an octave higher.

B. 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.

C. Dragging TO the Arp doesn't work - The Manual says "You can also drag a MIDI file to and from the Arpeggiator graph". From works (except as noted in A) but not so with TO - at least in Cubase 5.5 and Minhost 1.64.

3. Sync to Project Tempo:
"Stuck note" arp behavior rampant in Cubase and annoying as hell. 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 "off grid"

4. Waveshaper Acts differently on User Waves
Waveshaper controls behave inconsistently between imported User wavs vs 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.

5. Import fxb loses name characters & Bad numbering
A. Import .fxb cuts off preset names over 23 characters, which is worsened when using Original Order since that adds 6 characters to the front of each name.

B. When importing using "Original Order", numbering should start at zero for each bank (A, B, C, D, E, F). This reflects how banks were numbered in the older versions and makes it easier to correlate.

Notes hang when using Z3ta's arp in Maschine. Really annoying.

Yeah - it's a transport bug - see #3.....maybe you did. Useful info to note that it's broken in Maschine too

In Maschine you can go back to the start of your song or scene but the arp hangs until it is triggered by the same note it was left hanging on. I have to try and land back on the right spot when hitting stop. I feel a little like I'm playing slots in Vegas. JACKPOT! Arp stops! So I've been letting it hang and I'm getting all these weird swirling high pitched sounds. I've been hearing so much of them I'm starting to think I should add them to my track!

Sidenote, who the hell make a nice big GUI for the arp and it's uneditable with the mouse?

Wow, I missed the 1 year anniversary of this thread...And still no update to fix these bugs.

Sad state of affairs Cakewalk

...and YES, I'm back on this horse again

The chances seeing them fixed are probably higher when you report them directly to Cakewalk. The thing is, i never came along the bugs listed by you, so there's a probability that not so many people, or even noone reported them yet. Whether they get fixed or not is another question, but if Cakewalk are not even aware of them...

Pretty hard to miss the sync bug...Do you really use Z3TA+ 2 that much? What is your host?

I reported them at the Cakewalk forum as well, they are aware of them, have been for over a year. A Cakewalk representative PM'ed and thanked me for my efforts shortly after starting this thread on the 2.1 release bugs..and yet still nothing.

Hm, can't do much more about it then i guess. A lot of stuff to be read also about Cakewalk not really being responsive in that regard, that's for sure.

You're right btw, i probably didn't really use z3ta enough to come along the bugs you mentioned.

Your response makes me wonder if anyone is really using this plugin. The sync bug drives me nuts, so much that I may subconsciously be avoiding using it as much as I probably would were everything fixed.

That's a really, really great list. Sometimes I wonder about some devs, even when you hand them the most beautiful list, where they can follow along easily and you are at their disposal, they still don't budge...

Well to be fair to Cakewalk - they officially don't use forums (even their own) to monitor their products or customer input/problems. They have their own reporting system on their site. (Which I've used for these issues, getting back generic head patting responses)

If you are experiencing any of these or other issues with Z3TA+ 2, please feel free to use their Reporting System - the more the merrier http://www.cakewalk.com/support/contact/problemreport.aspx

FWIW Number 3 & 4 on my list are the most serious issues

I avoid using it as much as I can due to some of those bugs, quirks and other weird behaviour.

Makes me wonder how many people like me got all excited for this upgrade, with all its wonderful 'improvements', and paid money to upgrade/purchase it only to let it cool in their plugins folder. I used version 1.53 more, I rarely load up V2.1 because of the bugs and the lack of faith in a timely response from CW. A year to fix these few issues is ridiculous.

Times like these I wish guys like Urs Heckmann or Jon Ayres worked for CW, or could clone themselves. There we have two companies that are a model for the industry on how to treat and respond to customers and maintain your product. (There are certainly others, those two just top my list)

Not to bash on CW too much...I only wish them success, more of which they'd have if they'd only get the picture on product and customer support and how that affects your reputation and people's future inclination to make purchases from you.

Wow! I didn't realise you were the only guy using Z3ta+2 properly...

It's actually very easy to use Z3ta+2 and never run into the bugs you mention, I never notice them myself for example:

First, I don't use the arp, all my synth lines are programmed or played. On the rare occasion I want an arpeggio, I don't use the arp in Z3ta+2, I use Cthulhu.

Second, although I use the waveshapers all the time but I have never copied and pasted from an internal wave's waveshaper to an user wave's waveshaper. Not once have I ever needed to do this!

Third, I rarely use presets so I can't say I've ever noticed the name shortening bug.

So, as you can see I use Z3ta+2 every day and never get bothered by the bugs that you suffer from. It doesn't mean I don't use the plugin properly, it just means I use it in a different way to you.

I genuinely hope you get these bugs fixed, they are obviously a real pain for you and it sucks that they haven't been sorted yet. I just think maybe you shouldn't be so quick to jump to conclusions about us fellow users!