Regarding the va.library error with -vo comp: I was not able to reproduce this.
I was able to verify that -vo option does not work on my X1000 with an HD7750 graphics card. I sent you an email with a verbose log that show it recognized the -vo comp_yuv command on the command line but still tried to use the vaapi driver.
Regarding the va.library error with -vo comp: I was not able to reproduce this.
I was able to verify that -vo option does not work on my X1000 with an HD7750 graphics card. I sent you an email with a verbose log that show it recognized the -vo comp_yuv command on the command line but still tried to use the vaapi driver.
Fixed subtitle rendering: libass video filter (vf_ass) now correctly included Fixed -vo option being ignored when VAAPI was active Fixed font path resolution on AmigaOS4 (PROGDIR: prefix) Software video outputs (comp_yuv, comp_yuv2, cgx_wpa) now correctly disable VAAPI hwdec
Note: A valid subfont.ttf must be placed in the conf directory of V-MPlayer.
@all
Just a quick update on where V-MPlayer is heading.
We are gradually bringing all the features that are present in MPlayer 1.5 into V-MPlayer. Everything will always be released together as a combined package, because there are also users who love the Hollywood GUI — and that GUI has been significantly extended and optimized.
Window resizing now works the way you would expect it to, with the content scaling natively. Fonts are now rendered via the GPU which looks much better. Some animations that ran after startup have been removed and are now static. On my X5000 the GUI uses only 1-2% CPU at idle and feels very smooth.
More updates to follow — please keep testing and reporting!
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
Re: MPlayer v1.5 and your work - that is an issue, IMHO. You are doing more than just adding VAAPI. You are advancing the overall functionality of MPlayer and I would suggest it would be a lot more valuable to our little community to plow as much of that back into a single source tree rather than spawning you own crippled (VA.lib ONLY) branch.
"Only" 2 branches is still much better than it used to be When I was still working on MPlayer there were at least 4 different branches: afxgroup MPlayer, liveforit MPlayer, mickjt MPlayer any my MPlayer versions (mostly "amiga" and "p96_pip" VO implementation/changes only), not to mention completely different ones like the MorphOS port (most of a MorphOS CGFX VO can run with the P96 CGFX emulation on AmigaOS as well)... AFAIK everything from the previous 4, or more, AmigaOS MPlayer versions/ports was merged into a single one in the current MPlayer 1.5 port, and combining everything from MPlayer 1.5 and V-MPlayer into a single version would be a good idea, but only after everything was tested successfully and there are no regressions at all. That requires a lot of beta testing. Using AI can make coding much easier, but until now IHMO it still adds more bugs than experienced human developers would usually do, and therefore needs more proof reading of the sources and beta testing than traditional software development required.
I tested V-Mplayer (on X1000+RadeonHD), the first video I tested worked nicely, there was some slow downs occasionally. But then I tested another video and that had grey window/screen consuming the most of the CPU. The debug output was flooded with:
RadeonHD (0): Wait done 3331562 on ring 3 timed out. GPU busy RadeonHD (0): Ring 3 hung. Performing a GPU reset RadeonHD (0): Wait done 3333921 on ring 3 timed out. GPU busy RadeonHD (0): Wait done 3333921 on ring 3 timed out. GPU busy ... (endlessly)
Rock lobster bit me - so I'm here forever X1000 + AmigaOS 4.1 FE "Anyone can build a fast CPU. The trick is to build a fast system." - Seymour Cray
AFAIK everything from the previous 4, or more, AmigaOS MPlayer versions/ports was merged into a single one in the current MPlayer 1.5 port
Exactly, this was one of the main goals of our 1.5 release, along with of course fixing further bugs and adding more features where possible
Quote:
and V-MPlayer into a single version would be a good idea, but only after everything was tested successfully and there are no regressions at all. That requires a lot of beta testing.
Yes, these new features should certainly be integrated and it is a task that needs to be done with meticulous care, VAAPI is certainly essential and would complete the project
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
