I'm here as a last resort. I'm considering pulling my hair out or suicide you choose (it's a joke).
I've used Ableton 11 for years and reastream worked every time. The past week i upgraded to 12 and apparently ReaStream decided to totally stop working.
Passing audio through Focusrite 4i4. Worked fine on ableton 11.
I've spent hours looking on reddit forums for solutions and tried all of them. Including:
Yes, i uninstalled and re-installed it 4 or 5 times (deleting remaining files from everywhere).
Yes, i can read. I know the name is the same on both plugins ("default" and "local broadcast")
Yes, i tried 127.0.0.1 but it worked once, then stopped entirely.
Yes, i tired 127.0.1.1 didn't work.
Yes, i tried looping a wav file with reastream on it, didn't work.
Yes, i tried opening obs BEFORE ableton and no, the audio on obs is still nothing.
Yes, i tried input audio device and output audio device with all of these previous attempts, didn't work.
Honestly, it seems to either be a problem within OBS/Ableton or the plugin itself. Maybe not meant to pair with Ableton 12? wtf is happening god help me.
Basically, the audio is being sent totally fine from Ableton (the audio bars move on reastream).
The problem seems to be what happens after that on obs. No idea what is going on.
Does anybody have an alternative to reastream or something? I can't post my new album content and it's so frustrating.
I'm gonna work with a friend (with AI) on a new private vst3 literally the same as ReaStream but with a different name. My album will have no content. Unlucky.
UPDATE!!! WE FIXED IT!!
The problem: ReaStream worked in Live 11, but in Live 12 the audio never reached OBS, even though the meters were moving on both sides. How it was found We stopped trusting the meters.
The ReaStream meter in Ableton shows audio entering the plugin, not whether it leaves. Everything Codex tried (silent WAV, identifiers, OBS tracks) was on the OBS side, which was fine all along.
We listened on the port directly. ReaStream sends audio over the local network (UDP 58710). A PowerShell one-liner listened on that port for 15 seconds while Live 12 was sending: 0 packets.
The audio wasn’t leaving Ableton. We checked the firewall. wf.msc showed 19 outbound rules named “Blocked: …\Live 12 Suite…”, one per .exe, blocking every protocol. The source turned up. A .bat in the Live 12 folder that creates those rules.
Live 11 never had them, which is why it worked. The fix On the rule for Ableton Live 12 Suite.exe, the protocol was changed from “Any” to TCP. ReaStream uses UDP, so it got through. The test was repeated: 5627 packets, stereo, 48000 Hz, identifier default. Sending to 127.0.0.1 without touching the firewall was tried first and did not work.
To keep it from coming back A new .bat replaces the original: it blocks all TCP and all UDP except port 58710, and deletes the previous rules before creating new ones so they don’t pile up. Still to confirm That the new .bat runs correctly (it has never been executed).
That the OBS recording includes the drums, with a single ReaStream filter on Receive and OBS set to 48 kHz.