I was going insane because I thought it was just me. I mean I spent a good six, seven, maybe eight hours trying to build my own Docker container for PrismCast just to see if I can get it to work. I was successful. It still had the same issues.
I'm wondering, since I never used it, does Chrome Capture for Channels have the same issue?
Beats me. That project was a bit over my head, so I haven't tried it either. For now, I'll rely on TVE, ADBTuner and the Roku Bridge project.
The one thing I really like about it is the integration with tv.YTTV to get every subbed channel with no additional hardware investment (since I already had the Mac Mini).
You also have to consider this project is pretty new (only 47 days old), so who knows what the future holds for it.
It has good potential, and I will be eagerly watching any development. It would certainly benefit folks who can't, or don't want to invest in HDMI encoders and several tuner devices.
2 Likes
I think it's a great project with a ton of potential. I just can't use it until these video playback issues kind of get ironed out. It's a really great option for those who don't want to invest in HDMI encoders.
1 Like
If someone compares CC4C that will be interesting
The stats show A-V is not 0.000. There is an audio sync issue. It is likely caused by ffmpeg params used for AAC encode
2 Likes
Yeah, when I built my test container, which I ended up deleting because it didn't really fix the output frame dropping I forced it to re-encode rather than remux. It was just an experiment, but I noticed that the frame rate was level when I did that. So I think there is some sort of issue, possibly on the FFmpeg side. Once I started messing with ffmpeg parameters, it started getting better, but I just didn't get it 100% right. If I were investigating this, I would be messing with ffmpeg
There's something unusual with the PTS and video framerate.
Here is that recording in VLC showing as 29.97 fps
and in my video editor showing average 60.06 fps
(it thinks it's VFR Variable Frame Rate instead of CFR Constant Frame Rate)
For comparison, here's the TVE recording
I'm tinkering with something on my own fork. If I get anywhere, I'll let you guys know.
What I did figure out is bitrate drops directly correlate to frame rate drops, and it seems like MediaRecorder can't keep up.
2 Likes
Is that the browser extension used to extract the stream from the Chrome browser.
I believe it's the API used by Puppeteer, which is the extension.
I may have something in the next few hours using WebRTC.
I have video playing, there's just a frame pacing issue and a resolution issue that I'm working out.
I got the video actually displaying properly on the screen using WebRTC instead of MediaRecorder. Now it's just a frame pacing issue and an audio issue that I have to work out and then see if it actually helped.
Edit:
Unfortunately, I spent an entire day on this and got effectively nowhere. It is just fundamentally incompatible with Docker, as far as I can tell, unless someone else has any other ideas. I tried WebRTC, I've tried X11 Grab, I tried GStreamer. The issue with those last two is they capture the full screen, so you only get one stream. GStreamer was the most promising, but again you only get one stream. It also had issues with audio that I wasn't able to work out, but the video was perfect.
So I guess the solution would really be multiple virtual displays spawned and true display capture rather than tab capture. But that's beyond what I'm interested in. I have my Osprey set up that I dumped a couple hundred dollars into, and I was just doing this for the benefit of the community, but unfortunately, I just can't get it working, and I'm just going to continue with my Ospreys.
1 Like
Kudos to you for trying. Appreciate it.
Can't blame you for sticking with what works for you. I do the same.
Like I said
Who knows, we may see some improvements in the Project. It's young and sure has potential.
It is a really young project, and I really hope that it gets better on other platforms at some point. I think this is just a fundamental limitation of Chrome on Docker, that it just can't push the same frames that it does on bare metal.
Followed up in the Project thread with results for v1.6.0
And case closed