Skip to content
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

Windows - Setting Audio = True causes high cpu #409

Open
t3therdev opened this issue Nov 25, 2023 · 2 comments
Open

Windows - Setting Audio = True causes high cpu #409

t3therdev opened this issue Nov 25, 2023 · 2 comments

Comments

@t3therdev
Copy link

When using rtsptoweb built on windows 10/11, it works fine and uses minimal cpu.

When enabling audio (setting audio=true) and using mse , the cpu goes to 45-50% for a single stream. audio works but cpu goes very high.

the source stream video/audio format is

Duration: N/A, start: 0.014188, bitrate: N/A
Stream #0:0: Video: h264 (Main), yuvj420p(pc, smpte170m/smpte170m/bt709, progressive), 704x480 [SAR 10:11 DAR 4:3], 29.97 fps, 29.97 tbr, 90k tbn
  Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp
@t3therdev
Copy link
Author

t3therdev commented Nov 25, 2023

Seems to be some interaction between the source stream (if it has audio or not) and the setting in RTSPtoweb. Sometime a restart helps to reduce cpu back to normal.

If the source rtsp stream has an aac audio track, it also uses higher cpu, even if audio is not enabled. enabling audio on some streams seems to have lower cpu than not enabling it. setting audio = false when stream has audio puts cpu usage to 43%. Setting to true actually has it lower.

Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: h264 (Baseline), yuv420p(progressive), 640x436 [SAR 1:1 DAR 160:109], 29 fps, 29 tbr, 90k tbn Stream #0:1: Audio: aac (LC), 44100 Hz, stereo, fltp

@deepch
Copy link
Owner

deepch commented Dec 11, 2023

create cpu profile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants