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.