Now there is reason to celebrate, at least for me because Infinite Icons 1.5 is ready and today is Midsummer at least in Finland!

Making the update has required an incredible amount of planning work and actual work creating these from me but also i could already say from my good friend Michael Becker, he is behind
the work thanks to which we get to enjoy the installer for OS3.2 and AmiKit 12 & X13, without him these would not be available.

It seems to have been exactly 4 months since the last update, that's how long it took to get the update finished but the wait is worth it.

Here's what it contains in a nutshell:
- Over 700 new icons
- New cool 3D HDD icons with light and dark themes, these also on
OS3.2 and AmiKit
- OS3.2 updated installer with new installation options
- AmiKit installer
- AmiKit icons have been re-assembled and now cover
3 different colors
(Raven Black, Frost White and Classic Blue) and 2 different
drawer structures (Full & Split),
almost all AmiKit icons are covered.
- OS3.2 has also got a lot of new icons.

I hope you have a good time with the package because I had a lot of them while creating it!

You can now buy the icons from two different places:
https://www.amikit.amiga.sk/infiniteicons
There's an offer here this weekend so it's worth taking
advantage of it.
https://www.amiga-shop.net/en/

The update is still free for those who bought version 1.1 or later!

Now I'm going to dig up the scum and take a look at the new AmiKit X13, which I think has reached a new level, install the new icons for it and get to know it a little more deeply, i have the Rasberry Pi version.

The AmiKit installer works on all operating system versions (PC, Mac, Linux, Rasberry Pi)

If you haven't seen the Infinite Icons vibe video, please watch it, turn on your speakers and enjoy the show, and please also give a review, i.e. thumbs up or vice versa 🙂

Infinite Icons video YouTube:
https://www.youtube.com/watch?v=8u7mPa5R5kQ

Sorry this took a while!

@derfs

clib4 is missing from the requirements over the readme.Otherwise it won't work.

I did a fast check on the generated gcc packages as they come from adtools and there is no specs file included. I am goin to recompile one of them and see if that was skipped when the archive was created.

To be honest, I was not aware that a file called specs existed and could be used like what you guys describe. I will let you know if I find anything.

@LiveForIt
Quote:
No, I think it comes from EFI.

I think the important thing on vibe coding is - don‘t let
it do the whole stuff. Do it one method at a time or at
least class at a time. And do a manual review of the produced code,
at least roughly.

Let it do repetitive and copy/paste work or api replacement. But
the real big stuff and architectural work do yourselves.

@afxgroup

Probably the standard problems, none initialized pointers (causes random pointer values), and not checking if they allocated before freeing, freeing things twice, (freeing things while things are in-use. Async issues)…

I have noticed when vibe coding that AI’s often write code as examples not production code. I think Vibe coding might work better in Phyton and other languages where don’t need to be so picky.

It can well be that on Windows if free object it also close it, that is not true for AmigaOS. I doubt AI knows the different behavior of different OS's.

@joerg

Quote:

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:

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

@derfs

Jest tried a Swing tetris clone and:

1) keys are not working
2) When I close the window the system freeze. With sashimi I can see amiga_exit but the window is not closed and of course it doesn't return to console

I've compiled in on Linux with java 11 and tested on OS4

@K-L
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

Wiki Unified_Video_Decoder
Wikiwand Unified_Video_Decoder
https://en.wikipedia.org/wiki/List_of_AMD_graphics_processing_units

@TSK

VAAPI support on Radeon HD is not working correctly (you also need the V.5 driver).

It was reported months ago to Hans but he never found what was going wrong.

For full support of hardware decoding, you need a Radeon RX.

@ddni

Not my style..but thanks

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)

I put a NVMe card/device to the X1000 but boot process hang after displaying some RadeonHD info (on debug). I booted also on another partition which has that device driver made the other guy some time ago and the same result, the boot process hangs.

Sorry no, but order off Amazon and return if no good?

@LyleHaze

Thanks for the basic info!
I checked on line and there are so many adaptors to guess from..

Any more hints to a name that has been tested working?

Thanks in advance,

Michael

@pjs
Quote:"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.

@afxgroup
Quote:In case there are GCC distributions with missing "specs" file (why?) you can use, store it (the internal defaults of the GCC executable you are using) to the appropriate path (sorry, I don't remember where it is, or should be, and it might be a different path in different versions of GCC) and use that as a start:
You can change anything there you want, add additional C libraries, change the default C library, etc.

@ktaddQuote:

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

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!

@Gregor


gpt partition table is not supported by mounter.library.kmod

as far as I know.. its only RDB and MBR, unless gpt is handled internally in driver, this won't work..

clearly a system wide implementation is far better, then a per driver implementation. is not gpt made for bitlocker?

@samo79
Quote:
I'm available for testing.