homdax wrote:

Is this suitable for shared webhosting or would a VPS be preferrable?

Yes, it’s perfectly suitable for shared web hosting. That’s why the inference is performed on our AI servers

windracer wrote:

Thanks for the invite!

What's the expected turnaround time for processing submitted images? I see them all in the queue with a Pending status.

No worries about the invitation, I hope you like Piwigo AI :-)

The processing time depends on the current load on our servers. It can be almost instantaneous when the queue is light, or take a few minutes during peak usage.

Also, if you submitted images around 11:00 PM (Paris time / CET), there was a temporary delay on our side. The workers were restarted shortly after.

Everything should now be back to normal and processing should be smoother.

Let me know if you notice anything unusual

Last edited by Linty (2026-04-02 02:22:45)

Yes, this is most likely due to the video. The analysis probably stopped mid-process and the job didn’t go through the callback workflow

Regarding the queue, there are currently no available actions. However, in the upcoming 0.0.2-beta version that I’m preparing, I’ve added several actions such as the ability to cancel a job or force the AI server to retry an analysis...

I’m also working on a way to make the plugin more proactive without impacting page load times (some backend actions can only be triggered when a Piwigo page is opened)

homdax wrote:

sent a message using the form for the api and such

Hi,

I already sent you an invitation email. Check your spam folder, or send me a mail via the forum so I can give you your API key

Hello!

A new version of the plugin has been released with the following changes:
- add degraded mode for databases without native VECTOR support
- add overview page (For now, it just displays a message if the database isn't compatible. More features are coming soon.)

- add direct image file upload as an alternative to sending the image URL (useful when the AI server can't reach private galleries)
- add pull mode via admin polling as an alternative to the auto-callback (useful when the AI server can't reach private galleries)
- add outdated plugin detection

We have also received new requests to test Piwigo AI, so we will be sending out a few API keys.

I like the dashboard.

I was able to use the "Check Tickets" to "unstick" a bunch of items I had pending. That worked for everything except one old one from 4/7 that still shows pending. Any way to clean that out?

windracer wrote:

I like the dashboard.

I was able to use the "Check Tickets" to "unstick" a bunch of items I had pending. That worked for everything except one old one from 4/7 that still shows pending. Any way to clean that out?

Thank you ! :-D

That last ticket is probably from the old system, so I imagine that’s why it’s still stuck. I’ll add handling for this case in the cleanup process.

Denzel wrote:

What a brilliant feature! Will it be possible to "tell" the AI what to prioritize regarding tags and descriptions? Maybe a little bit of context, for better results. Perhaps even include the file and album names? Honestly, automatic tagging based on existing keywords would be enough for me. I love it! :)

Thank you so much!

And to answer your question, we are actually thinking a lot about this topic right now. The goal would be to allow users to provide additional context when requesting an analysis, which could open the door to many features, such as (non-exhaustive list):

- automatic tagging based on existing tags
- suggesting which album would best match an image
- generating more accurate descriptions using the gallery context
- and more

This is definitely something we find very exciting as well :-)