I have feedback from the developer.
For those files with TrueHD, can you please retest with some other audio codec?
The root cause was actually the audio codec. I was in error.
If you can confirm the problem does not exist when not using the EAE codec (videoss with AAC, AC-3)
then the solution to this issue has been identified and solved. Release in a ‘hot fix’ is imminent .
If not, then we need to dig deeper and find it.
I will attempt to convert the audio track on my sample file and will get back to you on whether it actually worked!
I have a movie that has TrueHD and AC3 5.1. I will run a test with each audio track and report back.
Just finished up manually converting the TrueHD audio to AAC and remuxing. I’m running my conversion test now.
Here are my results… I think you are correct @ChuckPa it is related to TrueHD… Although I have seen it recently with other types of streams because it happens even when there is no one playing TrueHD files. I will keep an eye on what types they are to see if I can correlate something they have in common.
That is very encouraging.
EDIT: I’ve done some reading, This is the EAE codec. DTS, TrueHD, etc. (The heavily licensed codecs)
In my test, I used ffmpeg to transcode the TrueHD audio into AC3 and it appears that that did the trick! I’m holding steady at about 1GB used.
Speaking of this hotfix, how long do you estimate this to come to production?
I read the in-process notes and the candidate release notes.
It’s been marked as ASAP and is already in QA hands. I’d say extremely soon. I don’t know if testing has already begun or not. I do know I’ve not been asked to participate (yet).
There are three (3) fixes in this hot fix. Of the three, two are easy to test & regression test. I have no visibility into the third given what it corrects but presume Engineering already has that in the other attached process notes.
Ah that would make sense. I will look next time I see high mem usage to see if someone is transcoding one of those codecs.
@ChuckPa I did not see a fix for this in the release notes… I assume it maybe in the next one?
Sorry for the delay in replying. I had to find out what happened.
Before I start, TL;DR, The corection didn’t get included.
A mistake was made and now having a post mortem review of what happened and how to prevent it in the future.
Thanks for the reply. Hopefully the next one will be out soon and will have the fix.
It will be in the next release. Of that much I am certain 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
