-
Notifications
You must be signed in to change notification settings - Fork 22
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
set video_callback bitrate #26
Comments
I don't know. |
ah, yes the api, I understand. comparisons with the official rtsp (1000kbps avg) and the libcallback (200kpbs avg) the difference is remarkable. |
How do you measure that bitrate? |
@mnakada i have discovered you can adjust the bitrate using:
the api can reset these changes, be aware.
the first one is MAX BITRATE the quality is much improved. |
Is the video bitrate mentioned here refers to the video saving to SD-card? |
i am not sure if it related to SD card, you should try it |
Thanks for the information. |
@gtxaspec Is it possible to make the audio better quality? |
@thematrixdev not sure, from what I have discovered, the debug tools only allow us to adjust some of the video parameters. perhaps @mnakada has some further insight or knowledge from his experience. |
@gtxaspec @thematrixdev |
@mnakada i understand, perhaps there are differences between the atomcam and wyze. Would you share the output of |
@thematrixdev maybe it could be related to the noise suppression of the T31 SDK... the documentation states:
checking
i'm not sure how to check what it is set to |
@gtxaspec The output of impdbg -enc_info is as follows.
|
ah, i can see the default settings are simliar: AtomCam:
Wyze:
running the following increases quality from the rtsp stream significantly for:
you can run |
The setting values have changed, but the RTSP bitrate is still the same.
Maybe AtomCam has some other setting. |
closing pending more research! |
@mnakada, are you familiar with a way to set the bitrate (kbps) for the video hooked by video_callback? perhaps it could be adjusted in the source.
The text was updated successfully, but these errors were encountered: