[Support]: audio OK on 0.13 but not 0.15 #15827
-
Describe the problem you are havingUsing this part of config.yml means that 0.13, hosted on a TrueNAS appliance, gets decent audio and the go2rtc logs simply show However, 0.15 (admittedly via dockge on a different host) sees all sorts of problems when using that same part of the config (with other parts altered from 0.13 to suit 0.15), and in this case the go2rtc logs show Altering 0.15's config.yml to instead say gives me a clean go2rtc log the same as 0.13 Disabling audio on the restream gets rid of the problem, but I would like to discover the likely cause. Is it because the version of go2rtc is different between 0.13 and 0.15 and, if so, how might I start to fault find please? Version0.13.2-6476F8A & 0.15.0-87e7b62 What browser(s) are you using?Version 131.0.6778.204 (Official Build) for Linux Mint (64-bit) Frigate config fileplease see main post for what I hope is the pertinent sectionRelevant Frigate log outputn/aRelevant go2rtc log outputplease see main post for pertinent sectionFFprobe output from your camera0.13 says
[{"return_code":0,"stderr":"","stdout":{"programs":[],"streams":[{"avg_frame_rate":"0/0","codec_long_name":"H.265/HEVC(HighEfficiencyVideoCoding)","height":360,"width":640},{"avg_frame_rate":"0/0","bit_rate":"64000","codec_long_name":"PCMmu-law/G.711mu-law"}]}},{"return_code":0,"stderr":"","stdout":{"programs":[],"streams":[{"avg_frame_rate":"0/0","codec_long_name":"H.265/HEVC(HighEfficiencyVideoCoding)","height":1080,"width":1920},{"avg_frame_rate":"0/0","bit_rate":"64000","codec_long_name":"PCMmu-law/G.711mu-law"}]}}]
0.15 says
[{"return_code":0,"stderr":"","stdout":{"programs":[],"stream_groups":[],"streams":[{"codec_long_name":"H.265 / HEVC (High Efficiency Video Coding)","width":640,"height":360,"avg_frame_rate":"0/0"},{"codec_long_name":"PCM mu-law / G.711 mu-law","avg_frame_rate":"0/0","bit_rate":"64000"}]}},{"return_code":0,"stderr":"","stdout":{"programs":[],"stream_groups":[],"streams":[{"codec_long_name":"H.265 / HEVC (High Efficiency Video Coding)","width":1920,"height":1080,"avg_frame_rate":"16/1"},{"codec_long_name":"PCM mu-law / G.711 mu-law","avg_frame_rate":"0/0","bit_rate":"64000"}]}}]Frigate statsn/aInstall methodDocker Compose docker-compose file or Docker CLI command#version: "3.9"
services:
frigate:
container_name: frigate015
privileged: true # this may not be necessary for all setups
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:0.15.0-beta4
shm_size: 256mb # update for your cameras based on calculation above
devices:
- /dev/apex_0:/dev/apex_0
- /dev/dri/renderD128:/dev/dri/renderD128
volumes:
#host : container
- /etc/localtime:/etc/localtime:ro
- /opt/frigate/config:/config
- type: tmpfs
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- 5000:5000
- 8554:8554 # RTSP feeds
- 8555:8555/tcp # WebRTC over tcp
- 8555:8555/udp # WebRTC over udp
environment:
LIBVA_DRIVER_NAME: i965
PLUS_API_KEY: #####################################
networks: {}Object DetectorCoral Network connectionMixed Camera make and modelFloureon: probably a Hikvision clone Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
0.14+ does have a newer go2rtc version, you could try using |
Beta Was this translation helpful? Give feedback.
-
|
I changed it to say but unfortunately I see go2rtc errors which is interesting because it is only three out of the eight identical (supposedly) cameras which report problems: lower steps So I changed back to opus and it's the same three problematic cameras. I will leave out their |
Beta Was this translation helpful? Give feedback.
-
|
update: using the Frigate UI in 0.13 and 0.15 to do I suppose that 0.13's version of ffprobe deals with problems differently from the version in 0.14+ but in any case, the problem clearly lies with my cameras so please close this post. I'll carry on messing around to see if I can find differences (e.g. in camera f/w via my NVR's UI for example). |
Beta Was this translation helpful? Give feedback.
update: using the Frigate UI in 0.13 and 0.15 to do
ffprobe, I can see that the problematic cameras do not have any audio codecs reported, whereas the cameras with working audio all say "Codec: PCM mu-law / G.711 mu-law"I suppose that 0.13's version of ffprobe deals with problems differently from the version in 0.14+ but in any case, the problem clearly lies with my cameras so please close this post. I'll carry on messing around to see if I can find differences (e.g. in camera f/w via my NVR's UI for example).