Hi.
I've just installed firmware 2.0.1 and WOW Korg, it's really great! You listened to us and implemented a lot of requested things.
One of those, which I was also waiting for, is Performance Hold function, so I've used it right away, but unfortunately it seems to be buggy. The synth is going out of CPU power after some minutes of playing with Perf Hold ON.
I've posted a video here https://streamable.com/oferf3 to demonstrate what's happening.
In this video I've used a very simple sound. As you can see, CPU is around 10% at idle. With one voice sounding it's around 15%. Then I started playing notes repeatedly (here I'm playing the same note, but it's irrelevant) and, after a while, you can see CPU is at 25% while again a single voice is sounding. By continuing to play notes, CPU usage rises to 100% and from there on, no voice is allowed to play anymore.
By switching Performance Hold off, CPU goes down to around 70% and new voices are again allowed to play, then while continuing to play notes, CPU usage gradually lowers to normal values.
This seems to occur with any performance, be it simple or complex.
Can anyone reproduce it?
Bozzy
Performance HOLD Bug?
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Performance Hold Bug
I am experiencing a different Performance Hold bug;
running WS 2.0.1, single layer with sustaining multisample, such as Wnd: Tape Flute:
1. activate performance hold,
2. play a note,
3. release key,
4. change performance through Home/perform button to anything else
sound from first patch persists beyond SST Hold Time, sometimes indefinitely? Can't quite figure out how to make it turn off, returning to original performance and turning hold on / off isn't working.
Any ideas?
running WS 2.0.1, single layer with sustaining multisample, such as Wnd: Tape Flute:
1. activate performance hold,
2. play a note,
3. release key,
4. change performance through Home/perform button to anything else
sound from first patch persists beyond SST Hold Time, sometimes indefinitely? Can't quite figure out how to make it turn off, returning to original performance and turning hold on / off isn't working.
Any ideas?
- danatkorg
- Product Manager, Korg R&D
- Posts: 4205
- Joined: Fri Jan 21, 2005 7:28 am
- Location: California, USA
- Contact:
I think we may have discussed this on Facebook, but to close the loop: yes, we've confirmed that this can happen in some cases, and are looking into how to address it.Bozzy wrote:So nobody else is experiencing this behaviour?
Dan(atkorg)?
Dan Phillips
Manager of Product Development, Korg R&D
Personal website: www.danphillips.com
For technical support, please contact your Korg Distributor: http://www.korg.co.jp/English/Distributors/
Regretfully, I cannot offer technical support directly.
If you need to contact me for purposes other than technical support, please do not send PMs; instead, send email to dan@korgrd.com
Manager of Product Development, Korg R&D
Personal website: www.danphillips.com
For technical support, please contact your Korg Distributor: http://www.korg.co.jp/English/Distributors/
Regretfully, I cannot offer technical support directly.
If you need to contact me for purposes other than technical support, please do not send PMs; instead, send email to dan@korgrd.com
-
- Posts: 8
- Joined: Sat May 28, 2022 2:29 pm
- Location: UK
More than a year on from the last post on this thread - sorry.
If I use "hold" on a variety of factory programs or even with ones I've created myself, I often find the machine cuts out. It doesn't freeze, it just cuts out as I'm playing. Looking at the CPU in Utilities, it's cutting out when it reaches 100% - the problem is that it reaches 100% so frequently. Why?
It feels like I'm overloading the synth, but surely that's absurd - how can you play the machine freely if you have to keep easing back? I'm not exactly a keyboard basher, I'm more Max Richter than Keith Emerson! However I do like to set hold and do some serious knob twiddling, very often that's when I feel I'm really exploring the Wavestate's potential.
I can't believe this issue is unique.
Dan?
If I use "hold" on a variety of factory programs or even with ones I've created myself, I often find the machine cuts out. It doesn't freeze, it just cuts out as I'm playing. Looking at the CPU in Utilities, it's cutting out when it reaches 100% - the problem is that it reaches 100% so frequently. Why?
It feels like I'm overloading the synth, but surely that's absurd - how can you play the machine freely if you have to keep easing back? I'm not exactly a keyboard basher, I'm more Max Richter than Keith Emerson! However I do like to set hold and do some serious knob twiddling, very often that's when I feel I'm really exploring the Wavestate's potential.
I can't believe this issue is unique.
Dan?