Updating to latest version

[Bigmack3000]

If i want to update to the latest version, do I simply docker compose down, change the text of the yaml file to the latest version, and then docker compuse up?

Thanks.

[NeptuneHub]

you need to change the tag for update to the last version and then restart the container. If this don't work you can also delete the image (NOT THE VOLUME) and then restart, to force a re-download.

Just I don't remember if you use some old CPU without AVX2 support, I just discovered in this issue:
#289

that AVX2 support is needed from the v0.8.7

[Bigmack3000]

Ok, i guess i won't upgrade. Why does the need for that keep going back and forth? Are there plans to drop the requirement again?

[NeptuneHub]

I'm really sorry for this but I had to update the version of different library, that was very old, and this bring back the AVX2 requirements. So it wasn't planned and I discovered only after the release not having any old CPU for test.

I don't think I'll remove another time this requirements, but seems that the user @Cwavs is planning to do a fork of AudioMuse-AI to support the old CPU.

To me, not having an old CPU for actual testing, it become difficult to maintain this and I prefer to keep this requirement on.

Meanwhile the actual AudioMuse-AI v0.8.6 is still fully functional and sticking on it you will be able to keep enjoy using AudioMuse-AI.

Thanks.

[Bigmack3000]

Well that is very disappointing and a bit frustrating after how long it took to scan my library for it to already be obsolete.

Can i make 2 requests before you stop supporting this version? One small, one not as small.

1. Can you just add the album title request I made, so I know where a song is coming from when choosing it?

2. Is it possible to add an option to Song Path to limit one song per artist?

Again, I know you're moving on with avx, but these two things would keep it very usable for me for a long time.

Thanks.

[Cwavs]

Hi Just dropping in to drop some info. It seems that there isn't anything that has a hard dependency on AVX or AVX2, I'm currently working on a modified dockerfile that should allow for building without a hard requirement on them, allowing 0.8.7+ to continue to run on older CPUs

[Bigmack3000]

That would be amazing!

[NeptuneHub]

Going to close this because as you can se a -noavx2 image was deployed.

It's important to highlight that I don't have the proper machine to do this kind of test, so I really don't know for how long it will be able to work. But as soon as it fixable with not much effort, why not.