BRIDGE6 - Development Roadmap

Summary (show)

A no-holds-barred MIDI controller for the modern music world. We're committed to developing the firmware and software with as much community involvement as possible!

In progress

New Features

LFO'd MIDI CCs

Set an LFO rate and have your MIDI CC's value automatically change over time.

New Features

Device Link

Link many Flexiport-enabled devices (Bridge6, Bridge4, Flexihub) with 3.5mm TRS cables for fast, bi-directional communication between units

- Link devices to increase the MIDI inputs and outputs
- bank up/down, change state simultaneously

Up next

New Features

Insertable delays into message stacks with 1ms incremental resolution

Along with all the usual MIDI message types, a custom delay message can be inserted at any point into any message stack to delay future messages.

Features (4)
  • 1ms increments
  • Insert as many delays in whatever order you like (up to the max number for the given message stack)
  • 1ms-30s delay range
  • Delays can be configured for individual outputs, and filtered to only delay messages for certain channels

Future

Enhance User Experience

MIDI 2.0 Implementation

Enhance User Experience

Expression Doubler

Turn your TRS flexiport into two TRS Expression pedal inputs

Exp Doubler is a small box with:
- 1x 9v DC jack
- 2x 3.5mm TRS Flexiport outputs
- 4x 3.5mm TRS expression pedal inputs

Enhance User Experience

Flexihub

A small MIDI interface with
- USB C
- 3 Flexiports
- 1 TRS Relay Switch (dual amp channels)
- 4 MIDI outputs
- 4 MIDI inputs
- 2 CV/Expression inputs
- 2 CV/Expression outputs

all 3.5mm TRS jacks

New Features

Custom MIDI Chord Builder

Grapgical interface on the app for building chords with MIDI notes to be triggered by the Bridge6

Last updated 15 days ago
Recently completed
No results.
Add Idea
New idea
Large Font Size for Button "Scribble Strips"

For the visually challenged looking at the a display in the floor, allow the font (and secondary icon) size be configurable to a larger size.

Last updated 2 months ago
0
0
New idea
Minimalist Screen Options

Add the settings in the editor to disable screen objects for a minimal layout. For example, if you’re using the controller just for the six buttons triggering single notes, hide all other icons and display elements except for the main title and button titles.

Last updated 2 months ago
0
0
New idea
Update display by sysex

Performance hosts such as Gig Performer could dynamically send the preset/scene/snapshot name via a sysex message. Or even dynamically update the individual button labels. This functionality is currently possible with RJM Mastermind and would be a great addition.

Last updated 2 months ago
0
0
New idea
Control multiple expression CC values ... seperately ... with one expression pedal ... and remember last value for "catch up changes"

One expression pedal that is multiplexed by the device "state" where one pedal can toggle back and forth between controlling two or more CC values. A midi "expressionator".

For example, expression pedal is controlling volume. Press a button and the expression pedal now controls a wah. Press the button again and you're back to the volume pedal.

Ideally there is mechanism for "catching up to the current value" of the changed expression input. If expression CC A had a value of 90 and switched to expression CC B and then back to A, no CC's on A would be sent out until the you moved the expression through 90. It's an intuitive way to avoid jumps when switching between devices (that is hard to describe).

Last updated 2 months ago
0
0
New idea
Link / Group sets of Footswitches

A way to link or group the LEDs/footswitches to turn the others off when a footswitch within the same group is engaged... Example: My HX Effects has 4 snapshots. I'd like to assign footswitches 1, 2, 4 & 5 to them. If switch 1 is engaged (led on) and I step on footswitch 4, I'd like the LED on switch 1 to turn off so only one LED for any of those 4 footswitches would be on at any point, without affecting the other 2 footswitches (3 & 6).

Last updated 2 months ago
0
0
New idea
Open Device Link

Open the source or develop a public protocol layer/electrical specification for Device Link to enable the DIY community to integrate their controllers/hubs with the Bridge/FlexiHub ecosystem.

Last updated a month ago
0
0
New idea
Specific values as a step sequencer or at random order

Abillity to set specific custom values to be sent in the style of a step sequencer or at random sequence. This would be nice for example to set a delay time to jump and change the feedback and create some sort of false pitch shifting, be it in a specific sequence or at random, or even to send specific notes for a synth generator in a step sequence so it can trigger a synth while you play something else...

Last updated 2 months ago
0
0
New idea
Ability to dial in exact BPM on the fly

It would be great to be able to dial in and save an exact BPM on the fly, as tapping in is not always perfectly accurate. (My thought is to replace e.g. my Disatster Area Smartclock pedal). Perhaps a mobile bluetooth app could be used for this.

Last updated 2 months ago
0
0
New idea
Optional lock BPM in predefined steps/increments (80,90,100…)

Setting a precise clock might be cumbersome with only foot switches. Only way to achieve this easier would be, if we could set one/both clocks to lock in to only certain amounts/steps. Easiest method would be to lock it to full 10s: tapping in anything between 86–95 sets the clock at 90 bpm.

Last updated 2 months ago
0
0
New idea
Shared Data Map Protocol

Add a new shared data map protocol (i.e. Modbus or similar concept) as an alternative to Device Link for integration with DIY/third-party controllers via Flexiports.

Last updated a month ago
0
0
New idea
LFO - synchronizable/triggerable S&H/stepped/interpolated/sequenced waveforms - outputs to MIDI (CC) and expression (analog)

Really excited that you guys are planning on including multiple LFOs! This is kinda like what Source Audio Reflex had in the past, but I have a few ideas for your LFO implementations:

  • would be useful to specify 'density/frequency' (i.e., how often/populated CC messages are sent per unit of time (ex. per beat or second, etc), for example... we wouldn't want to send super dense and gazillion different CC msgs on multiple channels all at once when less dense groups of msgs would do just fine without making 'zipper noise' obvious for some devices)
  • if the above can be specified in terms of n-msgs-per-beat and can be sync'ed (or not) relative to the clock (and/or triggered by a command), each LFO can function like a simple arpeggiator/sequencer of sorts (Ex., 1-msg-per-beat would be a CC and/or analog expression cv value sent out per quarter note, 4-msgs-per-beat would be values sent out as 16th notes, )
  • some kind of a simple math operator to each LFO output value, like wave oper val1 val2 val3.. etc... (for example: sine/cosine which runs +1..0..-1 MULT 20 PLUS 30... to produce +50...+10 as a CC msg value... and val3 might be the 'depth' modulator fetched from an expression pedal input or a MIDI msg)
  • some kind of a simple math operator to force-correlate frequencies of LFOs (for example: LFO1 freq = LFO2 freq TIMES 2 )
  • now comes the kicker: specify two metrics for the number of msgs per unit of time as X) messages per unit of time and Y) user specified values per unit of time. For example., the user can specify 4 values per 'wave cycle' that's triggered per note (or per second or whatever), but depending on the value of X, these values can be just those exact values (when X=Y) or interpolated / smoothed out (when X > Y) --- like, setting 2 values for Y as 0.0 and 1.0 (or 0 and 127 or whatever) and setting something like X = 30 for a smoothed wah movement etc.

Actually, re-reading this, I have another idea - Since LFO-capable 'expression outputs' can be a MIDI msg and analog out over Flexi, make all these maths normalized to something like -100...0...+100%, and in a separate 'hardware config page' specify what each 'port' is actually capable of sending hardware-wise (ex. Ch.1 MIDI CC 0-23, Ch.2 MIDI CC 32-50, Flexi out1 0-1v, Flexi out2 0-5v, etc., with proper hardcoded value limits in software)

Last updated 12 days ago
0
0
New idea
Unlock external aux switches to match full functionality of main switches

Increase the functionality of external aux switches connected via Flexiports to match the full functionality of the main (on unit) switches. If some form of compromise has to be made then at least increased Midi commands.

Last updated 5 days ago
0
0
New idea
LFO with voltage output (like a regular exp pedal)

Like the TWA SIDE STEP pedal.

Last updated 2 months ago
0
0
New idea
Kemper two way communication

The kemper has a two way midi protocol that publishes the rig names and the state of the stomp blocks. It also provides access to the tuner information. It’s be great if the Bridge 6 could support this level of integration with the Kemper.

Last updated 17 days ago
0
0