These tasks are simple when using a macOS machine. ![]() (you could allow a hidden shortcut e.g.Distributing a macOS software is not an easy task – it requires taking the binary, signing it, packaging it, signing the package and notorizing it. seems to me, you’d likely want to use the same firmware version as editor version? perhaps it would be best to distribute the firmware within the application (as a resource), then the user could just click ‘flash firmware’, and app will know where to pick it up.do you need really need the view/edit toggle? - seems a bit unnecessary to me.you might also want to allow a blank description or default it to something, so that you can flash without editing the description (I think often people will leave this blank/not bother).One small ‘typo’ : when you change presets on GUI, it still says its going to clear the description, but that’s no longer true as its storing it on the midihub. It can now do a whole load of “creative” stuff as well as the more common routing tasks! Microtunings import/export dialog great update … really has taken the midihub to the next level,.Initial window positioning on first run improved.Midihub now stores up to 1024 bytes of description in its flash memory.Added ‘Duplicate Whole Pipeline’ right click menu option.Added current preset number display above the pipeline.Added toolbar to filter pipes properties, so making bulk changes is easy.Added more fine granularity to Filter pipe.Filter pipe got split into Filter and Channel Filter.Midihub now keeps track of all the notes, it should be impossible to get a dangling note when building the pipeline, or changing pipe param values, it should always produce either ‘all notes off’ or individual note off messages.Dragging and dropping leftmost pipes will rearrange the pipelines.Removed ‘description will be lost’ message.Fixed storing of preset with empty description.Properties window column widths will be retained between runs.Parameter Name column initially is now a bit wider.Limiter pipe split into Limiter and the new Rescale pipe.Fixed editing of Randomizer pipe’s Negative parameter.* All stored presets and microtunings will be removed during the firmware upgrade process * - you’ll have to back it up manually by loading each preset and saving them to disk with different names, a ‘data dump’ function to automate this, and to automatically do that during firmware update is planned to be done before the public release. Then connect to it with the editor, go to Device->Flash Firmware, pick the downloaded bfw file and hit OK. In the firmware upgrade mode, all the LEDs should be lit up. To update the Midihub firmware, switch it on while holding down The Button. Some changes and fixes were made to the UI for smoother user experience. ![]() Up to 1024 bytes of description text will get stored to Midihub flash memory. ![]() Of course you can still get a stuck note if you disconnect the external device that produced a Note On event before the respective Note Off event, but on changing the preset, or deleting the related input/output that should be taken care of. Midihub now keeps track of all the notes flowing through it, it should be impossible to get a dangling note when adding / removing pipes, or changing pipe param values, it should always produce either a ‘all notes off’ or individual note off messages when necessary. Each pipe has its documentation in the Context Help section of the editor, let us know if it’s comprehensible enough.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |