Skip to content

[HW Accel Support]: ffmpeg high cpu caused by "-c:a aac" in record stream #11498

Discussion options

You must be logged in to vote

To summarize, aac was being re-encoded due to different profiles, the solution here is one of two things.

  1. If you are able to change the source encoding (I'm using a wyze cam with wz_mini_hacks, so go2rtc encoding parameters are able to be changed), change the encoding profile to 'aac_low' and try to make sure the bitrate is 128k
    This gives the most compatibility, as some clients cannot play back aac-he\

  2. Set the frigate ffmpeg 'record' output arg to preset-record-generic-audio-copy profile to avoid re-encoding the audio track.
    This will work, but certain players (EG android chrome) cannot play the resulting stream

The camera was exporting an HE-AAC stream, which was being re-encoded …

Replies: 2 comments 4 replies

Comment options

NickM-27
May 23, 2024
Collaborator Sponsor

You must be logged in to vote
1 reply
@gwmullin
Comment options

Comment options

You must be logged in to vote
3 replies
@MarcA711
Comment options

@gwmullin
Comment options

@MarcA711
Comment options

Answer selected by gwmullin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment