MiniHub 0.5.0 — pre-alpha

Still pre-alpha, still unsigned. The same two ways in: the installer, or the portable ZIP you unzip over the old folder. Settings, projects and recordings live outside the application folder, so upgrading over 0.4.0 keeps your work.

This one is mostly about knowing where you are and being able to get there.

A transport at the top

The header carries the whole transport now: back to the start, back one bar, Play/Pause, Stop, forward one bar, to the end of the arrangement, and the position in bars and beats.

It is in the shell because that is where it is needed. Inside a One Ring node, on a plugin's page, in the Patch Bay, the arrangement is not on screen — and once you have left the timeline, "where am I" has no other answer. The readout turns green while the transport runs.

Play doubles as Pause, and Pause and Stop are not the same command. A pause holds the arrangement where it is and leaves a One Ring running on its own clock; a Stop stops both. Neither rewinds — returning to the start is its own button, next to them, where you can see it.

A step back from the middle of a bar lands on the bar you are in; pressed again it goes back one. That is the step that makes Back usable.

Minutes and seconds, above the bars

The arrangement has a second ruler over the bar ruler, in minutes and seconds. Its marks are clickable like a bar's, and it redraws itself when you change the tempo — sixty-four bars are sixty-four bars at any tempo, two minutes are not.

The two rows only line up where a bar happens to fall on a round second: at 120 BPM a bar is exactly two seconds and every bar line meets one, at 90 BPM they meet every three bars, at 174 they never do. That is the tempo talking, not a drawing error.

The Patch Bay goes as far out as your patch

Align laid a dozen nodes out correctly and then showed you two thirds of them: the zoom could not go below 25%, and a rank of twelve nodes needs less than that to fit.

The floor is 5% now, so "frame everything" is never a lie. What changes with distance is how much of a node is drawn, not how far you can go: past 50% the badges, the port names and the faceplate's legends step aside, the node's own name grows so it stays readable while the node shrinks, and past about 18% the node is a coloured block. The background grid drops its fine tile when its lines get too close to be a grid.

Fixed

• The Sequencer's tracks no longer empty as you scroll. Every scroll of the timeline raised an error, so the repaint that draws the clips you are scrolling towards never ran: move more than a screen away from where the arrangement was last drawn and the lanes went blank.
• The arrangement stays where you scrolled it. Only the horizontal position was put back after a repaint, so past the thirteenth track every edit — and a MIDI port appearing counts — threw the view back to the first tracks. "+ MIDI Track" made a track below the fold and showed you the top. The view stays now, and a new track is brought to the screen.
• The timeline does not end. It used to stop four bars after the last clip, sixty-four bars at the least, so a clip could not be dropped at bar 200 of an empty arrangement and the transport could not run past it. There is always a screenful of empty bars ahead of the view.
• A right-drag pan in the Patch Bay no longer opens the context menu when you let go. The menu was suppressed for 800 ms from the moment the pan began, and every pan anyone actually makes lasts longer than that.

Known, and not fixed here

• One Ring is still young. It is covered by tests and it runs, but it is the newest thing here and that is where the rough edges will be.
• The Arpeggiator, Mixer and Morpher pages do not redraw when a One Ring sequence changes them: the value has changed, the knob on screen has not moved yet.
• Kilohearts plugins (kHs Gain, kHs Filter, kHs Reverb) still do not load: "setProcessing(true) failed".
• Massive X can still move a parameter by itself for up to half a minute after its window opens, and a Learn armed during that time may take that parameter instead of your knob. Arm it again once the plugin has settled.
• MiniHub.exe still describes itself as Electron in its file properties, so Windows may show that name — in Task Manager, for one.

Checksums

Unsigned, so SmartScreen will ask: More info, then Run anyway. SHA256SUMS.txt is published beside the downloads so you can check them yourself.