When switching to ZDF based transponder it takes several seconds until sound is heard #98
Comments
|
I can confirm this one. For me, it happens intermittently (maybe in one of five cases). While for other channels, sound is there always immediately, for ZDF HD it sometimes takes several seconds as described by @Space2Man |
|
Mar 11 18:01:45 [vdr] [10723] ERROR: TS packet not accepted in Transfer Mode make sure to check dmesg for driver issues like audio or video or dvb |
|
One thing to note ... this happens also on other ZDF based channels like ZDFinfo. Picture is there right from the beginning but after some time there is this brief pause and then sound is there also. There are no errors in dmesg btw and issue was only noticed on ZDF based channels ... maybe related to DD soundformat? Need to investigate during next downtime window :) |
|
And if I remember I only started to notice this recently ... but can't remember when it started ... |
|
Yes, also noticed that only quite recently. But right now (with latest git state) I cannot reproduce it anymore. Not sure if this is coincidence, caused by the program currently sent, or if it has been fixed by one of today's commits (I believe I still saw it yesterday). |
|
I still can reproduce the issue on current commit (53d44aa) ... but it seems to happen only (and not every time) if I come from a different transponder ... If I switch between two ZDF transponders I could not reproduce it ... on my system with Nvidia + softhddev I can not reproduce ... I need to test with some old commits and see if I can find the place where it showed up for the first time. |
|
I can confirm this issue too, but here the involved channels are not only from ZDF. |
|
Funny thing is ... by accident only the SATIP server was used after restart today and then I could not reproduce this issue ... |
|
after some testing SATIP completely got stuck and I saw lot's of
and the picture froze forever. But that's something completely different ... so I am not sure if this is related to Sat reception or something else ... if other people have the same issue it still might be an issue in vaapidevice. Because with Nvidia I never had this issue ... |
|
have seen this also here but could not identify jet whats the root cause |
|
With the last commit, the problem is still present. System: Kernel: 4.15.0-11-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: N/A vainfo: VA-API version: 1.1 (libva 2.1.0) ffmpeg version 3.4.2-1build1 Copyright (c) 2000-2018 the FFmpeg developers 7 220 SVDRP VideoDiskRecorder 2.3.8; Thu Mar 15 09:40:00 2018; UTF-8 |
|
Hi, even with current VDR + vaapidevice I could reproduce the issue: And find attached the current report of my system: ... VAAPIDEVICE SYSTEM INFORMATION REPORTinxivainfoffmpeggccsvdrpsendINCLUDE THIS REPORT INTO YOUR GITHUB ISSUE... |
|
the only change on the vdr-2.3.9 is rate limit the the logging to 1 per minute for the "TS packet not accepted in Transfer Mode" message, so nothing to expect here |
|
Yes, I know, but I thought from the commit message that maybe a6aac5f would have helped ... |
|
For me this is a serious issue and I can't use the plugin in the current stage :( |
|
I'm unable to reproduce this issue. Does the plugin setting "Soft start a/v sync" have any effect? |
|
@pesintta : VAAPIDEVICE SYSTEM INFORMATION REPORTinxivainfoffmpeggccsvdrpsendINCLUDE THIS REPORT INTO YOUR GITHUB ISSUE |
|
Can I do anything to help trace this issue? Some log level? |
When switching to ZDF based transponder there is silence for several seconds, then the picture stops for a brief moment and then both sound and picture are available (in this case at 18:01:45):
Best regards,
VAAPIDEVICE SYSTEM INFORMATION REPORT
inxi
vainfo
ffmpeg
gcc
svdrpsend
INCLUDE THIS REPORT INTO YOUR GITHUB ISSUE
The text was updated successfully, but these errors were encountered: