Well, thats basically how it should work. Commented code doesn't get executed uncommented does:
# decode_MPG2=0x00000000 -> commented -> mpg2 hardware codec not active
decode_MPG2=0x00000000 -> uncommented -> mpg2 hardware codec active
sure, but isn´t the hardware encoded way the better one ?
Sure it should be the better one. But you said it works better if uncommented, uncommented means hardware decode is active. But maybe I understood you wrong there.
I edited the previous post to be more clear.
(2015-03-06, 13:53)da-anda Wrote: [ -> ]@Fraludio - absolutely unrelated to this thread - please ask in general help.
I tried with kodi 14.1 stable and it works, so it seems it HAS something to do with these builds.
(2015-03-07, 12:17)Trickname Wrote: [ -> ]this is strange:
when i use purcased mp2 codec my livetv is stuttering and out of sync
i tryed to uncommend decode_MPG2 and livetv works fine.
setup is: rpi2 build 304 using dvbviewer with win8 DD cine c/t
same with tvheadend but openelec 5.0.5 works with enabled codec
Does disabling deinterlace (with hardware decode enabled) help?
Note: software decode doesn't support deinterlace.
(2015-03-07, 10:09)Milhouse Wrote: [ -> ]With the two test commits reverted, the menu dirty region rendering is back to normal (low CPU, <2% on 1GHz Pi2).
Yes, it's "test: Set and reset the dirty flag in a more sane way" - I've reverted it.
when i disabling deinterlace it looks a little bit better from startup
but have best results when disabled mpg2 hardware codec
sorry FlowT:
i mix up something
# decode_MPG2 = good results
decode_MPG2 = stuttering
decode_MPG2 + disabling deinterlace = little stuttering after playing few minutes A/V not sync
(2015-03-07, 13:53)Trickname Wrote: [ -> ]when i disabling deinterlace it looks a little bit better from startup
but have best results when disabled mpg2 hardware codec
Do you see this behaviour from a recording? If so can you upload a sample?
(2015-03-07, 14:14)Trickname Wrote: [ -> ]when i play the recorded file all is fine 
You are saying that recordings don't have the problem (with hardware decode enabled)?
Did any earlier Milhouse builds behave better with hardware decode enabeled?
yes hardware decode is enabled
the problem is since i have my rpi2 with all millhouse-rpi2 builds
this is not with OE beta build (5.0.5) also tryed OSMC and recalboxOS with no problems
But the file you uploaded to dropbox - does it have any problems playing?
(2015-03-07, 13:23)Fraludio Wrote: [ -> ] (2015-03-06, 13:53)da-anda Wrote: [ -> ]@Fraludio - absolutely unrelated to this thread - please ask in general help.
I tried with kodi 14.1 stable and it works, so it seems it HAS something to do with this builds.
I stand corrected then, sorry for that. It's just that reports like this occured so often in the past and where always related to a wrong file structure inside the zip of some random github downloads
(2015-03-07, 13:23)Fraludio Wrote: [ -> ]I tried with kodi 14.1 stable and it works, so it seems it HAS something to do with this builds.
Do you mean OE 5.0.5 or some other build?
