they only improved later
Tech giants simply want to lock you into their own formats
Simply doesn't matter if you go for quality anyway.
Storage is cheap as well.
Midnight over here... taking a break now :D
In that case, trigger an manual index / import after restarting.
Manual file system changes (without WebDAV) also won't trigger it.
Just tested auto indexing with PhotoSync. Works just fine.
It uses the same copy / move setting as selected in the UI in Library > Import
@graciousgrey Can you test this again using our latest preview build?
1 reply
Reduce the safety delay as needed - the default of 15 minutes may be too long for some users. See config options in our docs.
There might also be edge cases where index AND import are triggered at the same time - which is not possible. So one may be canceled, depending on which runs first.
you guys, and girls :P are doing a wonderful job!!! :)
preview functionalities are enabled only with patreon or can be unlocked also with a one time donation?
The preview build can be used by everyone, only permanent delete and dark themes are early-access for now: If you're a contributor or sponsor and don't know how to enable it -> email to hello@photoprism.app :sparkles:
Just pushed a ton of improvements for dates and time zones - preview build is running
@lastzero I am having some issues with transcoding time of longer videos on my raspberry pi 4. Is there something I can do to speed this up or get some kind of UI feedback how much longer one has to wait before the video starts streaming?
To put some numbers here, trying to watch a 40mb video is over a minute of wait time. My guess would be that ffmpeg is not using any hardware acceleration. Can I configure the codec somehow? According to this (https://www.willusher.io/general/2020/11/15/hw-accel-encoding-rpi4),
h264_v4l2m2m would be a codec that is supported on an RPI4.
There's a GitHub issue for transcoding configuration
No sponsors yet though
Well, ideally I wouldn't want to configure anything. In the end, I just want the UX of larger videos to be better. I am not fussed about whether that happens via a config option where I set the codec or via auto-detection of codecs that are implemented in hardware. Could we potentially outsource this "choose a fast and good codec" to ffmpeg? I am not that familiar with it but it sounds like something ffmpeg might support so apps like photoprism don't need to implement such a detection algorithm
Happy to sponsor an issue that moves photoprism forward here, I am just not sure if a configuration option is the best way. Keen to get your opinion here.
Thinking about it, a video transcode config option is probably the simplest to implement.
Setting that correctly could always be done by an installation script based on the given hardware.
Thinking about it, a video transcode config option is probably the simplest to implement.
Setting that correctly could always be done by an installation script based on the given hardware.
