Advanced users • PI 4 ATSC stream debugging with FFMPEG and azap

I have a PI 4 set up with a Happauge usb stick. I am trying to grab ATSC streams so i can check for errors. Running azap gives me

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
Version: 5.12 FE_CAN { ATSC + DVB-C (B) }
tuning to 563000000 Hz
video pid 0x0041, audio pid 0x0044
status 1f | signal f332 | snr 00f5 | ber ffffffff | unc 000000ff | FE_HAS_LOCK
status 1f | signal f5c1 | snr 00fa | ber ffffffff | unc 00000000 | FE_HAS_LOCK
status 1f | signal fae0 | snr 0107 | ber ffffffff | unc 00000000 | FE_HAS_LOCK
status 1f | signal f5c1 | snr 00fa | ber ffffffff | unc 00000000 | FE_HAS_LOCK
status 1f | signal f0a2 | snr 00f2 | ber ffffffff | unc 00000000 | FE_HAS_LOCK
status 1f | signal f5c1 | snr 00fb | ber ffffffff | unc 00000000 | FE_HAS_LOCK

which looks to be correct. Running

ffmpeg -f mpegts -i /dev/dvb/adapter0/dvr0 -loglevel debug -f null

Gives no output after all the library's are loaded.

Splitting the commandline.
Reading option '-f' ... matched as option 'f' (force format) with argument 'mpegts'.
Reading option '-i' ... matched as input url with argument '/dev/dvb/adapter0/dvr0'.
Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'null'.
Trailing option(s) found in the command: may be ignored.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option loglevel (set logging level) with argument debug.
Successfully parsed a group of options.
Parsing a group of options: input url /dev/dvb/adapter0/dvr0.
Applying option f (force format) with argument mpegts.
Successfully parsed a group of options.
Opening an input file: /dev/dvb/adapter0/dvr0.
[mpegts @ 0x28ec010] Opening '/dev/dvb/adapter0/dvr0' for reading
[file @ 0x28ec4e0] Setting default whitelist 'file,crypto,data'

That is where it stops. I have tried a few variations of the ffmpeg command with similar results. I feel the received channel is not making it past the tuner. Is this a PI limitation or am I missing something? I can debug multicast streams all day on this pi.....

Statistics: Posted by geosapien — Thu Jan 09, 2025 4:46 pm — Replies 0 — Views 37

---