ffplay
Chris Gransden (337) 1207 posts |
I’ve uploaded a Beagleboard compatible ffplay command here. If you haven’t got it already the original !FFplay is available here. Just drop it over the original inside the !FFplay folder. For best results run in a 32thousand colour mode. It can just about manage video up to 640×480 for certain files with the sound off at 1GHz. It’ll be interesting to see what effect vfp/neon will have. |
Stephen Leary (372) 272 posts |
I tried this bug just get the error: “no writeable memory at this address”. I have set 20Mb of RAM for it. |
Holger Palmroth (487) 115 posts |
Did you changed the obey file ”!WimpSlot” within ”!FFplay”? I just appended a “0” to -min and -max values to get rid of the error. The sensible amount is likely to be way lower but i am too lazy to experiment right now. |
Chris Gransden (337) 1207 posts |
I’d forgotten I have the Absolutely module loaded. Either load this or change the ”!WimpSlot” file to “WimpSlot -min 12100k -max 12100k”. Hopefully sometime soon once the gcc 4.6 compiler issues are sorted out I’ll upload a NEON enhanced version. This should be able to cope with higher frame rates/resolution. |
Holger Palmroth (487) 115 posts |
It’s more like “WimpSlot -min 13100k -max 13100k”. Installing the “Absolutely” module looks like an good idea. ;) |
Stephen Leary (372) 272 posts |
Thanks guys, That got me through the worst of it. Seems there is no sound support on the DevKit8000 though. Or at least i can hear any sound. |
Chris Gransden (337) 1207 posts |
Sound needs the DRenderer module. |
Stephen Leary (372) 272 posts |
Beats me why the lot cant be bundled together but hey ho. |
Stephen Leary (372) 272 posts |
I have this all working on the IGEP. It’s very flakey. Dragging a window around frequently results in a crash and closing a window often results in nothing happening except the window frame vanishes with no way to kill the video. Thoughts? |
Chris Gransden (337) 1207 posts |
Although it multi-tasks it’s probably best not to do anything else at the same time. :-) If you do need to move the window, pause it first by pressing ‘space’ or ‘p’ while the mouse pointer is over the window. If it gets stuck use ‘alt-break’ to quit it or else press ‘q’. |
Jan Rinze (235) 368 posts |
hmm.. it simply barfs on my beagleboard. i see in a flash a window created and deleted. |
Stephen Leary (372) 272 posts |
Thats what I saw initially. Until i changed the wimpslot and ran the absolutely module. |
Holger Palmroth (487) 115 posts |
FFPlay does that without Chris’ BeagleBoard-compatible binary. I vaguely remember that it didn’t got replaced on my BIK with a simple drag. Didn’t explored it further and simply deleted the original binary before dragging Chris’ binary over. |
Stephen Leary (372) 272 posts |
Indeed, Jan, you sure you copied the new binary into the application directory? |
Jan Rinze (235) 368 posts |
right.. the copy options in the filer were to blame. I thought i had copied the file over but it was still the original file. Now it runs but it still is far from stable. often the window contents remains somewhere on the screen and the window can only be killed through the task manager. |
Jan Rinze (235) 368 posts |
or sometimes the entire machine hangs when killing it through the taskmanager.. |
Stephen Leary (372) 272 posts |
Jan, Yes its the probably flakiest bit of software i’ve ever seen. |
Jan Rinze (235) 368 posts |
yeah.. i’ll stick to !Kinoamp for playing video ;-) |
Chris Gransden (337) 1207 posts |
For those that haven’t been put off by previous comments. :-) I’ve uploaded a cortex-a8 optimised version of ffplay here. It’s slightly faster than the previous one. Run in as low a resolution as possible 32thousand colour mode for best results. Use !Kino if you just want to play mpeg1/2 videos. Anything else ffplay should be able to play at varying speeds. Try to stick to videos below 640×480 otherwise it will end in tears. |
Raik (463) 2062 posts |
What is the latest version of ffplay and where I find? The links here are broken. |