Reply to thread

Message

<blockquote data-quote="Scythe42" data-source="post: 511123" data-attributes="member: 95833">This is the only constant I left in as it is a workaround. If fps information cannot be detected, use 40ms. Therefore it should be safe to use m_rtTimePerFrame as a base for everything. I don't have ts files to test though and all my files provide frame rate information.I thought about this is well like buffering the first second of playback. Probably a value that could adjust itself during playback if too many frames are received late from the mixer. Mixer quality control notifications didn't have any impact in my tests on this. Probably because the filters/codecs don't support notifications themself or don't send them out to the mixer. But not something I'd see happening for 1.1.0 as they are more important issues that need to taken care of to get at least an RC out. I'm a big supporter of stability before new features unless the feature are really enhancing the user experience or a simply overdue compared to other solutions.</blockquote>

[QUOTE="Scythe42, post: 511123, member: 95833"] This is the only constant I left in as it is a workaround. If fps information cannot be detected, use 40ms. Therefore it should be safe to use m_rtTimePerFrame as a base for everything. I don't have ts files to test though and all my files provide frame rate information. I thought about this is well like buffering the first second of playback. Probably a value that could adjust itself during playback if too many frames are received late from the mixer. Mixer quality control notifications didn't have any impact in my tests on this. Probably because the filters/codecs don't support notifications themself or don't send them out to the mixer. But not something I'd see happening for 1.1.0 as they are more important issues that need to taken care of to get at least an RC out. I'm a big supporter of stability before new features unless the feature are really enhancing the user experience or a simply overdue compared to other solutions. [/QUOTE]

Verification