M1 KLC - Odd Channel Problem Is Driving Me Nuts!
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
-
- Posts: 9
- Joined: Mon May 25, 2015 9:28 pm
M1 KLC - Odd Channel Problem Is Driving Me Nuts!
The plugin loads easily into Sonar Artist DAW, displays correctly, and edits easily and sounds good, but often the sound will inexplicably move over to my right channel/speaker. Sometimes it will go hours working correctly, but once it starts doing this, it tends to move to the right channel/side within a few minutes or seconds, often while I'm creating a new patch. At first I thought it was ALL sound from M1, because I tend to solo one sound at a time while fine-tuning a patch. But last night I was listening to a mix of two sounds and only the sound in the first slot (the one I was editing) went right, the other sound appeared to stay centered or as it was. I've also noticed an odd, subtle change in the tone of the sound, but maybe this is a result of isolating some stereo effect or similar.
Now the only way to reset this behavior is to reload that patch, not just by reselecting it temporarily. So, if I'm in the middle of creating a patch, I have to save the patch and then reload it. And then it will be back to a correct stereo mix - but for how long - sometimes for an hour or two, sometimes for only a few seconds!? But if I walk away from the desk for a sustained time, it will always be panned hard right when I return!?
And yes, I've checked all functions of the DAW, cables, EQ, audio card, monitors, etc., including hidden track changes or modifiers, etc. And it only happens with M1, and has never occurred with any other softsynth or effect.
I've tried erasing all traces of M1/Korg anything, and re-installed, and tried 64 and 32 bit versions, and I have the latest v1.70 update through all of this.
Dell i7 4ghz, Win 7 64bit, 16gb ram, 2tb 7200rpm, Focusrite Scarlett 2i4, M-Audio keys, Sonar Artist, dBx EQ, Mackie monitors, Hosa MIDI cables (can't think of any other pertinent info). All tested and retested for possible causes for this channel problem, but all signs point to back to M1!?
So as much I enjoy M1 (and have created nearly 400 patch/combos for it) it's so annoying to work with, I'm having to avoid it now! What a shame!
Thanks for any help!
Now the only way to reset this behavior is to reload that patch, not just by reselecting it temporarily. So, if I'm in the middle of creating a patch, I have to save the patch and then reload it. And then it will be back to a correct stereo mix - but for how long - sometimes for an hour or two, sometimes for only a few seconds!? But if I walk away from the desk for a sustained time, it will always be panned hard right when I return!?
And yes, I've checked all functions of the DAW, cables, EQ, audio card, monitors, etc., including hidden track changes or modifiers, etc. And it only happens with M1, and has never occurred with any other softsynth or effect.
I've tried erasing all traces of M1/Korg anything, and re-installed, and tried 64 and 32 bit versions, and I have the latest v1.70 update through all of this.
Dell i7 4ghz, Win 7 64bit, 16gb ram, 2tb 7200rpm, Focusrite Scarlett 2i4, M-Audio keys, Sonar Artist, dBx EQ, Mackie monitors, Hosa MIDI cables (can't think of any other pertinent info). All tested and retested for possible causes for this channel problem, but all signs point to back to M1!?
So as much I enjoy M1 (and have created nearly 400 patch/combos for it) it's so annoying to work with, I'm having to avoid it now! What a shame!
Thanks for any help!
Last edited by SciFiArtMan on Sun Jul 26, 2015 6:45 am, edited 1 time in total.
-
- Posts: 9
- Joined: Mon May 25, 2015 9:28 pm
UPDATE: It's still driving me nuts! Seems like it's doing it more than ever, rendering my exciting new sonic tool all but useless (not to mention extremely irritating!) And now even once I do get it working correctly, it will be hard to trust it enough to use in an actual production!
After removing and reinstalling everything, I can't imagine what would cause this!?!? I didn't install the stand-alone version - wonder if there's any way that could make a difference!? I'll explore that idea...
After removing and reinstalling everything, I can't imagine what would cause this!?!? I didn't install the stand-alone version - wonder if there's any way that could make a difference!? I'll explore that idea...
-
- Posts: 9
- Joined: Mon May 25, 2015 9:28 pm
Time for the next exciting chapter of the never-ending saga!
So, of course, I stopped using dear ol' M1 KLC plugin due to its crazy behavior in my Sonar Artist DAW. But I was retooling a slightly older tune with a nylon guitar lead, and I remembered I had created a very nice nylon guitar in M1 (even fixing the odd upper octave issues - tricky!), so I loaded up the old dinosaur, and found the patch sounded fantastic in this arrangement! (I really dig M1 - when it works correctly) But before long it starts its old tricks of only coming from the right channel, until I reset the MIDI, then repeat processes endlessly!
Of course, through the weeks and months of trying to resolve this issue I've tried every fix I could imagine - reinstalling entire plugin - with and without the stand alone, redownloading from Korg, even re (what's it called...) reauthorizing the plugin, updating and checking errors in Sonar and every step in the audio chain, etc. etc.
But, while testing this fairly natural-sounding nylon guitar patch (it has a little chorus and a hint of reverb within M1) along with the eventual loss of the left channel, I noticed the patch sounded very odd - like it had a med-slow tremelo effect and deep reverb tone to it! And for some reason that reminded me of some copyrighting watermarking effects you might get from a demo with such occasional sonic weirdness. But then all disappears for a while once I reset the MIDI within Sonar.
So is this a demo copyright effect a possibility? I downloaded the file (multiple times) directly from Korg, and the authorization always seemed to go well, and afterwards showed as fully registered.
One slightly unusual, and maybe a no-no, is I have installed this on my music computer (the one with the weird channel issue), AND on my modest laptop (on which I created over 400 patches for it with no issues of any kind). Could dual installation trigger some odd effect on the authorization of the plugin on my music box!?
I don't know! I'm running out of ideas! I really wish it just would work right and I could fine-tune and enjoy all these cool patches/combos I've made and move on with my pathetic life!!!
Maybe its' a very subtle alien attack from the 12th dimension! Or maybe Sonar and M1 just hate each other!? I'm so confuzzled!
SFAM
So, of course, I stopped using dear ol' M1 KLC plugin due to its crazy behavior in my Sonar Artist DAW. But I was retooling a slightly older tune with a nylon guitar lead, and I remembered I had created a very nice nylon guitar in M1 (even fixing the odd upper octave issues - tricky!), so I loaded up the old dinosaur, and found the patch sounded fantastic in this arrangement! (I really dig M1 - when it works correctly) But before long it starts its old tricks of only coming from the right channel, until I reset the MIDI, then repeat processes endlessly!
Of course, through the weeks and months of trying to resolve this issue I've tried every fix I could imagine - reinstalling entire plugin - with and without the stand alone, redownloading from Korg, even re (what's it called...) reauthorizing the plugin, updating and checking errors in Sonar and every step in the audio chain, etc. etc.
But, while testing this fairly natural-sounding nylon guitar patch (it has a little chorus and a hint of reverb within M1) along with the eventual loss of the left channel, I noticed the patch sounded very odd - like it had a med-slow tremelo effect and deep reverb tone to it! And for some reason that reminded me of some copyrighting watermarking effects you might get from a demo with such occasional sonic weirdness. But then all disappears for a while once I reset the MIDI within Sonar.
So is this a demo copyright effect a possibility? I downloaded the file (multiple times) directly from Korg, and the authorization always seemed to go well, and afterwards showed as fully registered.
One slightly unusual, and maybe a no-no, is I have installed this on my music computer (the one with the weird channel issue), AND on my modest laptop (on which I created over 400 patches for it with no issues of any kind). Could dual installation trigger some odd effect on the authorization of the plugin on my music box!?
I don't know! I'm running out of ideas! I really wish it just would work right and I could fine-tune and enjoy all these cool patches/combos I've made and move on with my pathetic life!!!
Maybe its' a very subtle alien attack from the 12th dimension! Or maybe Sonar and M1 just hate each other!? I'm so confuzzled!
SFAM
One slightly unusual, and maybe a no-no, is I have installed this on my music computer (the one with the weird channel issue), AND on my modest laptop (on which I created over 400 patches for it with no issues of any kind). Could dual installation trigger some odd effect on the authorization of the plugin on my music box!?
---
So if on the laptop there's no problem, then whats the pc specs?
Did you try different settings on M1> Preferences> Audio Device> Driver type: ASIO/DirectSound with different settings?
Possibly if the Buffer Size/Sample Size/Latency etc. is too small xx.xx ms could corrupt sounds glitches etc.
Compare and verify the same settings/components as the laptop specs.
Software vst M1 etc needs powerfull and fast PC and enough memory to be glitch free.
---
So if on the laptop there's no problem, then whats the pc specs?
Did you try different settings on M1> Preferences> Audio Device> Driver type: ASIO/DirectSound with different settings?
Possibly if the Buffer Size/Sample Size/Latency etc. is too small xx.xx ms could corrupt sounds glitches etc.
Compare and verify the same settings/components as the laptop specs.
Software vst M1 etc needs powerfull and fast PC and enough memory to be glitch free.
-
- Posts: 9
- Joined: Mon May 25, 2015 9:28 pm
Thanks for the reply and insight, BradKorg! I'll explore your ideas this evening.
FYI, my computer specs (in case this info helps!) are:
Laptop = i5 M560 2.67ghz with 8mb ram through integrated Nvidia HiDef audio card.
Music Box = i7-4790 with 16gb RAM through a Focusrite Scarlett 2i4 USB audio interface.
I've produced dozens of complex songs with my music rig, and have used 100+ plugins throughout the process, and never had any audio issues with anything but this M1 plugin, beyond the initial set-up pains of any new computer.
Obviously, this M1 plugin is experiencing some kind of corruption within this system, so I'll take your ideas and explore the possibilities. Why the plugin will always work perfectly when first attempted (via opening a song file, for example), and then may work for a couple of hours or only a few minutes before the left channel drops out, etc., mystifies me! I keep thinking some part of the initial installation got corrupted, and with all my attempts to remove every trace and reinstall, I'm missing an important piece of the puzzle!?
Anyway, I'll keep fighting the good fight (it's just so depressing when it fails!!!!) Thanks again BradKorg!
FYI, my computer specs (in case this info helps!) are:
Laptop = i5 M560 2.67ghz with 8mb ram through integrated Nvidia HiDef audio card.
Music Box = i7-4790 with 16gb RAM through a Focusrite Scarlett 2i4 USB audio interface.
I've produced dozens of complex songs with my music rig, and have used 100+ plugins throughout the process, and never had any audio issues with anything but this M1 plugin, beyond the initial set-up pains of any new computer.
Obviously, this M1 plugin is experiencing some kind of corruption within this system, so I'll take your ideas and explore the possibilities. Why the plugin will always work perfectly when first attempted (via opening a song file, for example), and then may work for a couple of hours or only a few minutes before the left channel drops out, etc., mystifies me! I keep thinking some part of the initial installation got corrupted, and with all my attempts to remove every trace and reinstall, I'm missing an important piece of the puzzle!?
Anyway, I'll keep fighting the good fight (it's just so depressing when it fails!!!!) Thanks again BradKorg!
-
- Posts: 9
- Joined: Mon May 25, 2015 9:28 pm
Thanks again for your input and reply, bradkorg!
So, I bought a new VSTi the other day (AtmosFire, dedicated cinemascape sampler fun) and after a while it started doing this panning right effect too! So I downloaded MuLab DAW to see if the issue was with Sonar Artist, and the same issue appeared in MuLab as well!
So this tells me it's probably not M1, AtmosFire or Sonar, and more likely my Focusrite Scarlett 2i4 interface or some setting or malware within my system!? I have already gone through every setting in regards to audio or MIDI or ASIO and buffers in Sonar and MuLab, with no change with this issue.
Another interesting observation; I noticed in M1 after resetting the plugin (by re-selecting the patch, only way!) if I played softly the panning would stay centered, but as I increase the velocity of my playing, especially in higher registers, it would "trigger" the right only panning issue, which kind of reminds me of some sort of "shorted" cord effect.
I thought I should heavily test or replace all my cords. BUT this right pan issue clearly shows on the individual track output meter and on the master output meter, so... a bad cord wouldn't cause that!? And this thought leads me back to some issue with the Focusrite interface, except ALL my other synth plugins work as intended!? And in my mind, an issue with the interface would only affect the actual audio, and not the panning difference within the plugin and displayed at the meters as recorded MIDI notes are played back!?
So, the mystery continues! I just hope I'm not missing something obvious (I've never felt completely confident with all the various buffer/latency settings and DAW set-up in general!)
And as I doubt this issue is directly related to M1 specifically, this will probably be the end of my posts (yeah!) unless further dialog occurs. But I wanted to post this on the distant chance that someone would stumble across it, and be able to help guide me (and maybe others) to clearer sailing ahead.
Thanks!
SFAM
So, I bought a new VSTi the other day (AtmosFire, dedicated cinemascape sampler fun) and after a while it started doing this panning right effect too! So I downloaded MuLab DAW to see if the issue was with Sonar Artist, and the same issue appeared in MuLab as well!
So this tells me it's probably not M1, AtmosFire or Sonar, and more likely my Focusrite Scarlett 2i4 interface or some setting or malware within my system!? I have already gone through every setting in regards to audio or MIDI or ASIO and buffers in Sonar and MuLab, with no change with this issue.
Another interesting observation; I noticed in M1 after resetting the plugin (by re-selecting the patch, only way!) if I played softly the panning would stay centered, but as I increase the velocity of my playing, especially in higher registers, it would "trigger" the right only panning issue, which kind of reminds me of some sort of "shorted" cord effect.
I thought I should heavily test or replace all my cords. BUT this right pan issue clearly shows on the individual track output meter and on the master output meter, so... a bad cord wouldn't cause that!? And this thought leads me back to some issue with the Focusrite interface, except ALL my other synth plugins work as intended!? And in my mind, an issue with the interface would only affect the actual audio, and not the panning difference within the plugin and displayed at the meters as recorded MIDI notes are played back!?
So, the mystery continues! I just hope I'm not missing something obvious (I've never felt completely confident with all the various buffer/latency settings and DAW set-up in general!)
And as I doubt this issue is directly related to M1 specifically, this will probably be the end of my posts (yeah!) unless further dialog occurs. But I wanted to post this on the distant chance that someone would stumble across it, and be able to help guide me (and maybe others) to clearer sailing ahead.
Thanks!
SFAM
-
- Posts: 9
- Joined: Mon May 25, 2015 9:28 pm
Wonderful idea, bradkorg!
My first thought was some kind of panning automation or similar modifier, but of course nothing was there/visible within Sonar (originally). I have an older Edirol controller (what a crappy keyboard this thing has!) that I'll give a spin. Makes perfect sense - let's see! I'll give my connecting MIDI cable a change-out too.
Thanks, as always!
My first thought was some kind of panning automation or similar modifier, but of course nothing was there/visible within Sonar (originally). I have an older Edirol controller (what a crappy keyboard this thing has!) that I'll give a spin. Makes perfect sense - let's see! I'll give my connecting MIDI cable a change-out too.
Thanks, as always!
-
- Posts: 9
- Joined: Mon May 25, 2015 9:28 pm
No more calls please - we have a winner!
Wow, do I feel dumb!!! (Yes I do!) It turns out my ol' trusted M-Audio Radium Controller is sending out erroneous CC10 signals! I don't have all the details as I just found this, but that's the culprit! It was actually pretty clearly right in front of me, but I didn't know where to look. I just never dreamed this keyboard would act-up like that (or maybe I've set this situation up without knowing it!). Now I'll try to figure out how to eliminate the source of this signal, or just move on to a new controller, if needed.
It all seems so obvious now, but... guess I need to spend a little more time familiarizing myself with the mechanics of the machines I use, and not just jump in and start composing away like a mad man!
Sorry to waste everyone's reading time with my long-winded saga!
And a big ol' THANK YOU to bradkorg for pointing me in the right direction, and getting me to look in such an obvious place for a solution!
(I once spent 10 minutes looking for a pair of scissors, only to find them when I went to switch the item in my right hand (scissors!) so I could better search through the junk drawer! And sadly this was free of any intoxicants! Ya just can't fix stoopit!)
Thanks again all, esp. bradkorg!
SFAM
Wow, do I feel dumb!!! (Yes I do!) It turns out my ol' trusted M-Audio Radium Controller is sending out erroneous CC10 signals! I don't have all the details as I just found this, but that's the culprit! It was actually pretty clearly right in front of me, but I didn't know where to look. I just never dreamed this keyboard would act-up like that (or maybe I've set this situation up without knowing it!). Now I'll try to figure out how to eliminate the source of this signal, or just move on to a new controller, if needed.
It all seems so obvious now, but... guess I need to spend a little more time familiarizing myself with the mechanics of the machines I use, and not just jump in and start composing away like a mad man!
Sorry to waste everyone's reading time with my long-winded saga!
And a big ol' THANK YOU to bradkorg for pointing me in the right direction, and getting me to look in such an obvious place for a solution!
(I once spent 10 minutes looking for a pair of scissors, only to find them when I went to switch the item in my right hand (scissors!) so I could better search through the junk drawer! And sadly this was free of any intoxicants! Ya just can't fix stoopit!)
Thanks again all, esp. bradkorg!
SFAM
-
- Posts: 9
- Joined: Mon May 25, 2015 9:28 pm
To wrap this thread up, and for anyone who might find this thread searching for a similar issue, I cured my misbehaving M-Audio Radium MIDI controller by spraying a quick blast of Caig DeOxit D50 cleaner/lube (one of those magical products - I use it all my guitars, basses, stereo and studio hardware with amazing results!) in all pots on the keyboard, and everything works like new now!
SFAM
SFAM