crash when using +I in a scene

Look forward for the update and I am curious, will midifire get syntax update similar to streambyter AU ver. 1.5 ?
Are these two apps bundled in app store ?

Also a suggestion to reduce number of IFs

IF N2-3 5-7 20-2A
...
...
End

This may replace 7 nested IFs

Hi slmnv ,

> will midifire get syntax update similar to streambyter AU ver. 1.5 ?

Yes, the forthcoming update will include the new StreamByter

> IF N2-3 5-7 20-2A

The N2-3 ... notation is the old pattern matching style whereas an IF is a StreamByter II rule, so it's a little problematic to do this.

Here's a little workaround:

# save the event into I0-2
ASS I0 = M0 M1 M2

# convert the event to 'special' sysex if matches
N2-3 5-7 20-2A = F0 7D 22 F7

# if we matched our special sysex
IF M0 == F0 7D 22 F7
  # restore the event back into M0-2
  ASS M0 = I0 I1 I2

  # do the processing here
END

Regards, Nic.

Hey Nic!

1) About MidiFire being an auv plug-in, I completely understand what you mean. I still think it would be nice to be able to use individual MIDI outputs as auv3 midi machines. Perhaps making MidiFire be able to act as a host for AUv3 plugins instead could work too. I would gladly throw in some cash on an IAP for this. In such case, ApeMatrix has done an amazing job with their AUv3 hosting. The way you can resize the plugins is amazing.

But in anyway, an example of what I mean with my terrible explanation of why AUv3 support would be amazing:

ApeMatrix doesn’t allow you to isolate midi Channels by itself.

Being able to load “MidiFire X” as an input machine on one of ApeMatrix’s inputs would make it all quite tidier.

Right now, I am doing the following to get around this:

Sending all MIDI signals through MediaFire “0” and then utilizing Mozaic Engine (the app) to split the signals and filter them accordingly. The problem with this setup is that for every independent channel that I want to route in ApeMatrix, I need to have an input “slot” wasted on Mozaic just to filter.

My understanding is that StreamByter is actually very similar to Mozaic, so utilizing it would end up in the same workflow. Am I correct?

I think MidiFire + ApeMatrix work amazingly, but ApeMatrix’s limitations about loading virtual and real interfaces isn’t great. Although this is something ApeMatrix should hopefully eventually adopt, as of now having MidiFire be able to be an AUv3 midi plugin would be amazing. Would probably save a lot of performance but I’m obviously not sure about this.



2) yes I have noticed you can pan the view around the canvas: I still think it’s too small for complex setups (rerouting several midi Channels, notes and program changes to interface my PODHD500x with my iOS device).

I do 3D work and I’m very used to using nodes to program textures and stuff, so perhaps I’m just “abusing” the system with ease, but yes I do believe a canvas 2 to 3 times bigger would be a huge improvement. Having the option to resize such canvas at will would be the best (or have it extend automatically as the “finger cursor” drags nodes outside of the allowed area).


Now, let me just say a few more things...
MY OTHER (less important perhaps) SUGGESTIONS:

1) it would be nice to be able to pan the view with one single finger WHEN not touching on a node (and being able to drag 2 fingers independently of whether one is touching the nodes or not as an alternative). To me it feels much more natural to be able to pan the view with a single finger. Maybe this is just me, but it feels as if all the node software I use on PC would translate in this way (Substance Designer, Blender, Unreal’s Blueprint System and Material Editors... etc).

Being able to pan with a single finger when not touching any node would feel very natural to me but perhaps this is only my preference. However I’ve noticed there’s no command associated to touching an empty spot on the canvas so perhaps having this as an option could make more users than me very happy.

2) alternatively, having the [+] menu pop up on an extended press on an empty spot on the canvas would be nice too. Also having such nodes pop up where the cursor activated such pop up menu as opposed to on the top left corner would be very appreciated as a lot of “traveling” across the canvas occurs because of this positional property of the new nodes.

3) I love the idea of scene merging and assigning! Is there anyway this part of the UI interface could be shared with the “modules” to alter midi?

Having MIDI outputs and inputs be the first thing to show on the [+] menu means that a lot of scrolling has to occur just to get to such modules (I often have around 10 inputs and outputs so it’s 20 things I need to scroll away from everytime I add a new node).

Perhaps {inputs and outputs} AND {modules} should be separated or at least have the modules show up first as they are more utilized than inputs and outputs.

However, separating these would allow for a new [+] menu specific to the modules and scenes which could be very convenient.

As a small example, I’ve separated all the modules on the “Quick Monitors” scene so that I can easily get a single module out of it quickly in the same way I can add a StreamByter so to speak. Now I simply merge the desired module when needed (Vol, PC, CC, etc). These are essentially scenes with a single module. Although these are technically StreamByters, they could very well be their own nodes. Since we can merge scenes this is not necessary but streamlining the process of merging scenes and separating it from the load menu could allow for a more organic way of “creating” and “reusing” setups.

For now, I just label them specifically to know which scenes are “master scenes” and which are only “little modules” that I have created for my convenience.

I think the Merge menu could be very well together with the [+] menu if the UI undergoes a few changes; ultimately I think it would streamline the workflow but that’s just my opinion.

4) last thing, it would be nice to be able to change the canvas’s color to something different, having options like ApeMatrix would be amazing.

I am far too used to having my node networks spread across black canvases with grids. The grids help a lot for placement and organization and it would be nice to have both a displayable, snappable grid, and being able to change the canvas’ Background. I’m sorry if this comes off as offensive! I personally don’t like the fire on the canvas, in my personal opinion it makes the software look a bit “silly” and less professional. However, this is naturally quite a dumb remark from me and isn’t necessarily that important. The other points do feel more “relevant” for an update.


That being said, I still have to thank you for finally giving me the freedom to do what I want with MIDI. Your app is seriously fire 🥵🔥🔥🔥🔥🔥 and all of my suggestions are based on the fact that I don’t ever want to have to find an alternative to this: it is amazing and it fits my “already used to” node programming workflow.

Thank you so much for such a wonderful product! I will keep the advices in mind in case it ever crashes again like before, as of now I have simply redone my setup and made sure to back all of my scenes and nodes to my Files in case this happens again.

Thank you so much Nic! Sounds very promising.

I must say:

Thanks Nic! Sounds like some very nice features will be coming soon. Who knows? If I really dig the update I might just get the StreamByter itself once I have some cash to spare.

Thanks for the responses you’ve been very helpful and quick at it, something I assure you is deeply appreciated.