[mythtv-users] MythTV Raspberry Pi2 - Raspbian Jessie Image Testing

[Curtis Gedak]

This post contains observations from testing two different RPi2 0.27.x
tarballs on Raspbian Jessie, and some questions.

Ref  Image
---  ------------------------------------------------
PB   mythtv-raspi-v0.27.6-62-gbb9eec4.tar.bz2
LR   mythtv-v0.27.5-115-g00c0993-RPI2-jessie.tar.bz2

Both of these mythtv images play smooth video and clear sound.

For comparison I looked at bug reports/tickets that mention
"Raspberry" so that I can test these specific items.

Following are my observations:


#12643 - Raspberry pi: Failure when resolution changes
https://code.mythtv.org/trac/ticket/12643

PB: Example video from this ticket plays and doesn't crash.  About 10
    seconds in it shows "Please Wait..." and then resumes with the
    next section of video.

LR: Example video from this ticket plays for about 10 seconds,
    displays "Please Wait..." and then crashes.


#12644 - Raspberry pi: Loses sound when skipping backwards
https://code.mythtv.org/trac/ticket/12644

PB: The sound immediately returned when skipping backwards (for
    example enter "5" and then "left arrow" key).

LV: Sound disappears when skipping backwards.  Sound can be returned
    if skip forward.


#12675 - Raspberry pi: Need a default video display profile for OpenMAX
https://code.mythtv.org/trac/ticket/12675

PB: Not implemented.

LV: Not implemented.


#12677 - Raspberry Pi: jerkiness and interrupted audio during OSD
https://code.mythtv.org/trac/ticket/12677

PB: There is still an issue and is much worse with themes that use
    larger OSD displays.

LV: OSD is rock steady with no noticeable jerkiness when using eglfs.
    All is not perfect though because if OSD fade is enabled and then
    it adversely impacts audio.


Peter,

Is there anything specific you would like me to test with the image
you created?

I'd like to help where I can.  Next I will see if I can locate and
compile your code.

Note that I have signed up to the mythtv-dev mailing list in case that
is a more appropriate location for discussion.

Regards,
Curtis