-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically set resolution #14
Comments
this has been open for ages - and i think it would be a really useful feature, so i've set a small bounty to hopefully get the ball rolling. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bounty on this is now $195 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bountysource is going to take the money in this bounty on July 1st unless the funds are redirected. Alternatively I can close this out, collect the bounty and ZoneMinder will hold the funds until it is properly closed. |
If the resolution field is empty or zero, let zmc auto-detect the resolution and store it in the shared memory.
This is possible by using epadding1 32bit padding variable by splitting it into two unsigned 16bit variables. This will keep the shared memory size and layout backwards compatible with older versions.
This is fairly easy to do for most cases. For remote streams such as http(mjpeg), ffmpeg or rtsp, we get the resolution after decompressing the first frame. For local cameras, we can simply attempt to use highest resolution supported by the device.
The only problem is that memory allocation happens first, so we have to allocate lots of memory to support the highest possible resolution defined in src/config.h. Hopefully we will find a way around this approach.
This is an important another step in the direction to make ZM quicker and simpler to configure. Adding a new monitor should not take more than a few minutes.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: