via MeeBlip:
"Today, we’re announcing MeeBlip cubit go - a unique USB MIDI interface with incredibly tight timing.
It’s got the ports you most often need when mobile - one input, so you can perform, and four outputs, for sending notes and/or clock.
Here’s the twist: we’ve integrated hardware MIDI thru circuitry on the four outputs. Anything you send to the interface’s output goes to all four jacks simultaneously. There’s no software delay - you get rock-solid, ultra-tight timing.
That makes cubit go the perfect follow-up to our cubit splitter, introduced earlier this year. You still get four outs with identical timing - but now in a USB MIDI interface you can connect to your computer or mobile device.
cubit go is driverless and USB powered, so it works with any desktop OS, but also on phones and tablets (with the appropriate cables, sold separately). And the jacks are top-mounted for convenience.
Just plug it in and use it - there’s nothing to install, no separate power supply needed, and nothing to worry about. cubit go is palm-sized, lightweight, rugged, performs perfectly, and is easy to use.
Features:
1x1 USB MIDI interface with integrated hardware MIDI Thru
Class-compliant USB MIDI - no drivers needed
Four hardware-mirrored output jacks - no software lag
High performance 32-bit ARM Cortex processor
Bright green MIDI light flashes when sending or receiving data for easy troubleshooting
Size: 108 x 76 x 25 mm (4.25 x 3 x 1 inches), weighs 110 g (3.9 oz)
Includes 1 m (3 ft) USB cable
USB powered
Works with macOS, Windows, Linux, iOS and Android*
Made in Canada, available only direct
cubit go is available now for $59.95 US.
Find the product page here.
Through August 23, we’re offering free worldwide shipping on cubit go and MeeBlip geode. Local tax and import duty may apply to international customers.
Also, if you missed it, we visited the amazing Hainbach last week [posted here], and our little MeeBlip geode got to meet his giant wall of sound. It was really fun to do."
Update: I reached out to Peter Kirn of Meeblip and Create Digital Music for some additional clarity on the cubit go. Here's what he had to say:
"It's a 1x1 USB MIDI interface.
The 1 input port is straightforward - that goes to the computer (or iPad or whatever).
The computer then *sends* MIDI to the output port.
That single output port's data is mirrored across all four MIDI output jacks, simultaneously - that's the MIDI thru circuitry. So for something like MIDI clock, it means all four output jacks have essentially zero timing variance from one another. (James likes to be precise - it's a maximum of 44 *nanoseconds*, so billionths of a second.)"
You can find some additional info on Create Digital Music here. Via the FAQ at the bottom:
Should I get cubit go or cubit splitter?
cubit splitter is the device for you if you want to take data sent to one MIDI input jack, and transmit that to four output jacks. (This is also called a “MIDI thru” box – they’re the same thing.)
cubit go is what you want if you need to get MIDI into and out of a computer or supported phone/tablet.
USB on cubit splitter is for power only. USB on cubit go carries both power and data.
Update2: If this is still conceptually foggy, I sent the following to Peter Kirn and he confirmed this is correct. In the most simplest terms, the MeeBlip cubit go is a USB only MIDI interface:
"The MIDI IN jack on the cubit go does not go directly to the MIDI OUTs but rather to the connected computer/USB device, which then does whatever you tell it to do (pass through or process). The USB device then sends to the four OUTs simultaneously as one OUT. The only messages going to the OUTs on the go come from the USB In. The MIDI OUT is just there so you can use external MIDI gear through the connected USB device. An example of how this is useful would be running multiple MIDI tracks on your software sequencer or DAW. The entire output would be transmitted to the four outs on the cubit go. If you have four tracks running you can assign a different MIDI Channel to each and then set each of your four MIDI devices to a corresponding MIDI channel. You can assign the incoming MIDI device coming through the cubit go a specific MIDI channel or channels either on the device itself or your software if supported (pass through or processed)."
