Song to Combi

[Orbvs_Tomarvm]

Hi, can you convert a song in sequencer mode to a combi? Thanks.

[voip]

If the intention is to be able to recreate a complete song, including audio tracks, in a Combi, and to play the whole thing live, then the simple answer is no. If the song uses internal Timbres only, then there are some possibilties, such as using external keyboards, or other MIDI sources, on different MIDI channels, or zoning of the Timbres, plus the audio tracks could be combined into a long Sample (or samples) and that/those Sample(s) could be mapped to keys and played that way, but it would be far from straightforward.

.

[toeti]

Hi,

I think you are talking about the timbres?

If I know it right, it's only possible in the other direction, from combi to song.

[bpoodoo]

It's a mostly manual process except for copying effects.

You may have seen this topic on the Triton Extreme section:

http://www.korgforums.com/forum/phpBB2/ ... p?t=128680

[Orbvs_Tomarvm]

Hi, thanks for all the replies.

the main reason for the post was because the smooth sound transition "SST" was not working moving between songs i was putting together in sequencer mode. every time i go forward (or backward) to next song, you get that horrible tritonesque midi cutoff.

i erroneously thought this was probably because this function didn't work in sequencer mode.

so i painstakingly copied a couple of songs to combi mode, but the same crappy cutoff is happening there too, just with the combis i made.

can anyone tell me what i'm doing wrong? the SST was one of the main selling points of the kronos for me!

Thanks.

[Dan Stesco]

Sometimes the SST not working properly due the limit of data processing. Mostly SST problem coming from effects counting. The interruption can be caused by the number of effects and the type of effects used. For example O-Verb consume a lot of data, try to use only one or maxim two O-Verb in a combi. Delete any unused IFX. Try to reduce the IFX slots. Select the not used timbre as status off. The timbre consume resources even is Muted or different MIDI Ch and not play. Optimise the combi, check if both OSC is important for each timbre. If not, select only the OSC you have to use. Sometimes the second OSC start at SW and maybe is not important.

[Orbvs_Tomarvm]

well, that is the answer i was absolutely dreading. thank you though.

is there a list of effects that sap the cpu the most?

for example i use a lot of rotary speakers, phasers and yes - that o-verb

thank you.

[KK]

To see if you have effects or notes overdose in a program/combi, look at the CPU meters under Perf Meters while playing. Any effect assigned to something else than 000 (No Effect) will use CPU, even when turned Off.

Experiment adding 12 IFX that serve no purpose and at off and then go back to the Perf Meters tab. You will see how several effects are CPU hogs.

[Orbvs_Tomarvm]

this info is vital and very useful. thanks very much.

i've basically put three months of very hard programming in, that looks like needing completely overhauled, so any tips and tricks to ease the pain of that is so gratefully received.

one question: do both combi/songs between which the SST has failed need drastic simplification? can you have ANY complicated patches? And, is the whole thing just completely unpredictable so that you have to keep experimenting dropping an oscillator here; an effect there, between BOTH patches where the SST has failed?

thanks again. (floundering in the dark)

[Orbvs_Tomarvm]

I have mitigated the problem:

creating a simple patch (like a final chorus) to link the two complicated patches. eg (darkside of the moon is my present project):

to link the tracks 'brain damage' and 'eclipse', create a separate 'simple' patch for the buzzy/string theme at the end of brain damage (that i had originally placed on the eclipse patch). and have that patch placed between the two complicated patches, so as not to wallop the cpu. you can do that on all tracks, as links either as the remainder of the previous song or the start of the next. just chop a chorus off as a stand alone patch; remove all unnecessary effects and oscillators, and use that to SST into the next big patch/song.

yet to split them up to test it, but theoretically that should work i think

cheers everyone. you're such a helpful community

[Dan Stesco]

Using Layer or Split function from display will force the system to add more effects. Maybe is better to check which effects are in use and manage yourself.
For example if two timbres use Chorus, Load the Chorus in MFX then send for each timbre the signal to have enough chorus for both. Remember that MFX is a send return signal routing so 100% Fx mean 50% dry and 50% Fx. Except if output L/R is off for that timbre. So don't use Eq, Exciter, Limiters, Compressors to avoid the unphase signal and bed sound.
Manage the split, layers yourself and add only useful IFx, MFx,TFx to avoid any cut SST sound.

[pete.m]

If you're performing the whole album as a set, then one way of doing it would be to have the whole set - all the songs - running as one long song.

You can copy any tracks from any song into another song, so if the first song is (say) 00 bars long, you could copy what would normally have been the second song over to anywhere after that point on the first one, and so on for the entire set.

That would be simple enough. You'd just need to spend some time inserting program changes, FX changes, pan, volume, time sigs etc at the point where the songs and individual tracks change throughout the set so that everything changes as you want it. SST would cease to be a problem doing it this way.

As for the problem with heavy CPU is concerned, you could take a mix of some of the individual tracks in each song, and then insert the resulting audio file as an audio track to remove that pressure.

I don't know if there's a limit to the number of bars in one song, but I think it should work as long as that isn't an issue. If you decide to change the order later on, it would be easy enough to move the various sections around or even insert new sections, and of course you'd still be able to save the old version. It might take you a couple of hours to set everything up for the first time, but it would solve your problem.