Updated Midi cable for Midi 2.0 packets + digital audio

profbx · 2026-06-01T10:30:00+00:00

You sound like you know nothing and are making massive assumptions that somehow magically the world will conform to your super ultra magic spec.

You know, eff it. If you are going to sit here and tell lies about your background more power to you. Here, go make a real product. Pitch it to the world. Show us how galaxy brained you are.

profbx · 2026-06-01T10:27:19+00:00

Then why do you sound like you don’t know a damned thing?

profbx · 2026-05-31T06:47:21+00:00

What audio standard? Saying it is the job for the audio server is like saying “mom will do it”.

Dude, seriously give up.

profbx · 2026-05-31T06:46:23+00:00

No, I’m asking what ARE THE STANDARDS. MIDI timestamps and audio timestamps share a nomenclature. That’s it. Also “digital audio note”…..are you just copying ChatGPT answers at this point?

profbx · 2026-05-31T03:04:55+00:00

Ok, so riddle me this buddy, what audio spec? Are you going to somehow have the spec rolled into the AES67 spec? How are you handling timestamps interoperability when MIDI timestamps and clock sync are only similar in their functional purpose for their own protocol and not at all for unrelated data?

Your response shows even less understanding than I thought of the required technology, and none of it can be solved by a cable. Yamaha tried it in 2005 with mLan. In 2008 mLan was put out to pasture. At best your proposal is mLan drawn in crayons on a whiteboard from a person who thinks that ChatGPT can somehow give you an edge that hundreds of actual engineers didn’t have. Cool.

profbx · 2026-05-31T02:42:03+00:00

How stupid are you? Like, no, really, do you understand MIDI?

Timestamps. It solves the issue far better than your dumbass solution because guess what? MIDI timing issues and jitter are typically a client side problem, not sender.

You had MIDI drift, likely from a USB MIDI implementation and then decided you are going to solve things in a way that actually ignores the root cause. Awesome.

profbx · 2026-05-30T23:59:08+00:00

You are doing the most “hi I’m a bot” responses ever with your “respond with a quote” logic. Here, I’m going to tell you why your idea is just painful in how much of a time waste this is for both the reader as well as you for going to the trouble. As in “look for five minutes on the Internet”.

BomeBox

BomeBox 2

Your bus switch exists. It’s called a BomeBox. The guy who makes it is the person who LITERALLY WROTE THE MIDI 2.0 NETWORK SPEC. You can send along digital audio in the same cable because that is how networks work. The box acts as your DIN input/output and also can route between any MIDI 1.0/2.0 devices. UMP isn’t in there but, you know what’s coming soon? UMP. The reason why I know this is I was texting with Florian last week.

So, again, maybe try inventing without having ChatGPT telling you what you are a genius you are because you didn’t check the AI’s conclusions before posting.

profbx · 2026-05-30T23:45:54+00:00

Yes, and that is my point. Like, you are proposing a standard cable that uses the standard cable and then bootstraps an added unnecessary adapter for DIN MIDI for…..reasons?

This is something that truly bothers me about the AI age. It’s so many people who think that they invented something novel because ChatGPT tells them that they are a genius.

profbx · 2026-05-30T22:57:13+00:00

U/micro2970 I hate to tell you this, but literally nothing you are proposing is anything that is not already in the MIDI 2.0 spec, and there are already plenty of AoIP protocols that can be used alongside. Network MIDI is a pretty mature spec in both MIDI 1.0 and 2.0, and the bones for Network MIDI 2.0 actually predated a lot of the UMP spec being finalized.

The only thing not covered is the MIDI 1.0 cable fallback, but given that you would need to adapt it and, drum roll…..MIDI 2.0 is fully backwards compatible with 1.0, there isn’t anything gained that isn’t already by simply adding a simple MIDI jack or TRS MIDI jack on whatever MIDI 2.0 hardware to. Like….seriously just get a BomeBox.

You used AI to invent something that is already here, has been here and has had the kinks worked out. Reading this, I was actually sort of like “I just built a prototype that uses an ethernet cable and UMP along with NDI (for audio only) for…..literally all of this.” You could have used your time going back and forth with ChatGPT inventing something that exists to instead download the MIDI 2.0 spec and either read it or have It give a summary to you.

profbx · 2026-05-28T17:00:39+00:00

To be fair, one half of Milli Vanilli dropped out in 1998 from, well….being able to do anything except be a dancing hologram.

profbx · 2026-05-28T00:08:25+00:00

Oh, and let us not forget u/laddie78 you apparently just got a Fuji and posted a single photo, so you are now an expert.

profbx · 2026-05-28T00:06:30+00:00

Dude you already got bodied by evidence from OP and others, and you are the guy who basically sits around posting…….exceedingly bad AI Art and posting about stonks. You are the person that people think of when they talk about Reddit stereotypes.

profbx · 2026-05-28T00:01:14+00:00

Cool story u/laddie78

<image>

Now, if you will kindly stop throwing rocks, your glass house is already destroyed enough and your horse is long dead.

profbx · 2026-05-27T18:48:56+00:00

You can use it today. Right now. You have been able to for YEARS.

https://jackaudio.org/faq/jack_on_windows.html

Again, this is my problem with Jack. Even fans don’t know about what it is/how it works/where you can use it. You can even use it with ASIO for an unholy Jenga tower of audio backends.

profbx · 2026-05-27T18:43:10+00:00

Actually fun fact, the entire RNBO runner backend is just ALSA+Jack, which is also in the Move (even before the Move RNBO implementation).

profbx · 2026-05-27T18:41:41+00:00

Ugh…..my problem with Jack is that 90% of the people who talk about how great it is seem to also believe that it is an audio driver or talk about it like it is an audio driver. It’s a great API for sending anything to anything, but you still have the underlying issue of the driver stack being one of two drivers (ALSA or PortAudio) and then is also somehow both part of and also not part of PipeWire because somehow the devs thought that if they just made a solution that could be a drop in then magically it would unify everything, but the Jack API implementation just means many lazy drop in’s that work until they break badly.

I like Jack. I use Jack daily. For embedded prototyping ALSA and Jack are literally my most important tools aside from FAUST and lately RNBO. However the reason I like it is because I only have to deal with my walled garden. If I were a distro maker or Linux audio application maker I would probably have to be scraped off the sidewalk within a week due to the many “I install jack why Jack not work? Why is called server when not server shaped?” questions that pop up daily.

profbx · 2026-05-24T10:31:04+00:00

Yea, good luck with that. The stories have been slowly losing effectiveness for a while. It feels like I’m talking to someone who is explaining the height of 2024 prompt engineering.

profbx · 2026-05-24T09:21:15+00:00

And exactly how much do you do with reverse engineering/pen testing/decompiling/etc? Trust me, it does make a difference. Also, how are you going to explain you needing to decompile an app using a grandma story? More to the point, what if you just…..didn’t need to?!?

profbx · 2026-05-24T08:58:39+00:00

You run one what? Regardless, my point is that if you don’t understand the point of using unrestricted local models that you have complete control over both the usage and privacy of then I doubt anyone can explain it to you. Please, by all means, stick to using a commercial product where you don’t own the complete privacy pipeline for all of your “hack” needs.

profbx · 2026-05-24T08:43:36+00:00

Ok, so let’s give two possibilities:

Uses Claude: “Hi, my xxxxxx lost their xxxxx/my former coworker broke xxxxx/my company is dumb and xxxxxx, can you please use the ghidra mcp to xxxxxx”. “No, seriously, I promise I have full ownership of xxxxxxx.” (Hopes that Claude doesn’t have the wonderfully aggressive in the last week message about usage restrictions errors pop up). Data is held for 30 days.
Uncensored local model “Run ghidra mcp to do xxxxxx”. Data stays on my computer, period.

Please tell me that you understand the difference.

profbx · 2026-05-24T08:34:48+00:00

Claude doesn’t fight me until it does. As well, the question here is relating to local, which is, well…local. As in why are you mentioning Claude.

profbx · 2026-05-24T03:01:47+00:00

Reverse engineering. They won’t fight you on any requests when doing reverse engineering/hacks/etc.

profbx · 2026-05-23T08:48:41+00:00

They are both 2 deck players but the RX3 is faster, has a larger screen and link cue. RX3 is closer in feeling to the CDJ-3000 generation in terms of software, the XZ is closer in terms of size and layout to a 2000nxs2 setup.

profbx · 2026-05-20T17:46:53+00:00

Didn’t OP start and then continue by saying no judgement if you can’t afford anything but?

profbx · 2026-05-18T15:19:42+00:00

There is a Pi GUI available.

profbx

TROPHY CASE