mplayer_1.0rc1-maemo.18
 

A new version of mplayer is available at garage downloads page: https://garage.maemo.org/frs/?group_...release_id=776

It is an incremental update which improves performance a bit and also fixes a bug with inconsistent display state on exit which could be observed with mplayer_1.0rc1-maemo.17 in some circumstances. Check release notes at garage downloads page for more details about the changes which have been introduced in different mplayer releases.

This release is mostly interesting for the projects which use mplayer as a backend as it adds support for making PNG and JPG screenshots and enables ALSA sound output in N800 build (for use with A2DP). An important thing to take care when upgrading from mplayer_1.0rc1-maemo.16 is that framebuffer based video output is now set as default for N800 ('-vo nokia770'). If Xv video output is desired, it should be explicitly specified with '-vo xv' option when running mplayer.

This release will get uploaded to garage extras repository very soon unless regressions compared to mplayer_1.0rc1-maemo.16 are reported.

Re: mplayer_1.0rc1-maemo.18
 

Serge: Milhouse suggested I forward to you my query to him of today. Any advice? Regards, Jim

"Milhouse: This is a new query, unrelated I believe to anything above, but as it concerns A2DP, I believe it is appropriate that I put it here.

"It concerns my inability to play ogg-formatted music on Kagu using my Bluetooth headphones. Without burdening you with the details, I had to rip one of my cd's using my Linux box as my PC's cd-player wouldn't recognize that particular cd! When I transferred the ripped music to my N800 and scanned with Kagu, it was readily accepted and played by Kagu -- except when I tried listening to it using my Bluetooth headphones (which of course were enabled for Kagu use by your wonderful A2DP application). Can you see any reason why your application wouldn't be equally viable for ogg-formatted music as it is for MP3? Any help would be appreciated, as usual."

Re: mplayer_1.0rc1-maemo.18
 

Does this mean we can use a2dp directly without having to run kaju in the background??

If yes.... that is great news.... now may be i can browse while simultaneously using a2dp via stereo bluetooth....

Re: mplayer_1.0rc1-maemo.18
 

Great stuff serge!

Any chance you could make a chinook compatible version?

edit:
missing dependencies during install:
hildon-fm1
libdbus-1-2

Yeah, did force install on n810 and tested uktube with it. Result:
error while loading shared libraries: libdbus-1.so.2: cannot open shared object file

Anyhoo. Would be great if you could publish the n810 comparible version soonish, so that I could make sure uktube plays nice with it.

Re: mplayer_1.0rc1-maemo.18
 

Yes, N810 and OS2008 will be supported in mplayer eventually. But mplayer uses a few hardware/system specific optimizations, so it might require some tuning and testing on real N810 hardware. It took some time before mplayer could work on N800 more or less acceptable, hopefully N810 and OS2008 does not differ so much and it will require less work. As soon as OS2008 FIASCO image gets available, I'll ensure that mplayer works on N800 with the new OS.

You can try to build mplayer for OS2008 youself. Just run
or
in scratchbox with maemo 4.0 SDK to get deb-package. I still did not test it myself though, but I hope that there will be no compilation issues (mplayer is not heavily dependent on hildon).

Re: mplayer_1.0rc1-maemo.18
 

Great! I love mplayer, on my laptop and on my N800. Thank you!

What does framebuffer or xv based video output do? Is one faster or more stable?

Re: mplayer_1.0rc1-maemo.18
 

Framebuffer output is faster, but it may break on major OS upgrades. Xv based output is somewhat slower (unless https://bugs.maemo.org/show_bug.cgi?id=1278 was fixed, which I suppose should be done in OS2008). Xv is a standard API for video output, so it should always work.

Re: mplayer_1.0rc1-maemo.18
 

Sorry, but I have hext result
because

Re: mplayer_1.0rc1-maemo.18
 

gLobster: Try editing 'debian/control' removing the libraries which fail dependency check from 'Build-Depends:' until mplayer starts compiling. All the libraries needed to build mplayer should be included in SDK theoretically.

Re: mplayer_1.0rc1-maemo.18
 

Thank's, I replace x-dev with x11proto-core-dev and can to build project! Now I am waiting OS 2008 realese for N800 :)

Re: mplayer_1.0rc1-maemo.18
 

I'm no dev but sounds like mplayer might need it's dependency changed from x-dev to x11proto-core-dev, they did rename some package's for the OS2008.

Also as a side note, the hardware between the N800 and N810 is pretty much the same, even the CPU's will be the same speed under the OS2008 as they are clocking up the N800 to a 400mhz compared to the 330mhz, So compiling it for the N800 on OS2008 'should' be the same result on the n810 in OS2008.

Just some thoughts, keep up the good work :D I love mplayer!

-Rip

EDIT: Sorry been a few hours before I refreshed the page! and missed the new posts.

Re: mplayer_1.0rc1-maemo.18
 

800 & 810 have same CPU. I think what speed will be equal in both devices. It's properties OS, but not device

Re: mplayer_1.0rc1-maemo.18
 

Also just out of curiosity has software AC3 codec's been removed from mplayer for the Maemo device? I have alot of movies with low quality AC3 sound in them and can't seem to get sound, so I'm assuming it was removed for package size? or too CPU intensive?

Cheers
Rip

Re: mplayer_1.0rc1-maemo.18
 

I've gone though the packages in your mplayer svn, and it looks like all the libs are there that are required... libfaad2, libavcodec, liba52. I'm not exatly sure which one decodes AC3 but I think its liba52?

Has anyone else tried watching a movie with AC3 audio? or anyone have any ideas?

cheers
Rip

Re: mplayer_1.0rc1-maemo.18
 

I don't have any movies encoded with AC3 audio except for DVDs. I tried to play AC3 audio track from DVD movie with mplayer running on Nokia 770 very long ago, but it did not work well and was causing problems when started from GUI frontend (don't remember exactly, it either deadlocked and kept mplayer process running forever or caused some other nasty effect) so it was disabled in configure. Apparently the number of AC3 users is very low as I don't remember anybody else asking about AC3 support. Though I might have missed such requests or forgotten (but anyway, there are no AC3 related issues registered in garage mplayer trackers).

Yes, you are right it is liba52 (libfaad2 is used for AAC).

You can edit 'debian/rules', enable liba52, build the package and do some tests. Feedback is very much welcome. I would also like to have a sample of such movie with low quality AC3 audio track sent to me in order to add it into my test collection.

Re: mplayer_1.0rc1-maemo.18
 

Ok, worked perfectly, Audio seems fine :) I was hoping to get away with not re-encoding my video collection for the n800 as they are generally only 700meg files that I stream around the house with my Xbox, but I fear some of them are a bit too large. I have cut 2 of my generic movies into 2min and 1min clips if you want me to email them to you? 1 is 10meg the other is 11meg.


Cheers
Rip

Re: mplayer_1.0rc1-maemo.18
 

Are you talking about mplayer in OS2008 or OS2007?:confused:

Re: mplayer_1.0rc1-maemo.18
 

Thank you for testing and suggesting this improvement, I have just enabled liba52 support in SVN, it will be released with the next mplayer package.

Thanks a lot. I have already found AC3 sample for testing a few hours ago (downloaded from upstream mplayer ftp :) ), so now your file is not needed.

It applies to both OS2007 and OS2008.

Re: mplayer_1.0rc1-maemo.18
 

What toolchain is used for producing mplayer? It says gcc4.
It's a modified scratchbox or a regular crosscompile?

Thanks for the software, it's a must for the tablets!

Re: mplayer_1.0rc1-maemo.18
 

MPlayer releases (.deb files) are still built using standard toolchain from SDK. I also experimented with building it using crosscompiler outside scratchbox (gentoo crossdev) and using alternative gcc 4.x toolchains in scratchbox (for example scratchbox-toolchain-arm-linux-2006q3-27-1.0.6-1-i386.tar.gz): http://scratchbox.org/download/files...ophis/tarball/

Toolchain upgrade is needed to solve the following problems:
https://garage.maemo.org/tracker/ind...id=54&atid=269
https://garage.maemo.org/tracker/ind...id=54&atid=269

Unfortunately, the upgraded toolchain, while fixing these issues adds some new ones (and some problems still remain):
https://garage.maemo.org/plugins/scm...ew=rev&rev=223

Looks like building mplayer is quite a challenging task for any compiler and has a high chance of triggering one problem or another. Surely, all these problems are not necessarily compiler faults, some code in mplayer might have 'undefined behaviour' bugs. But finding such bugs is a real PITA and I don't have extra spare time for that.

Re: mplayer_1.0rc1-maemo.18
 

Genius, I didn't realise there were other compatible toolchains out there. This may help with a fair few things I'm trying to compile that either create internal compiler errors or just don't like GCC 3.x.x (e.g. giac/xcas, cln).

Thanks :)