From a56c7688eae02b1313e5156cc332dfcfeebe71c0 Mon Sep 17 00:00:00 2001 From: Rich Shumaker Date: Thu, 18 Jan 2018 19:33:26 -0800 Subject: [PATCH] Some sizes just don't work - some cause immediate errors I took out the immediate errors from this list. I also lowered 720p to 60fps as that worked and 90 fps would not record. This is on a Pi Zero which is an overclocked original CPU/GPUI am not sure how 1640 X 1232 works as it is over the 1080(V) that the encoder can handle. I wonder how high you can go. I tried several 1920 X 1400ish(4:3) sizes and none worked that I tried. Also I have lowered my recording from 30 to 24 as I do film recording and have found the extra savings in frames helps to keep from glitching. --- www/uPresetsN-IMX219.html | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/www/uPresetsN-IMX219.html b/www/uPresetsN-IMX219.html index 00735496..06af07de 100644 --- a/www/uPresetsN-IMX219.html +++ b/www/uPresetsN-IMX219.html @@ -1,15 +1,17 @@ - - + - # Version 2.x (IMX219) # H264 Encoder Limits are 1920 X 1080 based on the GPU - Exploring Higher Frame Rate options and how that might be recordable - They just don't record video and the button does not work. +# Automatic Error occurs when you set capture resolutions above 1920(H) or larger then 1080(V) - Removed +# Error MSG - "Error in RaspiMJPEG: Restart RaspiMJPEG (./RPi_CAm_Web_Interface_Installer.sh start) or the whole RPi." +# How does 1640 X 1232 work? It does I just don't know how - How high could you go as I thought 1080(V) was the max for the GPU encode +#720P changed to 60fps as that recorded - 90fps did not work - This may require a RasPi 3 - I am using the original CPU/GPU Combo # Mode Size Aspect Ratio Frame rates FOV Binning # 0 automatic selection