Jump to content

Emby won't tune 12.1 NBC (Phoenix) via HDHR. Other channels work fine. 12.1 works in HDHR app.


RandallC

Recommended Posts

RandallC

@cayars - Looks like nope.  No errors, it creates the folder for the recording with all the metadata but then same error when I try to play back.  I looked on my NAS and there is no video file there.

Link to comment
Share on other sites

From a web browser can you run this then upload the sample file please.

http://192.168.1.28:5004/auto/v12.1?duration=120

That should create a 2 minute file so it's shouldn't take long to upload.

Link to comment
Share on other sites

At first glance I don't see anything wrong with the recording and it will transcode fine through Emby.

I see just a couple errors but they aren't unusual
17:13:17.131 [mpeg2video @ 000001fac6ff1900] Invalid frame dimensions 0x0. Last message repeated 10 times
17:13:17.163 [mpegts @ 000001fac6fd1b00] PES packet size mismatch Last message repeated 1 times

I honestly don't have an idea what the issue might be.
I don't know if this will give us more info or not but could you try going to scheduled tasks and doing a log rotation.
Then go to log menu and turn on debug option.
Try a playback from web for that channel.
Turn off debug log
Upload the server and any transcode logs for that time frame.

Link to comment
Share on other sites

Haven't looked yet but was this one playback that created 3 different ffmpeg logs?

Link to comment
Share on other sites

RandallC

Actually I think it created two of them.  The third had a timestamp slightly earlier so I wasn't 100% sure.  So - probably ignore the one ending in b0b_1.txt.

 

Link to comment
Share on other sites

All the ffmpeg logs show basically the same thing and for some reason Emby can't identify the codecs used in this stream

15:06:12.170 [mpegts @ 000002ca13e80680] PES packet size mismatch
15:06:12.171 [mpegts @ 000002ca13e80680] probed stream 0 failed
15:06:12.172 [mpegts @ 000002ca13e80680] Could not find codec parameters for stream 0 (Unknown: none): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
15:06:12.172 Input #0, mpegts, from 'http://127.0.0.1:8096/LiveTv/LiveStreamFiles/868e4e84c95f41299cdeac524d74e2a2/stream.ts':
15:06:12.173   Duration: N/A, start: 67241.871956, bitrate: N/A
15:06:12.173   Program 1 
15:06:12.173   No Program
15:06:12.173     Stream #0:0[0x35]: Unknown: none, Start-Time 67241.872s
15:06:12.175 Stream specifier 'v:0' in filtergraph description [v:0]format@f1=pix_fmts=yuv420p[f1_out0] matches no streams.

Grasping at straws here but is the firmware on this tuner from 2021?

@softworkz I think we've exhausted things we can look at, time to call in the big dog. :)

Link to comment
Share on other sites

RandallC

This is probably nothing, but should the address referenced be localhost and not the address of the tuner?  

15:06:12.172 Input #0, mpegts, from 'http://127.0.0.1:8096/LiveTv/LiveStreamFiles/868e4e84c95f41299cdeac524d74e2a2/stream.ts':

 

And yep, the tuner is running 20210422.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...