Description

Hey everyone,

I've made a new version of the main component to the M4L API, the bpatcher known as "M4L.SignaltoParameter".

There were two major flaws with the included one.

1) No control over actual max min values (just relative ones).

2) Everything happened at signal rate, which was almost always unnecessary, especially since the signal is downsampled dramaticaly before sending to live.remote~.

Solution:

I made a new bpatcher "M4L.FloatToParameter.JE", that allows you to set both relative and absolute max min values and, more importantly, runs at Max message rates. Now I can have more than 10 of them running at a time with much less of a load on the computer. If you have an application that still needs to turn signal to ctrl, then you can you a snapshot~ right before to get the same effect.

Hope you all find it helpful,

Jesse