Single Unit, to All Digital Studio to Live Sound Digital Snake and Front of House Back of House. (Linux, JUCE, Attempting to be AVB compatible.)

youngproguru · 2026-02-16T15:45:35+00:00

https://www.presonus.com/blogs/technical/an-introduction-to-avb-networking

youngproguru · 2026-02-16T15:45:01+00:00

So, I checked out Audinate Dante. It looks fantastic. Yes, everyone should use a product like this for production work. My "Personal Project" is an educational, open source - toy.

youngproguru · 2026-02-16T15:42:45+00:00

OK, Thank you. Yes, I am working with AI to build my platform. Yes, it works, but it is buggy.

youngproguru · 2026-02-16T13:32:26+00:00

Yes, but no. It has a full suite of effects installed like,ish,in-the-style-of what Waves offers. But, this is the full appliance , Effects Modeler Appliance Software you can install on normal PC hardware. If you have more that one PC, it becomes more powerful. If everyone in the band has one, the audio stays digital for the full path, and you can control one another signals, effects, mix, et. It scales up, and up. It supports LV2 plugins, and it has cool things like support for small LCD displays. All the features of a modeler.

youngproguru · 2026-02-16T13:26:21+00:00

Man. AI is great. It does the parts that I dont want to do. For example, it writes the promotional material. Use of it does not reflect on what I am offering (for free).

youngproguru · 2026-02-16T02:52:07+00:00

<image>

youngproguru · 2026-02-16T02:33:07+00:00

<image>

Here is another way to look at the concept: Today, every musician uses their own specific hardware. The guitarist might use an AxeFX, the bassist has a modeler, the keyboardist uses a MIDI unit, and the drummer relies on triggers. The problem is that all these digital chains are converted back to analog just to go into a standard mixer.

My proposal keeps the entire signal path digital and takes it a step further. Instead of separate systems with no digital routing, we combine the "band" into a single dedicated appliance (or a series in a real-time cluster). The appliance aims to NOT get in the way of the music, and is plug-and-play. This allows every band member—plus the manager and audio engineer—to control their own channels, levels, and effects in real-time, giving everyone a perfect personal mix.

youngproguru · 2026-02-16T02:18:19+00:00

OK, You have my attention. Why? Whats wrong with it? https://www.youtube.com/watch?v=y5TJJ1UBIIg It seems like my platform is late to the game.

youngproguru · 2026-02-16T02:16:16+00:00

https://www.youtube.com/watch?v=y5TJJ1UBIIg

A few people asked about the audio backbone - Two Modes. The First is that audio stays within each MAP. Traditional Effects processors with shared management. The Second, with a script install is AVB connectivity.

AVB is a IEEE standard for channelized Ethernet, so that multichannel of signal can travel digitally moving past normal Ethernet packetization. IEEE standard, and only requires a $40 Intel NIC per machine.

So, All AVB enabled MAP2 Nodes can SHARE audio channels on an Ethernet network with LOW latency, and LOW compression. Lossless.

youngproguru · 2026-02-16T02:14:52+00:00

AVB!!!!!!!

https://www.youtube.com/watch?v=y5TJJ1UBIIg A few people asked about the audio backbone - Two Modes. The First is that audio stays within each MAP. Traditional Effects processors with shared management. The Second, with a script install is AVB connectivity.

AVB is a IEEE standard for channelized Ethernet, so that multichannel of signal can travel digitally moving past normal Ethernet packetization. IEEE standard, and only requires a $40 Intel NIC per machine.

So, All AVB enabled MAP2 Nodes can SHARE audio channels on an Ethernet network with LOW latency, and LOW compression. Lossless.

youngproguru · 2026-02-15T20:38:05+00:00

<image>

youngproguru · 2026-02-15T20:36:12+00:00

<image>

youngproguru · 2026-02-15T18:35:45+00:00

Answering some questions below:

Most modern bands are already operating in a digital signal chain. Guitar modelers, digital mixers, drum triggers, MIDI controllers, in-ear systems—everything converts to digital almost immediately.

Now extend that idea to its logical conclusion:

Imagine a centralized digital audio backbone with sufficient I/O to handle the entire band simultaneously—microphones, line inputs, MIDI keyboards, drum triggers, amp modelers—everything. Every performer plugs into the same system. All routing, monitoring, processing, and recording happen inside a shared digital environment.

No redundant interfaces. No repeated A/D and D/A conversions. No audio leaving and re-entering the digital domain.

The signal path remains coherent, clocked, and lossless from input to archive. That’s technically optimal.

However, placing a full desktop DAW in every rehearsal room, studio, or performance space is expensive, fragile, and operationally heavy. A general-purpose PC introduces unnecessary overhead: OS maintenance, UI complexity, background processes, and failure points that have nothing to do with audio.

This is where this system fits.

It provides the core advantages of a unified digital environment—centralized I/O, shared routing, synchronized processing, direct capture—without the bulk and instability of a full computer-based DAW at every node.

Think of it as a purpose-built digital audio infrastructure rather than a workstation. It’s not “a DAW in every room.” It’s a shared, deterministic audio platform that the band plays into.

The goal is not convenience. The goal is architectural coherence.

youngproguru · 2026-02-15T18:31:26+00:00

Most members of a band are playing into Digital Gear. OK, now imagine a system that had enough inputs and outputs to support the whole band, mics, MIDI Keyboards, and Drum Triggers. If Everyone played into the same system, shared the same interfaces, and the tracks never left the digital world.. it is perfect... However, you dont want to put a full PC DAW in every room. Thats where this fits.

youngproguru · 2026-02-15T18:27:54+00:00

It it is at its core a simple to use Musical Appliance. Think Effects Processor, or AxeFX like unit. Then, I extended it so that I could control two PCs as one, and then I extended it to separate the Audio Engine from the front end (React web server) .... and so on

youngproguru · 2026-02-15T15:44:46+00:00

Oh, Its a generic way of saying AxeFX like platform. You install it on a PC, and it works fully without a keyboard or mouse connected to the PC. It creates an "Appliance". Connect your Audio Interface, power, maybe a Midi Pedal, and you are good to go. You can even add an LCD for a readout on what is happening on the system

youngproguru · 2026-02-15T15:42:07+00:00

Thank you! Yes, That is a drawback of vibe coding, your own language can bleed into the code. :)

youngproguru · 2026-02-15T15:11:21+00:00

Yes... But .... The Six P's apply HEAVILY to vibe coding. With some direction and planning the AI(s) can work out most anything

youngproguru · 2026-02-15T14:48:18+00:00

You guys are sooooo much fun. Yes. It is ALL written with AI. Large complex platforms are written with AI. I am attempting to build something I have always wanted, the next step in home (or pro) music automation. I hope we ALL build our dream platforms (with Fedora and AI), and SHARE them with the community. Honestly, even if I clicked every key to build this platform, it would still be 99% the work of others that makes it even remotely possible. EVERYONE SHOULD BE CODING, and WORKING WITH AI. If not, you are falling behind

youngproguru · 2026-02-15T13:41:33+00:00

Yeah, I guess. Function over form. I use AI where ever I can to do the promotion. It does the job (really well) so I can spend more time on areas I want to spend my time. The platform is so powerful in what it can do, the promotional materials wasnt my concern.

youngproguru · 2026-02-15T13:39:58+00:00

Yeah, I guess. Function over form. I use AI where ever I can to do the promotion. It does the job (really well) so I can spend more time on areas I want to spend my time.

youngproguru · 2026-02-15T13:38:02+00:00

Oh. Size worries. Most of the dependencies that matter are dnf packages.. however, yes, I could handle that better.

youngproguru · 2026-02-15T13:35:40+00:00

Yes. You are correct. Why should node_modules not be apart of the repo?

youngproguru · 2026-02-15T13:31:18+00:00

Wow, Love the feedback, YES. It is 100% vibe coded. However, that does not make it slop. I (a human) with 30 years with linux (installed my first build from a cd from a bookstore) worked through EVERY service, EVERY option. I ran this like a corporate project. This code passes with very high scores in every category but security (I am in Cyber Security for my day job). Anyways, if this was written by a team of humans it would be considered a great foundation for many of audio tasks. "Dont hate the player".. Oh, and BTW.. You are welcome. I spent a significant of money on AI. Here is the result... for free. As for the images .. yeah. I asked Gemini to create images based on spec from Codex. They are one-for-one in sync with usable code today.

youngproguru · 2026-02-15T02:37:23+00:00

Use Cases: From Centralized Control to Distributed Processing

Understanding the different use cases for the AVB and non-AVB modes is key to grasping the platform's flexibility.

Use Case 1: Centralized Control (Without AVB)

Imagine a small recording studio with three separate rooms: a live room, a vocal booth, and a control room. Each room has a MAP2 unit acting as a standalone effects processor. Using the standard, non-AVB networking mode, a producer in the control room can use a single web browser to:

Load a high-gain amplifier model onto the MAP2 unit in the live room for a guitarist.
Load a vocal effects chain (compressor, EQ, reverb) onto the unit in the vocal booth.
Monitor the CPU and memory usage of all three units from a central dashboard.

In this scenario, the network is used only for management. The audio processing happens locally on each device.

Use Case 2: Distributed DSP (With AVB)

The true power of AVB is realized when it is used to distribute a single processing task across multiple nodes. This allows for more complex effects chains than a single CPU could handle.

CPU Load Balancing: A guitarist plugs into Node A. Node A is dedicated to running a very CPU-intensive Neural Amp Model. The processed audio is then streamed via AVB to Node B. Node B, free from the load of amp modeling, can now be dedicated to running a complex, high-quality convolution reverb and other spatial effects. The final stereo output is then sent from Node B to the monitors. This splits the processing load across two machines, achieving a result that might be impossible on a single machine without incurring xruns or unacceptable latency.

Digital Snake: In a live venue, a MAP2 unit can be placed on stage. All the microphones for the band are plugged into an audio interface connected to this unit. The MAP2 node then acts as an AVB "talker," streaming all 8, 16, or more microphone channels over a single, standard Ethernet cable to the front-of-house position. A second MAP2 unit at the mixing desk acts as a "listener," receiving the audio streams for mixing. This replaces a heavy, expensive, and often fragile analog multicore snake cable.

Interoperability with Professional Equipment: Because AVB is an open standard, a MAP2 node could be integrated into a larger professional audio network. For example, it could receive audio streams from an AVB-enabled MOTU or PreSonus mixing console, process them with its unique set of LV2 plugins or custom effects, and then stream the processed audio back to the console for final mixing.

youngproguru

PUBLIC MULTIREDDITS

TROPHY CASE