Suggestion Box

'embedded module' user-defined capability

MidiFire is to me much like other modular software that you can connect modules up together to form completely customized working patches; a structured, object[module]-oriented style of programming app with 'cords' interconnecting the functions. I see the user-defined module to be a great help for organization of complex logic ideas and functions as patches grow. Embedded Scenes within Scenes ??, adhering to the nomenclature that is already in place. Instead of all the snippet-blocks/modules populate the canvas using the merged function, it is encapsulated into individual module with inlets/outlets. This being an option of the merge we already have available.

The idea is to be able to embed the more complex modules within a single user-defined module, similarly, in Plogue Bidule you have groups, in MaxMSP, PureData, you have sub-patches that you can later call up for other needs. 

As power and complexity grows, I see the canvas becoming extremely busy . . .

It can have inlets and outlets. The number of each, user's choice? at least one inlet, one outlet (depends..)
We have Global Vars now, so passing data would be a breeze too.

On the main canvas:

[inlets]
{
my-embedded-module
               #........ --> inside has several modules of Stream Byter, Range filters etc... 
}
[outlets]

May not be even possible, but in any case, I hope this makes sense to everyone

g~

Some random ideas from putting together some scripts the other day:

- Have a straight up BLK command in Stream Byter, instead of having to use XX = XX +B

- Perhaps have an END or ABT command in Stream Byter that just terminates script execution for the current event? (Not sure if this actually provides any meaningful performance benefit)

- Allow note name literals in script that are translated to hex codes at install time -- for example, being able to type "[C#3]" instead of having to look up a chart and type "31"

- My controller sends out fairly frequent MIDI active sense messages, basically causing continuous flashing on my screen -- an alternative display indicator for active sense activity (or just the ability to ignore it) might be nice

>>> Nic: upcoming version 1.10 has a setup option to ignore all incoming active sensing messages (defaulted to ignore)

- Have a Stream Byter command that can invoke Panic (so I can trigger panic from my controller)

>>> Nic: good chance of that happening soonish

Thanks for the great product!

>>> Nic: Thanks for kind words. Will consider other suggestions.

Hi carnbot,

I plan to look into this!

Regards, Nic.

Hi Nic,
I just started with the app today, please forgive me if I'm posting in the wrong location or any other breaches of etiquette I may be committing!

1.) My biggest issue right off the bat: It would be very helpful if the scrollable block menu was made resizable in the Mac OS version. My laptop screen is 1920 pixels wide, but all the names of the modules in the menu are truncated with "..." so I can't see what I'm about to click on.

2.) Similarly, it would be nice if the blocks themselves could be resizable horizontally so that the name was not truncated there either.

3.) Could an Undo function be added? I hit Merge and it overlaid the merge scene on top of the existing one. Just wanted to back out of the operation.

4.) A way to select multiple blocks and move them all at once?

5.) I absolutely LOVE gary's idea of encapsulating scenes into their own blocks. This makes the display hierarchical, with every block potentially containing a scene of multiple sub-blocks, each of which... etc.

Thanks for listening!

Steve

Hi Team,

First of all, i have discovered Midifire full capabilities and i really like the power of StreamByter (2).

When doing conditional actions depending on a variable, i’m missing the capacity to do exclusive test: an ELSE keyword would be great for that.

Do you plan to add this feature?

>>> 30 Dec 18 - Nic: I've wished for this myself at times. I will see what I can do.

Thanks, 

BenG