aaronwmorris
commented
2 weeks ago Try upgrading. I merged #1327 last night which might be the cause.
Closed laterrible closed 2 weeks ago
aaronwmorris
commented
2 weeks ago Try upgrading. I merged #1327 last night which might be the cause.
laterrible
commented
2 weeks ago Sadly no dice. Ran the upgrade just now. It has generated a couple timelapses in the last week, all of which have very quirky artefacts (red outlines, horrible exposure etc). Scaling is set to 50%, so expecting t isn't a memory-related thing.
I'll dig into the logs, see if I can find anything else sticking out. Thanks Aaron
aaronwmorris
commented
2 weeks ago If ffmpeg generates an error, it should be logged. All timelapse errors would be under the Video worker.
You can search for Video worker related errors with:
grep Video /var/log/indi-allsky/indi-allsky.logAh nice, thanks, saved me hunting around. OK, so that log points at a few things namely
[warning] deprecated pixel format used, make sure you did set range correctly\n[libx264 @ 0x557f91ade0] [error] width not divisible by 2 (1521x 1140)\n[error] Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height\n'
over and over again.
I'll have a closer look at the config and settings, see where it's gone wrong. Thanks again Aaron
/edit: yep, changing the scaling from a percentage to one of the IMX477 scaling seemed to have fixed it, was able to generate timelapses. Time now to configure all the bits and bobs, but great success. Thanks!
aaronwmorris
commented
2 weeks ago Beat me to it...
Okay, that helps, I think the cause is the image scaling combined with the video scaling. Since you are scaling the image by 75%, then ffmpeg is supposed to scale that by 50%, but the resulting resolution is not divisible by 2.
I have protections in indi-allsky to make sure that any action in its own control that changes the image dimensions, the resulting image wlll be divisible by 2, but this is a case I cannot manage because ffmpeg is the cause.
aaronwmorris
commented
2 weeks ago The IMX477 specific scaling options set a specific size and do not calculate the scale mathematically. That is why it works.
Hey team, recent fresh install going pretty well, it's been a while since I last used this and it's better than ever, with one exception: I can't get timelapses to generate.
Both auto and manual attempts fail. Here's the support log. 4b with pi hq camera, running from Poe hat installed on a USB stick I've had success with before.
What goofy things have I setup incorrectly or overlooked?
/home/admin/indi-allsky/misc/support_info.sh: line 61: warning: command substitution: ignored null byte in input #################################
indi-allsky support info
#################################
indi-allsky config (passwords redacted) 2024-06-16 07:17:17,877 [INFO] MainProcess config._dump() [890]: Dumping config
#################################
end support info
#################################