SynthMaker

M2F (midi to float) bug?!

Archive · 2005 5 old posts

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

Shifrin ·

Hi,

I've tried using the M2F component but can't get it to work the way I'd expect it to. Check out the following schematic :-

Am I using the M2F right? As the 'poly to float' (using the analyser/graph to float) works just fine. I assumed the M2F would work the same way, but simplify things?!

Hmmm. Any info greatly appreciated 🙂

Shif.

jorge ·

Shifrin wrote: Am I using the M2F right? As the 'poly to float' (using the analyser/graph to float) works just fine. I assumed the M2F would work the same way, but simplify things?!

Hmmm. Any info greatly appreciated 🙂

Shif.

Maybe if you include a DirectSoundOut and switch it on it will work. Here is an example of an M2F in use:

The MonoToFloat component samples a running mono path whenever it receives a trigger. You must have a mono path with values going through it and that's why at the moment you need the DirectSoundOut or ASIOOut to be running. The analyser works in a different way, it keeps inside a separate section of compiled code that runs whenever it receives a trigger. So think of the analyser trigger as a "run" trigger and the M2F trigger as a "sample" trigger.

Here is another example of an adaptation of unkargherth lvlmeter schematic to work with the M2F:

[old link]

jorge ·

here's an example that works:

At some stage I'll try to change it to be more flexible and work even when there is not output device selected. Please note that while the Code inside the analyser runs only once when it receives a trigger, the mono code connected to the M2F in the schematic above runs constantly at sample rate.

Shifrin ·

jorge wrote: Please note that while the Code inside the analyser runs only once when it receives a trigger, the mono code connected to the M2F in the schematic above runs constantly at sample rate.

Ok, thanks for making that clear!!! If I want to use the code component for float maths then I'd be better off using the analyser method right, seeing as it's not running at sample rate but only when needed?!

Cheers,

Shif.

jorge ·

Shifrin wrote: If I want to use the code component for float maths then I'd be better off using the analyser method right, seeing as it's not running at sample rate but only when needed?!

Yeah, that's the best way, the code only runs when the analyser receives a trigger and it is very efficient compiled code although for float calculations you dont need efficient code.

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.