Smooth Sound Transition...

[Derek Cook]

I really like SST - very cool. Personally I have never needed to switch beyond one sound transition, so the current implementation works for me.

To the OP, Combi mode would be a good way to do what you want to achieve. All the patches you need are in the Combi - split and layered as you need. Keep your pad held down, and have the other sounds mapped across the keyboard as splits. If you need the same play range for both sounds, use the control surface (or foot pedal) to mix the sound you want to hear (there could be a better way of doing it, but I am away from my Kronos for a few days).

[Zeroesque]

[snip]
But neverheless, for the future, Korg should work on it, because the situation happens very often, that the second sound is not the right one and you have to change again, but you need the first sound playing.

While I normally defend Korg against us end users, I do see part of the point here.

I don't think it is "often," but I have certainly made the mistake of hitting the wrong patch change during a performance and had to let up on a sustained sound to grab the correct one. It would be interesting if the Kronos could check to see if sound "B" is currently silent (or hadn't even been used) and load the next patch in its place rather than replacing sound "A" and cutting that off.

My guess is that this type of stuff was discussed during design or construction, and I'm sure there are a lot of gotchas that I'm not (and couldn't possibly be) thinking of.

[danatkorg]

[snip]
But neverheless, for the future, Korg should work on it, because the situation happens very often, that the second sound is not the right one and you have to change again, but you need the first sound playing.

While I normally defend Korg against us end users, I do see part of the point here.

I don't think it is "often," but I have certainly made the mistake of hitting the wrong patch change during a performance and had to let up on a sustained sound to grab the correct one. It would be interesting if the Kronos could check to see if sound "B" is currently silent (or hadn't even been used) and load the next patch in its place rather than replacing sound "A" and cutting that off.

My guess is that this type of stuff was discussed during design or construction, and I'm sure there are a lot of gotchas that I'm not (and couldn't possibly be) thinking of.

I've added a feature request.

- Dan

[ErnstDabest]

[snip]
But neverheless, for the future, Korg should work on it, because the situation happens very often, that the second sound is not the right one and you have to change again, but you need the first sound playing.

While I normally defend Korg against us end users, I do see part of the point here.

I don't think it is "often," but I have certainly made the mistake of hitting the wrong patch change during a performance and had to let up on a sustained sound to grab the correct one. It would be interesting if the Kronos could check to see if sound "B" is currently silent (or hadn't even been used) and load the next patch in its place rather than replacing sound "A" and cutting that off.

My guess is that this type of stuff was discussed during design or construction, and I'm sure there are a lot of gotchas that I'm not (and couldn't possibly be) thinking of.

I've added a feature request.

- Dan

Could you perhaps add another feature request for "in-track sampling" & "tone adjust" ??
The topic is being discussed here in this thread ---> http://www.korgforums.com/forum/phpBB2/ ... 524#651524

[danatkorg]

While I normally defend Korg against us end users, I do see part of the point here.

I don't think it is "often," but I have certainly made the mistake of hitting the wrong patch change during a performance and had to let up on a sustained sound to grab the correct one. It would be interesting if the Kronos could check to see if sound "B" is currently silent (or hadn't even been used) and load the next patch in its place rather than replacing sound "A" and cutting that off.

My guess is that this type of stuff was discussed during design or construction, and I'm sure there are a lot of gotchas that I'm not (and couldn't possibly be) thinking of.

I've added a feature request.

- Dan

Could you perhaps add another feature request for "in-track sampling" & "tone adjust" ??
The topic is being discussed here in this thread ---> http://www.korgforums.com/forum/phpBB2/ ... 524#651524

Unless I'm mistaken, that's a thread about the Triton.
The Triton is long discontinued, so I wouldn't expect any software updates.
I was not involved with the Triton; at that time, my group was working on the OASYS PCI and OASYS keyboard.

[ErnstDabest]

Unless I'm mistaken, that's a thread about the Triton.

Indeed.
and by the viewcount you can tell there are lots of Triton owners who would like to have those neat features

The Triton is long discontinued, so I wouldn't expect any software updates.
I was not involved with the Triton; at that time, my group was working on the OASYS PCI and OASYS keyboard.

It's not really a <software> upgrade, per se.. As stated the Triton Extreme as well as Triton Studio already have these features
You could also find these same features "tone adjust" and "in-track sampling" in the Korg M3 I believe so does the OASYS since the M3
share most of OASYS features.... The firmware program to do this has already been develop it's written in the Extreme / Studio

So, it's just a matter of loading the same "in-track sampling" "tone adjust" program into Classic !!!

Perhaps you could run the idea by your colleages @Korg ??

[danatkorg]

Unless I'm mistaken, that's a thread about the Triton.

Indeed.
and by the viewcount you can tell there are lots of Triton owners who would like to have those neat features

The Triton is long discontinued, so I wouldn't expect any software updates.
I was not involved with the Triton; at that time, my group was working on the OASYS PCI and OASYS keyboard.

It's not really a <software> upgrade, per se..

Of course it is, per se and otherwise.

As stated the Triton Extreme as well as Triton Studio already have these features
You could also find these same features "tone adjust" and "in-track sampling" in the Korg M3 I believe so does the OASYS since the M3
share most of OASYS features.... The firmware program to do this has already been develop it's written in the Extreme / Studio

The features exist on different hardware, yes.

The Triton was released 16 years ago, and has been discontinued for a long, long time. It would be wise to not expect any future software updates for a long-discontinued instrument.

[ErnstDabest]

Of course it is, per se and otherwise.


The features exist on different hardware, yes.

It's not a contest, Dan.. I clearly said above that the software running the program already exist
The Tritons are compatible w/ eachother so there is no need for developers to design a new program specifically for the Classic
The same program running “intrack sampling” & “tone adjust” on the other Tritons could be loaded in the <Triton> Classic

The Triton was released 16 years ago, and has been discontinued for a long, long time. It would be wise to not expect any future software updates for a long-discontinued instrument.

Ford Model Ts can still be found on the road with brand new (rebuilt) engines, and all.


-----------------------------

Sometimes in a thread a discussion can change directions ( it happens) but I wouldn't want this thread to veer completly off topic
please, join me instead in this thread ---> http://www.korgforums.com/forum/phpBB2/ ... 524#651524 should
you wish to continue having this conversation ?

[NormC]

The topic is being discussed here in this thread ---> http://www.korgforums.com/forum/phpBB2/ ... 524#651524

LOL, there is no discussion there. Just lots of silly memes and photos.

[SanderXpander]

Of course it is, per se and otherwise.


The features exist on different hardware, yes.

It's not a contest, Dan.. I clearly said above that the software running the program already exist
The Tritons are compatible w/ eachother so there is no need for developers to design a new program specifically for the Classic
The same program running “intrack sampling” & “tone adjust” on the other Tritons could be loaded in the <Triton> Classic

The Triton was released 16 years ago, and has been discontinued for a long, long time. It would be wise to not expect any future software updates for a long-discontinued instrument.

Ford Model Ts can still be found on the road with brand new (rebuilt) engines, and all.


-----------------------------

Sometimes in a thread a discussion can change directions ( it happens) but I wouldn't want this thread to veer completly off topic
please, join me instead in this thread ---> http://www.korgforums.com/forum/phpBB2/ ... 524#651524 should
you wish to continue having this conversation ?

The fact that the Tritons are "compatible with each other" just means that they can read each others sounds. Mostly. You can't simply transfer an OS to different hardware like that. What do you think would happen if you swapped the mobo in the Kronos for a different architecture? Regardless of my own assumptions, I'm going to take Dans opinion on this, seeing as he's a lot closer to the fire, so to speak.

[danatkorg]

I clearly said above that the software running the program already exist

And I understood what you were saying.

The Tritons are compatible w/ eachother so there is no need for developers to design a new program specifically for the Classic
The same program running “intrack sampling” & “tone adjust” on the other Tritons could be loaded in the <Triton> Classic

As SanderXpander notes, the compatibility of the sounds does not mean that the software is the same.
Each model of Triton has its own version of the OS.
Software is not structured as you imply above. There are not separate "programs" which can be "loaded" for features such as in-track sampling.

What you are asking for is to transplant features from one long-discontinued codebase to a second long-discontinued codebase.
Both features involve multiple parts of the system, so it's not like you could just copy and paste a single chunk of code.
This would be a non-trivial development exercise.

More to the point: it's simply not going to happen. The Triton "Classic" was introduced 16 years ago, and replaced by the Triton Extreme 11 years ago; it's been discontinued for a long, long time. No more software updates should be expected.
If you want these features, my advice is to buy an instrument which has them.

[ErnstDabest]

The topic is being discussed here in this thread ---> http://www.korgforums.com/forum/phpBB2/ ... 524#651524

LOL, there is no discussion there. Just lots of silly memes and photos.

You know as the saying goes, a picture is worth a thousand words.. Please follow the link
I've respond to you, Dan, and SanderXpander -- Yes, it's doable folks !


..............

Sound stealing occurs, be it note events or EFX, when the KB is processing too much data planning ahead is really the best solution
For this you need to know the song that you are playing really well, make necessary arrangements like keymapping the keyboard into
different zones -- where one octave can be designated to string pads, another octave designated to piano or whatever..

What you are essentaially doing is programming your own COMBIs, thus having to change sounds (loading EFX) less often.

[danatkorg]

The topic is being discussed here in this thread ---> http://www.korgforums.com/forum/phpBB2/ ... 524#651524

LOL, there is no discussion there. Just lots of silly memes and photos.

You know as the saying goes, a picture is worth a thousand words.. Please follow the link
I've respond to you, Dan, and SanderXpander -- Yes, it's doable folks !

I've responded to you in the current thread, patiently and in detail. You appear unwilling to accept my answer, so I'm not sure what more there is to discuss.