OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: padishah_emperor on April 12, 2004, 12:50:16 pm
-
I flashed my 860 to pdaXrom this week end to give it a full workout to see if I can use it permanently.
All the \'issues\' I found were quickly resolvable except one.
The only GUI for mplayer was via, xmms. Any attempt to configure the mplayer plug in caused a segfault, so I found a workaround for that.
But I got really poor video results, far more inferior than that achievable under Qtopia with Kino2, no full screen and plenty of frame skips.
--EDITED--
I\'ve noticed other requests about this and noone has taken the bait, I\'d would be interested to hear from anyone who has tried to get video working, good or bad.
Or does anyone know how to switch to QVGA as on Qtopia?
Come on, bite...
-
Add \"fs=1\" in the mplayer config file located in \"~/.mplayer/config\". This will allow the video to run in fullscreen mode. You may want to add the framedrop option too..
-
Tried that one, plus framedrop. I got a frame every 10 seconds or so with popping sounds from the audio.
Have you or anyone got fullscreen @ 25 fps, I could with Kino2. I want to watch full length movies as I usually do for trips etc.
Did sashz ever make an mplayer with vidix driver? I know he said he would in an old thread.
-
Hi Emperor,
in Kino2, best video I can have is DivX5 Quality based 2 (600kps) @ 15 fps. I am looking also for enable QVGA with mplayer, but I think there is no way. I read somewhere that pdaXrom already use 640x480, it is why we can not get QVGA enabled.
What are your setting for your movies ? for Kino2.
If someone could help us to find an issue for enable QVGA, it could be very useful.
-
I use mencoder on my Debian to produce wmv files with MP3 audio at the moment, but I am revising that at the moment. My current encodes are designed for small storage so I get about 1 - 1.5 MB per min, the pay off is the images can get blocky during movement on the screen, but ok at arm\'s length, it serves my needs.
Stigmata comes to 126.6MB
Futurama episode 28MB
Video
vcodec=wmv1
vbitrate=64
vhq
24 fps
320x240
Audio
mp3lame
vol=3
cbr
br=96
srate=44100
On the Z I followed instructions posted somewhere here on ZUG to remove Kino\'s mplayer and install a newer faster one.
-
Or does anyone know how to switch to QVGA as on Qtopia?
You can try shutting down X (killall X) and starting mplayer from the TTY with the appropriate flags (mplayer -vo xvidix or mplayer -vo fbdev).
-
Have you actually tried that on pdaXrom? Does it run at full speed, fullscreen?
-
I got Matrix Revolutions...whole movie with outstanding results.
I like extremely high quality for my video. Here is what i got:
Audio - MP3 at 48K and 128K.
Video - DIVX5 Pro, 2 Pass, Ultra Slow for Max Quality coded for 29.97 FPS at 453KB (calculated so as not to exceed 512M).
Using the latest mplayer (v1.00) with the ATI code.
512M for the entire movie. Its nearly as clear as watching TV...although you can tell a frame drops every once in a while. Killing processes or a fresh boot on the Z seems to cure this. Yes I know its big for a movie, but thats the tradeoff for quality. The pixilated artifacts really get annoying after a while.
When I have time, I may write a howto for video on the Z that is perfect everytime. It requires the following tools: DVDDecryptor, IFOEdit, VOBRator, DIVX5(Pro) and DVD Tool. The downside is look for an entire movie to be converted in 5-7 hours depending on length. But...ooohhhh the quality.
-
I would be very interested in a howto to produce high-quality encodings that are playable on a Z. Encoding time is no object when compared to the added enjoyment of a movie without pixelation.
-
Where did you get the v1.00 mplayer with the ATI code from? Is there an IPK available?
-
well the problem seems to be the audio plugin in pdaXrom. The performance is the same as in kino2 in qtopia when audio is switched from madplay to ffmpeg(thats the standard plugin in pdaXrom mplayer).But i havent managed to play the audio with madplay in pdaXrom with -ao and the plugin. Is it true as the mplayer suggests that it would need a recompilation to support this? When i use -ao sdl there simply is no audio ,but no matter how high quality the video is, it always plays with perfect framerate. Anyone with the kino2 config file in qtopia? maybe there lies an answer
-
For synfin0
To use only with Kino2.
Encoding settings :
Audio - First choice of ogg compression in the list
Video - 320x240 - DivX5 quality Based 2 (97%) - 15 fps
Kino2 decode very well ogg audio compressed, and Video with Quality Based 2 gives a bitrate of 600 Kps.
Now, I begin to encode my DVDs for watching during my transportation to office with these settigns, it was the best setting I can found. any other ideas ?
-
Erm, ok..
pmf: That doesn\'t solve the problem, the best I can get outside X is a tiny window, literally 320x240 in the middle of the screen. Making the resolution of the video bigger will cause other problems.
Synfin0: To loose the pixelation, up the bitrate, but not so much that the Z can\'t keep up.
doublec: I\'m trying to get that info for you now ;-) It\'s for Qtopia but I HAVE got it to work under pdaXrom if you remove the existing one by hand. It\'s grief, and made no diffence. Under Qtopia it can crash, but there are less frames dropped. Will PM you or post here.
eonblueapocalypse: Nice pic, nice name, will check that for you, pm me if I forget :-)
Pixelation can be reduced but then there is the space consideration, since my encodes are for on-the-move video, the way I do it now gives the best performance per meg. At arm\'s length it\'s fine and 15 fps is too jerky for me, it gives me a migrane. ;-)
Cheers everyone, keep posting we may hit on the right combo for pdaXrom. Or someone may just fix it!!!! Hint...
-
Thanks hwkeye and padishah. I\'m just looking for the best combo of framerate and bitrate (and res?) that the Z can handle (not too concerned about file size).
-
I\'ve found that on the C860 with the Cacko QT ROM and the newer mplayer, 24 fps is more than doable but I only have 512MB compact flash, and a whole movie can easily go over that. I\'ve got DivX\'s at 384k looking more than acceptable, but they are too big. I like 1 or 2 movies and 3 or 4 albums on my card at once, plus docs, pdf, pics, ebooks etc....
Resolution wise 320x240 is optimal, with pixalation reduced the results on a small screen are stunning (it\'s only a bit smaller than VCD), you will have severe problems over that size and you will increase pixelation with any other resolution but 160x120 - no good.
Of course this was all on Qtopia, different magic may be needed for pdaXrom, but I\'m not flashing back to it until video improves, playing movies is a feature I use and I don\'t want to give it up, no matter how sexy pdaXrom is, and oh boy it is!
can someone give me the output of mplayer -vo help
-
Great info padishah.
Not sure what version of mplayer you\'re looking for, but from cacko QT:
# mplayer -vo help
MPlayer 0.91-3.3.1 (C) 2000-2003 MPlayer Team
Reading config file /usr/local/etc/mplayer/mplayer.conf: No such file or directory
Reading config file /home/zaurus/.mplayer/config
Available video output drivers:
fbdev Framebuffer Device
png PNG file
null Null video output
pgm PGM file
md5 MD5 sum
mpegpes Mpeg-PES file
yuv4mpeg yuv4mpeg output for mjpegtools (to "stream.yuv")
Edit: Sorry if this isn\'t relevent for pdaXrom (ignored thread title)
-
sorry I mean from pdaXrom ;-)
-
Hi guys,
look at this thread (veedub post)
http://www.zaurususergroup.com/index.php?n...&highlight=qvga (https://www.oesf.org/forums/index.php?showtopic=2457&highlight=qvga)
he talks about QVGA and X11 incompatibility.
Maybe an issue is to play Mplayer outside X11.
But we have to found the good mplayer version.
i got mplayer 1.0.3 but it seems to not enable QVGA.
Maybe another issue is to make fbdev:vidix driver working on Zaurus,
anybody know how to ?
cheers.
-
Thx padishah.I dont forget too that zaurus is also a PDA and watchin videos still is a priority even if programming on it was the main attraction in the first place.the help you asked for:
...
...Reading config file /home/root/.mplayer/config
Available video output drivers :
x11 X11 (XImage/Shm )
fbdev Framebuffer device
png PNG file
jpeg JPEG file
null NULL video output
pgm PGM file
md5 MD5 sum
mpegpes MPEG-PES file
yuv4mpeg yuv4mpeg output for mjpegtools (to \"stream .yuv\")
xvidix X11 (VIDIX)
-
is there a summary of how to make/convert/encode video for best performance on the pdaxrom?
Scott
-
If someone could help us to find an issue for enable QVGA, it could be very useful.
It is very simple actually. It is supported out of the box by the Zaurus framebuffer device driver. You just need to know how to tell it about your needs
There is a standard tool to perform mode switching on framebuffer devices, it is called \'fbset\'. Pdaxrom includes a version of it, but unfortuately, the version supplied (from the busybox suite) is not configured right and so is quite useless.
It has to be recompiled to be useful. With normal \'fbset\', you just do
fbset -xres 320 -yres 240
or
fbset \'mode name\', where mode configurations reside in /etc/fb.modes
and it works
Pdaxrom developers, would you please turn on one option in your busybox configuration? It\'s \"Linux System Utilities -] fbset -] Turn on fbset readmode support\". The tool would be useful then.
The other problem is that changing current video mode would screw up the running X server. And it has no use with X11 applications
I would actually very much enjoy if the pdaXrom X server supported mode switching via xrandr. ATI Imageon chip supports both 320x240 and 240x320 in hardware. We would have a nice fullscreen performance with games and video, that would be totally awesome!
-
ikm
Have you actually done this? Are you able to run mplayer fullscreen? Do you have a compiled binary or ipk?
I could reflash pdaXrom again :-)
I wouldn\'t mind the hassle of quitting X, changing fb mode and running mplayer if that is all that is involved.
-
Found this page with a newer version of mplayer with support for the Zaurus graphics chip (apparently). I haven\'t tried it though:
http://wiki.self-core.org/atty/?MPlayer (http://wiki.self-core.org/atty/?MPlayer)
-
ikm
Have you actually done this? Are you able to run mplayer fullscreen? Do you have a compiled binary or ipk?
Yes. It works fullscreen and plays smoothly.
You can just grab the binary from the Debian project, it works.
http://ftp.us.debian.org/debian/pool/main/...2.1-6.1_arm.deb (http://ftp.us.debian.org/debian/pool/main/f/fbset/fbset_2.1-6.1_arm.deb)
It\'s in Debian .deb format though, you will have to have linux on the desktop to use either \'dpkg-deb -X fbset_2.1-6.1_arm.deb .\', or \'ar x fbset_2.1-6.1_arm.deb\' and then \'tar xfz data.tar.gz\'. Alternatively it maybe possible to install .deb with ipkg, but I would not recommend.
If somebody\'s willing to put that binary for download somewhere, I can send it. Or he can just extract it himself and put it somewhere
p.s. Beware that console would be screwed up too. It just screws up everything because everything is supposed to work in 640x480 only. The video plays fullscreen perfectly, either from X or from console. It just leaves a mess after itself =) Changing framebuffer to 640x480 right after mplayer exits would help, but not entirely.
-
Hi ikm,
could you give us the right coammand line to play mplayer with fullscreen ?
which command you use starting from scratch ?
fbset -xres 320 -yres 240,
and ........
thanks a lot.
you can send me the package here richardtfr@yahoo.fr
-
A script to launch it with \'fbset\' and \'clean\' before and after?
-
Hi ikm,
could you give us the right coammand line to play mplayer with fullscreen ?
which command you use starting from scratch ?
fbset -xres 320 -yres 240,
and ........
Yes, something like
fbset -xres 320 -yres 240 && mplayer -ac mad file.avi && fbset -xres 640 -yres 480
you can send me the package here richardtfr@yahoo.fr
Will you put it somewhere for public download? I don\'t like to be bothered with mass-mailing.
Btw, it\'s not the package, just one executable. To install, assuming it lies on your CF:
rm /usr/sbin/fbset
cp /mnt/cf/fbset /usr/sbin/fbset
chmod +x /usr/sbin/fbset
-
fbset -xres 320 -yres 240 && ( mplayer -ac mad file.avi ; fbset -xres 640 -yres 480 ; clean )
-
fbset -xres 320 -yres 240 && ( mplayer -ac mad file.avi ; fbset -xres 640 -yres 480 ; clean )
Yep, that\'s better
-
Hi,
Thanks for yours command line, but ikm, should we use the new fbset package, because there is already one in pdaXrom.
Don\'t worry about mass mailing !!! I don\'t have any FTP to upload the file, but you can send it to me, and if someone ask me for this file, i can give it to him.
Regards,
hwkeye
-
Hi,
Thanks for yours command line, but ikm, should we use the new fbset package, because there is already one in pdaXrom.
Don\'t worry about mass mailing !!! I don\'t have any FTP to upload the file, but you can send it to me, and if someone ask me for this file, i can give it to him.
Regards,
hwkeye
I think ikm\'s point was, that the one supplied does not work.
-
Hi,
Thanks for yours command line, but ikm, should we use the new fbset package, because there is already one in pdaXrom.
I think ikm\'s point was, that the one supplied does not work.
Yes, that\'s right, the one supplied won\'t work since the required features are not compiled in.
hwkeye, have you received my mail?
-
I may give it a test tonight, I\'ve reflashed my poor Z so many times I think it needs a rest. If it works and is a solution a few of us should write to the Cacko team to ask them to incorporate a working fbset and fb modes, unless one of them is reading here and wants to comment?
ikm, do I need to create a file with the modes? /etc/fb.modes?
-
Thanks Ikm,
I got your file.
I encode my DVD with
Video : DivX5 Quality Based 2 (600kps) 15 fps
Audio : Ogg 64kps stereo
What do you think ? What is your encode tips ?
-
For optimal performance, don\'t set the FPS. The key is calculating the bitrate such that it fits the size of the file you want to produce. The bigger the file, then the better the quality (of course): Hree are some tips:
Get DVTool (freeware download). Use the calculator protion of it. I like high quality, so I set my file size for 512M. Then, enter the audio for 48000hz. I usually use 128K as its high quality. Some like 160K, but I seriously doubt there is anyone who can tell the idfference between 128k adn 160k on a Zaurus. The 128K value will give you more space for video. Then enter the length of the movie...this is usually on your DVD cover or imprinted on the DVD itself. The video bitrate will result for maximum quality in the space you requested.
Then use Vidomi. Set your audio setting for 48000hz and 128k bit. Set the video to use DIVX 2 Pass. In the DIVX settings, set your calculated video bit rate from DVTool and also set the quality for \"Slowest\". \"Slowest\" means it takes its sweet time in getting you the highest quality. Unselect the hyper scale and set the Width = 320 and Height = 240.
Start recording...be prepared to wait between 4 and 6 hours to complete. The method above will give you maximum quality, but takes the longest. A 512M movie done as listed above will give you a video with no artifacts...as clear as TV. Case in point, I converted Matrix Revolutions down to a 512M file size with no artifacts and excellent sound. If you shorten the size below 512M, you will begin to get artifacts. I have several movies that I burned down to 200M/180M and they have a good set of artifacts, but they are watchable.
A few more tips:
Try only doing the first few minutes of the movie to be sure the audio and video sync up. Some of the things that cause the audio and video to not sync is the lousy FBI warning and the blue film ratings screen. In order to get rid of those you can try to edit them out in Vidomi (which doesn\'t always work very well for this sync problem), or use IFOEdit and VOBRator to physically remove the FBI/Film Ratings VOB Ids. I usually delete all the VOB Ids before the beginning of the movie to ensure a perfect sync. Use IFOEdit to reburn the VOBs without those evil VOB Ids.
Good luck, and if you follow the above, you will get a perfect Z movie everytime.
javab0y
-
ikm, do I need to create a file with the modes? /etc/fb.modes?
You don\'t have to. It\'s more just a matter of taste. Instead of passing \'-xres 320 -yres 240\' each time, you can write /etc/fb.modes and put that info there under some short name, and do fbset \'your mode name\' instead.
-
Great stuff
;-)
-
If you guys have gotten it working, I can temporarily post it on the web until we get a more permaneant home for it.
Email it to: justinengler(a)yahoo.com
where (a)=@
-
I\'ll mirror any file... that\'s legit.
send me a message here if you want to arrange transfer.
Scott
-
Hi scott,
You need the fbset file ? if yes give me your mail.
thanks to ikm for the file.
We try to do not spam everyone. It is a good idea scott if you can share somewhere for zaurus user can download files.
Thanks.
-
Finally managed to test it, I fouled something up bad on my first attempt, dunno what I did but it totally fouled busybox up, couldn\'t even boot back up - reinstall job.
We\'ve managed to get a working solution to video playback, it may not be elegant, but it works. ikm, big thanks to you.
Anyone looking to try this, it\'s best as mentioned before to call mplayer from a script, fbset to 320x240 before, fbset 640x480 after. The screen will be garbled but \'startx\' will fix that.
Nice work all
:-)
-
my goal is to play advmame in 320x240 full screen without using mame to \"zoom\" or \"fat bit\" the display -- as that
seems to slow it down to a CRAWL!
I am scott@spy.org -- you can mail there.
Scott
-
my goal is to play advmame in 320x240 full screen without using mame to \"zoom\" or \"fat bit\" the display -- as that
seems to slow it down to a CRAWL!
Scott
Well, does it utilize SDL? If it does, you can run it from console. SDL supports frambuffer and can automatically switch to 320x240, and even cleanly restore back to 640x480 upon exit.
Now, people, on the mplayer in 320x240 fullscreen: it is actually possible to achieve the same result without any external \'fbset\' tool, as the needed functionality is actually already present in mplayer itself. I\'m making a separate thread about it so more people would know.