YorVeX
Member
YorVeX updated xObsBeam [BETA] with a new update entry:
Version 0.8.0 Beta
Read the rest of this update entry...
Version 0.8.0 Beta
What's Changed
Read the rest of this update entry...
What's Changed
What's Changed
What's Changed
Full Changelog: v0.8.1-beta...v0.8.2-beta
- Decouple frame processing from OBS video thread when frame buffer is used (coupling was inadvertently introduced with previous releases)
- Added safeguard code to prevent OBS audio buffering increases in certain situations
Pipe is only for setups where both receiver and sender are on the same PC, it doesn't work through network. You need to set both sender and receiver to socket mode.Hi, I'm trying this out.. but my receiver PC doesn't see the sender. Same version everything, hardwired over ethernet on the same network. Receiver PC doesn't see it in available feeds and manual pipe name also doesn't work.
Ah ok, sorry about that.Pipe is only for setups where both receiver and sender are on the same PC, it doesn't work through network. You need to set both sender and receiver to socket mode.
But thanks for posting this, it reminds me that I actually wanted to make socket mode the default, because that's what most people will want.
What's Changed
- Fixed audio and video frames occasionally being dropped
As you can see from the table on the first post 4K60 NV12 would need more like 6 Gbps, you try to squeeze it through a 1 Gbps line, what exactly do you expect to happen? Of course it will fail and break and drop most frames.When the transmitting bandwidth exceeds bandwidth available of ethernet, happens this
4K60 NV12, 1Gbps ethernet.
commit size is about 220GiB, memory usage is 7.6GiB, 90% of Skipped frames due to encoding lag. and it crashs at some point.
It is ok to transmit 640*480 I444, and no memory leak?, but disabling Beam doesn't make memory usage normal.
View attachment 96366
If memory was leaked, then it was leaked, the only way to recover from that is to restart OBS. And then use a setting you have sufficient bandwidth for.but disabling Beam doesn't make memory usage normal
No, I wasn't aware of such a bug until now. Will have to make some tests and try to reproduce it later, probably at some point during the weekend. I created GitHub issue #25 for it.Is it a known bug? I didn't see anyone talks about memory leak. I meant that if bandwidth is insufficient, memory leaks.
I know it will never work properly at all, I'm just wating for a cheap realtek 5GbE controller. I will connect PC to PC directly, and use 1080P I444.
Also, I think things like downloading something, or SMB can cause memory leak at the point.
I cannot reproduce any memory leak with the current 0.8.3 version. I changed my network card to 1G mode and set OBS to transmit 1080p60 BGRA, which would need 3800 Mbps and therefore constantly disconnects, because the available bandwidth is not sufficient. I let this run for a long time, the memory consumption stays stable. Left side receiver, right side sender:When the transmitting bandwidth exceeds bandwidth available of ethernet, happens this
4K60 NV12, 1Gbps ethernet.
commit size is about 220GiB, memory usage is 7.6GiB, 90% of Skipped frames due to encoding lag. and it crashs at some point.
It is ok to transmit 640*480 I444, and no memory leak?, but disabling Beam doesn't make memory usage normal.
View attachment 96366
That page file is crazy big, why did you set it that high? Just let Windows manage it.Download zip file from github, and install xObsBeam only, launch it as portable mode.- YouTube
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.youtu.be
Memory also leaks from my laptop when I host it, but seems that garbage is collected at some point, not just keep growing.
Maybe it is because I set max of page file about 230GiB?(I did same thing with my laptop)
Receiver side is just working fine, memory usage graph is just like what you've uploaded. if the resoultion is too big, memory usage fluctuates, but no leak, at least.
Yes, this is when I enable Beam source from receiver side to receive the stream.Just for clarification, when in the video you say "started" at 0:28 this is when you connect the receiver, right?
If bandwidth is sufficient, there is no ever-increasing memory usage at all just like using OBS without any plugins. and I tried streaming 720P 30FPS I444 for about an hour yesterday, no leak at all.(PC to PC directly by RTL8153 NIC for both)Another question: what happens when you transmit with a speed that your 1G connection can handle, e.g. 720p30 with NV12 just to be on the safe side? Do you still get ever-increasing memory usage on the sender PC or does it stay stable in this case?
Thanks for taking the time, because of your report and your log I could now find out what the problem is.Yes, this is when I enable Beam source from receiver side to receive the stream.
If bandwidth is sufficient, there is no ever-increasing memory usage at all just like using OBS without any plugins. and I tried streaming 720P 30FPS I444 for about an hour yesterday, no leak at all.(PC to PC directly by RTL8153 NIC for both)
It does stay stable in this case.
Log with -p --verbose.
What's Changed