Jump to content


Photo

replacing h264 software encoder with ffmpeg on ics and later possible ?

- - - - -

  • Please log in to reply
6 replies to this topic

#1
lunario

lunario

    Regular

  • Members
  • PipPip
  • 94 posts
  • Gender:Male
  • Location:Portugal
  • Devices:zte blade (sapo a5)
maybe this already covered but I saw this http://stackoverflow...fmpeg-based-one then in there I saw this too http://omxil.sourceforge.net/ and http://limoa.sourceforge.net/. maybe someone can be make this work to get hq you tube on arm6

  • 0

#2
Rdogg112

Rdogg112

    Newbie

  • Members
  • Pip
  • 11 posts
  • Gender:Male
  • Devices:ZTE Libra/Blade
It can probably be done, "OMX" itself isn't a library, it's a specification like OpenGL, OpenCL, Open*, they have to be implemented by whoever wants to use them, I even contacted Khronos, the guys who make the specification and they stated that Android(Google/Manufacturers) need's to do it, not them since they just specify the standards.

  • 0

#3
lunario

lunario

    Regular

  • Members
  • PipPip
  • 94 posts
  • Gender:Male
  • Location:Portugal
  • Devices:zte blade (sapo a5)
yes I know but its more like replacing omx for ffmpeg to achieve the same effect without relying on qualcom or others

  • 1

#4
Rdogg112

Rdogg112

    Newbie

  • Members
  • Pip
  • 11 posts
  • Gender:Male
  • Devices:ZTE Libra/Blade
Yeah, but We'd have to modify the apps themselves for that, because ffmpeg doesn't have the same methods/functions as a OMX API, so it would require some work, but it could be done ;).

  • 0

#5
TehStalker

TehStalker

    Regular

  • Members
  • PipPip
  • 57 posts
  • Gender:Male
  • Devices:ZTE Blade
From the information available I have gathered that the problem is that the necessary proprietary libraries needed for hardware acceleration are note working anymore due to changes in recent versions of android. The magic is done by a certain processor called QDSP5, and the specifications for this one are not publicly available. Therefore, porting anything over to the blade and using this processor will be very hard. Is this correct or am I completely wrong?

If this is correct however, what happens if you revert/modify the Android code that changed between 2.3 and 4.0 that made the libraries not work anymore? Would this not work for any special reasons? Certain issues might occur, but could you in theory wedge in 2.3 video code and perhaps an 2.3 youtube .apk?

Everything I have written might be complete nonsense, so sorry, but I am curious.

  • 0

#6
vNa5h

vNa5h

    Addict

  • Members
  • PipPipPipPipPip
  • 774 posts
  • Gender:Male
  • Location:India
  • Devices:Dell XCD35 (ZTE Blade)
any progress on this..

  • 0

Dell XCD35 a.k.a ZTE Blade a.k.a Orange San Fransisco

Powered by

CM10.1 KonstaKANG, Soundmagic PL11 earphones, Samsung class 6 16GB



Apps installed

TV Shows / Movies .....I have watched....


#7
t0mm13b

t0mm13b

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 1,784 posts
  • Gender:Male
  • Location:Ireland
  • Devices:GT-S8500,Zte Blade,SE ST15i
  • Twitter:@t0mm13b

From the information available I have gathered that the problem is that the necessary proprietary libraries needed for hardware acceleration are note working anymore due to changes in recent versions of android. The magic is done by a certain processor called QDSP5, and the specifications for this one are not publicly available. Therefore, porting anything over to the blade and using this processor will be very hard. Is this correct or am I completely wrong?

If this is correct however, what happens if you revert/modify the Android code that changed between 2.3 and 4.0 that made the libraries not work anymore? Would this not work for any special reasons? Certain issues might occur, but could you in theory wedge in 2.3 video code and perhaps an 2.3 youtube .apk?

Everything I have written might be complete nonsense, so sorry, but I am curious.


The OMX libs are proprietary to Qualcomm for the ARMv6 chipset, perhaps its a licensing issue, so it would be no-go!

  • 0
try{ not_laugh; }catch{ FAIL; }finally{ laugh; }




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users