Hello everybody ! I have a problem :
when I try to move a knob with my mouse , let's say on the polysix : the value goes down to zero and i cannot change this value = it is stucked to 0 unless i move it with my midi controller.
This occurs on the MS-20 and the polysix for most of the knobs.
For example "potamento" knob on the MS 20 and "the cut-off" on the Polysix.
This occurs on the standalone and the VST.
I tried different movement type : nothing seems to work
I tried different mouse driver : no results
This is very annoying so i hope someone can help me.[/b]
The knobs in KLC 1.19 are not working with the mouse
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
-
MartinHines
- Platinum Member
- Posts: 3041
- Joined: Tue Jan 21, 2003 12:56 pm
- Location: Topeka, KS (USA)
-
Synthesizist
- Posts: 8
- Joined: Thu May 01, 2008 10:22 am
-
Polynomial_C
- Posts: 3
- Joined: Thu Aug 07, 2008 6:10 pm
To reiterate what Synthesist posted, try this:
Turn off everything that transmits or receives MIDI in your studio. This includes controller keyboards, synth keyboards, synth modules, hardware samplers, and your MIDI interface (if this isn't powered, disconnect it from the computer).
If you use bus-powered hardware then also physically disconnect this from the computer.
With nothing else running on your computer, launch the standalone KLC synth. Now try changing the settings with the mouse.
Do the synth's knobs still behave as described?
If they behave normally, power up (or reconnect) your MIDI interface and test again. Then, one at a time, power up (or reconnect) your MIDI units, not forgetting to test your KLC synth each time.
My bet is that you'll find one hardware unit that's transmitting either a system reset or zero values for the Control Change numbers, thus resetting the knobs.
Kind regards.
Turn off everything that transmits or receives MIDI in your studio. This includes controller keyboards, synth keyboards, synth modules, hardware samplers, and your MIDI interface (if this isn't powered, disconnect it from the computer).
If you use bus-powered hardware then also physically disconnect this from the computer.
With nothing else running on your computer, launch the standalone KLC synth. Now try changing the settings with the mouse.
Do the synth's knobs still behave as described?
If they behave normally, power up (or reconnect) your MIDI interface and test again. Then, one at a time, power up (or reconnect) your MIDI units, not forgetting to test your KLC synth each time.
My bet is that you'll find one hardware unit that's transmitting either a system reset or zero values for the Control Change numbers, thus resetting the knobs.
Kind regards.
Dave Bourke
- ideation -
- ideation -
Hi Dave,
Thanks for the tip but it didn't work for me. I have every MIDI in and out going to 2 JL Cooper Synapse MIDI patchbays. I turned off the Synapses and my interfaces and still had the problem.
It wasn't likely to be that anyway because, for one thing, the onscreen knobs didn't move until you tried to move them with the mouse, whereupon they would jump to the lowest value and stay there. If anything were transmitting control data, the knobs would be moving before I touched them, for example. Also it would effect other plugins or at least be writing a constant stream of data into Logic. Nada on both counts.
No, what finally worked for me was to uninstall the new challenge/response version, plug my USB key in, and install the dongle-protected version. Worked right away without changing anything else. I was hoping to get rid of the dongle but I seem to be having issues with the new versions. <sigh>
Thanks for the tip but it didn't work for me. I have every MIDI in and out going to 2 JL Cooper Synapse MIDI patchbays. I turned off the Synapses and my interfaces and still had the problem.
It wasn't likely to be that anyway because, for one thing, the onscreen knobs didn't move until you tried to move them with the mouse, whereupon they would jump to the lowest value and stay there. If anything were transmitting control data, the knobs would be moving before I touched them, for example. Also it would effect other plugins or at least be writing a constant stream of data into Logic. Nada on both counts.
No, what finally worked for me was to uninstall the new challenge/response version, plug my USB key in, and install the dongle-protected version. Worked right away without changing anything else. I was hoping to get rid of the dongle but I seem to be having issues with the new versions. <sigh>
re: Using Mouse On Knobs Fails
The problem of not being able to use the mouse to move the knobs in the Polysix & MS-20 synths seems to be widespread.
Many have tried to re-install the software with mixed results. Unfortunately, that didn't work on my system.
Although I've been able to get knobs to move via a MIDI controller by using the 'learn' command to assign them, not being able to use the mouse to move the knobs is quite frustrating.
Has anyone heard of any other fixes to remedy this problem?
(Mac version 1.2.3 - Polysix and MS-20)
update:
Did a complete 'clean' install of OS X on my G5 and re-installed the entire Korg Legacy collection from scratch and the problem is still there!! All knobs fail to respond!
Many have tried to re-install the software with mixed results. Unfortunately, that didn't work on my system.
Although I've been able to get knobs to move via a MIDI controller by using the 'learn' command to assign them, not being able to use the mouse to move the knobs is quite frustrating.
Has anyone heard of any other fixes to remedy this problem?
(Mac version 1.2.3 - Polysix and MS-20)
update:
Did a complete 'clean' install of OS X on my G5 and re-installed the entire Korg Legacy collection from scratch and the problem is still there!! All knobs fail to respond!
Fix on the way
Hello all,
Following correspondence with Korg UK a few weeks ago I have just been sent some beta updates to try out. These solved the problem in my case and I've confirmed this to Korg UK, so I expect that a final release update will be available soon.
Regards
Kevin
Following correspondence with Korg UK a few weeks ago I have just been sent some beta updates to try out. These solved the problem in my case and I've confirmed this to Korg UK, so I expect that a final release update will be available soon.
Regards
Kevin
No further word from Korg as yet so here are the links to the "hotfixes".
------------------------------
1. Download hotfix from the following link.
(If installed product is KLC-AE07, please download from KLC-AE07 link. If installed product is KLC-1 v1.2, please download from KLC-1 v1.2 link.)
[KLC-AE07]
http://www.korguser.net/downloadfile/fi ... hotfix.zip
[KLC-1 v1.2]
http://www.korguser.net/downloadfile/fi ... hotfix.zip
2. Unzip the file.
3. Overwrite the unzipped files to the following path.
[HD Name]/Library/Audio/Plug-Ins/VST/KORG
------------------------------
1. Download hotfix from the following link.
(If installed product is KLC-AE07, please download from KLC-AE07 link. If installed product is KLC-1 v1.2, please download from KLC-1 v1.2 link.)
[KLC-AE07]
http://www.korguser.net/downloadfile/fi ... hotfix.zip
[KLC-1 v1.2]
http://www.korguser.net/downloadfile/fi ... hotfix.zip
2. Unzip the file.
3. Overwrite the unzipped files to the following path.
[HD Name]/Library/Audio/Plug-Ins/VST/KORG
-
mikemolloyuk
- Moderator
- Posts: 748
- Joined: Wed May 23, 2007 9:22 am
- Location: Milton Keynes, UK