wwaldner
I have a Phoenix application that I have setup to create a RTP session with LiveView server. LiveView currenty handles the signaling part and I am getting the RTP packets on my LiveView. 
Now, I am trying to figure out the best way to process the media packets. I see two options.
- Use membrane with a custom source element that take the RTP/Opus packets and builds up a pipeline to do whatever processing needs to be done.
- Use boombox(this would be my preference). But I don’t see how to create the input that boombox needs. The WebRTC input takes a signaling server(which I have already taken care of). Not sure how to get the RTP packets into boombox so it can create the output. Perhaps I could use
Membrane.WebRTC.SignalingChannel, to handle the signalling part and then pass that to BoomBox…However, I have not figured out how the SignalingChannel gets used. Could I start this in my LiveView and pass the signaling messages from client to the SignalingChannel?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest Membrane Threads
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
mat-hek
Hi, the Membrane way will work, but the SignalingChannel way won’t. The SignalingChannel proxies WebRTC session negotiation messages only - then the RTP messages don’t go through it, but directly to Boombox/WebRTC source. What you would need is Boombox accepting plain RTP. We’re working on that right now, but we also decided it’s high time we paid some tech debt in the Membrane’s RTP implementation, so it may take a month or two.
kingdomcoder
Hey @wwaldner
I’m trying something similar to what you’ve described here. Curious what direction you eventually took.
I noticed the
rtpoption has been added to boombox. Perhaps that’d be useful to you.Do you mind sharing how you achieved this? Examples of membrane apps seem a bit sparse.
wwaldner
I ended up going a different direction. Instead of using WebRTC in browser I just capture the audio recorder, downsample to 16k and send it to LiveView.