MPlayer 2026 SVN/CVS FFMPEG7.1/Vaapi

@pjs

Quote:

It looks like bsdsocket.library crashes first, and then V-MPlayer follows suit. How did you test it?

And yes, the full log would be very helpful—could you upload it to os4depot for V-MPlayer?

@Maijestro

That's awesome. :)

@Majistero

Works very well on my X1000 - thank you very much!

@all

V-MPlayer 1.6.4 / Spectra 1.1 is on OS4Depot.

This update is free. No key, no demo. If you like it, a donation would
help a lot so I can keep working on V-MPlayer, including the Spectra GUI.

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

What is new:

- Video overlay on standalone V-MPlayer (YouTube, CLI, own window):
play, seek, clock, mute, volume, window size 640/800/1024, letterbox
or fill, fullscreen. Same bar for local video and streaming (VA-API
and yuv2). Not on the Spectra stage.

- Streaming: start a new stream while one is playing. The running
engine is stopped, then the new stream starts. DualPlay and all
video outputs.

- AmiDock miniplayer. Closing the dock tile restores the Spectra
window; it does not quit Spectra.

- Spectra now auto-detects the CPU and starts the matching engine:
V-MPlayer (X5000), V-MPlayer.x1000 (X1000 / AltiVec) or
V-MPlayer.a1222. Leave all three files in the folder. Do not copy
one over another. Start Spectra, not the V-MPlayer icon.

- New A1222 SPE build (V-MPlayer.a1222) is in the pack. Spectra starts
it on A1222. It is untested on real hardware and still needs to be
confirmed. If you have an A1222, please try it and report back.

Bug reports and ideas for improvements are very welcome. I cannot
fix what I do not hear about.

Thanks, and enjoy.

@Maijestro

and what about to detect Sam460 or 440 ?? VOB files seem not work....

@Maijestro
Quote:
The Spectra GUI opens up on the A1222p but when I go to play a video nothing happens. So, I tried running V-Mplayer.A1222 from the command line and it produces the following errors when reading the config file and no video plays:

5.Work:Video/Players/V-MPlayer> V-MPlayer.a1222 Demons.mp4
Creating config file: PROGDIR:conf/config
The probesize option must be >= 32: 1000000
Error parsing option lavfdopts=probesize=1000000:analyzeduration=5000000 at line 8
The autosync option must be >= 0: 10
Error parsing option autosync=10 at line 11
The autosync option must be >= 0: 10
Error parsing option autosync=10 at line 15
The autosync option must be >= 0: 10
Error parsing option autosync=10 at line 19
The autosync option must be >= 0: 10
Error parsing option autosync=10 at line 23
5.Work:Video/Players/V-MPlayer>


Note: I've also tried it on my X1000 and it seems to be working on it, with the usual gray screen once in a while with a Radeon HD card as expected, since it appears to be a driver issue.

I like the new interface much better than the old one. Donation coming your way.

Thanks for the continued work.

@ktadd

Could you test a few a1222 builds? A debug build is currently being created so we can identify and reproduce the problem. Right now, V-MPlayer.a1222
returns this error when reading PROGDIR:conf/config. SPE vs. newlib causes the
integer range check to reject valid values (autosync=10, probesize=1000000),
resulting in the engine terminating before VA-API starts.

The issue has already been fixed, but it still needs to be tested.

Debug Build A1222/SPE https://we.tl/t-KchGgfZXkTp52PBB

And thanks for the feedback...

@Maijestro

Yay! This gets better and better. Testing perfectly on my X5000 with RX580 card playing a variety of video files. I played a feature-length 1080p film all the way through and everything is rock solid. Greatly appreciate that this new version respects the aspect ratio when resizing and going full screen. I'll buy you a beer soon!

Today I will see how it is able to deal with things on an X1000 with an R9 270 card and older driver. It's a shame we've never been able to get the most out of those cards and the X1000.

@mbrantley

Quote:

I’m glad the new version works better for you. Yes, the aspect ratio was rebuilt completely. Before, I had tuned it to my own needs, but that was the wrong approach.

Next I’ll try to optimize it further across all builds. Right now the audio still drops out briefly when switching to fullscreen; that has to be fixed, and there are more things to come.

If you run into any bugs, please report them. I need those reports so I can act on them.

And thank you for the donation — it helps me keep working on this.

@MaijestroQuote:

EDIT:
Ignore this. I went on Discord and saw there was a later version. I downloaded and tried that version. Posted the results on Discord.

Downloaded and test this version.
Here are the shell output results:

5.Work:Video/Players/V-MPlayer> V-MPlayer.a1222.debug Demons.mp4
The osdlevel option must be >= 0: 0
Error parsing option osdlevel=0 at line 5
The probesize option must be <= 2147483647: 1000000
Error parsing option lavfdopts=probesize=1000000:analyzeduration=5000000 at line 8
The autosync option must be <= 10000: 10
Error parsing option autosync=10 at line 11
The autosync option must be <= 10000: 10
Error parsing option autosync=10 at line 15
The autosync option must be <= 10000: 10
Error parsing option autosync=10 at line 19
The autosync option must be <= 10000: 10
Error parsing option autosync=10 at line 23
5.Work:Video/Players/V-MPlayer>

@Maijestro

Hi!

OK, got a chance to install the new v1.6.4 build and was able
to recreate the DSI on the 6450 card in my X5K/020.

As requested, I posted a full report along with the console
history and crashlog on OS4depot.

I hope this helps debug the DSI.

Please post of you have questions or need more info.

Thanks!

PJS

@pjs

Quote:

Thank you for the detailed report—it was very helpful. This should be fixed in the next update.

@Maijestro

On my X1000, when I try to resize the GUI with the video running in it, it freezes the whole system.

No problem on Sam460 but ratio is not maintained when resizing the window. There should be black bars to keep the ratio. Ok in fullscreen.

I may also add that I find V-Mplayer to be less smooth than Emotion playing the same file (there are slight stuttering) and the image is shaprer with Emotion than with V-Mplayer.

But V-MPlayer consumes less CPU with the same file.

It seems Emotion was fully optimized to get the best of what it could achieve regarding video decoding.

Thanks!

@K-L

You shouldn't forget that Emotion has been developed over many years and, of course, has been optimized very well.

Emotion uses FFmpeg 2.x (2014), while V-MPlayer uses FFmpeg 9.x (2026)—that alone is a huge difference. I've already made some initial optimizations, and the resize issue has also been fixed.

@Maijestro

Of course, since it's the beginning of V-Mplayer, there is room for optimizations.

Regarding FFmpeg versions, what does it change for us, poor users? :)

@K-L
Video:

Hardware. Both can touch RX/HD through Enhancer va.library. Emotion stays on the H.264 UVD path from 2.2. 9.0.1 talks modern VA-API (H.264, HEVC, more if the card supports it). Vulkan is off in your build — it does nothing on OS4.

Network. 2.2 has no usable HTTPS for today’s streams. 9.0.1 has OpenSSL/AmiSSL, so DualPlay/YouTube can stay HTTPS. HLS/DASH/WebM are twelve years ahead.

Containers. MKV/MP4/MOV from 2015–2026 (HEVC, AV1, Opus, newer MP4 boxes) 2.2 often cannot parse. 9.0.1 can.

OS4 build. Emotion: shared libs, ABI frozen since 2017/2019. V-MPlayer: FFmpeg static in the engine, GPL/nonfree, dav1d/vpx/opus/lame/freetype. X5000 without AltiVec; X1000 extra with AltiVec.

What 9.0.1 does not magically fix on OS4. No x86 ASM, no Vulkan, no AltiVec on the X5000. Emotion can still look smoother in-window because one process composites — that is GUI, not FFmpeg.

In short on AmigaOS 4.1: 9.0.1 is HEVC, AV1, modern HTTPS, and VA-API. 2.2 is H.264/MPEG plus old libraries.

Audio:

Quality. 2.2 uses swresample 0.18 (Emotion’s swresample2.library). 9.0.1 resamples and mixes far more accurately (float planar, 24/32-bit, fewer pitch/sync glitches). AAC in 2.2 is the 2014 decoder; 9.0.1 is the current FFmpeg AAC path (ffaac). That showed on A1222: FAAD crawled, ffaac played.

Streams. Radio/YouTube audio today is often HTTPS AAC or Opus. 2.2 cannot do modern TLS. 9.0.1 can, via AmiSSL.

Output on OS4 (not FFmpeg). Emotion talks AHI directly. Live V-MPlayer is -ao sdl (AHI through SDL) on X5000/X1000; the A1222 extra uses Emotion-style ahi_dev2. Filters (10-band EQ, karaoke, extrastereo) are MPlayer af, not something Emotion’s 2.2 stack has.

What does not change. Speakers, AHI, and CPU still limit 5.1/hi-res. 9.0.1 does not add a new Amiga sound driver; it decodes more formats and does it cleaner.

Short: 2.2 is stereo MP3/AAC/AC-3 from 2014. 9.0.1 is Opus, modern AAC, multi-channel, and HTTPS audio.