Autor Thema: Problem video when use PiP  (Gelesen 9445 mal)

Dima73

  • Jr. Member
  • **
  • Beiträge: 73
    • Profil anzeigen
Problem video when use PiP
« am: April 17, 2016, 01:21:05 Nachmittag »
Сhecked in ET85000/Formuler1/OS mini , tuners Sundtek DVB-T/C or DVB-S2
image openPLi

Example for test:
1)Activate PiP(live tv show service X/PiP window show service X)
2)Disable PiP --> PiP window close --> live tv stop video(pause) audio it runs at this moment.

The problem itself:
When close video decoder 1 --> video decoder 0(live tv) video not work

log:
<  1234.473> [eDVBCAService] new service 1:0:1:29E3:3CF0:13E:820000:0:0:0::Союз Int
<  1234.474> [eDVBCAService] add demux 0 to slot 0 service 1:0:1:29E3:3CF0:13E:820000:0:0:0::Союз Int
<  1234.474> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1234.475> [eDVBSectionReader] DMX_SET_FILTER pid=0
<  1234.475> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1234.476> [eDVBSectionReader] DMX_SET_FILTER pid=18
<  1234.480> RemovePopup, id = ZapError
<  1234.480> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1234.480> [eDVBSectionReader] DMX_SET_FILTER pid=0
<  1234.484> [eDVBFrontend] sleep 500ms
<  1234.847> [eDVBServicePMTHandler] PATready
<  1234.847> [eDVBServicePMTHandler] use pmtpid 00df for service_id 29e3
<  1234.847> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1234.848> [eDVBSectionReader] DMX_SET_FILTER pid=223
<  1234.848> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1234.848> [eDVBSectionReader] DMX_SET_FILTER pid=0
<  1234.850> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1234.850> [eDVBSectionReader] DMX_SET_FILTER pid=357
<  1234.851> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1234.851> [eDVBSectionReader] DMX_SET_FILTER pid=17
<  1235.034> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1235.034> [eDVBSectionReader] DMX_SET_FILTER pid=457
<  1235.036> [eDVBServicePlay] eventNewProgramInfo timeshift_enabled=0 timeshift_active=0
<  1235.038> [eDVBServicePlay] have 1 video stream(s) (00f3), and 1 audio stream(s) (00fd), and the pcr pid is 00f3, and the text pid is ffffffff
<  1235.039> [eTSMPEGDecoder] decoder state: play, vpid=00f3, apid=00fd
<  1235.040> [eDVBVideo0] VIDEO_SLOWMOTION 0 ok
<  1235.040> [eDVBVideo0] VIDEO_FAST_FORWARD 0 ok
<  1235.040> [eDVBVideo0] VIDEO_CONTINUE ok
<  1235.040> [eDVBAudio0] AUDIO_CONTINUE ok
<  1235.310> [eDVBCIInterfaces] gotPMT
<  1235.311> [eDVBCAService] don't build/send the same CA PMT twice
<  1235.311> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1235.311> [eDVBSectionReader] DMX_SET_FILTER pid=223
<  1235.317> [eDVBVideo0] VIDEO_GET_EVENT SIZE_CHANGED 544x576 aspect 2
<  1235.448> [eDVBVideo0] VIDEO_GET_EVENT FRAME_RATE_CHANGED 25000 fps
<  1235.448> [eDVBVideo0] VIDEO_GET_EVENT PROGRESSIVE_CHANGED 0
<  1235.449> [eDVBVideo0] VIDEO_GET_EVENT SIZE_CHANGED 544x576 aspect 2
<  1235.577> [eDVBVideo0] VIDEO_GET_EVENT FRAME_RATE_CHANGED 25000 fps
<  1235.578> [eDVBVideo0] VIDEO_GET_EVENT PROGRESSIVE_CHANGED 0
<  1235.579> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1235.580> [eDVBSectionReader] DMX_SET_FILTER pid=459
<  1235.582> [Dish] tuning failed
<  1235.727> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1235.727> [eDVBSectionReader] DMX_SET_FILTER pid=18
<  1235.854> [eDVBServicePMTHandler] sdt update done!
<  1241.584> action ->  ColorActions blue
<  1241.602> [SKIN] Parsing embedded skin <embedded-in-'PictureInPictureZapping'>
<  1241.634> [SKIN] Parsing embedded skin <embedded-in-'Dishpip'>
<  1241.690> playing pip service 1:0:1:29E3:3CF0:13E:820000:0:0:0::Союз Int
<  1241.691> [eDVBResourceManager] use cached_channel
<  1241.691> [eDVBServicePMTHandler] allocate Channel: res 0
<  1241.692> [eDVBCIInterfaces] addPMTHandler 1:0:1:29E3:3CF0:13E:820000:0:0:0::Союз Int
<  1241.692> [eDVBChannel] getDemux cap=01
<  1241.692> [eDVBServicePMTHandler] ok ... now we start!!
<  1241.692> [eDVBServicePlay] eventNewProgramInfo timeshift_enabled=0 timeshift_active=0
<  1241.692> [eDVBServicePlay] have 1 video stream(s) (00f3), and 1 audio stream(s) (00fd), and the pcr pid is 00f3, and the text pid is ffffffff
<  1241.692> [eDVBChannel] getDemux cap=01
<  1241.693> [eTSMPEGDecoder] decoder state: play, vpid=00f3, apid=ffffffff
<  1241.693> [eDVBVideo] Video Device: /dev/dvb/adapter0/video1
<  1241.694> [eDVBVideo] demux device: /dev/dvb/adapter0/demux0
<  1241.694> [eDVBVideo1] VIDEO_SET_STREAMTYPE 0 - ok
<  1241.694> [eDVBVideo1] DMX_SET_PES_FILTER pid=0x00f3 ok
<  1241.694> [eDVBVideo1] DEMUX_START ok
<  1241.695> [eDVBVideo1] VIDEO_FREEZE ok
<  1241.695> [eDVBVideo1] VIDEO_PLAY ok
<  1241.700> [eDVBVideo1] VIDEO_SLOWMOTION 0 ok
<  1241.700> [eDVBVideo1] VIDEO_FAST_FORWARD 0 ok
<  1241.700> [eDVBVideo1] VIDEO_CONTINUE ok
<  1241.701> [eDVBCAService] add demux 0 to slot 1 service 1:0:1:29E3:3CF0:13E:820000:0:0:0::Союз Int
<  1241.701> [eDVBCAService] don't build/send the same CA PMT twice
<  1241.701> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1241.701> [eDVBSectionReader] DMX_SET_FILTER pid=0
<  1241.702> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1241.702> [eDVBSectionReader] DMX_SET_FILTER pid=18
<  1241.702> [eDVBChannel] getDemux cap=00
<  1241.993> [eDVBServicePMTHandler] PATready
<  1241.994> [eDVBServicePMTHandler] use pmtpid 00df for service_id 29e3
<  1241.994> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1241.994> [eDVBSectionReader] DMX_SET_FILTER pid=223
<  1241.995> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1241.995> [eDVBSectionReader] DMX_SET_FILTER pid=0
<  1241.996> [eDVBServicePlay] eventNewProgramInfo timeshift_enabled=0 timeshift_active=0
<  1241.998> [eDVBServicePlay] have 1 video stream(s) (00f3), and 1 audio stream(s) (00fd), and the pcr pid is 00f3, and the text pid is ffffffff
<  1241.999> [eTSMPEGDecoder] decoder state: play, vpid=00f3, apid=ffffffff
<  1241.999> [eDVBVideo1] VIDEO_SLOWMOTION 0 ok
<  1241.999> [eDVBVideo1] VIDEO_FAST_FORWARD 0 ok
<  1241.999> [eDVBVideo1] VIDEO_CONTINUE ok
<  1242.001> [eDVBCIInterfaces] gotPMT
<  1242.001> [eDVBCAService] don't build/send the same CA PMT twice
<  1242.001> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1242.001> [eDVBSectionReader] DMX_SET_FILTER pid=223
<  1242.309> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  1242.309> [eDVBSectionReader] DMX_SET_FILTER pid=18
<  1242.467> [eDVBVideo1] VIDEO_GET_EVENT SIZE_CHANGED 544x576 aspect 2
<  1242.467> [eDVBVideo1] VIDEO_GET_EVENT FRAME_RATE_CHANGED 25000 fps
<  1242.467> [eDVBVideo1] VIDEO_GET_EVENT PROGRESSIVE_CHANGED 0
<  1242.468> [eDVBVideo1] VIDEO_GET_EVENT SIZE_CHANGED 544x576 aspect 2
<  1242.468> [eDVBVideo1] VIDEO_GET_EVENT FRAME_RATE_CHANGED 25000 fps
<  1242.468> [eDVBVideo1] VIDEO_GET_EVENT PROGRESSIVE_CHANGED 0
1088
<  1244.770> [eConsoleAppContainer] Starting /bin/sh
<  1244.777> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 68(16)
<  1245.909> action ->  myShowHideActions hide
<  1247.145> action ->  MsgBoxActions ok
<  1247.168> [eTSMPEGDecoder] decoder state: play, vpid=ffffffff, apid=ffffffff
<  1247.169> [eDVBVideo1] DEMUX_STOP  ok
<  1247.210> [eDVBVideo1] VIDEO_STOP ok
<  1247.210> [eDVBVideo1] destroy
<  1247.210> [eDVBCAService] free slot 0 demux 0 for service 1:0:1:29E3:3CF0:13E:820000:0:0:0::Союз Int
<  1247.211> [eDVBCAService] don't build/send the same CA PMT twice
<  1249.649> [eDVBLocalTimerHandler] diff is 0
<  1249.650> [eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
<  1249.650> [eDVBLocalTimerHandler] not changed
<  1249.652> [eDVBChannel] getDemux cap=00
<  1251.242> action ->  GlobalActions volumeUp



I see this problem for two years.

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 7784
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #1 am: April 17, 2016, 01:23:23 Nachmittag »
Enigma2 problem - this is unrelated to us.
Sundtek Support Engineer

Dima73

  • Jr. Member
  • **
  • Beiträge: 73
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #2 am: April 17, 2016, 01:33:13 Nachmittag »
Why do you think so, what basis?

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 7784
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #3 am: April 17, 2016, 02:25:09 Nachmittag »
We only register our tuner in the system and use those interfaces which are available.
We have nothing to do with PiP.
Sundtek Support Engineer

Dima73

  • Jr. Member
  • **
  • Beiträge: 73
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #4 am: April 17, 2016, 02:55:45 Nachmittag »
We only register our tuner in the system and use those interfaces which are available.
We have nothing to do with PiP.
This is not a problem with the internal DVB-T tuners.
I'll try to deal with this on an Enigma level.If possible.
When enigma if there is no error, then I'll get back to you.

Okay, another question.
TimeShift is not working tuners DVB-T/C or DVB-S2.
Like this?

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 7784
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #5 am: April 17, 2016, 02:56:57 Nachmittag »
Image problem, timeshifting is working (last tested with VTI and Vu+).

Have a closer look at the debug logs of enigma2.
Sundtek Support Engineer

Dima73

  • Jr. Member
  • **
  • Beiträge: 73
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #6 am: April 17, 2016, 03:29:37 Nachmittag »
Image problem, timeshifting is working (last tested with VTI and Vu+).

Have a closer look at the debug logs of enigma2.
<  2428.776> [eDVBServicePlay] have 1 video stream(s) (1416), and 1 audio stream(s) (1417), and the pcr pid is 1416, and the text pid is ffffffff
<  2428.777> [eTSMPEGDecoder] decoder state: pause, vpid=1416, apid=1417
<  2428.777> [eDVBVideo0] VIDEO_SLOWMOTION 0 ok
<  2428.777> [eDVBVideo0] VIDEO_FAST_FORWARD 0 ok
<  2428.777> [eDVBVideo0] VIDEO_FREEZE ok
<  2428.777> [eDVBAudio0] AUDIO_PAUSE ok
<  2428.777> [eDVBServicePlay] timeshift
<  2428.778> [eDVBServicePlay] timeshift
<  2428.779> [eDVBServicePlay] timeshift
<  2428.780> [eDVBServicePlay] timeshift
<  2428.780> resolved to PAUSE
<  2428.780> [eDVBServicePlay] pause
<  2428.781> [eDVBServicePlay] timeshift
<  2428.781> [eDVBServicePlay] timeshift
<  2428.783> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2428.783> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2428.783> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2428.786> [eDVBServicePlay] timeshift
<  2428.787> [eDVBServicePlay] timeshift
<  2428.891> [eDVBServicePlay] seekTo -90000
<  2428.891> [eDVBChannel] seek.
<  2428.892> [eFilePushThread] wait for driver eof aborted by signal
<  2428.892> [eFilePushThread] waiting for pause
<  2428.892> [eFilePushThread] PAUSED
<  2428.894> [eDVBAudio0] AUDIO_CLEAR_BUFFER ok
<  2428.921> [eDVBVideo0] VIDEO_CLEAR_BUFFER ok
<  2428.930> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2428.930> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2428.930> [eDVBChannel] getLength failed - can't seek relative to end!
<  2428.930> [eDVBServicePlay] timeshift
<  2428.931> [eDVBServicePlay] timeshift
<  2428.932> New timeshift filename:  20160417 1624 - Riga TV24 - Rampas ugunis
<  2428.937> [eDVBChannel] pvrEvent evtStopped
<  2429.180> [eFilePushThread] wait for driver eof timeout
<  2429.284> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2429.284> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2429.285> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2429.430> [eFilePushThread] wait for driver eof timeout
<  2429.681> [eFilePushThread] wait for driver eof timeout
<  2429.784> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2429.784> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2429.784> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2429.931> [eFilePushThread] wait for driver eof timeout
<  2430.182> [eFilePushThread] wait for driver eof timeout
<  2430.284> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2430.284> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2430.284> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2430.432> [eFilePushThread] wait for driver eof timeout
<  2430.580> [eEPGCache] schedule finished(1460899475)
<  2430.682> [eFilePushThread] wait for driver eof timeout
<  2430.784> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2430.785> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2430.785> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2430.933> [eFilePushThread] wait for driver eof timeout
<  2431.183> [eFilePushThread] wait for driver eof timeout
...........................
<  2466.915> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2466.915> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2466.915> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2466.990> [eFilePushThread] wait for driver eof timeout
<  2467.240> [eFilePushThread] wait for driver eof timeout
<  2467.415> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2467.415> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2467.415> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2467.491> [eFilePushThread] wait for driver eof timeout
<  2467.741> [eFilePushThread] wait for driver eof timeout
<  2467.992> [eFilePushThread] wait for driver eof timeout
<  2468.242> [eFilePushThread] wait for driver eof timeout
<  2468.251> [eDVBServicePlay] timeshift
<  2468.251> action ->  InfobarTimeshiftActions timeshiftStop
<  2468.251> [eDVBServicePlay] timeshift
<  2468.252> [eDVBServicePlay] timeshift
<  2468.492> [eFilePushThread] wait for driver eof timeout
<  2468.743> [eFilePushThread] wait for driver eof timeout
<  2468.993> [eFilePushThread] wait for driver eof timeout
<  2469.243> [eFilePushThread] wait for driver eof timeout
<  2469.494> [eFilePushThread] wait for driver eof timeout
<  2469.744> [eFilePushThread] wait for driver eof timeout
<  2469.782> action ->  MsgBoxActions ok
<  2469.799> [eDVBServicePlay] timeshift
<  2469.799> [eDVBServicePlay] SwitchToLive
<  2469.800> [eFilePushThread] stopping thread
<  2469.800> [eFilePushThread] wait for driver eof aborted by signal
<  2469.800> [eFilePushThread] STOP
<  2469.801> [eTSMPEGDecoder] decoder state: play, vpid=ffffffff, apid=ffffffff
<  2469.801> [eDVBVideo0] DEMUX_STOP  ok
<  2469.802> [eDVBVideo0] VIDEO_STOP ok
<  2469.802> [eDVBVideo0] destroy
<  2469.802> [eDVBAudio0] AUDIO_STOP ok
<  2469.826> [eDVBAudio0] DEMUX_STOP ok
<  2469.830> [eDVBAudio0] AUDIO_CONTINUE ok
<  2469.830> [eDVBAudio0] destroy
cleaning up
TuxTxt cache cleared
<  2469.836> [eDVBServicePlay] have 1 video stream(s) (1416), and 1 audio stream(s) (1417), and the pcr pid is 1416, and the text pid is ffffffff
<  2469.837> [eDVBChannel] getDemux cap=01
TuxTxt cache cleared
<  2469.842> [eTSMPEGDecoder] decoder state: play, vpid=1416, apid=1417
<  2469.842> [eDVBPCR0] DMX_SET_PES_FILTER pid=0x1416 ok
<  2469.842> [eDVBPCR0] DEMUX_START ok
<  2469.843> [eDVBAudio0] DMX_SET_PES_FILTER pid=0x1417 ok
<  2469.843> [eDVBAudio0] DEMUX_START ok
<  2469.843> [eDVBAudio0] AUDIO_SET_BYPASS bypass=1 ok
<  2469.843> [eDVBAudio0] AUDIO_PAUSE ok
<  2469.843> [eDVBAudio0] AUDIO_PLAY ok
<  2469.845> [eDVBVideo] Video Device: /dev/dvb/adapter0/video0
<  2469.845> [eDVBVideo] demux device: /dev/dvb/adapter0/demux0
<  2469.845> [eDVBVideo0] VIDEO_SET_STREAMTYPE 1 - ok
<  2469.846> [eDVBVideo0] DMX_SET_PES_FILTER pid=0x1416 ok
<  2469.846> [eDVBVideo0] DEMUX_START ok
<  2469.846> [eDVBVideo0] VIDEO_FREEZE ok
<  2469.846> [eDVBVideo0] VIDEO_PLAY ok
<  2469.852> [eDVBVideo0] VIDEO_SLOWMOTION 0 ok
<  2469.852> [eDVBVideo0] VIDEO_FAST_FORWARD 0 ok
<  2469.852> [eDVBVideo0] VIDEO_CONTINUE ok
<  2469.852> [eDVBAudio0] AUDIO_CONTINUE ok
<  2469.852> [eDVBTeletextParser] Starting!
<  2469.852> [eDVBTeletextParser] disable teletext subtitles page ffffffffffffffff (und)
<  2469.852> [eDVBPESReader] Created. Opening demux
<  2469.852> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  2469.852> [eDVBTeletextParser] created teletext subtitle PES reader!
<  2469.852> [eDVBPESReader] Created. Opening demux
<  2469.853> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  2469.853> [eDVBTeletextParser] starting PES reader on pid=ffffffff
<  2469.853> [eDVBServicePlay] timeshift
<  2469.854> resolved to PLAY
<  2469.854> [eDVBServicePlay] unpause
<  2469.855> [eDVBServicePlay] timeshift
<  2469.855> [eDVBServicePlay] timeshift
<  2469.858> resolved to PLAY
<  2469.858> [eDVBServicePlay] unpause
<  2469.858> [eDVBServicePlay] timeshift
<  2469.859> [eDVBServicePlay] timeshift
<  2469.861> [eFilePushThreadRecorder] stopping thread.
<  2469.862> [eDVBRecordFileThread] waiting for aio to complete
<  2469.862> [eDVBRecordFileThread] buffer usage histogram (20 buffers of 188 kB)
<  2469.862> [eDVBRecordFileThread]   1:      2
<  2469.862> [eFilePushThreadRecorder] THREAD STOP
<  2469.863> [eDVBServicePlay] remove timeshift files
<  2469.863> [setIoPrio] best-effort level 7 ok
<  2469.863> [eBackgroundFileEraser] deleting '/media/hdd/timeshift/timeshift.jSOCkV.del'
<  2469.864> [eDVBServicePlay] timeshift
<  2469.867> not pauseable.
<  2469.868> [eDVBServicePlay] timeshift
<  2471.099> [eDVBVideo0] VIDEO_GET_EVENT SIZE_CHANGED 704x576 aspect 2
<  2471.172> [eDVBVideo0] VIDEO_GET_EVENT FRAME_RATE_CHANGED 25000 fps
<  2471.172> [eDVBVideo0] VIDEO_GET_EVENT PROGRESSIVE_CHANGED 0
<  2471.173> [eDVBVideo0] VIDEO_GET_EVENT FRAME_RATE_CHANGED 25000 fps
<  2471.173> [eDVBVideo0] VIDEO_GET_EVENT PROGRESSIVE_CHANGED 0
<  2480.830> [eEPGCache] schedule other finished(1460899526)
<  2480.831> [eEPGCache] stop caching events(1460899526)
<  2480.831> [eEPGCache] next update in 60 min
963

Dima73

  • Jr. Member
  • **
  • Beiträge: 73
    • Profil anzeigen

Dima73

  • Jr. Member
  • **
  • Beiträge: 73
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #8 am: April 20, 2016, 09:10:48 Vormittag »
Ok.
Timeshift not work only ET/xtrend box.
This problem ET/xtrend drivers.

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 7784
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #9 am: April 20, 2016, 10:29:51 Vormittag »
Dreamboxes and Vu+ also work without problem.
Sundtek Support Engineer

Dima73

  • Jr. Member
  • **
  • Beiträge: 73
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #10 am: April 20, 2016, 06:11:35 Nachmittag »
Ok.This not sundtek problem.
Tested on avermedia a857 same problem(stop video when close pip)

PLi and ATV image again same problem.

PiP work OK for formuler1.

PiP problem again drivers Xtrend.
« Letzte Änderung: April 20, 2016, 07:51:51 Nachmittag von Dima73 »

Dima73

  • Jr. Member
  • **
  • Beiträge: 73
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #11 am: September 22, 2016, 12:30:01 Nachmittag »
VU+solo4k
timeshift no problems
PiP no problems

Only wrong DVB API v5 statistics

Dima73

  • Jr. Member
  • **
  • Beiträge: 73
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #12 am: September 23, 2016, 07:57:10 Nachmittag »

Sundtek DVB-S/S2 (IV) is type DVB-C!!!

root@vusolo4k:~# dvb-fe-tool -f 11
Device vtuner fe (/dev/dvb/adapter0/frontend11) capabilities:
     CAN_FEC_1_2
     CAN_FEC_2_3
     CAN_FEC_3_4
     CAN_FEC_5_6
     CAN_FEC_7_8
     CAN_FEC_AUTO
     CAN_GUARD_INTERVAL_AUTO
     CAN_INVERSION_AUTO
     CAN_QAM_16
     CAN_QAM_64
     CAN_QAM_AUTO
     CAN_QPSK
     CAN_TRANSMISSION_MODE_AUTO
DVB API Version 5.10, Current v5 delivery system: DVBC/ANNEX_A
Supported delivery systems:
     DVBS
    [DVBC/ANNEX_A]
     DVBS
     DVBS2
     DVBC/ANNEX_C
root@vusolo4k:~# dvb-fe-tool -f 10
Device vtuner fe (/dev/dvb/adapter0/frontend10) capabilities:
     CAN_FEC_1_2
     CAN_FEC_2_3
     CAN_FEC_3_4
     CAN_FEC_5_6
     CAN_FEC_7_8
     CAN_FEC_AUTO
     CAN_GUARD_INTERVAL_AUTO
     CAN_INVERSION_AUTO
     CAN_QAM_16
     CAN_QAM_64
     CAN_QAM_AUTO
     CAN_QPSK
     CAN_TRANSMISSION_MODE_AUTO
DVB API Version 5.10, Current v5 delivery system: DVBS
Supported delivery systems:
    [DVBS]
     DVBC/ANNEX_A
    [DVBS]
     DVBS2
     DVBC/ANNEX_C
DiSEqC VOLTAGE: OFF
ERROR    FE_SET_VOLTAGE: Operation not permitted
root@vusolo4k:~# dvb-fe-tool -f 9
Device Vuplus FE (/dev/dvb/adapter0/frontend9) capabilities:
     CAN_FEC_1_2
     CAN_FEC_2_3
     CAN_FEC_3_4
     CAN_FEC_5_6
     CAN_FEC_7_8
     CAN_FEC_AUTO
     CAN_INVERSION_AUTO
     CAN_QPSK
     CAN_RECOVER
DVB API Version 5.10, Current v5 delivery system: DVBS
Supported delivery systems:
    [DVBS]
     DVBS2
DiSEqC VOLTAGE: OFF
ERROR    FE_SET_VOLTAGE: Operation not permitted
root@vusolo4k:~#  cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 0
NIM Socket 1:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 1
NIM Socket 2:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 2
NIM Socket 3:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 3
NIM Socket 4:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 4
NIM Socket 5:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 5
NIM Socket 6:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 6
NIM Socket 7:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 7
NIM Socket 8:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 8
        I2C_Device: 4
NIM Socket 9:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 9
        I2C_Device: 4

NIM Socket 10:
        Type: DVB-T
        Name: Sundtek DVB-T (III) (1/0) (USB)
        Frontend_Device: 10
NIM Socket 11:
        Type: DVB-S2
        Name: Sundtek DVB-S/S2 (IV) (0/0) (USBDVB-S2
        Frontend_Device: 11root@vusolo4k:~#

Dima73

  • Jr. Member
  • **
  • Beiträge: 73
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #13 am: September 24, 2016, 11:09:02 Nachmittag »
and
dvb-fe-tool -f 10 =  Sundtek DVB-S/S2
?????
vusolo4k login: root
root@vusolo4k:~#  cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 0
NIM Socket 1:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 1
NIM Socket 2:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 2
NIM Socket 3:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 3
NIM Socket 4:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 4
NIM Socket 5:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 5
NIM Socket 6:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 6
NIM Socket 7:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 7
NIM Socket 8:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 8
        I2C_Device: 4
NIM Socket 9:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 9
        I2C_Device: 4

NIM Socket 10:
        Type: DVB-S2
        Name: Sundtek DVB-S/S2 (IV) (0/0) (USBDVB-S2
        Frontend_Device: 10root@vusolo4k:~#  dvb-fe-tool -f 11
ERROR    No such file or directory while opening /dev/dvb/adapter0/frontend11
root@vusolo4k:~#  dvb-fe-tool -f 10
Device vtuner fe (/dev/dvb/adapter0/frontend10) capabilities:
     CAN_FEC_1_2
     CAN_FEC_2_3
     CAN_FEC_3_4
     CAN_FEC_5_6
     CAN_FEC_7_8
     CAN_FEC_AUTO
     CAN_GUARD_INTERVAL_AUTO
     CAN_INVERSION_AUTO
     CAN_QAM_16
     CAN_QAM_64
     CAN_QAM_AUTO
     CAN_QPSK
     CAN_TRANSMISSION_MODE_AUTO
DVB API Version 5.10, Current v5 delivery system: DVBS
Supported delivery systems:
    [DVBS]
     DVBC/ANNEX_A
    [DVBS]
     DVBS2
     DVBC/ANNEX_C
DiSEqC VOLTAGE: OFF
ERROR    FE_SET_VOLTAGE: Operation not permitted
root@vusolo4k:~#  dvb-fe-tool -f 9
Device Vuplus FE (/dev/dvb/adapter0/frontend9) capabilities:
     CAN_FEC_1_2
     CAN_FEC_2_3
     CAN_FEC_3_4
     CAN_FEC_5_6
     CAN_FEC_7_8
     CAN_FEC_AUTO
     CAN_INVERSION_AUTO
     CAN_QPSK
     CAN_RECOVER
DVB API Version 5.10, Current v5 delivery system: DVBS
Supported delivery systems:
    [DVBS]
     DVBS2
DiSEqC VOLTAGE: OFF
ERROR    FE_SET_VOLTAGE: Operation not permitted
root@vusolo4k:~#  dvb-fe-tool -f 10
Device vtuner fe (/dev/dvb/adapter0/frontend10) capabilities:
     CAN_FEC_1_2
     CAN_FEC_2_3
     CAN_FEC_3_4
     CAN_FEC_5_6
     CAN_FEC_7_8
     CAN_FEC_AUTO
     CAN_GUARD_INTERVAL_AUTO
     CAN_INVERSION_AUTO
     CAN_QAM_16
     CAN_QAM_64
     CAN_QAM_AUTO
     CAN_QPSK
     CAN_TRANSMISSION_MODE_AUTO
DVB API Version 5.10, Current v5 delivery system: DVBS
Supported delivery systems:
    [DVBS]
     DVBC/ANNEX_A
    [DVBS]
     DVBS2
     DVBC/ANNEX_C
DiSEqC VOLTAGE: OFF
ERROR    FE_SET_VOLTAGE: Operation not permitted
root@vusolo4k:~#

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 7784
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #14 am: September 25, 2016, 02:38:17 Nachmittag »
I think this is rather a bug in the vtuner module, if the appropriate commands would be forwarded to the driver itself it would show up the correct information.

I think the command for retrieving the information directly from the driver is:
/opt/bin/mediaclient --frontendinfo /dev/dvb/adapter1/frontend0

aside of that you might try your commands the following way:
export LD_PRELOAD=/opt/lib/libmediaclient.so
dvb-fe-tool -f 10

I think we override the frontends in adapter0 for engima2 so it will even skip the vtuner implementation. The export will take care that the override mechanism is active.
« Letzte Änderung: September 25, 2016, 03:47:15 Nachmittag von Sundtek »
Sundtek Support Engineer