Bug with Common LFO in HD-1 mode
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
-
- Platinum Member
- Posts: 1150
- Joined: Mon Feb 20, 2017 11:28 am
- Location: France
Bug with Common LFO in HD-1 mode
Hello friends,
(Sorry in advance if the same issue has been already addressed.)
Analyzing a Prog from a sound bank I've purchased, I've found what it could be a bug, at least in my system. I have a Kronos 2 73 notes, with 3.1.2 system installed.
Here are the steps to follow :
1°) Go to a Prog in HD-1 bank.
2°) Initialize it. (so you get one Osc with the first Rom sample. It's ok)
3°) Set "Common LFO Frequency” to 50 (whatever speed works)
4°) In “Filter LFO Mod” set “Common LFO, Intensity to A” to max, +99 (here again, whatever setting is working but it’s easier to hear.
Now, you can hear the Cutoff frequency sweeping. It’s OK.
You can try to put it back to 00, it stops sweeping. Ok again. Put it back to 99.
5°) Save this Prog on the same place (“Write”)
6°) Now, go back to “Filter 1 LFO MOD” and set “Intensity to A” to 00. Now you shouldn’t hear the cutoff sweep anymore.
Here is the bug : it's not the case. whatever setting, from -99 to +99, the cutoff sweeping stays the same as we have saved. Impossible to modify it and get a straight sound. The only way I’ve found is to set it to 00 then save the Prog with “write” command. Only now, it’s OK.
My conclusion is : there is a link between one parameter and the “write” command. Of course it’s absolutely not normal.
I must say that all works fine with the 8 other engines.
So what I would want to know is if you get the same issue when applying these settings.
Thank you very much.
(Sorry in advance if the same issue has been already addressed.)
Analyzing a Prog from a sound bank I've purchased, I've found what it could be a bug, at least in my system. I have a Kronos 2 73 notes, with 3.1.2 system installed.
Here are the steps to follow :
1°) Go to a Prog in HD-1 bank.
2°) Initialize it. (so you get one Osc with the first Rom sample. It's ok)
3°) Set "Common LFO Frequency” to 50 (whatever speed works)
4°) In “Filter LFO Mod” set “Common LFO, Intensity to A” to max, +99 (here again, whatever setting is working but it’s easier to hear.
Now, you can hear the Cutoff frequency sweeping. It’s OK.
You can try to put it back to 00, it stops sweeping. Ok again. Put it back to 99.
5°) Save this Prog on the same place (“Write”)
6°) Now, go back to “Filter 1 LFO MOD” and set “Intensity to A” to 00. Now you shouldn’t hear the cutoff sweep anymore.
Here is the bug : it's not the case. whatever setting, from -99 to +99, the cutoff sweeping stays the same as we have saved. Impossible to modify it and get a straight sound. The only way I’ve found is to set it to 00 then save the Prog with “write” command. Only now, it’s OK.
My conclusion is : there is a link between one parameter and the “write” command. Of course it’s absolutely not normal.
I must say that all works fine with the 8 other engines.
So what I would want to know is if you get the same issue when applying these settings.
Thank you very much.
Same Behavior on my Kronos 2, lastest OS.
This is a bug that needs to be fixed. The value retained by the Kronos seems to be the buffer value used for the program editing, instead of the the saved value.
This is a bug that needs to be fixed. The value retained by the Kronos seems to be the buffer value used for the program editing, instead of the the saved value.
New Timelapse Kronos soundset:
http://www.barbandco.com/store/c14/Sons ... iques.html
http://www.barbandco.com/store/c14/Sons ... iques.html
-
- Platinum Member
- Posts: 1150
- Joined: Mon Feb 20, 2017 11:28 am
- Location: France
Thanks for this precision. I didn't notice it.KK wrote:Bug confirmed on my K2 too.
Identical bug happens if you try with LFO1 and LFO2 on the same page.
Hope Korg adds this fix in their next update.
In fact, there is also the same issue when using double OSC in one HD-1 prg and swapping the OSCs. I didn't mention it not to burden the post.
It seems that the Kronos behavior is dysfunctionnal in this sector.
When you say : "Hope Korg adds this fix in their next update", for sure they wouldn't do anything unless we notify them. The most numerous we'll be to inform them, the faster they will address the problem, I guess.
- danatkorg
- Product Manager, Korg R&D
- Posts: 4205
- Joined: Fri Jan 21, 2005 7:28 am
- Location: California, USA
- Contact:
Thanks for noticing this. I just looked at the problem. It seems to have worked properly in 3.0.4, but not in 3.12. I've contacted the appropriate people (my group is working on other products at the moment). I'm sorry for the inconvenience.
In general, btw, you can contact your Korg Distributor to report bugs - details in my signature.
Best regards,
Dan
In general, btw, you can contact your Korg Distributor to report bugs - details in my signature.
Best regards,
Dan
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
-
- Platinum Member
- Posts: 1150
- Joined: Mon Feb 20, 2017 11:28 am
- Location: France
Thank you Dan, I'm sure we all appreciate you've reacted so quickly.danatkorg wrote:Thanks for noticing this. I just looked at the problem. It seems to have worked properly in 3.0.4, but not in 3.12. I've contacted the appropriate people (my group is working on other products at the moment). I'm sorry for the inconvenience.
In general, btw, you can contact your Korg Distributor to report bugs - details in my signature.
Best regards,
Dan
-
- Platinum Member
- Posts: 1150
- Joined: Mon Feb 20, 2017 11:28 am
- Location: France
-
- Platinum Member
- Posts: 1150
- Joined: Mon Feb 20, 2017 11:28 am
- Location: France
Hi, Dan,danatkorg wrote:Thanks for noticing this. I just looked at the problem. It seems to have worked properly in 3.0.4, but not in 3.12. I've contacted the appropriate people (my group is working on other products at the moment). I'm sorry for the inconvenience.
In general, btw, you can contact your Korg Distributor to report bugs - details in my signature.
Best regards,
Dan
I'd like to know if you've got any news about that issue ?
Thanks