I posted something a while back about FF/REW not working as well
starting with V0.29, but I'm now thinking it may have started because I
upgraded my hardware and version at the same time and maybe it's because
of the hardware change and Intel onboard vs Nvidia.
Since V0.31, my frontend crashes if I try too many things during FF/REW
(like reversing direction). Today I got around to taking a look at the
frontend output during FF (after a FE crash) and, although this doesn't
show a crash, it shows a LOT of output during FF operation. The sample,
below, repeats over and over during FF (which is not very smooth or
responsive to control input). I'm thinking the performance problem is
due to the FE continuously attempting to "va_openDriver()" and
re-creating "VAAPI 1.6 display for VAAPI DRM".
Is this normal? Should I be installing something that's missing?
Should I try different playback profiles or change some settings? Might
this be an indication of what's causing the poor FF performance and/or
crashes?
Dave D.
Sample of frontend output during FF (repeats continuously during FF):
libva info: VA-API version 1.6.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
2020-04-20 20:38:38.388774 I [1149386/1149386] CoreContext
opengl/mythopenglinterop.cpp:264:DeleteTextures OpenGLInterop: Deleted
2 textures in 1 groups
2020-04-20 20:38:38.392268 I [1149386/1149386] CoreContext
mythplayer.cpp:3096:ProcessCallbacks Player(0): Executing VAAPI context
creation
2020-04-20 20:38:38.392286 I [1149386/1149386] CoreContext
opengl/mythopenglinterop.cpp:158:GetInteropType OpenGLInterop:
Rendering supported for frame type 'VAAPI' with VAAPI DRM
2020-04-20 20:38:38.393373 I [1149386/1149386] CoreContext
opengl/mythvaapiinterop.cpp:116:InitaliseDisplay VAAPIInterop: Created
VAAPI 1.6 display for VAAPI DRM (Intel i965 driver for Intel(R) Coffee
Lake - 2.4.0)
2020-04-20 20:38:38.393722 W [1149386/1149386] CoreContext
decoders/mythcodeccontext.cpp:415:NewHardwareFramesContext
MythCodecContext: Error: 6 concurrent hardware frames contexts
2020-04-20 20:38:38.407721 I [1149386/1149504] Decoder
mythplayer.cpp:3081:HandleDecoderCallback Player(0): Queuing callback
for VAAPI context creation
libva info: VA-API version 1.6.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
2020-04-20 20:38:38.507889 W [1149386/1149504] Decoder
mythplayer.cpp:3085:HandleDecoderCallback Waited 100ms for VAAPI
context creation
2020-04-20 20:38:38.544701 I [1149386/1149386] CoreContext
opengl/mythopenglinterop.cpp:264:DeleteTextures OpenGLInterop: Deleted
2 textures in 1 groups
2020-04-20 20:38:38.549544 I [1149386/1149386] CoreContext
mythplayer.cpp:3096:ProcessCallbacks Player(0): Executing VAAPI context
creation
2020-04-20 20:38:38.549567 I [1149386/1149386] CoreContext
opengl/mythopenglinterop.cpp:158:GetInteropType OpenGLInterop:
Rendering supported for frame type 'VAAPI' with VAAPI DRM
2020-04-20 20:38:38.550344 I [1149386/1149386] CoreContext
opengl/mythvaapiinterop.cpp:116:InitaliseDisplay VAAPIInterop: Created
VAAPI 1.6 display for VAAPI DRM (Intel i965 driver for Intel(R) Coffee
Lake - 2.4.0)
2020-04-20 20:38:38.550458 W [1149386/1149386] CoreContext
decoders/mythcodeccontext.cpp:415:NewHardwareFramesContext
MythCodecContext: Error: 6 concurrent hardware frames contexts
2020-04-20 20:38:38.555658 I [1149386/1149504] Decoder
mythplayer.cpp:3081:HandleDecoderCallback Player(0): Queuing callback
for VAAPI context creation
2020-04-20 20:38:38.655913 W [1149386/1149504] Decoder
mythplayer.cpp:3085:HandleDecoderCallback Waited 100ms for VAAPI
context creation
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
starting with V0.29, but I'm now thinking it may have started because I
upgraded my hardware and version at the same time and maybe it's because
of the hardware change and Intel onboard vs Nvidia.
Since V0.31, my frontend crashes if I try too many things during FF/REW
(like reversing direction). Today I got around to taking a look at the
frontend output during FF (after a FE crash) and, although this doesn't
show a crash, it shows a LOT of output during FF operation. The sample,
below, repeats over and over during FF (which is not very smooth or
responsive to control input). I'm thinking the performance problem is
due to the FE continuously attempting to "va_openDriver()" and
re-creating "VAAPI 1.6 display for VAAPI DRM".
Is this normal? Should I be installing something that's missing?
Should I try different playback profiles or change some settings? Might
this be an indication of what's causing the poor FF performance and/or
crashes?
Dave D.
Sample of frontend output during FF (repeats continuously during FF):
libva info: VA-API version 1.6.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
2020-04-20 20:38:38.388774 I [1149386/1149386] CoreContext
opengl/mythopenglinterop.cpp:264:DeleteTextures OpenGLInterop: Deleted
2 textures in 1 groups
2020-04-20 20:38:38.392268 I [1149386/1149386] CoreContext
mythplayer.cpp:3096:ProcessCallbacks Player(0): Executing VAAPI context
creation
2020-04-20 20:38:38.392286 I [1149386/1149386] CoreContext
opengl/mythopenglinterop.cpp:158:GetInteropType OpenGLInterop:
Rendering supported for frame type 'VAAPI' with VAAPI DRM
2020-04-20 20:38:38.393373 I [1149386/1149386] CoreContext
opengl/mythvaapiinterop.cpp:116:InitaliseDisplay VAAPIInterop: Created
VAAPI 1.6 display for VAAPI DRM (Intel i965 driver for Intel(R) Coffee
Lake - 2.4.0)
2020-04-20 20:38:38.393722 W [1149386/1149386] CoreContext
decoders/mythcodeccontext.cpp:415:NewHardwareFramesContext
MythCodecContext: Error: 6 concurrent hardware frames contexts
2020-04-20 20:38:38.407721 I [1149386/1149504] Decoder
mythplayer.cpp:3081:HandleDecoderCallback Player(0): Queuing callback
for VAAPI context creation
libva info: VA-API version 1.6.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
2020-04-20 20:38:38.507889 W [1149386/1149504] Decoder
mythplayer.cpp:3085:HandleDecoderCallback Waited 100ms for VAAPI
context creation
2020-04-20 20:38:38.544701 I [1149386/1149386] CoreContext
opengl/mythopenglinterop.cpp:264:DeleteTextures OpenGLInterop: Deleted
2 textures in 1 groups
2020-04-20 20:38:38.549544 I [1149386/1149386] CoreContext
mythplayer.cpp:3096:ProcessCallbacks Player(0): Executing VAAPI context
creation
2020-04-20 20:38:38.549567 I [1149386/1149386] CoreContext
opengl/mythopenglinterop.cpp:158:GetInteropType OpenGLInterop:
Rendering supported for frame type 'VAAPI' with VAAPI DRM
2020-04-20 20:38:38.550344 I [1149386/1149386] CoreContext
opengl/mythvaapiinterop.cpp:116:InitaliseDisplay VAAPIInterop: Created
VAAPI 1.6 display for VAAPI DRM (Intel i965 driver for Intel(R) Coffee
Lake - 2.4.0)
2020-04-20 20:38:38.550458 W [1149386/1149386] CoreContext
decoders/mythcodeccontext.cpp:415:NewHardwareFramesContext
MythCodecContext: Error: 6 concurrent hardware frames contexts
2020-04-20 20:38:38.555658 I [1149386/1149504] Decoder
mythplayer.cpp:3081:HandleDecoderCallback Player(0): Queuing callback
for VAAPI context creation
2020-04-20 20:38:38.655913 W [1149386/1149504] Decoder
mythplayer.cpp:3085:HandleDecoderCallback Waited 100ms for VAAPI
context creation
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org