KVR Audio

IrionDaRonin · Post by **IrionDaRonin** » Mon Jul 08, 2013 1:15 pm

Now that i have started a new soundset for Z3ta 2. I just noticed that the LFOs are not working correclty or they are just stopping working without any reason.
As soon as i press play on FL Studio 11, the LFOs are not moving.

Anyone else with this problem?
Any quick solution?

Thanks and have a nice day

IrionDaRonin · Post by **IrionDaRonin** » Thu Jul 11, 2013 10:23 am

Little bump.

I hope anyone could point me this strange thing.

Thanks again.

GeorgK · Post by **GeorgK** » Sat Dec 21, 2013 3:40 pm

Sorry for waking up this dead thread after 6 months, but I just ran into the same problem. Once "play" or "record" inside the host is started, it is impossible to modulate the waveshaper parameters anymore (both by hand and via the mod matrix). The graphics still changes (at least when manually adjusting the parameters), but not the sound. Other targets in the mod matrix are not affected.
What I suspect: As waveshaper modulation was introduced with the z3ta2+ update, and possibly without contribution from the original developer (R. Caballos), the guys at cakewalk did not programm it properly, but just "frickled" it to the code by interfering with the MIDI automation. Once the host takes over control, the whole thing is f'ed up.
Maybe there is a way to set up the host so that it does not block the waveshaper automation. But all three programs I have tested (Sonar, Reaper, Cubase) caused the aforementioned bug "by default".

Georg

Davias · Post by **Davias** » Sun Dec 22, 2013 2:54 am

Crap I think I experienced the same problem with FL...

EnGee · Post by **EnGee** » Sun Dec 22, 2013 6:29 am

I have tested the lfos for some time and they are working fine with me in Studio One. But, I have another problem. When moving the cursor above EG Section or Osc/Perform section, the cpu clips!! Although I like the sound of it a lot but I can't tweak/design the sounds with such behaviour!

BlitBit · Post by **BlitBit** » Sun Dec 22, 2013 2:41 pm

I can confirm both problems:

When the mouse is moved over the graphical EG and OSC representations the CPU usage goes up significantly and sometimes leads to audible crackling sounds, especially during playback.
Modulations of the waveshaper parameters via LFO or automation go missing when playback in the DAW is stopped and started again.

I could live with the clipping problem and have already gotten used to it by just using the knobs to tweak the sound. However, the second problem is more pressing in my opinion because it robs you of using a wide range of great, interesting sounds in your production. Especially considering the fact that waveshaping seems to be one of the defining features of Z3TA+ 2.

In case one of the developers follows this thread, here is a description of how to reproduce the waveshaper problem in Reaper 4.581 (OS is Windows 8.1, everything 64 bit):

Start Reaper and create a new project.
Insert "Z3TA+ 2" as a new virtual instrument on a new track.
In Z3TA+ 2: Program > Initialize.
OSC 1 > WAVE: "VINT SAW 1".
LFO 1 > WAVE 1: "4 STEPS" > SYNC: "1" > PHASE: "0 deg".
MOD > SOURCE: "LFO 1" > RANGE: "100%" > DESTINATION: "Oscillators > All Oscillators > Waveshaper > Bit Reduction". If you now play a sound on the keyboard you can clearly hear the modulation of the bit reduction parameter.
In Reaper: Create a new MIDI item for the instrument and enter a long note, e.g. C3 for 1 bar. While entering the note the modulation can still be heard.
After you have entered the MIDI data press play. The modulation is now gone.
Automations of the parameter "Osc 1 Bit Crush" are also ignored while playing back the note.

If you haved saved the patch described above in "User Content" here is one way to get the modulation back during faulty playback: Open the Z3TA+ 2 instance in question and switch to any sound from "Factory Content" and then back to the saved patch in "User Content". For this workaround to work it seems to be important to cross that border between "Factory Content" and "User Content". If I only switch between my patches in "User Content", e.g. using the arrows next to the presets, the modulation still does not come back. Unfortunately, this workaround obviously does not help if you want to render a track with waveshaper modulations applied.

There is an older thread with the list of known bugs which was commented on by Brian Desmond and Ben Staton from Cakewalk. So I hope they (or someone else from Cakewalk) will notice this thread as well and do something about these problems because I really like the sound of Z3TA+ 2 and its quick workflow.

Although I have "only" paid 50 Euros during the 50% sale bugs like these still dampen the enjoyment of my purchase.

If needed I am willing to enter a ticket in Cakewalk's official ticketing system. And I will definitively do so anyway in case there is no reaction here.

Kind regards,

BlitBit

chk071 · Post by **chk071** » Sun Dec 22, 2013 2:53 pm

BlitBit wrote: There is an older thread with the list of known bugs which was commented on by Brian Desmond and Ben Staton from Cakewalk. So I hope they (or someone else from Cakewalk) will notice this thread as well and do something about these problems because I really like the sound of Z3TA+ 2 and its quick workflow.

I wouldn't at all count on it. The best would be to report the bugs to Cakewalk support, i guess if enough people report it, they will react on it. At least it can't be wrong if everyone who has this problem reports it to them.

Think i will check later too if i can reproduce this, i didn't use the waveshaping modulation so far.

BlitBit · Post by **BlitBit** » Wed Jan 15, 2014 10:40 pm

I have issued a bug report regarding the modulation of the waveshaper parameters and will try to keep you informed about any status updates.

Davias · Post by **Davias** » Thu Jan 16, 2014 12:05 am

Great ! Hope they will fix it soon ^^

BlitBit · Post by **BlitBit** » Tue Apr 01, 2014 6:00 pm

Quick update: No answer or reaction from Cakewalk during all these weeks since reporting the bug.

GeorgK · Post by **GeorgK** » Wed Apr 02, 2014 5:34 am

It is not a bug. The waveshaping modulation is a fake feature in a fake product from a fake company. Simple.

EnGee · Post by **EnGee** » Wed Apr 02, 2014 7:18 am

BlitBit wrote:Quick update: No answer or reaction from Cakewalk during all these weeks since reporting the bug.

Unfortunately this bug can't be ignored. After all, this is the main advantage over Z3ta+1, the ability to modulate the waveshaping parameters in the modulation matrix!

It is easy to reproduce it (I did it in Sonar X3). Drawing the note then playing the host deactivates the modulation! Even if I do it manually by altering the parameter in the waveshaper with the mouse, it doesn't work!

Have you tried writing in their forum?

GeorgK · Post by **GeorgK** » Wed Apr 02, 2014 7:23 am

It is not only the main advantage over version 1, it is also the only reason why people paid actual money for the upgrade. Since then I just don't see them as a reliable, serious company anymore. F'them.
G.

EnGee · Post by **EnGee** » Wed Apr 02, 2014 8:01 am

Well, it might be not difficult to fix as the modulation works before you record any midi notes, so it is already there and functioning but 'something' is deactivating the functionality of the waveshaper when you add midi notes to the piano roll in the host.

My experience with Cakewalk staff and forum is good and positive in general (if they answer, that's it ). For me I still have some faith in them and I want to give them a new chance because I don't know, I feel they are serious this time to fix the bugs in their software (as they are doing with Sonar X3), so let's hope they won't disappoint us.

[Edit]
I have posted it in their forum:
http://forum.cakewalk.com/Bug-in-Wavesh ... 18192.aspx

GeorgK · Post by **GeorgK** » Wed Apr 02, 2014 10:52 am

I am quite sure that my former assumption (posted at Dec 21st) is correct. Therefore I doubt that it is an "easy fix".
G.

A problem with Z3ta 2 and LFOs in FL Studio 11