Reply to thread

Message

<blockquote data-quote="CCob" data-source="post: 376725" data-attributes="member: 84421">What would happen if you removed the audio graph from the chain just for forwarding/rewinding purposes and the re-added it when you hit play, would that work, or will it incur a substantial delay?Also does the audio render in MP use a separate IReferenceClock for the audio chain than the rest of the directshow graph?&nbsp; If not, perhaps you could implement a custom IReferenceClock for the audio chain and offset the IReferenceClock when fast forwarding/rewinding (but mute the audio), which would essentially trick the audio to move forwards/backwards.&nbsp; Just an idea.Or another option when doing to high speed fwd/rwd would be to seek to the next/previous key frames instead of using SetRate, would that work?Or I guess the other solution would be to write a custom audio renderer which does support more than 2x and not use the default renderer which is limited to 2x.</blockquote>

[QUOTE="CCob, post: 376725, member: 84421"] What would happen if you removed the audio graph from the chain just for forwarding/rewinding purposes and the re-added it when you hit play, would that work, or will it incur a substantial delay? Also does the audio render in MP use a separate IReferenceClock for the audio chain than the rest of the directshow graph? If not, perhaps you could implement a custom IReferenceClock for the audio chain and offset the IReferenceClock when fast forwarding/rewinding (but mute the audio), which would essentially trick the audio to move forwards/backwards. Just an idea. Or another option when doing to high speed fwd/rwd would be to seek to the next/previous key frames instead of using SetRate, would that work? Or I guess the other solution would be to write a custom audio renderer which does support more than 2x and not use the default renderer which is limited to 2x. [/QUOTE]

Verification