MPlayer on Raspberry Pi 3 working?
Pages: 1 2
Raik (463) 2026 posts |
Have use streams from a lists e.g. you can find here: Looks like the list are often changed and the streams also. Anytimes it works. Often not. Can only try from Germany. If it works, it takes a bit more time (more than a minute) before the IPTV-ts-stream is displayed. The German MP4-streams are faster. |
Chris Gransden (337) 1148 posts |
There’s another updated mplayer executable available here. The version is the same. It’s been rebuilt with the latest ffmpeg libraries (3.4, was 3.3.4) and the latest gnutls libraries to enable https support. Also sound on certain files should no longer be distorted on the RPi. When opening audio or video streams over a network try adding the ‘-nocache’ option to the !Run file. (remove ‘-cache’ if present. Also make sure ‘mplayer$heap’ is not set). !UnixHome still needs to be seen first to avoid an error. |
Raik (463) 2026 posts |
Thanks a lot. Have try with German https streams. Is working fine. Any older questions I have. |
Raik (463) 2026 posts |
Have play around with ffmpeg (watermark, blend, concat, …) and other. The result you can find here mp4 or mpeg. For a quick try, it looks nice, I find. ;-) |
Raik (463) 2026 posts |
-noconsolecontrols in mplayers commandline change this. Shortcuts only working if the mplayer-window is activ. |
Andrew McCarthy (460) 126 posts |
I thought I would give MPlayer a test run today and I am running into a “No writeable memory at this address” error message. I’m using a Pi 3 with RISC OS 5.23 (13-Apr-17). I’ve updated the application directory with the lastest files and even increased the wimpslot, but I can’t get past the error message. Any thoughts as to why this is happening? |
Raik (463) 2026 posts |
Have you aemulor aktiv? Limit the AppSpace to 28MB for all, also the 32bit Apps. Close it complete. |
Andrew McCarthy (460) 126 posts |
Yes, I did. Not an easy process to stop it from running, as I had to remove the module from predesk, but MPlayer now works! :-) |
David Feugey (2125) 2687 posts |
The latest version can be ‘quitted’, and restores the normal wimpslot. |
David Pitt (3386) 1248 posts |
Have you aemulor aktiv? If Aemulor has been installed in PreDesk then there may not be an iconbar icon to Quit from. There is a configurable option “Display the Aemulor icon after booting”, available from the iconbar icon, which may not be there. A minor Catch 22. If Aemulor is running without an iconbar icon then double click on the Aemulor module and the icon appears. Now Aemulor can be fully quit with the “Emulator too” option. |
Andrew McCarthy (460) 126 posts |
On the Pi3 (RISC OS 5.23, 13-Apr-17) Aemulor (2.40) doesn’t appear to restore a normal wimpslot, as I still get the memory error. I’ve even tried moving the wimpslot after quitting Aemulor. The only thing that works, so far, is removing Aemulor from PreDesk.
Possibly. The default setting observed so far is for an iconbar icon to appear. The common thing here is that although the Aemulor can be stopped, you still get the memory error from MPlayer which suggests that it doesn’t restore a normal wimpslot. |
David Pitt (3386) 1248 posts |
To fully quit Aemulor slide right off of Quit on the iconbar menu and go for “Emulator too”. Wimpslot can then go above 28MB, as verified on my RPi3 with MPlayer. |
Andrew McCarthy (460) 126 posts |
I did that a number of times which leads me to ask. What version of RISC OS, Aemulor and MPlayer are you using? Is Aemulor being run from PreDesk when you quit it? |
David Pitt (3386) 1248 posts |
Something a bit weird is going on. Starting with Aemulor in PreDesk on fully quitting Aemulor Wimpslot can be increased to beyond 28MB, however there seems to be no way to persuade MPlayer to start.
It’s odd!! I have tried increasing the wimpslot requirement to 30MB in another application and that does start after the PreDesk Aemulor has been fully quit. |
Adrian Lees (1349) 122 posts |
Fair enough. When Aemulor is running it also makes itself available via the ‘Apps’ icon to the left hand side of the iconbar and you can double-click on the !Aemulor icon to start the user interface. It was never really supposed to have one tbh; I wanted it to be entirely transparent. If Aemulor cannot quit fully when you choose ‘Quit→Emulator too,’ because other system-level modules are loaded and RISC OS will not allow Aemulor to detach, it can linger. Open a TaskWindow or press F12, and then type *Modules to see whether the Aemulor module is still loaded. The problem is usually another OS_ClaimProcessorVector claimant which has been loaded after Aemulor, so perhaps list the modules below Aemulor in the list (higher module numbers) and that may provide a clue. Since the user interface has already closed it cannot report an error, and it is obviously better to leave the WimpSlot restriction in place rather than the system unstable. Should you find a candidate suspect, you could try *RMKilling that and then *RMKill Aemulor. If it disappears this time and your full WimpSlot is restored, that’s what happens. I put quite a lot of effort into ensuring that it remains stable and killable in that situation. I’ll see if I can do anything to make this clearer/tidier. There’s really little reason for OS_ClaimProcessorVector to have its current ‘chaining’ API and I part-wrote a patch to resolve that contention a long time ago, but unfortunately it hasn’t been completed… |
David Pitt (3386) 1248 posts |
The issue persists with a minimal boot in which Aemulor, in PreDesk, is the only module loaded. Also the Aemulor module really does disappear on being quit with “Emulator too”. |
Pages: 1 2