[davilla]

I doubt it, A10 is like AmLogic, no stagefright hw decode.

[Koying]

I doubt it, A10 is like AmLogic, no stagefright hw decode.

Ah ok, thanks.

[CruNcher]

All,

I you see lines like this in your log:

Code:

00:01:49 T:28888136   ERROR: CDVDVideoCodecStageFright:: - failed to open, codec(28), profile(100), level(51)
00:01:49 T:28888136   DEBUG: FactoryCodec - Video: stf-h264 - Failed

It means no HW decoder was found to play the requested file and thus SW ffmpeg was used.

Apparently, most A10 cannot. Are there postive reports using A10?

Im not sure if this has always to be the case ?

as this vc-1 bitstream in .mkv fails to be hardware decoded with XBMC

V/XBMC (11603): 03:42:45 T:1746372192 DEBUG: FactoryCodec - Video: stf-xxxx - Opening

I/OMXClient(11603): Using client-side OMX mux.

V/XBMC (11603): 03:42:45 T:1746372192 ERROR: CDVDVideoCodecStageFright:: - failed to open, codec(72), profile(3), level(3)

V/XBMC (11603): 03:42:45 T:1746372192 DEBUG: FactoryCodec - Video: stf-vc1 - Failed

V/XBMC (11603): 03:42:45 T:1746372192 DEBUG: FactoryCodec - Video: - Opening

V/XBMC (11603): 03:42:45 T:1746372192 DEBUG: SECTION:LoadDLL(libswresample-0-arm.so)

V/XBMC (11603): 03:42:45 T:1746372192 DEBUG: Loading: /data/data/org.xbmc.xbmc/lib/libswresample-0-arm.so

V/XBMC (11603): 03:42:45 T:1746372192 DEBUG: SECTION:LoadDLL(libavfilter-2-arm.so)

V/XBMC (11603): 03:42:45 T:1746372192 DEBUG: Loading: /data/data/org.xbmc.xbmc/lib/libavfilter-2-arm.so

V/XBMC (11603): 03:42:45 T:1746372192 NOTICE: CDVDVideoCodecFFmpeg::Open() Using codec: SMPTE VC-1



but this .mkv vc-1 plays Hardware decoded perfectly fine with the Stock RockChip Player and MX Player

though there is a difference most RockChip decoder are registered with the naming scheme omx.rk. a few though doesn't seem to share this and are named just like in the case of the VC-1 Decoder "VC1Decoder" im not sure if that plays into the Software Fallback in anyway.

V/XBMC ( 1782): 06:00:31 T:1746340176 DEBUG: FactoryCodec - Video: stf-xxxx - Opening

V/XBMC ( 1782): 06:00:31 T:1746340176 INFO: CBitstreamConverter::Open bitstream to annexb init

I/OMXClient( 1782): Using client-side OMX mux.

I/OMXCodec( 1782): [OMX.rk.video_decoder.avc] AVC profile = 100 (High), level = 40

I/OMXCodec( 1782): [OMX.rk.video_decoder.avc] video dimensions are 1920 x 818

I/ ( 100): init done status 0

V/XBMC ( 1782): 06:00:32 T:1746340176 DEBUG: CStageFrightVideo:: - component: OMX.rk.video_decoder.avc

V/XBMC ( 1782): 06:00:32 T:1746340176 DEBUG: FactoryCodec - Video: stf-h264 - Opened

V/XBMC ( 1782): 06:00:32 T:1746340176 NOTICE: Creating video thread




as here for H.264 you get the response from the Decoder with it's registered OMX component name
which is somehow not the case in the above VC-1 fail which just sends it failed to open the profile but not it's component name i find this somehow strange.

V/XBMC (11603): 03:42:45 T:1746372192 ERROR: CDVDVideoCodecStageFright:: - failed to open, codec(72), profile(3), level(3)

[Koying]

but this .mkv vc-1 plays Hardware decoded perfectly fine with the Stock RockChip Player and MX Player

Oh yeah. There could still be bugs in there, and, as I said, the next version should solve the one for VC-1 and others

as here for H.264 you get the response from the Decoder with it's registered OMX component name
which is somehow not the case in the above VC-1 fail which just sends it failed to open the profile but not it's component name i find this somehow strange

Well, the message says it couldn't find a component to play the file. It can hardly give you the name of a component, then

[CruNcher]

Makes perfect sense so it never reaches it and this message comes frome XBMC not finding the component for playback @ all i just thought the RK Bitstream parser might not accept the stream and thus fail i had a test case on the other players that im still looking @ that it rejects older asfbin fixed .wmv streams.
Could you redirect 10 bit bitstreams directly to the ffmpeg decoder for the RK VPU it makes no sense to play them it doesn't support them but their Parser doesn't seem to know the difference between 8 and 10 Bit which is somehow strange as in the aforementioned asfbin fixed VC-1 stream i guess the reject Problem has todo actually with the Bitdepth flag which seems to have been changed by asfbin to 16 bit

And do you have any idea yet what's might going on with those CPullup crashes i reported earlier ?

[davilla]

I doubt it from CPullup, more a symptom than the real cause.

[zeptic]

Running the 21/1-2013 version on a HTC Desire S without problems; movies (dvd rips) are accessed through SMB. Video performance have improved greatly compared to RC3. RC3 was choppy and the videos was unwatchable -- now they are smooth as butter ;O)

Playback does tend to get a bit choppy when OSD is displayed.

[poo706]

I tried it on my Mele A1000 (Allwinner A10) but none of the files I tested worked properly (~10 FPS). A thing I noticed is that XBMC is not affected by the "black screen" bug (both the stock player and MX Player will only show a black screen when the resolution in Android is set to 720p instead of 1080p). I guess XBMC fails to use the hardware decoder and uses software decoding instead.
Here is the debug log: http://pastebin.com/C0nYkWCT

What iteration of Android are you running on your A1000? The 720p black screen bug has been fixed for some time now. I recommend ThierryMerle's mod of the official 1.3 beta from Mele. http://www.slatedroid.com/topic/36614-me...ntry450173

[poo]

[Koying]

I doubt it from CPullup, more a symptom than the real cause.

I agree. Those are just log msg from another thread.

The first crash I don't know, but as I'm doing some serious refactoring, it might disappear on its own.
The second one doesn't seem to be directly XBMC

Code:

I/DEBUG   (   94): pid: 669, tid: 671, name: GC  >>> com.avast.android.mobilesecurity <<<

, although it might be memory exhaustion...

[Koying]

Here is my test with last built http://mirrors.xbmc.org/test-builds/andr...bi-v7a.apk

Wrong apk.

[Martijn]

Ho!
I though I had to use the last one?

Check what you download!
Always check OP for correct one

[MastaG]

Ned Scott, I've tried the 21/01/2013 build on my Galaxy S3 and Galaxy Tab2 running recent builds of CM10.1 (Android 4.2.1).
And it's working very well. No lags no stutters. Simply the best.
I was using the XAF build before with MX Player but that won't get me the OSD so I can't load the subtitle plugin.

Would it be possible to commit this to Frodo so it gets merged with the official release?

EDIT: I've tested various YouTube 1080p and Navi-X 720p and 1080p videos.
Also my 20GB 1080p Avatar bluray rip works fine (only tested this on my Tab2).

[Martijn]

Would it be possible to commit this to Frodo so it gets merged with the official release?

No

What about a check-box somewhere in the video settings like: "Enable experimental Android 4+ Hardware Acceleration".
And only make the box show on Android 4 devices.

no. if you want to use this you need to install the experimental version.

EDIT:
removed all of topic discussion!!

[vegarringdal]

Phone, samsung note 2 GT-7100

android 4.1.2,wanamLite rom v2.4


Log file
http://xbmclogs.com/show.php?id=30168

hddvd mkv 1080p vc1 ap l3 18mbps ac3 none Direct hddvd remux Very choppy
Monsters mkv 1080p h264 high profile 4.1 10mbps dts Unstyled subs Typical recompressed 1080p ok, about 23 fps I think

Both had sound

[eviltuna]

Hardware: iMito MX2 (RK3066)
Firmware: Stock November Firmware (v411)

Using version from 2013-1-21

hddvd mkv 1080p vc1 ap l3 18mbps ac3 none Direct hddvd remux - 9-11 FPS, very choppy, some artifact on start, sound stuttering, CPU0- 30-60% CPU1-70-100%
Planet mkv 720p h264 high profile 5.1 6mbps ac3 Unstyled subs Typical recompressed 720p - Everything playing great, constant 24fps, didn't see any issues CPU- both at 30-55%
Monsters mkv 1080p h264 high profile 4.1 10mbps dts Unstyled subs Typical recompressed 1080p - 15-18FPS, a bit choppy, no artifact, CPU0-50-70% CPU1-70-100%, froze up on second run

Logfile:
http://xbmclogs.com/show.php?id=30183


EDIT: Also tried some 720P Youtube videos and they worked great, didn't try 1080p youtube yet. Keep up the good work guys