TonyLikeSocks
SMSoftware Mansion
•Created by TonyLikeSocks on 10/3/2024 in #membrane-help
Pipeline Error: Pipeline Failed to Terminate within Timeout (5000ms)
The inference time is ~1 ms according to my logging.
13 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 10/3/2024 in #membrane-help
Pipeline Error: Pipeline Failed to Terminate within Timeout (5000ms)
It's stable insofar as it works. The delayed shutdown is just puzzling. I'm guessing it's Ortex + the use of Rustler. Though I've looked through those docs and the code, and I didn't see an "unload" or cleanup type function.
Though tellingly, if I replace my
do_predict/3
function with a dummy function like so:
I don't get the same timeout failure. So it's defintely that Ortex.run/2
call.13 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 10/3/2024 in #membrane-help
Pipeline Error: Pipeline Failed to Terminate within Timeout (5000ms)
Here's a gist with the module. I was thinking of open sourcing it, if I could get it stable.
https://gist.github.com/Tonyhaenn/66c9148b2ae73a5009894250a0b6f6d7
13 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 10/3/2024 in #membrane-help
Pipeline Error: Pipeline Failed to Terminate within Timeout (5000ms)
13 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 10/3/2024 in #membrane-help
Pipeline Error: Pipeline Failed to Terminate within Timeout (5000ms)
Ahh. Interesting, I did your method and got an entirely different result.
13 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 10/3/2024 in #membrane-help
Pipeline Error: Pipeline Failed to Terminate within Timeout (5000ms)
I didn't do that, but I did just try;
I get a VAD shutdown time of 0ms, and then 5000ms later, I get the error message. Unless this test isn't reliable
13 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 10/3/2024 in #membrane-help
Pipeline Error: Pipeline Failed to Terminate within Timeout (5000ms)
How should I go about determining why my element is taking too long to terminate? I don’t have a handle_terminate callback defined.
13 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 10/3/2024 in #membrane-help
Pipeline Error: Pipeline Failed to Terminate within Timeout (5000ms)
I'm loading the Ortex model within the element init and storing it within the state
model = Ortex.load(@model_path)
But beyond that, everything else seems pretty straight forward logic / state management (if prob > threshold blah, etc.)13 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 9/4/2024 in #membrane-help
Fly.io + UDP
Thanks @shuntrho. That’s helpful to know on needing to pass in the tuple not a domain name.
I am migrating away from fly.
17 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 9/4/2024 in #membrane-help
Fly.io + UDP
Thanks for the tip on chrome://webrtc-internals. Testing now (with no changes, still on fly) -- Chrome thinks UDP is connected and sending / receiving bytes. But I also see the same timeout errors, and I never exposed UDP in my fly.toml. Very odd. For future searches, Fly.io is weird.
17 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 9/4/2024 in #membrane-help
Fly.io + UDP
Thanks @mickel8 Super helpful convo. I’ll work on moving to a bare provider.
17 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 9/4/2024 in #membrane-help
Fly.io + UDP
At least not reliably
17 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 9/4/2024 in #membrane-help
Fly.io + UDP
Ok - so the advice is to migrate off fly. It should work, but the evidence suggests it is not
17 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 9/4/2024 in #membrane-help
Fly.io + UDP
Yeah, that was our assumption when we launched. That error message is really throwing me
17 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 9/4/2024 in #membrane-help
Fly.io + UDP
😅 yeah, I heard. Migrating right now isn’t in the cards to ex webrtc though. I’ve got too much built out.
Does the error message suggest I need UDP?
17 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 6/12/2024 in #membrane-help
Issue Membrane Upgrade to 1.1 (from 0.12.9)
Thank you. That got us past that error, but now I see a new one:
16 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 6/12/2024 in #membrane-help
Issue Membrane Upgrade to 1.1 (from 0.12.9)
I added the new element as part of the spec defined in handle_pad_added. However, I get the error above.
16 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 6/12/2024 in #membrane-help
Issue Membrane Upgrade to 1.1 (from 0.12.9)
This is my setup:
Would you add a parser after the opus decoder in the handle_pad_added callback?
16 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 6/12/2024 in #membrane-help
Issue Membrane Upgrade to 1.1 (from 0.12.9)
membrane_rtp_plugin ~> 0.24.1, which is a child dependency of membrane_rtc_engine ~> 0.22.0 and of membrane_rtc_engine_webrtc ~> 0.8.0
16 replies
SMSoftware Mansion
•Created by TonyLikeSocks on 6/12/2024 in #membrane-help
Issue Membrane Upgrade to 1.1 (from 0.12.9)
I think I’m on latest for everything but the file plugin. I don’t explicitly pull in :membrane_rtp_plugin
Membrane
{:membrane_audio_mix_plugin, "~> 0.16.1"},
{:membrane_fake_plugin, "~> 0.11"},
{:membrane_ffmpeg_swresample_plugin, "~> 0.20.2"},
{:membrane_file_plugin, "~> 0.16"},
{:membrane_mp3_mad_plugin, "~> 0.18.3"},
{:membrane_mp4_plugin, "~> 0.34.0"},
{:membrane_opus_plugin, "~> 0.20.2"},
{:membrane_raw_audio_format, "~> 0.12.0"},
{:membrane_rtc_engine, "~> 0.22.0"},
{:membrane_rtc_engine_webrtc, "~> 0.8.0"},
{:membrane_tee_plugin, "~> 0.12"},
16 replies