-
Notifications
You must be signed in to change notification settings - Fork 111
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
Audio decoding errors / Muxing buffer overflow? #175
Comments
Just found a small test clip online: https://we.tl/Ufd0JVRXec |
trueHD in mkvなどで、ptsが数フレームに1回しかなく、それ以外はAV_NOPTS_VALUEの場合がある。 このフレームを落としてしまいデコードできなくなっていたのを修正。
Thank you for the information and also providing a sample video which reproduces the issue. Thanks to the sample, I was able to fix this issue. It was caused by timestamp pattern which I did not expect. (but not related to max_muxing_queue_size.) NVEnc 4.57 should solve this problem. |
Seems to work fine at first. But encoding ca. two hour long 1080p content with truehd tracks results in system memory usage which climbs up to 20GB and during the encode the performance of it continuously drops. See the encodes below with the same basic command line as above: With TrueHD:
With DTS:
I think there is still something broken. #177 also suggests this. Btw: System memory usage also rises with DTS tracks during the encode but not nearly as fast. |
I've found memory leak in audio processing which seems to be causing the continuous rise in system memory usage, I'll fix it in next release. |
AVFrame構造体が残ってしまうことで、パケット数の多いtrueHDなどでメモリリークが顕著に見られていた。 av_frame_free ... AVFrame構造体自体も解放。 av_frame_unref ... bufferの参照カウントを減算するのみ。
NVEnc 4.58 should fix the memory leak in audio processing, below shows the virtual mem usage of NVEncC when handling trueHD audio. The mem usage of NVEnc 4.57 continuously rises, but the mem usage of NVEnc 4.58 keeps stable. |
Thank you. Looks good. No excessive memory usage usage or performance drops on a clip with 2 TrueHD tracks. Currently I cannot see reason to keep this open. Closed. |
With some files I immediately receive audio decoding errors.
Step 1: Simple conversion with NVEncC
Command line: NVEncC64 --avsw -i "infile.mkv" --audio-codec aac -o "outfile.mkv"
Errors:
Step 2: Testing decoding of the audio track with ffmpeg
Command line: ffmpeg -loglevel error -i "infile.mkv" -map 0:2 -f null -
Errors: no errors
Step 3: Testing a simple conversion with ffmpeg
Command line: ffmpeg -loglevel error -i "infile.mkv" -map 0:v -map 0:2 -f null -
Errors:
Step 4: Adding -max_muxing_queue_size 1024
Command line: ffmpeg -loglevel error -i "infile.mkv" -map 0:v -map 0:2 -max_muxing_queue_size 1024 -f null -
Errors: no errors
Question: Is it possible that NVEncC also suffers from ffmpeg bug #6375 (https://trac.ffmpeg.org/ticket/6375) altough it outputs different errors? And if so can you work around it by making "-max_muxing_queue_size" available as an option or setting it internally to a safe value?
The text was updated successfully, but these errors were encountered: