-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cea608 issues #33
Comments
How did you run it? Did you run tvctl first? What is your data source for captions? The filter kernel won't be the problem. CEA608 is designed to work with VHS tapes. |
I came across the issue myself and noticed that it seems to work intermittedly. I'm on a Raspberry Pi 4b tvctl needs to be on first, yes, perhaps an error should be thrown when its off. It also wouldn't work when PAL was off, turning that on seemed to fix things. I also made sure to disable dtoverlay. And after 30 minutes of fiddling with settings to try and get it working, it worked! And then I stopped it and tried to run it with an output and got this:
And launching it regularly doesn't work either until I restarted. and when i restarted, it again didn't work the first time, and i had to relaunch it. Passing stuff through stdin generally doesn't seem to work. Running |
Yes, I ran:
And then ran
|
I haven't been able to get cea608 captions to display with the recent update, even when testing with multiple different displays. While there's a non-zero chance it's operator error, I found what might be an issue in the caption data generation.
With a "standard" boot config, I get this output:
The caption data line is resized by dispmanx horizontally using a Hamming upscaling method, as mentioned in raspberrypi/firmware#104 (comment) , which results in a blurry data line.
Adding the line
scaling_kernel=8
toboot.config
to use Nearest Neighbor scaling results in an output that looks much closer to other examples I've seen:However, even with that change, I'm unable to get a TV and a projector to decode captions. It might help with some other borderline decoders that are more forgiving.
I've tested on a "Raspberry Pi 2 Model B Rev 1.1" , running an up to date Raspberry Pi OS Lite, firmware version
921f5efeaed8a27980e5a6cfa2d2dee43410d60d
,Linux raspberrypi 5.15.78-v7+ #1599
.I used
raspi2png
to capture Frame Buffer data.boot.config
:Let me know if there's anything else you'd like me to try / debug.
The text was updated successfully, but these errors were encountered: