BFrame Decoder Lag

Vax · Post by **Vax** » Sat Oct 11, 2008 8:24 pm

I dont know how to..thats the problem X_X

Vax · Post by **Vax** » Sat Oct 11, 2008 10:29 pm

I switched programs, now its working.

JaddziaDax · Post by **JaddziaDax** » Sat Oct 11, 2008 11:11 pm

you don't know how to make clips? or like cut it off like in editing?

Vax · Post by **Vax** » Sun Oct 12, 2008 8:03 am

JaddziaDax wrote:you don't know how to make clips? or like cut it off like in editing?

Lol, first you tell me to use FFdshow, i know how to cut clips but how will that work? Doesnt really matter anymore since its working now.

JaddziaDax · Post by **JaddziaDax** » Sun Oct 12, 2008 10:01 am

i didn't tell you to use FFDShow i just summarized the method of what you need to do to get it to work without making your computer crash... then told you that it would be easier to just clip around it.. the bframe decoder lag is just one frame, its easy to snip it off of the beginning of your clip

Vax · Post by **Vax** » Sun Oct 12, 2008 11:33 am

Alright

Qyot27 · Post by **Qyot27** » Mon Oct 13, 2008 3:54 pm

I should note here that I do believe a lot of the problems/conflicts ffdshow had with other codecs have been resolved - the original source of those types of problems were commonly due to codec packs including ffdshow along with a crapload of other decoding filters, some of which were redundant amongst themselves even, so there was a steaming ball of conflicts waiting to happen.

ffdshow now includes a section in its configuration to disable its use in certain applications (explorer.exe is one of them; if that means what I think it does, it means Explorer won't crash anymore).

The reason I found it important to mention is that if you plan on doing any sort of encoding with XviD using VirtualDub, then you have to have both it and ffdshow installed. I can attest that I've never had a problem with libavcodec (ffdshow's decoding core; it's the same one that VLC and mplayer use) decoding XviD while the main VFW/DS version of XviD was also installed, but then again I know setups can differ. To be absolutely safe, you could just encode using xvid_encraw, but that requires you to either use MeGUI to interface with it or stick to command-line encoding - there could be other GUIs that can use it, but I don't bother to find out about them since I know MeGUI works.

Vax · Post by **Vax** » Tue Oct 14, 2008 8:29 pm

Qyot27 wrote:I should note here that I do believe a lot of the problems/conflicts ffdshow had with other codecs have been resolved - the original source of those types of problems were commonly due to codec packs including ffdshow along with a crapload of other decoding filters, some of which were redundant amongst themselves even, so there was a steaming ball of conflicts waiting to happen.

ffdshow now includes a section in its configuration to disable its use in certain applications (explorer.exe is one of them; if that means what I think it does, it means Explorer won't crash anymore).

The reason I found it important to mention is that if you plan on doing any sort of encoding with XviD using VirtualDub, then you have to have both it and ffdshow installed. I can attest that I've never had a problem with libavcodec (ffdshow's decoding core; it's the same one that VLC and mplayer use) decoding XviD while the main VFW/DS version of XviD was also installed, but then again I know setups can differ. To be absolutely safe, you could just encode using xvid_encraw, but that requires you to either use MeGUI to interface with it or stick to command-line encoding - there could be other GUIs that can use it, but I don't bother to find out about them since I know MeGUI works.

Wow thanks for telling me all of this