Some Things

[Atomsplitter]

I still can't seem to run the korg legacy collection stuff in cantabile yet it sort of hangs when scanning them.

Also im not sure why but i see in the plugins browser it's placing the TAL-U-No-62 synth as an effect, im guessing it may have audio inputs also perhaps so it's getting confused with the listing maybe.

If you are in Capture Keys Mode then on thesynth panel editor go to open program etc it does not cancel the capture so you cannot type text, maybe it should temp disable it until your back to a playing state in the app.

If you right click to hold a note too far to the left it holds the wrong key (not end one), doing this on the right triggers no held notes as expected though so it seems to be the left only. On testing with a not full window it happens always maximized on my large monitor it still happens but only nearer to the keyboard.

hope this is helpful, thanks

[bradr]

I still can't seem to run the korg legacy collection stuff in cantabile yet it sort of hangs when scanning them.

I think this will be fixed in the next build. I make some changes to plugin scanning and have has one user do some prelim testing who reports it now works.

Also im not sure why but i see in the plugins browser it's placing the TAL-U-No-62 synth as an effect, im guessing it may have audio inputs also perhaps so it's getting confused with the listing maybe.

Had a look at this and it's because the plugin is reporting kPlugCategEffect. Cantabile will make an educated guess based on number of inputs but only if the plugin reports kPlugCategUnknown. However, TAL-U, does have zero inputs, so it's a bit of a weird one... don't think this is Cantabile's fault.

If you are in Capture Keys Mode then on thesynth panel editor go to open program etc it does not cancel the capture so you cannot type text, maybe it should temp disable it until your back to a playing state in the app.

Yes, I've had a go at having it auto disable before but never succeeded. I will revisit this at some point. In the mean time, F12 is your friend.

If you right click to hold a note too far to the left it holds the wrong key (not end one), doing this on the right triggers no held notes as expected though so it seems to be the left only. On testing with a not full window it happens always maximized on my large monitor it still happens but only nearer to the keyboard.

That's a bug, thanks I'll look into it.

hope this is helpful, thanks

Definitely. Thank you.

[Atomsplitter]

I think this will be fixed in the next build. I make some changes to plugin scanning and have has one user do some prelim testing who reports it now works.

Sounds great

Had a look at this and it's because the plugin is reporting kPlugCategEffect. Cantabile will make an educated guess based on number of inputs but only if the plugin reports kPlugCategUnknown. However, TAL-U, does have zero inputs, so it's a bit of a weird one... don't think this is Cantabile's fault.

Hmm ok, maybe you could add a exceptions list inside cantabile then if there is a few oddly placed plugins it re-positions them to the correct part but it's not too major.

Yes, I've had a go at having it auto disable before but never succeeded. I will revisit this at some point. In the mean time, F12 is your friend.

Ok sure np, im guessing if theres trigger events you could do a 'if then' compare thing and if it's got a on value on menu trigger set to off, if close, ok, cancel then send a on trigger back in, but i have no idea about the setup so thats just a quick idea.

Anyway great app and support, many thanks

[TiUser]

<snip>...
Ok sure np, im guessing if theres trigger events you could do a 'if then' compare thing and if it's got a on value on menu trigger set to off, if close, ok, cancel then send a on trigger back in, but i have no idea about the setup so thats just a quick idea.

Anyway great app and support, many thanks

Don't make things too technical... Cantabile is already in a state that many great features are well hidden under the hood, quite logical and functional however, but practically a bit odd to use or at least not obvious to find and to remeber after a couple of weeks...

Just take the triggers in general... and add subsessions... you have to add a possibly long list, then you have to deactivate all unused ones for this subsession... technically ok and works, practically very inconvenient to use...

It's the tiny things, not only the mass of features - cantabile already has a lot of teh latter which most users do not recognize, do they?

[bradr]

If you are in Capture Keys Mode then on thesynth panel editor go to open program etc it does not cancel the capture so you cannot type text, maybe it should temp disable it until your back to a playing state in the app.

I've had another go at this an I think I've got something that works a little better. Cantabile will now not steal captured keys if focus is on an text box control. Unfortunately this only works for windows within Cantabile (not other processes) and it wont work in many plugin text editor fields (those that use VSTGUI), but it's better than nothing. Because this may not always be the desired behaviour, there's an option to turn it off and always capture.

Further, I've made it so that many common navigation keys are never captured (eg: home, end, arrows, tab, enter etc...).

This will be in the next build, probably tomorrow some time.

[bradr]

I still can't seem to run the korg legacy collection stuff in cantabile yet it sort of hangs when scanning them.

Should be fixed in build 2007 (available now)

Also im not sure why but i see in the plugins browser it's placing the TAL-U-No-62 synth as an effect, im guessing it may have audio inputs also perhaps so it's getting confused with the listing maybe.

Fixed in build 2007

If you are in Capture Keys Mode then on thesynth panel editor go to open program etc it does not cancel the capture so you cannot type text, maybe it should temp disable it until your back to a playing state in the app.

Improved in build 2007. Auto disables when on a text box.

If you right click to hold a note too far to the left it holds the wrong key (not end one), doing this on the right triggers no held notes as expected though so it seems to be the left only. On testing with a not full window it happens always maximized on my large monitor it still happens but only nearer to the keyboard.

Fixed in build 2007.

[Atomsplitter]

Thanks seems alot better, now im noticing a problem using rack files (Fixed now)

Edit -

Fixed this now all it required was a rescan of the plugins for the new location and it's working great, a cool idea for racks would be double click loading so you could just find a setup and instantly load it via the desktop etc, that would be a handy feature imo. Great work the korg plugins load in fine now

[bradr]

A cool idea for racks would be double click loading so you could just find a setup and instantly load it via the desktop etc, that would be a handy feature imo.

Shouldn't be too hard to do... I'll put it on the list.

[Atomsplitter]

Edited - Was wondering how to send from one rack to another i see you do it using the send to bit, simple and nice solutuion.

Edit 2 -

If using a whole rack as an effect a handy thing would be a global mix for the rack.

[bradr]

If using a whole rack as an effect a handy thing would be a global mix for the rack.

Not sure I fully understand what you're getting at... care to elaborate a little?

[Atomsplitter]

Not sure I fully understand what you're getting at... care to elaborate a little?

Sure, well basically this would only work if you were using a fx rack (so all the plugins in it were effects VSTs and it was being sent to from another rack), For each plugin we have Dry and Wet mixes but if you use these to shape the sound overall it will work great but if you then decided the effect was a bit strong you would have to adjust each wet/dry for the whole chain of plugins.

So the idea is if you have a long chain of effects it would be handy to have one at the top or very end just like on a single plugin but it would effect everything in the whole chain together. This way if you had a chain/rack of amp plugins say for example and had already used each of the wet/dry controls to shape a tone, this would allow you to keep that tone but make it less powerful if needed. Hope this makes sense.

[bradr]

Not sure I fully understand what you're getting at... care to elaborate a little?

Sure, well basically this would only work if you were using a fx rack (so all the plugins in it were effects VSTs and it was being sent to from another rack), For each plugin we have Dry and Wet mixes but if you use these to shape the sound overall it will work great but if you then decided the effect was a bit strong you would have to adjust each wet/dry for the whole chain of plugins.

So the idea is if you have a long chain of effects it would be handy to have one at the top or very end just like on a single plugin but it would effect everything in the whole chain together. This way if you had a chain/rack of amp plugins say for example and had already used each of the wet/dry controls to shape a tone, this would allow you to keep that tone but make it less powerful if needed. Hope this makes sense.

Ah OK... isn't this the same as gain slider on the rack? or are you talking about wet/dry mixers for the rack itself... interesting.

[Atomsplitter]

Ah OK... isn't this the same as gain slider on the rack? or are you talking about wet/dry mixers for the rack itself... interesting.

Yeah like a wet/dry for the rack itself, the gain seems to lower the volume if using it as an effect at the moment rather than effect the mixing, you could have a slot called rack globals etc maybe for this.

[Atomsplitter]

The bug where if you use a midi file to control a synth, then change preset it will jump back to the default preset is still there. It seems to do it when it loops or when you start and stop.

[bradr]

The bug where if you use a midi file to control a synth, then change preset it will jump back to the default preset is still there. It seems to do it when it loops or when you start and stop.

I've just tested it here and it seems to work fine - are you sure you've got "suppress program changes" enabled for the plugin in question (Plugin Slot -> Tools -> Suppress Program Changes)