Now this is how to show us a bugplauto wrote:There seems to be a bug in lfo, when using the option Wave1- Random, knobs become slow, it is almost impossible to make any changes.
Thanks, we'll take a look.
Didn't your sound designers notice this whilst testing and programming presets.briandesmond wrote:Now this is how to show us a bugplauto wrote:There seems to be a bug in lfo, when using the option Wave1- Random, knobs become slow, it is almost impossible to make any changes.
Thanks, we'll take a look.
Thanks I'm interested to see what's different about this .mid file that causes it not to work.......briandesmond wrote:I just grabbed it, thanks Tek.
They didn't, and not only did we have a pretty large sound design team, but we assembled a brand new synth beta team from people we polled right here at KVR.rob_lee wrote:Didn't your sound designers notice this whilst testing and programming presets.
That's some bug, should have been noticed right away
Now that's some slap in the "KVR superiority" facebriandesmond wrote:They didn't, and not only did we have a pretty large sound design team, but we assembled a brand new synth beta team from people we polled right here at KVR.rob_lee wrote:Didn't your sound designers notice this whilst testing and programming presets.
That's some bug, should have been noticed right away
Maybe you guys should learn something from Reaper - it has an integrated screencap movie feature and consequently a large percentage of bug reports are in this visual manner - very effective (also as a tutorial tool of course)briandesmond wrote:Now this is how to show us a bugplauto wrote:There seems to be a bug in lfo, when using the option Wave1- Random, knobs become slow, it is almost impossible to make any changes.
Thanks, we'll take a look.
Actually that was a valid question IMO, if the guy thought i was taking the piss so be it It's just a bug that you'd think would have been noticed straight away by someone trying tp program a preset using those features shown, it's not rocket science.kmonkey wrote:Now that's some slap in the "KVR superiority" facebriandesmond wrote:They didn't, and not only did we have a pretty large sound design team, but we assembled a brand new synth beta team from people we polled right here at KVR.rob_lee wrote:Didn't your sound designers notice this whilst testing and programming presets.
That's some bug, should have been noticed right away
I guess now they'll try to slap person which did selection or something similar
Anyway or other good luck in fixing bugs and congrats for this release
briandesmond wrote:, but we're working on a plan to fix some of this stuff.
Good to see you here! Always nice to be able to communicate with the person who's in control of the ones and zeros.......... Did you get a chance to look at the midi file I posted earlier? It shouldn't have any program changes imbedded but perhpas the Host it was created in adds a PC to it's midi files? That would explain why Z2 jumps to the first preset in the selected folder when trying to use one of the suspect arps. The Midi files I've created in other Hosts today have all worked perfectly.........perhaps it's something host specific............benstat wrote:Hi folks,
I'm one of the developers who worked on Z3TA+ 2. I have an idea how to fix some of these issues, such as reducing memory usage.
For example, I now know of an issue with imported arp patterns that contain program changes. We should make Z3TA+ 2 ignore those in an update.
Thanks,
Ben
Yes, very heartening in deed. Waiting till all these things have been fixed before I upgrade...1-2-Many wrote:BTW - CW's presence and attention in this thread is heartening - thanks guys!
Yes I did thanks. Your midi file helped me to find the cause of the problem - a program change message in the arp pattern. You could be right about it being host specific, but regardless, Z3TA+ 2 should ignore program changes in arp patterns anyway.Teksonik wrote:Did you get a chance to look at the midi file I posted earlier?
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement