Great - look like version 4 will be noticeably better than version 3.
I've been busy updating the version 4 library.
- The OutlineTextView has now been implemented so that'll enable someone (?) to test the VitamioMediaController SetInfoView (OutlineTextView1 As OutlineTextView) method.
- VitamioVideoView now has a GetMediaPlayer As VitamioMediaPlayer method which: Returns the underlying MediaPlayer used by the VitamioVideoView. The VitamioMediaPlayer has various methods which may be useful.
- The new VitamioMediaPlayer has methods that allow you to: get the current frame as a bitmap, enable/disable interlacing, enable/disable adaptive stream support and also set the playback speed.
- The VitamioMediaPlayer also has a method GetTrackInfo As VitamioTrackInfo[] which returns an array of VitamioTrackInfo objects - presumably giving you detailed info about the tracks being played.
- Lastly i have added some more of the class constants in VitamioVideoView.
Most of these updates are untested - i'll upload the new version and make time to play with the new methods later.
Updated library files available here:
http://android.martinpearman.co.uk/b4a/temp/VitamioBundle4_library_files_20130725.zip.
Demo b4a project link is in my previous post.
Martin.
Great - look like version 4 will be noticeably better than version 3.
I've been busy updating the version 4 library.
- The OutlineTextView has now been implemented so that'll enable someone (?) to test the VitamioMediaController SetInfoView (OutlineTextView1 As OutlineTextView) method.
- VitamioVideoView now has a GetMediaPlayer As VitamioMediaPlayer method which: Returns the underlying MediaPlayer used by the VitamioVideoView. The VitamioMediaPlayer has various methods which may be useful.
- The new VitamioMediaPlayer has methods that allow you to: get the current frame as a bitmap, enable/disable interlacing, enable/disable adaptive stream support and also set the playback speed.
- The VitamioMediaPlayer also has a method GetTrackInfo As VitamioTrackInfo[] which returns an array of VitamioTrackInfo objects - presumably giving you detailed info about the tracks being played.
- Lastly i have added some more of the class constants in VitamioVideoView.
Most of these updates are untested - i'll upload the new version and make time to play with the new methods later.
Updated library files available here:
http://android.martinpearman.co.uk/b4a/temp/VitamioBundle4_library_files_20130725.zip.
Demo b4a project link is in my previous post.
Martin.
following with interest devolpments regarding vitamio bundle 4. i have used the wrapper 1.05 with a fair amount of success.
there are a few quirks (eg, not being able to play certain .flv files and crashing the app occasionally after stopping one video and switching to another one, but with no reliable way of recreating the crash at will.), but for a personal app, they are liveable. i did contact the vitamio forum about the
.flv issue but no response.
i recently updated my nexus 4.2x to 4.3. as soon as the home screen appears, i see a message:
"unfortunately vitamio has stopped". (version 3, with the 1.05 b4a wrapper.) i click ok and the message appears a second time. i click ok.
i had not seen this before the update. curious, i launch my app. the message appears again. i click ok. i proceed to my menu selections, choose a
video stream and watch the video without a problem. i choose another stream, no problem. i choose a radio stream, no problem. in any case, i mention this because, regardless of whether you have vitamio library 3 or 4, there may be some issue with android 4.3's interaction with vitamio. if you don't have 4.3, you just haven't seen it yet. but your users with 4.3 will. that vitamio appears to continue to work even though android says it has stopped may or may not be of consequence. it certainly is confusing for the user. as, indicated, i see the message with vitamio library 3. i can't see it with bundle 4 yet, for the following reason:
i downloaded bundle 4 library and sample and read (and followed) the instructions regarding the library. i then built the sample and copied it over to the emulator. when i run it, "unfortunately vitamio has stopped running appears", but this time for real. when i click ok, the app stops.
the log reports:
java.lang.UnsatisfiedLinkError: Native method not found: io.vov.vitamio.MediaPlayer.unloadOMX_native
)V
at io.vov.vitamio.MediaPlayer.unloadOMX_native(Native Method)
at io.vov.vitamio.MediaPlayer.<init>(MediaPlayer.java:204)
at io.vov.vitamio.MediaPlayer.<init>(MediaPlayer.java:174)
at io.vov.vitamio.widget.VideoView.openVideo(VideoView.java:389)
at io.vov.vitamio.widget.VideoView.access$21(VideoView.java:377)
at io.vov.vitamio.widget.VideoView$3.surfaceCreated(VideoView.java:150)
at android.view.SurfaceView.updateWindow(SurfaceView.java:543)
at android.view.SurfaceView.access$000(SurfaceView.java:81)
at android.view.SurfaceView$3.onPreDraw(SurfaceView.java:169)
at android.view.ViewTreeObserver.dispatchOnPreDraw(ViewTreeObserver.java:671)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1820)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1000)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:4214)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:725)
at android.view.Choreographer.doCallbacks(Choreographer.java:555)
at android.view.Choreographer.doFrame(Choreographer.java:525)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:711)
at android.os.Handler.handleCallback(Handler.java:615)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4745)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
at dalvik.system.NativeStart.main(Native Method)
when i deploy the sample to my nexus, the same "unfortunately..." message appears.
i'm guessing the unsatisfied link error is at the heart of it. is there some linker setting needed on the java side for this to work? i assumed that, for a test, the sample would build and run out of the box. is there some back end step needed, eg in eclipse...? thanks