Static Vlc Media Player 0.8.2 Binary Available Now Options

[chrget]

Hello everybody,

since VLC media player has (finally!) reached version 0.8.2 yesterday, I decided to do a quick updated build of my static executable today and make it available here.

As a quick reminder, my build is targeted primarily towards SL-5500 (i.e. non-PXA-processor) Zauri running an original Sharp ROM, but people have successfully used it on other Z-models as well. Some more discussion about it can be found in this thread as well as this thread.

For those of you who just want to grab the executable, just grab the vlc_0.8.2_arm.zip attached to this post. For those of you feeling adventurous, there is also an IPK including a minimalist external frontend as well available now. Be warned, though: this is highly experimental, and you're using that IPK at your own risk. That said, if you're still interested, grab the vlcplay_0.8.2_arm.ipk attached to this post (also includes the same executable as the ZIP file, so you don't need both).

Best regards,
Chris.

Attached File(s)

 vlc_0.8.2_arm.zip ( 2.32MB ) Number of downloads: 518
 vlcplay_0.8.2_arm.ipk ( 2.35MB ) Number of downloads: 681

 

[brashley46]

Hello everybody,

since VLC media player has (finally!) reached version 0.8.2 yesterday, I decided to do a quick updated build of my static executable today and make it available here.

As a quick reminder, my build is targeted primarily towards SL-5500 (i.e. non-PXA-processor) Zauri running an original Sharp ROM, but people have successfully used it on other Z-models as well. Some more discussion about it can be found in this thread as well as this thread.

For those of you who just want to grab the executable, just grab the vlc_0.8.2_arm.zip attached to this post. For those of you feeling adventurous, there is also an IPK including a minimalist external frontend as well available now. Be warned, though: this is highly experimental, and you're using that IPK at your own risk. That said, if you're still interested, grab the vlcplay_0.8.2_arm.ipk attached to this post (also includes the same executable as the ZIP file, so you don't need both).

Best regards,
Chris.

Hi, I installed the vlcplay_0.8.2_arm.ipk but no frontend showed up. I'm running the 3.1.3 update Sharp ROM on my 5500 right now. How should I find the frontend?

[chrget]

[...] no frontend showed up. I'm running the 3.1.3 update [...]

The IPKG installation was tested to work on a stock 3.1.3, so it should run ok. My guess is that it didn't in your case. Please check your installation target, and if it is possible that the installation ran out of space. Installation was tested to internal memory only, and a rough total of 5.5 MByte is needed to hold the executables.

If all else fails, you may want to try installation after backing up your data and doing a full reset. If that doesn't work either, there is always the chance the IPKG got corrupted somehow along the way.

Best regards,
Chris.

[brashley46]

[...] no frontend showed up. I'm running the 3.1.3 update [...]

The IPKG installation was tested to work on a stock 3.1.3, so it should run ok. My guess is that it didn't in your case. Please check your installation target, and if it is possible that the installation ran out of space. Installation was tested to internal memory only, and a rough total of 5.5 MByte is needed to hold the executables.

If all else fails, you may want to try installation after backing up your data and doing a full reset. If that doesn't work either, there is always the chance the IPKG got corrupted somehow along the way.

Best regards,
Chris.

Thanks, Chris, I'll see tomorrow after the Tour de France first stage telecast how much memory I've got in there. I can always move the picturefiles I've got on internal memory to my SD card.

[brashley46]

[...] no frontend showed up. I'm running the 3.1.3 update [...]

The IPKG installation was tested to work on a stock 3.1.3, so it should run ok. My guess is that it didn't in your case. Please check your installation target, and if it is possible that the installation ran out of space. Installation was tested to internal memory only, and a rough total of 5.5 MByte is needed to hold the executables.

If all else fails, you may want to try installation after backing up your data and doing a full reset. If that doesn't work either, there is always the chance the IPKG got corrupted somehow along the way.

Best regards,
Chris.

Thanks, Chris, I'll see tomorrow after the Tour de France first stage telecast how much memory I've got in there. I can always move the picturefiles I've got on internal memory to my SD card.

okay. As a footnote, I had to backup, full-reset and restore ... but I got this vlc player successfully installed, including the frontend. Nice! Doesn't play .wmv files, but will play .avi, somewhat jerkily ... of course the sample .avis I loaded are a bit jerky on the pc anyway.

[chrget]

[...] Doesn't play .wmv files, but will play .avi, somewhat jerkily ... of course the sample .avis I loaded are a bit jerky on the pc anyway.

To correct these frequent misconceptions: it does play .WMV files, if the codec(s) used for the file are supported by FFMPEG (i.e. belong to/are related to the MPEG-4 family). The same of course goes for .AVI, .ASF, .MOV and of course .MP4/.3GP. These are all just containers, so the file type says nothing whatsoever about the encoding of the actual A/V data.

As for performance and parameter constraints for best playback, I suggest having a look at the aformentioned thread which has a lot of information with regard to that.

With regard to installation of the IPK, my guess is that it probably did run out of space. Never really looked at ipkg's code, so I have no idea how much temporary storage it needs while performing an installation, but it might well be double the size of the uncompressed package (anybody with more insight into that, feel free to correct me). Since I basically no longer use ipkg, I'm not quite up to speed on that.

Best regards,
Chris.

[ev1l]

I'm going to give it a try on a 860. If you're religious, pray for me.

[alexjlee]

it works, but use:

CODE

/home/root/vlc -V qte -skipframes --filter transform --transform 270 some_video.mpg

has anyone come up with a better set of command line options for the clamshells?

I'm going to give it a try on a 860. If you're religious, pray for me.

[brashley46]

[...] Doesn't play .wmv files, but will play .avi, somewhat jerkily ... of course the sample .avis I loaded are a bit jerky on the pc anyway.

To correct these frequent misconceptions: it does play .WMV files, if the codec(s) used for the file are supported by FFMPEG (i.e. belong to/are related to the MPEG-4 family). The same of course goes for .AVI, .ASF, .MOV and of course .MP4/.3GP. These are all just containers, so the file type says nothing whatsoever about the encoding of the actual A/V data.
[snip]
Best regards,
Chris.

Sorry, I had not looked at that thread. It wouldn't play the .wmv I tried. I'll try PocketDivXencoder and see if I get any better results.

[ken]

As a quick reminder, my build is targeted primarily towards SL-5500 (i.e. non-PXA-processor) Zauri running an original Sharp ROM, but people have successfully used it on other Z-models as well. Some more discussion about it can be found in this thread as well as this thread.

Tried it on the 6000L/Sharp ROM. No problems installing, except it wanted everything in the main memory (not an issue, just moved it to my SD card and symlinked to /usr/bin). Also unchecked magnify for better fonts.

I've noticed that you must play a song in order for it to exit out, or it'll loop

Additionally, I added in (not sure if it's the right thing or not):
audio/m4a m4a
to /opt/Qtopia/etc/mime.types (to handle m4a file types)

Once I did that, it would catch the m4a files

The front end is crude, but doable. I would prefer it not to handle anything except m4a and mp3's (I can always use media player to handle the other stuff). Also it'd be nice if we could limit the search to certain directories (for speed)

Good work!

[chrget]

has anyone come up with a better set of command line options for the clamshells?

Not that I would actually know, but using the frame buffer device might improve performance somewhat, albeit leave your palmtop in a mess afterwards (keep in mind that accessing the frame buffer device may require additional privileges, so you need to either run vlc with EUID 0 or grant regular users access to the /dev/fbX device)

[...] I've noticed that you must play a song in order for it to exit out, or it'll loop

Odd, never noticed that. You may want to give me a step-by-step account of what you did so I can reproduce and possibly fix it.

[...] The front end is crude, but doable.  I would prefer it not to handle anything except m4a and mp3's (I can always use media player to handle the other stuff).  Also it'd be nice if we could limit the search to certain directories (for speed)

Well, the main intent for creation of the frontend was Qtopia Document Tab MIME type integration and providing a solid, unchanging fullscreen background for video playback via the frame buffer device (and to clean up the mess it leaves). Adding an Open dialog was mainly an additional excercise in Qtopia GUI programming

AFAIK Qtopia does not really have a notion of the location of Documents when it comes to GUI file selection mechanisms, so it does not provide an appropriate Open dialog as we know it. To have one of those, you either have to write it yourself or use someone else's (IIRC libopie provides one as well). So it would take quite a bit of motivation to add something like that, especially given the fact that I find GUI programming positively ghastly

Best regards,
Chris.

[ken]

Odd, never noticed that.

Simple. open the player, but never select a song and try to exit.

use someone else's (IIRC libopie provides one as well). So it would take quite a bit of motivation to add something like that, especially given the fact that I find GUI programming positively ghastly

perhaps this would help:

http://www.rothfuss-web.de/zaurus/index.html

It's a java shell version interface for mplayer. I suspect it could be easily modified to handle vlc instead? He provides the source for it ...

[chrget]

Simple.  open the player, but never select a song and try to exit.

Hmmm, when running on my Collie, the file dialog sports a 'close' icon in the upper right-hand corner. After tapping that, the frontend drops back to the main document window, from where it can be terminated either using the menu (File/Quit) or the 'Cancel' key.

[...] It's a java shell version interface [...]

Java? Eeeeeek ... sounds like trying to get rid of Lucifer by calling in Beelzebub

Best Regards,
Chris.

[undrwater]

@ken

Did you try to play a movie using vlc on your 6000? I didn't install the GUI, just the binary, and it'll play movies...but they're not viewable. It looks as if it has been stretched vertically and replicated across the screen...with a lot of snow thrown in. Is this the result of the binary having been compiled for the 5500 arm? Or do I need a specific command line option? (I've tried a few, including the -V qte)

@chrget

I'm actually interested in compiling a static binary for the 6000. Did you use a cross-compiler, or did you do it on your 5500? Can you detail what tools you used, and any thoughts on what to look out for?

[chrget]

It looks as if it has been stretched vertically and replicated across the screen...with a lot of snow thrown in.  Is this the result of the binary having been compiled for the 5500 arm?

I seriously doubt that it has anything to do with restricting the instruction set used to the SA1110. My guess is some other problem either within the VLC video output module(s) used or some weird form of incompatibility.

Or do I need a specific command line option? (I've tried a few, including the -V qte)

Okay, so the obvious thing is that the QT/E video output is broken. How about the frame buffer? Did you try that as well (-V fb -- you need to run as root, though, if you do -- or grant the regular user access to the frame buffer device, otherwise VLC will fall back to the QT/E module). Would be interesting to know what the result is. The obvious step to finding the problem would be to increase VLC's verbosity, i.e. running it with -v, -vv or possibly even -vvv to find out if maybe it has a completely wrong notion about the screen dimensions or something like that.

I'm actually interested in compiling a static binary for the 6000.  Did you use a cross-compiler, or did you do it on your 5500?  Can you detail what tools you used, and any thoughts on what to look out for?

I'm working cross, mainly because it's a lot faster and more comfortable than doing it natively. I started out using the development packages provided by Sharp (i.e. the dreaded GCC 2.95 environment) and still use that for compatibility reasons whenever I build something that has to interface with existing C++ code within the Sharp ROM (everything Qtopia comes to mind). For other stuff I have eventually built my own GCC 3.4.3 cross chain, which brings quite an improvement in performance. What to look out for? Well, that's a tough call, really, not knowing your level of expertise. Personally I found it to be a pretty straightforward job, but then again I've been developing software for 25 years now. I suppose the smartest move is to start out small when it comes to possible features and prerequisites (and VLC has a ton of those ) and add most of those later when you're familiar with the entire environment.

Best regards,
Chris.