slmnv
Converser

Posts: 22
|
Post by slmnv on May 2, 2019 2:02:37 GMT
I attached 2 scenes that if merged make a crash on my iphone and ipad. The way to recover is to uninstall and install back the app because at each start it loads the same scene and crashes. I created this test to reproduce what I saw in a big scene when I push a button. Seems to be modules using +I causing it. Load Ccccc then merge Bbbbb Please take a look if you you see the same.
|
|
nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 2, 2019 10:43:45 GMT
Hi slmnv, Thanks for reporting this and providing material to reproduce! I will look into this and fix for next update to MidiFire. Regards, Nic.
|
|
slmnv
Converser

Posts: 22
|
Post by slmnv on Jul 6, 2019 14:06:46 GMT
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
|
|
|
Post by enriquepage91 on Jul 7, 2019 0:25:26 GMT
Hello Nic, just bought MidiFire yesterday and I’m quite happy with the purchase.
I do have a problem relating to the one mentioned on this thread too.
I have spent around 7 hours setting up my Line 6 Pod in MidiFire and all of a sudden the app crashed and no longer allowed me to start it (since it tries to load this “corrupt” scene I guess).
My biggest fear is, If I uninstall and install the app again to fix the bug will I lose my Line6 Controller scene? It’s quite complex already and I wouldn’t want to have to rebuild it.
My second question would be: are there plans to make this app AUv3 compatible? That would be quite a blessing honestly. I’d also really appreciate a little more real state as the canvas can be filled quite easily particularly on an iPhone (where I mostly run MidiFire)..
Thank you so much for the app and support and I hope a fix can be found for this.
|
|
nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jul 7, 2019 6:51:16 GMT
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-2AThe 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 ENDRegards, Nic.
|
|
nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jul 7, 2019 7:09:28 GMT
Hi enriquepage91 , > I have spent around 7 hours setting up my Line 6 Pod in MidiFire and all of a sudden the app crashed and no longer allowed me to start it (since it tries to load this “corrupt” scene I guess).> My biggest fear is, If I uninstall and install the app again to fix the bug will I lose my Line6 Controller scene? It’s quite complex already and I wouldn’t want to have to rebuild it.Yes, if you uninstall the app, it will delete all your saved scenes. To recover from a corrupt working buffer that prevents the app from starting up, you need to use iTunes or iMazing/iFunbox on a computer and remove the file '_working_buffer.mfr' from MidiFire's 'Documents' directory. Alternatively, use the above to copy out your work from Documents, delete app and then re-install/replace, but removing the working buffer is easiest. If you never saved your work in a scene and the working buffer is the sum of your labours, then don't delete it but copy it out. I'm happy to repair manually if you email it to me. > My second question would be: are there plans to make this app AUv3 compatible? That would be quite a blessing honestly.MidiFire itself is never going to be an AU Plugin I'm afraid - it relies on being a 'main' application in so many ways. StreamByter and the Channel Strip are available as AUv3 plugins though. > I’d also really appreciate a little more real state as the canvas can be filled quite easily particularly on an iPhone (where I mostly run MidiFire)..Not wanting to state what may be obvious to you, but just in case! The canvas is bigger than the device screen. You can use two fingers to zoom and pan the canvas which I thought was reasonably large (same virtual size on iPhone and iPad). Or are you filling up the virtual canvas? I could expand that in the next update I guess. Regards, Nic.
|
|
|
Post by enriquepage91 on Jul 7, 2019 16:16:21 GMT
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.
|
|
nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jul 8, 2019 9:27:54 GMT
Hi enriquepage91 , > Perhaps making MidiFire be able to act as a host for AUv3 plugins instead;-) > My understanding is that StreamByter is actually very similar to Mozaic, so utilizing it would end up in the same workflow. Am I correct?That's one way of putting it. As an AU, yes StreamByter would sit in your workflow the same way. However, StreamByter is included in MidiFire as a built-in and in this setup you might have more flexibility. > 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).Noted. I'll expand the canvas for the next release so. > Being able to pan with a single finger when not touching any node would feel very natural to meThis is how it worked originally, but iOS has to distinguish whether you are touching a node or doing a pan and the delay involved made the pan vs move thing really bad, so I opted for specific 2 finger pan/zoom. > 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?I have had this requested before. I can't promise anything, but I will consider it. Regards, Nic.
|
|
|
Post by enriquepage91 on Jul 8, 2019 17:32:08 GMT
Thank you so much Nic! Sounds very promising. I must say: 1) About the 1 finger panning, it would be nice if we could activate the feature, perhaps the compromise will be acceptable to us. I completely understand if you really think it won't work though, but at least on iPhone using 2 fingers to pan takes a lot of real state and makes it hard to look at where you're moving, this is why I think it would be a great addition at least for the phone version.
2) Indeed, now that I have Midifire I'm wondering if it was even worth it getting Mozaic. Although i will say it has a few really nice things (amongst which being an AUV3 Midi Source, but it seems MediaFire will be getting AUV3 Hosting if I can read between the lines of your previous post? this would be amazing). Regardless, once I saw the StreamByter I realized that it was pretty much "the same" as Mozaic, conceptually at least. Although I will say the language for Mozaic is far more "readable" to humans; my only complaint about the Stream Byter, but it has so much more given the ecosystem it belongs in, that it really isn't such a big deal. It's just gonna take some time to learn the Syntax for MIDI.
3) I have had the crash-thing occur to me again while using the StreamByter I. Would it be possible to explicitly ask the user if he would like to reload the previous session once launching the app? I imagine perhaps this isn't happening by default as it could interrupt sessions that are currently running. I'm not sure but it is my best guess.
The thing though is, iFunBox has always given me issues to go through my phone. It only used to work for me a few years back. ITunes perhaps could do the trick but I rarely connect my phone directly to my PC. It would be nice if we could just "abandon" the working buffer if it is crashing by deciding to simply start the app with a blank canvas when needed (ApeMatrix asks to reload previous sessions when started, I think this would be an amazing fix for the buffer crash)).
I'll be looking forward to that release! I'm amazed by the amount of MIDI stuff I have been able to do up to date, and I'm barely scratching the surface...
Guitar MIDI 2 + Fugue Machine + MidiFire + fancy instruments and DAW stuff = amazing.
|
|
nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jul 9, 2019 8:37:34 GMT
Hi enriquepage91 , > far more "readable" to humans; my only complaint about the Stream ByterThe latest StreamByter (currently just the AU, but coming to MidiFire in next update) has language extensions to make it more readable; long rule names, user defined aliases, macros and subroutines. There is also StreamByter University which guides you through writing code with the latest features. > I have had the crash-thing occur to me again while using the StreamByterWhen you are writing StreamByter code, I strongly recommend you turn off both holdover mode and event visualisation in the 'Setup' menu. There are some issues with that which will sporadically cause mysterious crashes. Next release should make this more robust. > if we could just "abandon" the working buffer if it is crashing Leave this with me. Maybe I can come up with a solution to this that isn't too onerous to implement. Regards, Nic.
|
|
|
Post by enriquepage91 on Jul 13, 2019 20:27:29 GMT
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.
|
|
nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Oct 30, 2019 10:22:06 GMT
Hi slmnv and enriquepage91 , Just following up on this thread for completeness. Latest MidiFire should fix the +I crash as per the original post. Also includes latest StreamByter language to bring it in sync with the StreamByter app/AU > I have spent around 7 hours setting up my Line 6 Pod in MidiFire and all of a sudden the app crashed and no longer allowed me to start it (since it tries to load this “corrupt” scene I guess).
> My biggest fear is, If I uninstall and install the app again to fix the bug will I lose my Line6 Controller scene? It’s quite complex already and I wouldn’t want to have to rebuild it.MidiFire 2.0 also includes crash on startup loop handling. If you start the app 3 times and it crashes each time, then, it moves the working buffer to a recovery scene so you won't lose your work and starts with a blank canvas. You'll know this has happened due to a message in the Activity Log. Of course, hopefully there won't be any more crashes on startup! :-) and > If I really dig the update I might just get the StreamByter itself once I have some cash to spare. StreamByter app/AU is now free, so no need to save any cash! Regards, Nic.
|
|