KVR Audio

plastique · Post by **plastique** » Tue May 16, 2006 4:07 pm

glad I could be of help

Lagrange · Post by **Lagrange** » Tue May 16, 2006 11:19 pm

I've been utilizing the plug in ext with success. Is there a CC for the Kill Button?? Im ctrl'n it in EXT with Dashboard in FL.

http://img103.imageshack.us/my.php?imag ... fls5lw.jpg

I think there might a problem with FLS's switch smart disable functions and perhaps the Automatically Save Plugin Options.
Both seem to be default settings in th Fruity Wrapper.

Also FL in general sends manditory Start Stop Tempo messages to all MIDI out's.. P-L crashes FL when you try to configure CC control settings from MIDI out to P-L.. Hope this helps...

C

plastique · Post by **plastique** » Tue May 16, 2006 11:29 pm

I'm not familiar with how Fruity Loops handles (strictly) midi purpose plugins, but I'm going to test it.
How would I go about sending midi from a track to the PL and then to a synth ? I've only got the demo, so a quick guide would be great.
Start/Stop shouldn't actually be a problem.
I'll inverstigate how you could automate the kill button , unless you can tell me if FL has some parameter automation feature (like showing the available automatable paramters), the it would be just a case of finding the according paramter and set it to the min value for off and max value for on.

plastique · Post by **plastique** » Tue May 16, 2006 11:41 pm

didn't see the first picture link ...

It's fairly easy to give the kill button a cc since you use it inside eXT, so either

- you right click on the plugin title in the left column of eXT and choose "show parameter" and select "kill" and a new fader will appear on this column . If you click the box right next to it you'll see an option "map to cc" and you're done - or

- in the plugin window menu, hit "File", then "CC map" and add a new cc mapping for the "kill" paramter and set it to a cc

Lagrange · Post by **Lagrange** » Wed May 17, 2006 8:52 am

I mean there is no drop outs etc in ext

http://img103.imageshack.us/my.php?imag ... fls5lw.jpg

The diagram shows the linkage between the 2 + Dashboard..

C

Lagrange · Post by **Lagrange** » Wed May 17, 2006 8:54 am

Hey what about porting to receptor??

plastique · Post by **plastique** » Wed May 17, 2006 12:01 pm

Lagrange wrote:I mean there is no drop outs etc in ext

http://img103.imageshack.us/my.php?imag ... fls5lw.jpg

The diagram shows the linkage between the 2 + Dashboard..

C

Ah great

, I must have been misunderstanding something.

Lagrange wrote: Hey what about porting to receptor??

I haven't used resp. don't own a receptor, but what I read so far about how compatibility is tested between receptor and plugins with unknown compatibilitiy is to just try them out if they work or not (if I remember correctly there is a way to drop unsupported plugins into some folder ?).
No question I would help out if there are any changes needed to be made to make them 100% compatible.
In any case let me know what the rsults are if you have the chance to test it

The plugin is going to go public anytime soon, so the chances to find someone who is willing to test it on a receptor is going to be growing. I just want to get rid of any possible problems before releasing it, to make sure I don't get flooded with bug reports

Polyphonic Voice Limiter/Controller