I do augmented reality by using library QCAR. I also compiled and used opencv library, and coded in C++ in android NDK:
I have this code in my project:
CvCapture* g=NULL;
g=cvCaptureFromAVI("/sdcard/testa.avi");
if(g==NULL)
__android_log_print(ANDROID_LOG_DEBUG, "libnav","error");
else
__android_log_print(ANDROID_LOG_INFO, "libnav"," ok");
But when it run, i always got "error" in DDMS. I don't know whether android supports loading avi file. If not support, can android support flv, how to load it, which function we must use, maybe in opencv or opengl.
The purpose is get frame from video to texture the rectangle in opengl, (utterly C or C++ )
Please help me! i do it for my thesis.
thanks
Related
NanoGL is a small and fast object oriented open source graphics library for Windows Mobile, written entirely in C++. It is based on GAPI. and intended to support most PocketPC devices.
I was wondering, Since we have an alpha of Ubuntu, and an Ubuntu installer, anyone try setting up XBMCbuntu? When I get the chance I'll see whats needed to run regular Ubuntu and see if theres enough support in it to run the XBMCbuntu
There isn't. You might be able to kludge it to the point it boots XBMC, but it's pointless. The GPU isn't working in Ubuntu so video acceleration is non-existant. The audio doesn't work either, so you'd be able to lag through low-res videos without sound. Not a great experience. Ubuntu right now is NOT for multimedia, it works great for office, productivity, and programming but not multimedia.
The XBMC guys are focusing all their ARM dev into the Raspberry Pi at the moment. Would be kinda cool, though especially if the TP had HDMI out.
I believe they're working on a xbmc for Android, so hopefully we will have one soon
The current version (which you have to compile from source as no APK has been released to the non-dev community) runs pretty decently on the Touchpad. I haven't tried playing any videos with it, yet. I'll check and report later.
You can find unofficial builds of the Android XBMC build online and it actually seems to work fairly well. The XBMC interface has been adapted a bit to work with touch interfaces and overall it's quite nice. I had issues playing music, but had limited success streaming DVD ISO's from my server and playing other types of video content.
*deleted*
Based on what I've seen today it still has no:
- system dictionary for definition lookup(only for predictive text). The Kindle App does nothing when I press & hold on a word, unlike on my iOS device.
- hi-speed media scrubber for music. you know the little round knob on the progress bar that allows you to move the time index to any point in a song or video.
- unified search aka Local Search(apps, music, videos, contacts, emails)
The music app is pretty bad. I had several attempts to build a proper one, but the developer can not interact with the music library, other than playing existing playlists or songs.
You can't make custom playlists(actually you can, but it very, very, VERY complicated and prone to error and simply does not worth the shot), change the order of music inside the list and stuff like that for a third party app, and that sucks.
There are no new APIs for XNA (which is used to access the songs in the phone) so there is no way of making one.
If there is something I can say it is not right on WP, that's the music app.
mcosmin222 said:
The music app is pretty bad. I had several attempts to build a proper one, but the developer can not interact with the music library, other than playing existing playlists or songs.
You can't make custom playlists(actually you can, but it very, very, VERY complicated and prone to error and simply does not worth the shot), change the order of music inside the list and stuff like that for a third party app, and that sucks.
There are no new APIs for XNA (which is used to access the songs in the phone) so there is no way of making one.
If there is something I can say it is not right on WP, that's the music app.
Click to expand...
Click to collapse
Does that imply that there´s the same limitation for video? ...and ...as a result of that a videoplayer with support for more codecs is very unlikely to ever happen?
TarKin said:
Does that imply that there´s the same limitation for video? ...and ...as a result of that a videoplayer with support for more codecs is very unlikely to ever happen?
Click to expand...
Click to collapse
The File-Assosciation feature in WP8 works like this. Your App can define certain file endings (e.g. .mkv) which it can handle. If those are found on a SD-Card or downloaded the according registered App is then started for those files. The App can then do whatever it is it does as long as it keeps to reading the file (the original can't be manipulated although the app could copy it into it's isolated storage and manipulate it their). But there is one Caveat - there are several file extensions that are reserved for the OS which means that 3rd party Apps can't register for them. One of them is .mp3. Avi is another one of those (you can look them up in MSDN).
.mkv on the other hand is an extension that Windows Phone itself does not know so people could build Apps that would be able to consume them. Given that we now have Native Code capabilities writing a decoder or recompiling one written for another platform is possible, though it remains to be seen wether anyone will put the effort into it.
StevieBallz said:
The File-Assosciation feature in WP8 works like this. Your App can define certain file endings (e.g. .mkv) which it can handle. If those are found on a SD-Card or downloaded the according registered App is then started for those files. The App can then do whatever it is it does as long as it keeps to reading the file (the original can't be manipulated although the app could copy it into it's isolated storage and manipulate it their). But there is one Caveat - there are several file extensions that are reserved for the OS which means that 3rd party Apps can't register for them. One of them is .mp3. Avi is another one of those (you can look them up in MSDN).
.mkv on the other hand is an extension that Windows Phone itself does not know so people could build Apps that would be able to consume them. Given that we now have Native Code capabilities writing a decoder or recompiling one written for another platform is possible, though it remains to be seen wether anyone will put the effort into it.
Click to expand...
Click to collapse
ok. i was mainly into psp dev. before, and never had a winphone in my hands so far.
but if you say that´s possible, then i´ll go for the lumia920, reg. for a dev account and see what i can do
StevieBallz said:
The File-Assosciation feature in WP8 works like this. Your App can define certain file endings (e.g. .mkv) which it can handle. If those are found on a SD-Card or downloaded the according registered App is then started for those files. The App can then do whatever it is it does as long as it keeps to reading the file (the original can't be manipulated although the app could copy it into it's isolated storage and manipulate it their). But there is one Caveat - there are several file extensions that are reserved for the OS which means that 3rd party Apps can't register for them. One of them is .mp3. Avi is another one of those (you can look them up in MSDN).
.mkv on the other hand is an extension that Windows Phone itself does not know so people could build Apps that would be able to consume them. Given that we now have Native Code capabilities writing a decoder or recompiling one written for another platform is possible, though it remains to be seen wether anyone will put the effort into it.
Click to expand...
Click to collapse
I haven't had the chance to look over what the native code can do and what it can't do, but it is to be expected that it will have limitations, just like C# has.
You can render images (obviously) and output them using Direct3D which is pretty much what e.g. VLC does on the Desktop. You have complete read access to files on the SD-Card for your registered filetypes. MKV could be registered, MP3 or AVI could not (because they are in use by the system already).
But of course you would not be able to offload processing to the dedicated decoding units like with the built-in Codecs, which will mean more processor utilization and worse battery life. Still as a programmer I don't see too many actual road blocks (but it's a bumpy road to do this to be sure).
@TarKin: before you drop the money perhaps it would be best to start looking into the SDK. I'm not an expert in Multimedia-programming by any measure so you might be able to spot problems in there beforehand.
If you're still going for a L920 with these uncertainties for your use-case: welcome to the family, I'm anxiously awaiting mine.
Hey community
someone recently asked me per email how i do ROM Development.
i prefer to use Android Studio, but it doesnt fully support all, as some internal and hidden api's are just not visible.
This video shows you, how to expose these features and make use of them while coding
for example, if you implement new Methods and Constants etc, android studio wont pick them up and display them by default.
with doing this little trick, it does.
i think its really usefull, but decide yourself
oh, before i forget, sorry for the bad video, im just bad at recording
----------------------------
Video Recorded on Linux, Elementary OS using Kazam
Used Software, Scripts, etc:
Android Studio
Dex2Jar
----------------------------
Link: http://www.youtube.com/watch?v=C9vXkhZiEyc
Hello,
I would like to announce my newest project called OpenAuto.
Donate
What is OpenAuto?
OpenAuto is an open source AndroidAuto(tm) headunit emulator application based on aasdk library and Qt libraries. Main goal is to run AndroidAuto(tm) on the RaspberryPI 3 board computer smoothly.
Demo video: https://www.youtube.com/watch?v=k9tKRqIkQs8
Status
Project is currently under beta testing.
Links and open source code
https://github.com/f1xpl/openauto
Features
480p, 720p and 1080p with 30 or 60 FPS
RaspberryPI 3 hardware acceleration support to decode video stream (video stream up to [email protected])
Audio playback from all audio channels (Media, System and Speech)
Audio input for voice commands
Touchscreen and buttons input
Bluetooth
Automatic launch after device hotplug
User-friendly settings
Supported platforms
Linux
RaspberryPI 3
Windows
Before you start using OpenAuto please read Readme and wiki page. Also check OpenAuto Pro.
Whoa, nice work. Would this also have a audio EQ/Crossover interface for the Pi?
Can you post a Windows binary build please? Thanks
Daved+ said:
Can you post a Windows binary build please? Thanks
Click to expand...
Click to collapse
Is this at least possible OP? Noobs here, Thanks in advance.
Will this work as standalone or does it need the app?
"Do not use while driving" Well where is the fun in that?
look like someone may able create Open AA instead and resolve blocking issue by google..i guess
Time to give my ride a sweet upgrade
Will raspberry survive high or low temperatures?
I'm trying to compile it, but I got a bit rusty in building under linux.
Code:
[ 6%] Building CXX object CMakeFiles/autoapp.dir/src/autoapp/Main.cpp.o
In file included repos/android-auto/openauto/src/autoapp/Main.cpp:19:0:
repos/android-auto/openauto/include/f1x/openauto/autoapp/USB/USBMain.hpp:22:40: fatal error: f1x/aasdk/USB/USBWrapper.hpp: No such file or directory
#include <f1x/aasdk/USB/USBWrapper.hpp>
Did I forget something when configuring with cmake?
f1x said:
Hello,
I would like to announce my newest project called OpenAuto.
Donate
What is OpenAuto?
OpenAuto is an open source AndroidAuto(tm) headunit emulator application based on aasdk library and Qt libraries. Main goal is to run AndroidAuto(tm) on the RaspberryPI 3 board computer smoothly.
Demo video: https://www.youtube.com/watch?v=k9tKRqIkQs8
Status
Project is currently under beta testing.
Links and open source code
https://github.com/f1xpl/openauto
Features
480p, 720p and 1080p with 30 or 60 FPS
RaspberryPI 3 hardware acceleration support to decode video stream (video stream up to [email protected])
Audio playback from all audio channels (Media, System and Speech)
Audio input for voice commands
Touchscreen and buttons input
Bluetooth
Automatic launch after device hotplug
User-friendly settings
Supported platforms
Linux
RaspberryPI 3
Windows
Before you start using OpenAuto please read Readme and wiki page.
Click to expand...
Click to collapse
Hi! First of all, thank you for bring us this post! Amazing I've the same question as another guy here, Could you post the Windows binaries or link to the step by step to get it running under windows?
Thanks a lot in advance!
Seriously impressive, great work.
Works perfectly on my Pixel 2/PI3.
Do you think it would be possible to get Android Auto Wireless functionality at a later point? Or does this require some specific wireless/bluetooth protocol that Google hasn't released just yet?
bluethoot
What can you do with the bluethoot feature ?
xbenjiiman said:
Seriously impressive, great work.
Works perfectly on my Pixel 2/PI3.
Click to expand...
Click to collapse
Thanks for your feedback. Great to see it working .
Zaf9670 said:
Do you think it would be possible to get Android Auto Wireless functionality at a later point? Or does this require some specific wireless/bluetooth protocol that Google hasn't released just yet?
Click to expand...
Click to collapse
I think it will be possible but needs some time and effort to implement it. OpenAuto is a hobbyist project and I cannot promise the exact deadline but this feature is on the TODO list.
brett1996 said:
What can you do with the bluethoot feature ?
Click to expand...
Click to collapse
What do you mean?
f1x said:
I think it will be possible but needs some time and effort to implement it. OpenAuto is a hobbyist project and I cannot promise the exact deadline but this feature is on the TODO list.
Click to expand...
Click to collapse
I wasn't sure how much of Android Auto is "open" to use. I haven't invested too much time looking into these forks like Auto and Wear but I know they're not quite as public as standard Android. At least that is the take I have gotten over the past few years.
Hopefully it's something that won't require some sort of specific hardware. Best of luck! I hope to test this out on my Pi 3 in a few weeks myself. I'll be sure to keep tabs on the project!
I promise I'm not one of those XDA ETA/update zombies.
Woohoo!! Thank you for this effort!
I'm curious which hardware, aside from the Pi, has been used successfully so far? Is that the Raspberry Pi Foundation touch display? Any HATs?
Thanks again!
-Chad
MasterCLC said:
Woohoo!! Thank you for this effort!
I'm curious which hardware, aside from the Pi, has been used successfully so far? Is that the Raspberry Pi Foundation touch display? Any HATs?
Thanks again!
-Chad
Click to expand...
Click to collapse
Only Raspberry PI 3 has been tested so far in case of embedded platforms. Code itself is portable for any Linux-based or Windows platforms. If hardware acceleration of video decoding is supported by underlying backend used in Qt multimedia library (GStreamer for Linux and DirectShow for Windows) then OpenAuto will run smoothly without additional effort. If hardware acceleration is not supported by underlying backends then it must be implemented in OpenAuto (like in case of Raspberry PI 3).
I apologize, I meant in addition to the Pi, not alternative platforms. Things like which screen is it that you've used, any HATs on your Pi, etc. ?
Thank you!
MasterCLC said:
I apologize, I meant in addition to the Pi, not alternative platforms. Things like which screen is it that you've used, any HATs on your Pi, etc. ?
Thank you!
Click to expand...
Click to collapse
Screen is the official one from PI Foundation (7''). Basically any screen should be suitable to run OpenAuto (as long as it is supported by the OS that hosts OpenAuto). The same for other hardware.
Dude! You're my hero, I've been playing around with so many ways to get this working, yours seems to be the perfect solution, I'll take it for a test drive tomorrow