Rank: Advanced Member
Groups: Registered
Joined: 11/14/2012(UTC) Posts: 350  Location: Finland Thanks: 217 times
Was thanked: 21 time(s) in 19 post(s)
|
Tried OMTake v1.2 app on an old iPhone over a wired local Lan network without internet connection. Seems to work with vMix 29.0.0.48, but when the stream is stopped in the OMTake app and then re-started, then vMix won't find the stream any more nor does BHM OMT Media Player. BUT: After vMix re-launch the stream works... The exact same behaviour on BHM OMT Media Player (decoder).... (Restarting iPhone or the app does not solve the problem. Only restarting the decoder on Windows side helps..) Colliding ports? OMTake and/or vMix/ or OMT bug?
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 11/14/2012(UTC) Posts: 350 Location: Finland Thanks: 217 times
Was thanked: 21 time(s) in 19 post(s)
|
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 11/14/2012(UTC) Posts: 350 Location: Finland Thanks: 217 times
Was thanked: 21 time(s) in 19 post(s)
|
Noticed that the OMTake source became available (discovered) to the decoder after about 30 minutes after the connection was re-made from the app....
|
|
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 8/18/2025(UTC) Posts: 4  Location: Schwindratzheim Thanks: 3 times
Was thanked: 4 time(s) in 4 post(s)
|
Hi jet,
thanks for the detailed report and especially the follow-ups. The ~30 minute self-recovery is the key clue here.
I'm the developer of OMTake. The fact that it behaves identically on both vMix and the BHM OMT Media Player, that restarting the app or phone doesn't help, and that it clears itself after about 30 minutes all point to a discovery/registration issue rather than a port collision. When you stop the stream, OMTake isn't cleanly de-registering its OMT source, so the decoder keeps holding the now-dead entry until its cache expires — which matches your 30-minute observation exactly. Restarting the decoder clears that cache immediately, which is why that's the only thing that works.
So the fix is on my side: on stop, OMTake needs to close the connection cleanly and send a proper de-registration so decoders drop the source right away instead of waiting for the cache to time out. I'm working on it and will post here when there's a build to test.
Thanks for the precise repro, it made this much easier to track down.
|
 1 user thanked xcapetir for this useful post.
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 8/18/2025(UTC) Posts: 4 Location: Schwindratzheim Thanks: 3 times
Was thanked: 4 time(s) in 4 post(s)
|
Quick update — OMTake 1.3 is now live on the App Store, and the reconnection issue from this thread is fixed. The cause was on the OMTake side: when the stream was stopped, the app wasn't cleanly de-registering its OMT source, so decoders held a stale entry until their cache expired (which is why only a decoder restart, or waiting, brought it back). 1.3 does a proper teardown and de-registration on stop, so the source is rediscovered immediately when you restart the stream. A few other fixes made it into 1.3 as well: the on-screen status label no longer disappears in landscape, and the thermal handling is now broadcast-aware — if the device throttles, the frame rate stays within the same family as your selected rate (50→25, 60→30, never a PAL/NTSC mismatch), and the on-screen indicator shows the actual emitted rate when that happens. Thanks to jet for the detailed reports that made all of this easy to track down. Feedback always welcome.
|
1 user thanked xcapetir for this useful post.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 11/14/2012(UTC) Posts: 350 Location: Finland Thanks: 217 times
Was thanked: 21 time(s) in 19 post(s)
|
Originally Posted by: xcapetir  Quick update — OMTake 1.3 is now live on the App Store, and the reconnection issue from this thread is fixed. The cause was on the OMTake side: when the stream was stopped, the app wasn't cleanly de-registering its OMT source, so decoders held a stale entry until their cache expired (which is why only a decoder restart, or waiting, brought it back). 1.3 does a proper teardown and de-registration on stop, so the source is rediscovered immediately when you restart the stream. Hi Xavier! Found the 1.3 update about 30 minutes ago and just tested it out. Unfortunately the issue still persists!Disconnecting the cable during straeming and reconnecting is not an issue. The stream is back right away when the cable is reconnected. But when using the Stop function and trying to Start again then stream is not found any more. Some kind of temporary "fix" would be that OMTake would stream right away when it is launced? The issue in this approach is that the stream can't be found after App restart because the root cause of the issue is still there.. Speaking of OMT (and NDI) in general: Start and Stop are unnecessary anyway when the bandwidth is only consumed when there is a decoder tapped to it. And what would be more annoyning knowing the camera is at the location, but someone did not press the Start button ;)
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 11/14/2012(UTC) Posts: 350 Location: Finland Thanks: 217 times
Was thanked: 21 time(s) in 19 post(s)
|
Would really appreciate a "Reset" function for OMT sources to be added to vMix.
|
|
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 8/18/2025(UTC) Posts: 4 Location: Schwindratzheim Thanks: 3 times
Was thanked: 4 time(s) in 4 post(s)
|
Agreed, a Reset on OMT sources in vMix would be a great safety net — it would let you clear a stale source without restarting vMix, regardless of which side caused it. This probably belongs in the vMix Feature Requests forum so it gets in front of the vMix team. Happy to add my voice there if you open one — on my side I'm still cleaning up the manual stop/start teardown so OMTake leaves as little stale state as possible.
|
1 user thanked xcapetir for this useful post.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 11/14/2012(UTC) Posts: 350 Location: Finland Thanks: 217 times
Was thanked: 21 time(s) in 19 post(s)
|
Originally Posted by: xcapetir Agreed, a Reset on OMT sources in vMix would be a great safety net — it would let you clear a stale source without restarting vMix, regardless of which side caused it. This probably belongs in the vMix Feature Requests forum so it gets in front of the vMix team. Happy to add my voice there if you open one — on my side I'm still cleaning up the manual stop/start teardown so OMTake leaves as little stale state as possible. Yes, here it is: https://forums.vmix.com/posts/t34278--Reset--function-for-OMT-sources
|
1 user thanked jet for this useful post.
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
Important Information:
The vMix Forums uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.
More Details
Close
