Skip to content
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

Regression in H264 decoding #126

Open
jeanpijon opened this issue Nov 15, 2014 · 6 comments
Open

Regression in H264 decoding #126

jeanpijon opened this issue Nov 15, 2014 · 6 comments

Comments

@jeanpijon
Copy link

Hi Pipelka,
I believe I am facing regression problem from #41
when switching to HD channel on 0624 with oscam+dvbapi I am getting theese errors:

Nov 15 23:50:21 htpc vdr: [10973] XVDR: Stream: H264 PID: 2010 1920x1080 DAR: 1,78 FPS: 25,000 (parsed: yes)
Nov 15 23:50:21 htpc vdr: [10973] XVDR: Stream: MPEG2AUDIO PID: 2020 48000 Hz, 2 channels, Lang: cze (parsed: yes)
Nov 15 23:50:21 htpc vdr: [10973] XVDR: Stream: AC3 PID: 2070 48000 Hz, 6 channels, Lang: cze (parsed: yes)
Nov 15 23:50:21 htpc vdr: [10973] XVDR-Error: transport error
Nov 15 23:50:22  vdr: last message repeated 710 times
Nov 15 23:50:22 htpc vdr: [10973] XVDR: sync found at offset 1840 (streamtype: AC3 / 4140 bytes in buffer / framesize: 1536 bytes)
Nov 15 23:50:22 htpc vdr: [10973] XVDR-Error: transport error
Nov 15 23:50:22  vdr: last message repeated 410 times
Nov 15 23:50:22 htpc vdr: [10973] XVDR: sync found at offset 686 (streamtype: MPEG2AUDIO / 2082 bytes in buffer / framesize: 576 bytes)
Nov 15 23:50:22 htpc vdr: [10973] XVDR-Error: transport error
Nov 15 23:50:22  vdr: last message repeated 205 times
Nov 15 23:50:22 htpc vdr: [10973] XVDR: sync found at offset 1684 (streamtype: AC3 / 4246 bytes in buffer / framesize: 1536 bytes)
Nov 15 23:50:22 htpc vdr: [10973] XVDR-Error: transport error
Nov 15 23:50:23  vdr: last message repeated 219 times
Nov 15 23:50:23 htpc vdr: [10973] XVDR: sync found at offset 282 (streamtype: MPEG2AUDIO / 2218 bytes in buffer / framesize: 576 bytes)
Nov 15 23:50:23 htpc vdr: [10973] XVDR-Error: transport error
Nov 15 23:50:23  vdr: last message repeated 327 times
Nov 15 23:50:23 htpc vdr: [10973] XVDR: sync found at offset 64 (streamtype: AC3 / 4140 bytes in buffer / framesize: 1536 bytes)

I am 100%sure, that this is not because of antenna - I've just connected to the same cable standalone set-top-box and HD is decoded fine.

I would be glad, if someone can look at it...
I am able to supply more info if requested...

Thanks a lot
Jan

@pipelka
Copy link
Owner

pipelka commented Nov 15, 2014

It looks like a reception problem.
If it's a regression, please tell me which version worked for you.

Regards
Alex

@jeanpijon
Copy link
Author

Sorry for confusion, I read ticket, which you closed (#41) and I think, this is exactly the same thing. I know, that it looks like a reception problem, but I am 100% sure, that reception is OK. moreover, it does this only on one transponder... I would give you a streamdump, but unfortunatelly I don't know exactly how to make it...

@pipelka
Copy link
Owner

pipelka commented Nov 16, 2014

Please make a recording of this channel and check if it's playing fine.
Give me a bit more infos when this problem surfaced first. Maybe you
updated vdr, dvbapi or xvdr?

@jeanpijon
Copy link
Author

I am using vdr 2.1.6, latest git of DVBAPI and XVDR, oscam r9965.
It started when they changed something on TP, at least encoding from QAM to 8PSK and FEC from 3/4 to 5/6... I have XBMC Gotham 13.2 as frontend with latest xvdr addon. If I record that corrupted chanell in xbmc and afterwards will try to play it back. it does look the same, not correct video data...

@pipelka
Copy link
Owner

pipelka commented Nov 16, 2014

If the recording is also corrupted it is a reception problem. The recording
is done entirely within vdr (there isn't any demuxing done by xvdr).

I suspect it's a problem of your DVB device. Maybe you are able to check
with different hardware.

@juriad
Copy link

juriad commented Jan 25, 2015

I had problems with multipe "XVDR-Error: transport error" and sometimes it even fails to decode channel. What helped me was to restart the server until it starts working. I supose that the problem is caused by the card (TBS6981 in my case). Everything is in the latest stable versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants