Originally Posted By: ZeroZero
I confess I don't really understand the 'thru track' concept. It's confusing - you see it in the mixer but nothing is recorded on it?

I propose we have a 'user track' this can be an audio track or a MIDI track that can either record audio or MIDI, can load a VST, play it, record it, and see and edit the data. It's not too much to ask, pretty standard stuff.

the whole thing needs a redesign


Many MIDI capable devices have three MIDI ports

In - Out - Thru

'In' is what is received by the MIDI device
'Out' is what the MIDI device transmits
The 'Thru' is just a way of sharing what comes In with other devices, rather than terminating the connection. It sends the In to somewhere else: the Thru - but only if a connected to another module is required.

However, the way the BiaB implements MIDI Thru is somewhat not really clear, and therefore confusing

I suggested some years a go a graphical map that displayed the connections and device names between the inputs, outputs, VST's and internal synths used, and connectivity of different ports. Unfortunately, it didn't get a guernsey.



BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones