Voice stealing in OS 3.02?

[laandodeman]

I have the impression that voice stealing has become more an issue since OS 3.02. Or is it just me?

I remember that with an earlier OS, voice stealing could be deminished by turning off channels in a combi. But I forgot how and and cannot find anymore what the solution was. It seems not enough to turn the part status from INT tot OFF.

[chini]

Logically what you have discovered would be a trade off for Korg adding more functions as they take a greater toll on the main processing chip. I have actually posted other threads concerning SST which certainly does not function with the same proficiency as it idid in OS2. One example of voice steeling that I have noticed is that a certain combie of mine that used to play its drum pattern immediately the keys are struck starts to play then suddenly gets cut off! I have not changed the parameters at all and have made sure the new meters display function is not switched in on the global page but still the drum pattern stops playing after a second. If I re-select the combie and retrigger the combie again the pattern plays correctly. Of course in a live situation (which is what I use the Kronos for) this is ridiculous! I will be posting this fault on the thread entitled "bugs still remaining in OS3" and possibly we should underline this problem so that Korg can see it is definitely an issue!

Thanks for posting!

[GregC]

Logically what you have discovered would be a trade off for Korg adding more functions as they take a greater toll on the main processing chip. I have actually posted other threads concerning SST which certainly does not function with the same proficiency as it idid in OS2. One example of voice steeling that I have noticed is that a certain combie of mine that used to play its drum pattern immediately the keys are struck starts to play then suddenly gets cut off! I have not changed the parameters at all and have made sure the new meters display function is not switched in on the global page but still the drum pattern stops playing after a second. If I re-select the combie and retrigger the combie again the pattern plays correctly. Of course in a live situation (which is what I use the Kronos for) this is ridiculous! I will be posting this fault on the thread entitled "bugs still remaining in OS3" and possibly we should underline this problem so that Korg can see it is definitely an issue!

Thanks for posting!

not making any excuses. I am not sure of too many keyboardists use the drums at gigs

If you look at the voice list there are about 18,000 drum programs. That must be a resource hog to load them all. Some thought might be put into not loading them if they will not be used.

[chini]

[/quote]

not making any excuses. I am not sure of too many keyboardists use the drums at gigs

If you look at the voice list there are about 18,000 drum programs. That must be a resource hog to load them all. Some thought might be put into not loading them if they will not be used.[/quote]

Thanks for your intuitive point here.

I agree that one could go through a large majority of presets and disregard a lot of the drum patterns as well as banks of combies or programs and remove the sample RAM they use. I have for rxample excluded all the Japanese piano samples but only replaced the revealed RAM space with my own samples (Ensoniq ESQ-M/Oberheim Matrix 6r/EX-8000 wave samples etc)

I only actually use drum patterns when I am doing solo gigs when triggering one note loops is impractical between patch changing. When I am with my whole band of course they never get used!

However the point still remains that there is definitely an issue here. Whatever Korg have done to bring us new functions with OS3, unfortunately it appears it has been for the sacrifice of performance regarding SST and voice steeling which for my purposes is unacceptable.

Maybe I should ask this question with a new thread but do you by chance know if it is possible to revert back to the older OS without disturbing my 2 SSD drives?

[GregC]

not making any excuses. I am not sure of too many keyboardists use the drums at gigs

If you look at the voice list there are about 18,000 drum programs. That must be a resource hog to load them all. Some thought might be put into not loading them if they will not be used.[/quote]

Thanks for your intuitive point here.

I agree that one could go through a large majority of presets and disregard a lot of the drum patterns as well as banks of combies or programs and remove the sample RAM they use. I have for rxample excluded all the Japanese piano samples but only replaced the revealed RAM space with my own samples (Ensoniq ESQ-M/Oberheim Matrix 6r/EX-8000 wave samples etc)

I only actually use drum patterns when I am doing solo gigs when triggering one note loops is impractical between patch changing. When I am with my whole band of course they never get used!

However the point still remains that there is definitely an issue here. Whatever Korg have done to bring us new functions with OS3, unfortunately it appears it has been for the sacrifice of performance regarding SST and voice steeling which for my purposes is unacceptable.

Maybe I should ask this question with a new thread but do you by chance know if it is possible to revert back to the older OS without disturbing my 2 SSD drives?[/quote]

i think there was a post about going back to 2.2. google search for that

another idea is to have custom pcg files on a usb. have 1 pcg for your band gig, another pcg for your solo work.

final idea is to trouble shoot any custom combis. they can be a surprise voice hog.

3.0.2 is a very good upgrade. i dont know whats a bug and what is not. if there is some kind of resource hog bug, i am confident Korg is addressing it.

might be worthwhile to stick with it for 2 or 3 weeks.

[DanielD71]

not making any excuses. I am not sure of too many keyboardists use the drums at gigs

If you look at the voice list there are about 18,000 drum programs. That must be a resource hog to load them all. Some thought might be put into not loading them if they will not be used.[/quote]

Thanks for your intuitive point here.

I agree that one could go through a large majority of presets and disregard a lot of the drum patterns as well as banks of combies or programs and remove the sample RAM they use. I have for rxample excluded all the Japanese piano samples but only replaced the revealed RAM space with my own samples (Ensoniq ESQ-M/Oberheim Matrix 6r/EX-8000 wave samples etc)

I only actually use drum patterns when I am doing solo gigs when triggering one note loops is impractical between patch changing. When I am with my whole band of course they never get used!

However the point still remains that there is definitely an issue here. Whatever Korg have done to bring us new functions with OS3, unfortunately it appears it has been for the sacrifice of performance regarding SST and voice steeling which for my purposes is unacceptable.

Maybe I should ask this question with a new thread but do you by chance know if it is possible to revert back to the older OS without disturbing my 2 SSD drives?[/quote]


could you share your combi and users could test it and see if the issue occurs also on their side.

Regards,

[SanderXpander]

Someone also noted a significant improvement after enabling "auto-optimize RAM" (though I think it normally should be enabled by default).

[psionic311]

I've noted quite a bit of voice stealing after installing OS3. Here's what I found to reduce it. These are all under GLOBAL/Basic/Basic.

-- enable Auto Optimize RAM
-- Internal Headroom set to STANDARD
-- set Mute Mode to "LIVE" (not Studio) // then be sure to Mute unused tracks in your Combi/Seq and SAVE.

These can be found on pages 756 and 757 in the updated Parameter Guide that comes in the Manuals folder when you download and extract OS3.

I also set Knob/Slider Mode to "Catch", just in case any loose controller gets jostled while playing the Kronos. This will prevent any sudden jumps to a new parameter value that may or may not affect the sound you're playing.

And of course, don't forget to save (Write) the GLOBAL settings after you make those changes. HTH

[psionic311]

Logically what you have discovered would be a trade off for Korg adding more functions as they take a greater toll on the main processing chip. I have actually posted other threads concerning SST which certainly does not function with the same proficiency as it idid in OS2. One example of voice steeling that I have noticed is that a certain combie of mine that used to play its drum pattern immediately the keys are struck starts to play then suddenly gets cut off! I have not changed the parameters at all and have made sure the new meters display function is not switched in on the global page but still the drum pattern stops playing after a second. If I re-select the combie and retrigger the combie again the pattern plays correctly. Of course in a live situation (which is what I use the Kronos for) this is ridiculous! I will be posting this fault on the thread entitled "bugs still remaining in OS3" and possibly we should underline this problem so that Korg can see it is definitely an issue!

Thanks for posting!

not making any excuses. I am not sure of too many keyboardists use the drums at gigs

If you look at the voice list there are about 18,000 drum programs. That must be a resource hog to load them all. Some thought might be put into not loading them if they will not be used.

From what I understand, loading those 18,000 drum programs is a resource hog for RAM, not for CPU use. Polyphony/voice count is a calculation based on CPU resources, not RAM. When you install more RAM, you don't increase your voice count.

On the other hand, using features like synthetic string resonance, light level meters use CPU, and heavy use of IFX all take CPU resources.

[chini]

...this is what I figured too! RAM has nothing to do with CPU usage! It's obvious now that OS3 has compromised performance of the cpu for the luxury of its new features.

Personally the new features (aside from bug fixes) IMO are more a welcome luxury but not a necessity. At the moment, for my needs live on stage too much has been compromised to warrant sticking with OS3 and I am now looking into reverting back to OS2 as soon as I have figured out a clear path to do so without upsetting both SSDs !

Anyone know or got a link explaining the procedure to reverting to the previous OS ?

Cheers,

H

[SanderXpander]

From what I understood from the person who did it, the Kronos doesn't discern between an upgrade and a downgrade. Each OS install is fully self-contained. I haven't tried this myself, but it seems like you could just do a regular "upgrade" procedure with your favorite version.

[chini]

From what I understood from the person who did it, the Kronos doesn't discern between an upgrade and a downgrade. Each OS install is fully self-contained. I haven't tried this myself, but it seems like you could just do a regular "upgrade" procedure with your favorite version.

Cheers for the tip chap! (or chapess!)

You are probably right! However I did a search on this a week or so back and did come across a thread that suggested there may be a few issues when "downgrading". By any chance do you have a link to any thread on reverting the OS? I am not gigging for a few weeks yet so I have a little time to ponder over this! In the meantime I can still keep prepping in OS3: t's just disconcerting when preparing setlist sounds for a live show one hears notes/fx tails and such cutting off between patches when in the previous OS this never happened!

[chini]

...Here's the "downgrade" thread warning I was referring to...
http://www.karma-lab.com/forum/showthread.php?t=19232

...bit of an obscure thread but still I imagine the same issues would appear between OS3 and OS2 no?

[chini]

I've noted quite a bit of voice stealing after installing OS3. Here's what I found to reduce it. These are all under GLOBAL/Basic/Basic.

-- enable Auto Optimize RAM
-- Internal Headroom set to STANDARD
-- set Mute Mode to "LIVE" (not Studio) // then be sure to Mute unused tracks in your Combi/Seq and SAVE.

These can be found on pages 756 and 757 in the updated Parameter Guide that comes in the Manuals folder when you download and extract OS3.

I also set Knob/Slider Mode to "Catch", just in case any loose controller gets jostled while playing the Kronos. This will prevent any sudden jumps to a new parameter value that may or may not affect the sound you're playing.

And of course, don't forget to save (Write) the GLOBAL settings after you make those changes. HTH

Unfortunately none of these things make any difference in my case! Admittedly I am using very complex combies but the fact remains that they simply aren't playing as they were in OS2- sounds dropping out - tails between patch changes cutting off inadvertently etc.

[laandodeman]

I am afraid for me it's the same. It seems the mute button makes no difference anymore.