MPlayer 2026 SVN/CVS FFMPEG7.1/Vaapi

@smarkusg

Quote:

Thank you for the hint and yes the donate button leads nowhere.Thank you for the hint and yes the donate button leads nowhere. Here I had a typo, it is

https://www.paypal.com/paypalme/Maijetsro

I would also like to mention here that I do not intend to profit from this port but simply want to recover the expenses I had myself and of course it motivates me to realise new projects.

@Maijestro
Quote:
MPlayer was compiled without ass font support. Unfortunatly this makes it unable to be used with SimpleSub. Could ass font support be added?

@Maijestro
Quote:
Arexx commands that are supposed to return values, never return the value which leaves the calling program waiting for a response.

Example using ARexxConsole:

no port > \port mplayer.1
---------------------------------------------------
Found ARexx port name >MPLAYER.1<
===================================================
MPLAYER.1> \DIAG
---------------------------------------------------
Turning ON diagnostics printouts
===================================================
MPLAYER.1> GET_TIME_POS
cmd ->GET_TIME_POS
---------------------------------------------------
Checking for port_name ->MPLAYER.1
sending ARexx message
ARexx message sent, waiting for reply


The reply never comes and the Arexx port seems to be locked up because even performing CTRL-C in the ARexxConsole program is not able to abort the waiting for reply like it should.

This seems to happen for all ARexx commands that are supposed to return a value.

@ktadd

Quote:

V-MPlayer is a standalone project and I have not tested it with SimpleSub or other tools, GUIs, or scripts. It is tailored to the V-MPlayerGUI. Nevertheless. Only the basic functions of Arexx were implemented so that the player can be fully controlled via the GUI.

I will take a look at it

@Maijestro
Quote:
Thanks. Asside from this one ARexx issue, V-MPlayer is working very well with VideoClipper. If this issue is fixed it will be THE player to use.

There is one issue that I see sometimes and that is that the video window will sometimes open showing just an all grey output. (solid grey color.) I think this might be more of a graphics driver issue as I beleive I have seen Emotion have this issue as well. I'll see if I can investigate further later.

I'm using an X1000 with an ATI Radeon 7750 graphics card.

I have also tried V-MPlayer on an A1222p with an RX550 graphis card and it doesn't work. The CPU usage goes to 100% and nothing happens. If you want to try to support the A1222p I can investigate further.

Heading to bed as it's 2AM.

@Maijestro
Oh, one last thing today while I'm thinking of it. Could you add something to the version string returned that indicates the version is V-MPlayer. Maybe call it V-Mplayer in the version string. This would allow my programs to not have to rely on the mplayer version number to identify it. That way, if the mplayer version number ever changes, I won't have to update my programs if the version number changes. Thanks

@ktadd

I have just fixed the problem. A new test binary is available — GET_TIME_POS, GET_TIME_LENGTH, GET_PERCENT_POS and GET_VO_FULLSCREEN should now all reply directly without hanging. Could you contact me privately or do you have Discord so

I can send you the test binary?

Let's take this one step at a time. The issues on the A1222 are most likely compiler problems or other SPE related issues, that will probably take some time to investigate and I no longer have such a machine. We should also get the versioning under control. Please get in touch so you can do some tests with the updated build.


Update: https://github.com/Maijestro/mplayer/releases/tag/v265-beta

I have an Amiga X5040 with a Radeon RX560 graphics card at 2560x1440 resolution. One problem I'm having is that the beginning of the video is sped up, then it slows down before finally stabilizing. The video is in 2160p MP4 H.264 and MP4 H.265.

Test video:



However, with the GUI, there are no problems; it works perfectly in 2160p H.264 and H.265.

It's on par with DV Player, DV Player can't play a 2160p H.265 video (slow motion). Emotion can't play a 2160p H.265 video (slow motion)




1080p MP4 H.264 and H.265 Video

V-MPlayerGUI MP4 H.264: graphical bug, H.265: graphical bug (full screen)

Emotion 1080p MP4 H.264: OK, fewer graphical glitches, H.265: slight graphical bug (full screen)

MPlayer: forget it

DV Player: same as V-MPlayer (full screen)




1080p MP4 video, original YouTube version

V-MPlayerGUI MP4 H.264: graphical glitches (full screen)

Emotion MP4 H.264: fewer graphical glitches (full screen)

MPlayer: forget it

DV Player: same as V-MPlayer (full screen)




2160p WebM video, original YouTube version

V-MPlayerGUI: forget it.

Forget about emotion!

Forget about MPlayer!

Forget about DV Player!



YouTube video:

MPlayer: No problem. YT.cfg and YT.rexx files from VideoVortex.

V-MPlayer: The audio cuts out at a certain point. YT.cfg received from Maijestro.

I don't know what the problem is.

@Maijestro
Thanks for the quick fix of the ARexx commands!

I have a couple more inputs on the GUI.

First the fonts are to small and I can barely read them with a 1920x1080 resolution and higher.

Second, when I click on the button to bring up the mini GUI, the main GUI is still visible. So both GUI's are displayed. I can iconify the main GUI manually but it would make more sense if it was automatically iconified or close.

It would also be nice if the user could set which GUI was displayed at startup by default. For a lot of cases I like the smaller GUI.

I'll send you a private message with my email and I do visit Amigains.net discord channel as ktadd.

Thanks again. I'm pretty happy about the work on V-Mplayer!

@Majestro
Tested a bit, and :

I think you soon will find for yourself that better to switch to reaction based gui and ditch hollywood one. Yes, boring, but you will surely be at this road soon or later. It just current gui is feels not system friendly.

Can you resize it as any other amiga window ? Probably no ? Will it simple use system font size ? Probably not, and for every monitor different resolution it will be always static giving issues. And many many other fundamental things which normal good app should have. You just will find yourself implementing one by one features which reaction based window will give you for free. All you need is saying to AI "Create reaction based window using blablab with blbalal and blblabla" , and then follow wiki.amigaos.net articles of how create guis today. Then on top of reaction based gui you always can use themes if you want "modern" look, just like DvPlayer or AmigaAMP do for example.

Also, did i get it right, that instead of default english it all in german ?:) Not that i fanboy of any country or language, but english were defacto standard for many of us for many years.

@Maijestro

Catching up on things...

I downloaded your archive from OS4depot and it looks like a lot
of stuff is missing.

I appreciate it appears your efforts were mainly centered around
your Hollywood GUI. Clearly you enjoyed that. Understood.

Honestly, I don't need a GUI. As I mentioned, I have my own
means for calling MPlayer. As such, my focus is just on the
best MPlayer we can have.

OTOH, it appears you stripped all the CLI functionalities as
well as old functional display modes from your port of MPlayer.

Could you please go back and re-constitute all the old code into
your new port of MPlayer? ....or add your new va.library code
back into the old FULL Mplayer?

At the very least, your MPlayer executable should do everything
the last, latest version did plus you additions. Think about
all the older NG machines abandonned by the VA-API drivers
(XE's, Pegs, 440's etc - the machines that needed it most).

I don't have a VA-API gfx driver yet (still need a Weasel-free
way to get one) and ALL of the old display modes need to be
maintained in any new MPlayer versions.

BTW, the default tool for all your readme files should be
"Multiview", not "Multiviewer". You're on AmigaOS!

Thanks,

PJS

The most logical thing, which should have been done earlier, is to take the good work done by Maijestro on his VAAPI driver and simply trasfer it to our standard MPlayer version.
It had already been done to include all the features of the old releases scattered throughout version 1.5, which really, we didn't feel the need for another fork.