Wirecast 15...weird NDI Network usage
Although Wirecast 15 is terminated, "/Applications/Wirecast.app/Contents/Resources/wirecastd" this process is still running and consumes over 45% of CPU and over 500 Mb/s of network resources.
I just added two NDI camera inputs (1080p30 each) to the blank document. so... It should be around 200 Mb/s. However, I restart each camera from the camera webUI and the network usage is increased.
It seems that "wirecastd" doesn't handle the NDI resouce well...
- OS (OSX 12.3.1)
- Wirecast Version (Version 15.0.0 (142.64a9eadd))
- MacBookPro Apple M1 Max 32Gb
- 2 NDI Camera (Birddog P400, 1080p30 each)
-
Jongseong Park said:
Although Wirecast 15 is terminated,How did you quit Wirecast?
-
CraigS
Cmd+Q
-
-
Jongseong Park said:
It seems that "wirecastd" doesn't handle the NDI resouce well...Wirecast 15.0
Testing on 13" MBP M1
macOS 12.3.1
Start Wirecast
Start Newtek NDI HX Camera in UHD
Two instances of wirecastd, one of which is just over 39% CPU use.
Quit Wirecast
wirecastd instances quits shortly thereafter.
Please provide more details since wirecastd might not be quitting for you.
-
CraigS
I said... It happens if I restart the NDI from the camera... this 'restart' includes unplugging and plugging the LAN cable, powering off and on the camera, to click 'restart' NDI video from the camera webUI. All reconnecting NDI video cause increasing the total usage of the network and if it happens, wirecastd will not quit properly.
I use full-NDI videos from two Birddog P400s.
In fact, this issue also happens on the previous versions of Wirecast. but I know how to prevent it and the wirecastd process is properly terminated when the parent process is killed... so I didn't report.
-
Jongseong Park We're trying to determine exact steps and reasoning.
As you can see in my test when Wirecast is quit wirecastd quits after that.
I'm not restarting my NDI HX source while Wirecast is running so is this the variable?
So do you believe restarting the NDI sources while Wirecast is running is the cause?Jongseong Park said:
but I know how to prevent it and the wirecastd process is properly terminated when the parent process is killed.Please explain.
While my example is different in that I'm using NDI HX, wirecastd quits when Wirecast is quit.
The developers need to know what happens in a linear step by step. If we have to interpret the developers may make wrong assumptions.
My guess:
Wirecast 15 is running.
NDI sources are running and added to Wirecast
NDI sources are restarted. (why are you doing this?)
Bandwidth and CPU use increases (this only happens after restarting NDI sources?)
Wirecast is quit
wirecastd continues to run.
Wirecast 14 showed increase bandwidth and CPU use while Wirecast was running but wirecastd was quit when Wirecast was quit.
We need confirmation on the steps. -
CraigS
1. open a new document in Wirecast
2. add a shot with NDI video source ( P400 in my case)
3. reboot NDI Camera
that's it!
please check the linked video.
-
-
Jongseong Park said:
this issue also happens on the previous versions of Wirecast. but I know how to prevent it and the wirecastd process is properly terminated when the parent process is killed... so I didn't report.We need this information to determine the change. It's not clear what issue you were experiencing in Wirecast 14 based on this description. Again I can guess but we want specific steps because developers may guess wrong. Sorry but we need exact steps to reproduce.
Investigation WIRE-20308
-
Jongseong Park said:
I said... It happens if I restart the NDI from the camera... this 'restart' includes unplugging and plugging the LAN cable, powering off and on the camera, to click 'restart' NDI video from the camera webUI.Why would you be restarting NDI sources?
It's not clear why you would do this unless you are all seeing another issue that you are trying to resolve. Again, sorry but we need very complete steps including the reason why if not obvious.
-
CraigS
I usually stream over 10 hours of academic conferences. Sometimes... I need to move the camera position. Sometimes I need to change the battery of a camera. Sometimes I keep the cameras off during break time in order to cool down. Simply, I do reboot NDI camera for a maintenance purposes.
-
-
Jongseong Park said:
I usually stream over 10 hours of academic conferences. Sometimes... I need to move the camera position. Sometimes I need to change the battery of a camera. Sometimes I keep the cameras off during break time in order to cool down.All good points. I'll make sure the developers understand this.
-
I am also able to reproduce this as mentioned in another thread.
Wirecast 15.0 release, Windows 10 21H1 19043.1645
I have reproduced this with NDI and NDI-HX sources. NDI seems to reproduce it more reliably and use more CPU in the remaining wirecastd process in my case.
For further cases of restarting NDI sources, I use Zoom Rooms as an NDI source, and need to re-pin remote presenters mid show. Even if I didn't have to re-pin, the possibility of a presenters connection dropping would mean the NDI source could disappear mid show. Less commonly, NDI screen capture for PowerPoint and that machine loses power or needs to restart for some powerpoint reason. Bottom line, NDI sources need to recover from failure gracefully.
Also, with Task Manager open, I can watch the Wirecast program group close, then a second or so later the wirecastd process pops up on its own.
-
Billy Davidson Thanks for that.
Billy Davidson said:
I can watch the Wirecast program group close, then a second or so later the wirecastd process pops up on its own.To clarify, you are quitting Wirecast and then seeing wirecastd process start or continue?
-
CraigS yes. Task manager open, close Wirecast, program group closes then wirecastd pops up on its own. I can't speak to whether that's just Window's process monitoring losing track for a sec or if it actually reopens.
-
Billy Davidson Thanks for that. It establishes a pattern.
-
CraigS further observations:
I've seen the issue with a Birddog pf120, NDI screen capture, AIDA HD NDI 200, pro video player NDI output, and Zoom Rooms NDI output. When the NDI issue is present, the shot layers Properties tab doesn't populate correctly, and NDI tally doesn't work.
-
-
Billy Davidson said:
When the NDI issue is present, the shot layers Properties tab doesn't populate correctly, and NDI tally doesn't work.When you mean "issue" do you mean the wirecastd issue?
If you don't have to reconnect it works as expected? -
CraigS said:
When you mean "issue" do you mean the wirecastd issue?Yes, but more specifically I mean that when the Properties tab fails to populate correctly then I know that when I do close Wirecast, wirecastd is going to be running on its own and chewing up CPU. So you can watch for the properties issue as a flag to know when the overall problem has been triggered since it doesn't occur every time I disconnect an NDI source, more like 75-80% of the time. I'm not sure if the amount of time an NDI source is disconnected affects the probability.
Correct vs Incorrect properties tabs below for reference. The NDI source is being displayed correctly in Live Shot Preview, preview, and live when both of these shots are taken. When the issue occurs the properties tab is incorrect for ALL NDI sources, not just ones that have disconnected and reconnected.
CraigS said:
If you don't have to reconnect it works as expected?The properties tab works correctly when the wirecastd issue hasn't been triggered.
-
Billy Davidson Very interesting observation. Thanks for that.
-
-
I can confirm that I am experiencing the same issue as Billy Davidson and can replicate it with ease. I actually ran across it by accident while setting up and testing a new PC for our Auditorium and did some digging and found this thread.
Wirecast 15.0.0 (134.64a9eadd)
Windows 10 Pro 21H2 19044.1288 -
I see there's a new version out, but no mention of anything that looks like this issue. CraigS have the developers looked into this yet? It's directly preventing me from upgrading to v15.
-
Billy Davidson We're still investigating this. Other users are seeing this as well.
-
CraigS Any progress? I'd love to move to 15.x, but this issue is a show stopper.
-
Billy Davidson Progress? Yes. Not ready yet.
-
-
Monthly bump...
-
Billy Davidson Still being worked on but the developers would like to have this fixed in an upcoming update (No promises they can do that though. It's a goal)
-
