Vanguard and Kore 2

Am I the only one that has noticed that loading .ksd files for Vanguard doesn't work properly. I just decided to build my Vanguard library in Kore 2 and noticed that when I load a Koresound into Vanguard, Kore 2 is sending program change messages which make Vanguard's patch browser jump to the slot that the program change is sent to. I have to click on the Koresound again to load the proper patch. So to sum it up, when you click on the Koresound, it will initially load whatever Vangaurd sound that was allready in the Vanguard bank, not the Koresound. I also went into the Vanguard setup page and activated "ignore midi cc's" which is supposed to thwart this type of behavior, but it still receives the program changes. WTF. Is anyone else having this problem?


.-.
---
I figured out where the .ksd file is getting it from. When you "import plugin presets" it also imports the preset slot number. So when initially loading a Vanguard koresound, it makes Vanguard jump to that slot, but doesn't load the koresound. If you click again on the koresound, it will then load the Vanguard koresound. This blows.

.-.

 

There's a few plugins that also share that "feature". What's happening is that the plugin's edit buffer is loaded with the patch from the bank already loaded into the plugin, and not the preset that you want loaded. Double loading clears out the edit buffer.

ew

 

Yeah, I guess there's nothing I can do about it. Thanks for your response ew.

.-.
---
It actually went from bad to worse. When loading the .ksd from the Kore browser , the Vanguard koresound that was loaded when the song was saved is not remembered when the project is opened again. It loads the preset from the Vanguard factory bank that belongs in that slot. The workaround is to not use the Kore 2 browser, and just use the Vanguard preset management system and the preset will be remembered when the project is loaded again. The only thing is that the Vanguard interface will not show the correct patch name. It will only show the factory preset name that resides in that slot. Damn I wish these freakin plugins could be updated to work with Kore. This is the 5th plugin I've got that doesn't function properly with Kore.


.-.

 

This wouldn't be an issue if Kore supported fxp/fxb. You should request it by emailing NI support.

 

I'm praying for that! Then all of my plugins would work with Kore 2. As it stands now, a lot of my plugins have been downgraded to "legacy" status as far as Kore is concerned. Please NI, consider the option of using .fxb and .fxp files with Kore.



.-.

 

as far as I know, the format .ksd includes all of the tags, and fxb/fxp does not have support for metadata like this. vstpreset - the format used dby vst3 plugs - does, but is not very popular with developers.

 

Correct

Correct again.

ew

 

any idea if the two could be converted, or if either allows for creation of user-customisable categorised/nested tags?

(sorry, completely off-topic now)

 

No you're not. You actually raised a good point about this subject. I was actually going to reply to your post last night, but I got shut down by the thought that it might be pretty difficult for NI to make Kore 2 to load, save and browse it's own .ksd files and load, save and browse raw .fxp files. I honestly wouldn't care if the .fxp files could be tagged or not after they are saved. I was kind of stumped as to how this support would be implemented. Only NI would know how to do this because they understand a hell of a lot more about this stuff we do.


.-.

 

I think it's unlikely we would see the 2 formats running parallel in Kore as clearly ksd has a lot more to offer in terms of meta information. The best we can hope for is support for opening and saving fxb/p format files (as opposed to just importing them).

However in the context of Vanguard I think the issue is not so much fxb/p support in Kore as Vanguard does already load and save fxb/p from its own gui - the problem is that presets converted to ksd format do not load correctly the first time (as with several other synths such as iMposcar). This I think is more an issue to take up with the Vanguard developers as it is to do with how they handle presets internally rather than a limitation of Kore itself.

Hopefully you will get a better response than I did recently over Firebird

 

Yes. That's exactly what I thinking would be the solution, but as you said, that probably would not be implimented.

That would be cool.

Yeah, as per ew and you explained. I never realized that certain vsti have this type of behavior when used in Kore 2.

I figured it would be safer to complain to the host developers than to... LOL

I know. It seems as if General Custer got a more freindlly response from the Indians than... LOL



.-.

 

Yeah probably, but the problem is I doubt it's something they can do anything about - it's the VST itself that needs changing (I won't say "fixing")

at least (as I was told by the dev) the next version of iMposcar shouldn't have this problem - not sure if Vanguard is in active development any more though

 

Dave Spiers told me the same thing when I ran into him at NAMM in January.

ew