Okay, the video is fine now; it all depends on how the YouTube video was encoded.
But I still have a problem: the audio cuts out at a certain point.
I've tried different versions of YT.rexx, but it doesn't change anything.
I've changed my screen resolution, disabled everything in WBStartup and in user-startup, and tried with different videos, but the audio cuts out again.
On X1000+RadeonHDv5 VAAPI works fine, but you cannot play H.265 videos here: Southern Island cards itselves have only HD(720p) H.264 decoder and no H.265 decoder - UVD3.1 To utilize full VAAPI you need Polaris card, which has FullHD H.264 and H.265 decoders - UVD6.3
Southern Islands can perfectly decode 1080p streams. There is something Hans nevers manage to find which prevents Southern Islands from decoding correctly 1080p videos (and even some 720p videos whereas CPU usage is still low).
Here are the capabilities of an R7 250 (from AI since I did no want to look out for many sites right now):
Quote:
1. Capabilities of the R7 250
The R7 250 has the UVD (Unified Video Decoder) block, version 4.x.
It can hardware decode Full HD 1920×1080 videos in: * H.264/AVC (common in .mp4, .mkv, Blu-ray) * MPEG-2 * VC-1
When playing back supported 1080p H.264, CPU usage typically drops to just a few percent.
2. Important limitations
No hardware decoding support for HEVC/H.265, VP9, or AV1 on this generation.
If your video is encoded in H.265 (common for recent encodes), decoding will mostly rely on the CPU.
It is optimized for 8-bit H.264; exotic profiles (high profiles, 10-bit, very high bitrates) may also fallback partially to CPU.
What's more, the driver crashes with a grey screen without any reason afters having watcheds one or two videos.
Hans explained he never found why this behaviour was occuring and advised to switch to an RX card.
-- AmigaONE X1000 and Radeon RX 560 Sam460 and Radeon RX 560 MiST FPGA Replay + 060 DB
Native ReAction interface, not a MPlayer skin Mesa / OpenGL ES stage (video in the well, visualizer for audio) Tabs: Media, Radio, Favorites, Plugins Playlist: open files, Open URL, drag-and-drop, Workbench / CLI hand-off to a running Spectra Play / Pause / Stop, Prev / Next, Seek, Volume, Mute Repeat, Shuffle, Fullscreen OSD cycle and subtitle cycle 10-band equalizer (live via ARexx) Audio filters (karaoke, extrastereo) and video filters (flip, mirror, deinterlace, brightness, contrast, saturation, hue, gamma) Beat-reactive GLES visualizer (6 scenes); off during video so the picture stays clean Skins (Neon, Studio, Ice, Player) plus optional GLES plugin libraries Internet radio via radio-browser (search, ICY titles, record to Records/) Favorites, resume last (URL, position, volume, viz, OSD) Folder cover art on the audio stage Mini player, iconify, single-instance (port SPECTRA) Type column shows the real format (mp3, wav, mpeg, mp4, …)
*V-MPlayer — engine*
FFmpeg *8.1* (was 7.1.4) VA-API hardware decode / display (H.264 and friends) ARexx control: pause, volume, mute, quit, seek, live EQ (`AF_CMDLINE`) DualPlay (`-audiofile`) for separate audio+video streams HTTPS / OpenSSL (AmiSSL) for secure streams Own window; Spectra embeds it in the Mesa stage OSD, ASS / subtitles (`conf/subfont.ttf`) PCM export for the visualizer (named memory) Local files, HTTP/HTTPS, HLS radio, playlists (m3u / pls)
Short blurb you can put above the lists:
Spectra is a native ReAction GUI with Mesa for V-MPlayer on AmigaOS 4.1. The engine now runs FFmpeg 8.1 with VA-API and a lot of extra playback features. Coming soon to AmigaOs4.1...
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
kas1e wrote:@Maijestro Wow, that start to looks like something cool ! No Hollywood anymore, pure C + Reaction ?
Can it woks without mesa too, right ?
Yes — Hollywood is gone. The GUI is plain C + ReAction, the engine is V-MPlayer (FFmpeg 8.1). Mesa GLES is only for the optional visualizer.
Without mesa.library the GUI still plays files, radio, video (VA-API), EQ and the rest. The Viz button just says it needs Mesa.
It’s impressive, and I wanted to do something with the new Mesa. Machines without va.library don’t get MPEG-4 video acceleration either — so yes, this is VA-API and Mesa, and it’s fully working on X1000 / X5000.
Edited by Maijestro on 2026/9/6 18:47:16
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
Looks very nice! Does it support Altivec if available? Can it?
There will be two engine binaries.
One is built for G4 with AltiVec — CPU SIMD for machines that actually have the vector unit (G4, and X1000). That’s the path that helps software decode and scaling when there is no VA-API.
The other is hard-tuned for X5000 (e5500, no AltiVec). That machine has no AltiVec, so enabling it would just crash. That build stays scalar on the CPU and leans on VA-API for video.
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
First have crashes on x1000, but then TearsOfMe point on the correct x1000 binary, and it works.
Some moments which you may want to fix :
1). When i open mp3, or video, it didn't auto-player. I didn't know if there option for, but have this one by default surely need it.
2). When you open video , dbl-click expected to bring it to the fullscreen, and dbl-click again back to "player" window.
3). "slider" for moving over the frames in video did't auto updates. Yes i can move it, but somehow expected its auto moves and show the current position, just like happens with Mp3.
4). When loading mp3 tasty image showsup. Maybe worth those PumpUps animated via "bass" ?
5). audio/video filters didn't works, but i release you add some registrations key , sadly :( Sure we all spend time on, but, well, better something than nothing i assume :)
Edited by kas1e on 2026/9/13 13:15:27 Edited by kas1e on 2026/9/13 13:16:10
First have crashes on x1000, but then TearsOfMe point on the correct x1000 binary, and it works.
Some moments which you may want to fix :
1). When i open mp3, or video, it didn't auto-player. I didn't know if there option for, but have this one by default surely need it.
2). When you open video , dbl-click expected to bring it to the fullscreen, and dbl-click again back to "player" window.
3). "slider" for moving over the frames in video did't auto updates. Yes i can move it, but somehow expected its auto moves and show the current position, just like happens with Mp3.
4). When loading mp3 tasty image showsup. Maybe worth those PumpUps animated via "bass" ?
5). audio/video filters didn't works, but i release you add some registrations key , sadly :( Sure we all spend time on, but, well, better something than nothing i assume :)
First of all, thanks for the feedback.
As for the crash, it’s because there are two binaries: one is the X5000 version, built with e5500 flags, which crashes on the X1000... the other is the X1000/Altivec version, which would crash on the X5000. But we’ll be making improvements to prevent this from happening again. Perhaps a feature where the user has to select which machine they’re using—X5000 or X1000—and the correct build is set accordingly.
Yeah, I'll definitely add the double-click feature, but you can already set full-screen mode using the GUI button—though yeah, double-clicking is cool.
As for the rest, yes, everything is there and works in the full version, but don't worry about it—it'll be free for everyone soon, as soon as I've collected a few donations.
Don't get me wrong, I'm just a wannabe AI programmer, and this is an expensive hobby.
Thanks again for checking it out; I'll work through the points and try to keep improving it.
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
This is a question/observation about V-Mplayer itself and not the new optional GUI. I have a 16:10 1920x1200 monitor I use with my X5000. When I go to fullscreen with the video playback, such as with a 1920x1080 16:9 video file, the correct aspect ratio is not respected but rather the image is stretched too tall to fill the 16:10 screen. I would prefer the aspect ratio to be maintained and black used to fill the difference. And when resizing the window (not full screen) I would prefer the aspect ratio of the source video to not be stretched out of proportion. Would this kind of fix be easy to implement? Or is there already a way to constrain the aspect ratio? Thanks!
mbrantley wrote:This is a question/observation about V-Mplayer itself and not the new optional GUI. I have a 16:10 1920x1200 monitor I use with my X5000. When I go to fullscreen with the video playback, such as with a 1920x1080 16:9 video file, the correct aspect ratio is not respected but rather the image is stretched too tall to fill the 16:10 screen. I would prefer the aspect ratio to be maintained and black used to fill the difference. And when resizing the window (not full screen) I would prefer the aspect ratio of the source video to not be stretched out of proportion. Would this kind of fix be easy to implement? Or is there already a way to constrain the aspect ratio? Thanks!
It'll be in the next update
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
News feed
OS4 Feedback forum
OS4Depot Feedback forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
