Automation linking bug with minimonsta & fabfilter time

kuniklo · Post by **kuniklo** » Tue Jan 29, 2008 5:41 pm

Try this:

1. load minimonsta vst on a track
2. load fabfilter timeless vst on the same track
3. adjust cutoff and resonance of minimonsta filter

Timeless filter #1 moves in sync. Anybody else seeing this?

System is iMac Core 2 Duo 2.4ghz
Live 7.0.2b5
built-in audio interface
OS X 10.5.1

kuniklo · Post by **kuniklo** » Mon Feb 04, 2008 5:32 pm

Bump. Anybody else seen this? It's reproducible in 7.0.1 too.

Post by **Alex** » Mon Feb 04, 2008 6:18 pm

Anybody else seen this?

Yes, we

We can confirm that issue and will investigate it.

Regards,
/Alex

kuniklo · Post by **kuniklo** » Mon Feb 04, 2008 6:21 pm

Great. Thanks for the update.

kuniklo · Post by **kuniklo** » Tue Feb 05, 2008 5:22 am

Looks like this also happens with Oddity + Timeless. Not sure if that helps.

jab · Post by **jab** » Tue Feb 05, 2008 6:11 pm

Hi kuniklo,

this linkage of the parameters is due to Midi messages that
are sent out by the Minimonsta when you change a parameter
and the 'MIDI Learn' function in Timeless.
If you turn off the switch in Timeless' 'MIDI Learn' section, the
plugin should stop to follow the Minimonsta's filter settings.

cheers,
Jan

kuniklo · Post by **kuniklo** » Tue Feb 05, 2008 6:14 pm

Ah ha. Thanks. It's weird that the GForce plugins output midi for parameter changes like that. It looks like changing the "Output Device" setting in Minimonsta to "None" also fixes this. Thanks!

jab · Post by **jab** » Tue Feb 05, 2008 6:16 pm

Hi kuniklo,

thanks for letting us know.
I will lock this thread now.

cheers,
Jan

Automation linking bug with minimonsta & fabfilter time

Automation linking bug with minimonsta & fabfilter timeless