ich777

Exactly, on your CPU HEVC needs to be decoded in software because your hardware isn‘t capable of decoding HEVC.

This is something that should be reported on the Photoprism Github since this is container specific, is it now working? This CPU (Haswell) isn't capable of transcoding HEVC (h265) from what I know: Click

Seems like your site is not available from your internal network or not configured properly so that it kicks you back. Please check your reverse proxy. Actually @Spectral Force helps me out with CSMM and 7DtD in general maybe try to join his Discord here: Click

Thank you for the report, should now be fixed, please update the plugin.

I think you are in the wrong support thread... The Picoshare template is maintained by @knex666

This is because it detects all devices also the card that you've bound to VFIO but that's basically a warning. Can you try to use as the key: h264_vaapi instead of h264_qsv (If that doesn't solve your issue, I would wait for the developer to answer) QuickSync needs the latest Intel Media Driver installed and I don't know if it's installed in Photoprism. This issue seems also related: Click

Installation works just fine for me, on 6.9.2 EDIT: @Squid when you uninstall the plugin and reinstall it it doesn't installs the package for the webgui. Is this option wrong for installing the plugin: upgradepkg --install-new ? EDIT2: @Squid Ah wait now I see it, I've forgot to implement the deinstallation from the package on deinstallation, added the webui on February and missed that probably. Everything fixed.

A GT620 would be not compatible with h265 anyways. Do you have passed through the device /dev/dri in the template (device not path!)?

Do you have Autostart on the plugin page enabled? Seems like it's disabled and that's why it's not working... Have you seen this: EDIT: Had to do this since it crashed some servers and with this method you first have to do a test on the plugin page before you can actually use it.

Please don't do symlinking, you have to move the files to the direction or change the startup parameter from what I know to reflect the path from the mods (CaSe SeNsiTivE). No, of course not, make sure that the files and folders are accessable by nobody:users (UID: 99 | GID: 100) and the permissions are set to 770 or 777.

@Squid why is it reported as not supported? I will look into this ASAP, give me a few hours please.

It supports RC4… Do you have any issues? EDIT: If you got a message from the Plugin Update Helper please see this post:

Can you post your Diagnostics? Can you post a screenshot from the template? What does the plugin itself say, is the TPU visible in there? What TPU do you own exactly? Very unlikely that the PCIe versions fail because I've set the throttle temperature a little lower as usually in the Coral driver except for the Dual Edge TPU because you need to come up with a custom cooling solution for this TPU on your own, but of course they could die because of other circumstances....

Das kannst du selbst machen aber indem du den Tag beim Container hinten hinzufügst, ich hab aber noch nicht porbiert ob der Tag 2.1.0-latest den Unraid server crashed wie der alte 2.0.0-latest. Viele User haben mir gemeldet das der 2.0.0-latest Tag den Server crashed und somit läuft der weiter auf 1.5.0, wenn es jemand ändern will bitte selbst machen. Beispiel: Du findest alle Tags hier: Klick latest = 1.5.0 2.0.0-latest = neuestes Stable 2.x.x Build 2.1.0-latest = neuestes Stabile 2.1.x Build master-latest = wird vom neuesten master branch gebaut Bin mittlerweile von check-mk weg da es mir zu closed source.

Did you maybe run a fix permissions on your appdata folder? If so, please don't do this, this can cause such issues...

Does the card work on another machine, the I/O Error is a little weird... No DVB cards on the used market available where you live? If you have a TBS webshop in your country they have really good cheap cards.

It would be probably the best to start over? Did you use a MariaDB or the integrated DB? Did you change anything trivial in the template?

I think the description from the container should be clear enough:

You can also try to change your syslinux.conf to: BOOT_IMAGE=/bzimage initrd=/bzroot saa716x_budget.int_type=1

Try to do: chown -R 99:100 /mnt/cache/appdata/photoprism from an Unraid terminal, of course stop the container first and change the path if it is different, after that try to start the container again and see if you get the error again (...and also remove the HOME variable).

Simply create a variable like this in your template: Keep in mind you have to set the path inside the container as the home path, not the path to the files on Unraid!

From my perspective you can safely upgrade to 6.10.0-rc4, data loss is very uncommon even on the RC versions. Please keep in mind that RC versions, at least in the case for Unraid, are tested really really really well and only have sometimes minor issues (rc4 has a UI bug that highlights a bit too much in the WebUI). Also don't forget that you can always go back to 6.9.2 if something isn't working for you.

I would recommend that you set the folder to 777 and user and group to 99:100: chmod -R 777 PATHTOFOLDER chow -R 99:100 PATHTOFOLDER

@untan Plex PX Series Tuners (Japan) are now available in the DVB Driver plugin (currently for Unraid 6.9.2 & 6.10.0-rc4 and will also be compiled for the coming Unraid versions): Please update or install the plugin and make sure that the plugin version is 2022.03.30, select the Plex PX Series Tuners (Japan), click Update and restart your server.

Message sent.