BAM

Internal engines seem not to respond to pitchbend. AUv3 instruments respond to pitchbend but it is not recorded. Any possibility to add pitchbend support for recording and editing? Thanks for your consideration! Best, Ricky

All clips defaults to a length of one bar - to change it you have first to got to timeline or composer, and decide the length you want. Problem sometimes you don’t know how long you need. It’s a bit of friction to the inspirational flow to have to think how long the part has to be before recording it you can’t set the clip length from the matrix and do all your recording from there. If you’re inspired and want to record different parts one after the other (eg verse, chorus) you always need to switch screens to continue and record the next part It’d be nice to have either of: Make it easier to change clip length from matrix, or set higher default clip length in settings or auto-extend clip on first recording

It feels still weird to have to tap buttons to move scenes and tracks, these days. Arranging would be much improved if scenes could be reordered by drag and drop. Same for tracks. The drag and drop could be activated via the shift button, similarly to copying clips around in the matrix.

Please support relative MIDI CC This means, the greater the difference from a base CC value, the faster the controlled value changes in either direction. Most used variant: ... ,61 (-3), 62 (-2), 63 (-1) <-- 64 --> 65 (+1), 66 (+2), 67 (+3), ... Alternative variant: ... ,125 (-3), 126 (-2), 127 (-1) <-- 0 --> 1 (+1), 2 (+2), 3 (+3), ... This will often used by Jog-Wheels, but is also available in other controllers, like Faderfox. It is extremely useful for Sample scrubbing Moving cursors/markers Finer control where 127 steps is not enough

It'd be great if the MIDI mapping defined when working a project could be reused in another project. Possibilities, maybe either of: tap button to set a default mapping for most common controls (transport control, volume sliders etc). then everyone just needs to create a BAM mapping in their controller load mapping from another project (that the user gets prompted to select) name current list of mappings and save it in BAM independently of projects, under a name, and in any project you can load one of these mappings.

While 128 steps seems to be sufficient for most controls, it doesn't work for everything. Especially when controlling something with pitch and some filters, a clearly noticeable stepping can occur. For this, the decades old MIDI 1.0 standard has implemented 14-Bit MIDI, which simply uses two CC values to allow values from 0-16383 Various hardware controllers like Faderfox UC4/EC4 can send 14-Bit high resolution CC values, but also apps like 4Pockets Surface Builder. There does not seem to be any iOS-specific DAW/AUv3 hosts at the moment that supports this extremely useful MIDI standard. BAM could be first. The implementation would also require to increase the automation resolution which, i could be wrong, seems to be at 128 steps at the moment.

Please implement MIDI feedback. This is required for encoder knobs, but also control surfaces like TouchOSC, to work properly. This means, whenever a value of an element changes, the value will also be send to the MIDI-learned hardware control.

To clarify at the beginning, this does not mean specialized controllers that require custom, driver like programming but standard midi controllers that send CC values. To make BAM even more a center-piece in music creation, maybe in the future also for live sessions, more extensive support of hardware controls should be taken in consideration. Because nothing can beat the immediacy, tactility and precision of physical controls. Following would be required (Details in separate requests): MIDI feedback 14-Bit/High resolution MIDI support Relative MIDI/Jog wheel support Per track MIDI assignment One Knob/Focus control

For users on iPhone, it would be nice to have a settings option that makes the font size / widget sizes larger. This would improve the readability of the BAM screen on the iPhones which have smaller displays (e.g. iPhone 16 Pro, iPhone 16, etc).