Comments (13)
The ASI178 has a very large sensor which produces large images (probably a few MB). The RPi is a very capable computer but it has its limits. Avconv is probably hitting a memory limit threshold and stops.
To make sure that's the issue, you can try running the timelapse manually:
scripts/timelapse.sh 20180817
Look for any errors, warnings, segmentation fault, etc and report them here.
My guess is that it will not always fail at the same image, which means there's no problem with the images themselves, just that the RPi has reached some memory limit.
One way to get things to work is to reduce the images
in scripts/timelapse.sh, on line 24, you can add something like that:
magick mogrify -resize 50% images/$1/*.$EXTENSION
That should reduce the length and width by 50% (image 4 times smaller on disk). Keep in mind that this command is overwriting the source images though.
from allsky.
I am a bit confused exactly where to put the: magick mogrify -resize 50% images/$1/*.$EXTENSION
I don't know how to tell if I am on line 24 or at the right spot or if I am putting it in right
from allsky.
Hey, I could have explained that better, I agree.
Here's what I would do:
# Shrink images coming from large sensors (ex: ASI178MM and ASI178MC). Adjust percentage to your own preference
magick mogrify -resize 50% images/$1/*.$EXTENSION
# Find invalid images (0 bytes size) and delete them to prevent errors during timelapse
find "images/$1" -name "*.$EXTENSION" -size 0 -delete
# find images, rename images sequentially and start avconv to build mp4; upload mp4 and move directory
ls -rt images/$1/*.$EXTENSION |
gawk 'BEGIN{ a=1 }{ printf "mv -v %s images/'$1'/%04d.'$EXTENSION'\n", $0, a++ }' |
bash
avconv -y -f image2 -r 25 -i images/$1/%04d.$EXTENSION -vcodec libx264 -b:v 2000k -pix_fmt yuv420p images/$1/allsky-$1.mp4
So I basically just added the mogrify command to reduce images size. I haven't tested it but I will try it with last night's data. If you want to be on the safe side, you can make a backup copy of last night and run timelapse manually. If 50% was not enough, you can restore your backup and try a lower percentage until the timelapse is successful.
Please keep me posted and I'll drop a note in the README for large sensors.
Thomas
from allsky.
I am a total newbie at this, but I seem to be unsuccessful so far, there was something about unable to encode the video...??. So then I tried it with a reduced number of images ....
( 40 instead of nearly 700, these are about 9.2 MiB in size so they are huge...) then this time the script will report "Time lapse was created" but the mp4 is unplayable. The actual file in the pi is reporting the mp4 file is (0 bytes) and will not play.
Oddly enough it actually did produce a playable time lapse the first time I tried this out but it has not produced one successfully since that one time.
from allsky.
Can you try running this directly from the terminal (adapt the date if you need to):
magick mogrify -resize 30% images/201808/17/*.jpg
And then look at the size of an individual image. It should be way less than 9.2MB.
Also, since your images are so large, have you checked how much space is left on your SD card?
from allsky.
Wait a second....do I have to download and install image magik first?
from allsky.
Nope, it should have installed when you ran sudo ./install.sh
at the beginning.
Open a terminal and type convert
. You'll see if it's installed or not.
from allsky.
I added the text to the script as suggested above and when I run scripts/timelapse.sh 20180821 i get an error that looks like this:
[swscaler @ 0x1481300] depreciated pixel format used, make sure you did set the range correctly
and
x264 [error]: malloc of size 20515824 failed
video encoding failed
[libx264 @ 0x1469e00] final ratefactor: 30.79
Conversion Failed!
- Timelapse was created
The timelapse is not playable, has 0 bytes and is basically an empty file.
Also when I try to run magick mogrify -resize 30% images/201808/17/*.jpg I get an error that says:
bash: magick: command not found
What is the next course of action I should take? Turns out the saved .jpg are 254.1 KiB each approx and they don't seem to be getting resized. There is 49.9 GiB of free space. A Keogram was generated.
from allsky.
Sorry, I should have tested that first. You don't need the magick
keyword. Try this instead:
mogrify -resize 30% images/201808/17/*.jpg
This should work and resize the images to something that avconv can handle.
from allsky.
I have tried a few things but from what I conclude it will try to make the timelapse but it always ends up as a "0 KiB" size file that doesn't play. ANy other bits of advic I can follow to track down the issue? It seems most files generated are now about 450 KiB after setting to JPG 80% quality. Thanks.
from allsky.
Does this happens also when you run it manually?
scripts/timelapse.sh 20180924
Can you copy the output from that command?
from allsky.
Yes when I run it manually usingn the script......it seems t generate an empty file. I have not tried to copy it and play it on my home PC, I just figured it would be an empty file. I'll try later when I get home.
from allsky.
This issue is from a much older release of the AllSky software. If you think it might still be relevant, please test it with the newest version and submit a new issue if needed. Thanks.
Please see the README.me file on the GitHub main page for workarounds to the "timelapse not created issue".
from allsky.
Related Issues (20)
- Fix locales
- Upload issues HOT 7
- Feature Request: SQM Analysis HOT 2
- [BUG] MQTT as part of module "Clear Sky Alarm" protocol error with Mosquitto MQTT in home assistant HOT 3
- sunset data is 3 days old: PWD: Operation not supported HOT 2
- CSRF updates
- [ENHANCEMENT] Check for more days of images than "Days to Keep"
- Help with wew heater status under System information
- [enhancement] install.sh should only look back two major releases
- Image meta data
- [BUG] "allsky.sh --help" doesn't work
- [BUG] Some floating point settings can be converted to integers before being passed to the capture program HOT 1
- [ENHANCEMENT] Use RPi_cameraInfo.txt file at runtime
- Is there a setting for Live Image sizing??
- [BUG] Check for 0-length module files
- [ENHANCEMENT] Additions to checkAllsky.sh
- Error ZWO ASI385MC HOT 13
- System Messages 'capture program stopped' (every morning) HOT 10
- [BUG] ZWO 676MC Not supported during install HOT 1
- [ENHANCEMENT] Allow startrails and keogram images to be stretched
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from allsky.