diagnosing the cause of "video/audio resync frames removed"

#21
Well, I guess that's that then. As disappointing as it is for me, I can totally understand optimisation for sources containing bursts of corruption being a low or zero priority scenario. With that said, I still think the design choice to decode the entire source to frame level in the previously described conditions is odd. That's probably baked into the architecture to the point that it couldn't be changed without a radical redesign.
 

Dan203

Senior Developer
Staff member
#22
It's just how VRD works. Basically any time you open and save a file in VRD it's demuxed to base elements and remuxed on output.
 
#23
I'm running Quickstream Fix on most of my recordings and the log indicates where the removed video resync frames were located, but I get no indication of where the removed audio recync frames are located. Is there anyway to find out where the audio frames were removed?
 

Dan203

Senior Developer
Staff member
#24
No. We really don't keep this information anywhere. With audio so many frames can be removed that we don't even log every one. You'll see in the log that when a large number are removed it says something like "...488 similar frames" or something like that, rather than having a line for every one.
 
Top