VLC For Android May Arrive In Early 2011
dkd903 writes "The development of an Android client for VLC has been going on for months now, but it has been slowed down by the fact that Android's multimedia output libraries are in Java. VLC itself is based on C and so translating them to Java is difficult and takes time. With the newer Android NDK, however, using native codes for Android apps has been becoming easier. So, the VLC developers have developed two basic modules for audio and video output based on the new NDK and most of the VLC libraries have been ported to Android."
This isn't going to use battery at all, especially since VLC's codecs aren't hardware accelerated...
No link?
but does this mean VLC for android will have limited codec support for now? Bring it to be honest, Archos has stopped providing some exotic ones, until I grab my wallet, in the new fw update of my 101 and free is better.
Any thoughts?
What the fuck?
I know it's not VNC (or is it?) or Android, but I'm looking for a way to share my local Windows 7 desktop across the LAN to another Windows 7 user who watches as I do something onscreen. And a recorder to play it back. If the recorder can take a microphone narration, that's perfect.
Is something like that built into Windows 7? Or is there a free app that can do it?
--
make install -not war
This is good news, as I love VLC player. However, and correct me if I'm wrong, but the platform only supports select codecs so essentially it will be just like any other media player in terms of supported media?
None of the pre-existing audio APIs for Android have proven very satisfactory so far, at least for anything that requires high performance and/or low latency - see the following links for details: http://createdigitalmusic.com/2010/05/android-2-2-badly-needed-improvements-to-audio-touch-more-whats-missing/ http://code.google.com/p/android/issues/detail?id=3434 However, it looks like OpenSL ES will provide the necessary C APIs VLC needs. Still, I guess any vestigial Java ports might prove useful for other platforms (J2ME maybe). On the other hands, whether Gingerbread will satisfy the requirements of audio creativity app developers is another question. It seems the ES standard might lack the rigor required for properly performant low latency audio apps. Some may doubt the value of such apps, but they are experiencing a huge boom in popularity on the iPad and iPhone. The multitouch surface offers a hugely expressive interface. With a bit more rigor from Google and phone manufacturers, it could seriously open up the market for realtime audio creativity apps on Android.
http://gigaom.com/video/vlc-for-android-coming-soon/
Not that there's much to it.
egypt urnash minimal art.
support so I dont have a clue what the VLC guys are going on about... more info here
the NDK has been available for years - what has taken them so long to find this out? create a texture, pass a pointer to it and compile the codec natively. nit more than a one-day job if you know what you are doing. the issue is more about the optimizations of the codecs, not the language barrier.
They're using Java for the frontend and some of the backend, with C++ for the codecs, obviously.
Really, do want.
This entire post/threads seems to be lacking some important information:
1) The Android SDK is a subset of java commands + android specific ones that are then compiled into DEX bytecode by the SDK to run on the Dalvik VM (which is MUCH MUCH more efficient than JVM, is *nix thread safe, *nix process separate, etc... a lot of nice things... )
2) The Android NDK is for development of native (ARM assembly) code to be used by java objects for specific tasks
2.1) This allows a portion of an API/object to be processed with assembly/open GL/etc
2.2) This portion of the API/object will be called by an Android DEX bytecode app (an "App" as we mostly know it)
3) So VLC has used the NDK to translate their C code into ARM assembly/other stuff? and probably made a single class/object that "does" the audio/video portions of the VLC application, and that will be created/used by the GUI class/object
Hope this helps clarify things for those who didn't know
... because I have been streaming video from VLC on my Android phone for months. Using VLC Stream & Convert.
Not only does it have VLC, it also has mplayer and friends. That, and you can get USB out of it too.
Local video, networked video, and no VM in between you and your media.
Twitter supports and protects racists - by smearing their critics with the "Hate Speech" label.
With the newer Android NDK, however, using native codes for Android apps has been becoming easier.
Codes, plural? What exactly is "one code"?
"Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
I love the idea of VLC. I can't imagine the blood, sweat and tears that went into this labor of love. It does a few things that QuickTime can't.
But the fact is that after so many years it is still buggy on my Macs (can't even start, stop or scroll thru a video reliably) and I have never been able to export even a simple video to another format (could be my ignorance). QuickTime on Mac is relatively solid, exports flawlessly, and offers some commonsense play options that VLC lacks.
Are we expecting a miracle in VLC for Android? Instant success? I recommend a great deal of patience.
...omphaloskepsis often...
Does anyone know if they are able to access and use the native multimedia decoders in Android directly? http://stackoverflow.com/questions/3912563
VLC is oft quoted as being based on Qt, and I notice that Qt is being ported to Android (and iOS). I wonder if these facts are related.
Max.
Cool, but vplayer already plays just about everything on android. What will vlc add?
I've found it very hard to find a player on Android that can handle pretty much any video format. But recently a new player has appeared that's superb: VPLAYER BETA. Seriously, give it a go. It might be beta, but it's working better than RockPlayer does, which was my previous favourite.
Not for the faint of heart, but there's Android (Nitdroid) for the N900:
Link
Twitter supports and protects racists - by smearing their critics with the "Hate Speech" label.
Ok, VLC is a pretty pluggable architecture... well even if it is a nightmare to code in. It's still a fair bit more manageable than coding for either GStreamer or ffmpeg.
You can easily change out or extend nearly every component of a CODEC on VLC. So, here's how it'll work :
1) Someone will port the code to run on Android
2) Someone will say "wow it works, but H.264 is so slow it makes my eyes want to bleed"
3) Someone will make it faster by optimizing for ARM.
4) Someone will add hardware decoding for a specific ARM chip from a specific vendor.
5) Someone will initiate a project to standardize the hardware acceleration decoding architecture on Android
6) Google summer of code will sponser a project to finish it.
7) The coder involved will start school again
8) The project will be forgotten
9) The forums will be filled with "Is there anyone working on this anymore" questions followed by guys who don't know how to code but seem to think they are "experts" providing useless responses including "it wouldn't be that hard to pick up the project an finish it".
10) Someone will eventually get sick of waiting and 2 years later release something useful.