I think some of these problems may have been reported already, but just in case they haven't, here they are: 1)Nic's latest decoder does not play back B-frames correctly on my computer. Instead of playing the frames chronologically, it jumps back and forth. I guess it's failing to reorder them correctly...? 2)Koepi, I downloaded XviD-12102002-1.exe from your site today and it doesn't have Nic's latest decoder. Found out the hard way when Nic's build decoded B-frames and yours didn't. 3)I have WMP 6.4 set to restart from the beginning once the end of the video is reached. However, when I'm decoding a video encoded with B-frames using Nic's decoder, after the video plays through once, only the last frame of the video is shown when WMP 6.4 goes to play it again. It works fine if the video is not encoded with B-frames. 4)This has probably been reported already: When using ffdshow to decode B-frames, at the bottom of the video are grey blocks stick out from the bottom edge. If no one has reported this yet, I'll be glad to post a screenshot. *SOLVED* Using latest ffdshow build. 5)Also probably reported already: When I open an XviD-encoded video with B-frames in VirtualDub, it says at the bottom: "Error decompressing video frame 1: An unknown error occurred (may be corrupt data). (error code -100)" This is with using Nic's latest decoder. I think I left out a few. I'll keep testing for more problems. B-frames look very nice though. :)
6)Using XviD.dll to decode B-frames causes WMP 6.4 to crash when I try to exit. 7)If I use ffdshow with "Decode with XviD", WMP 6.4 crashes when trying to play B-frames. Some of these problems may be one-time glitches. I'm going to test them again.
Hi gldblade, old pal! 1)correct. Will be solved, it's Ishibaar's baby. 2)so what? It's a sneak preview and Koepi has (rightfully so, it seems) worries about just giving it out to anybody 3)again, the playback-support is in its early stages 4)solved 5)no dshow-filter is used for this. VDub doesn't support B-frames properly, only support for DX5-style (1) B-frames was hacked in. XviD is bleeding' cutting edge;) 6)don't know what causes this 7)AFAIK it's an ffdshow error in some of the later versions that occurs with or without B-frames Please remember that this is NOT even a remotely stable release, expect errors and consider only the graver ones for report and make sure they haven't been reported, yet, and that they really are B-frames-related. Otherwise I fear we'll get flooded with so many reports, it will be hard to read all of them. Right now, I tend to change my mind and agree with Koepi that B-frame enabled builds shouldn't be made publicly available, anymore, even if this means I won't get one, either. I hope you enjoy the new features in spite of the problems. All best wishes, Tee
I refreshed my ie,even cleared history cache.Strange thing stills shows 11.But yhe build I downloades is 278kb whereas 11's build was 297kb,so guess it must be the new.I cant install it to be sure cause I am in a middle of encoding...
Easiest way to check is, does it decode bframes? :D lol. Im pretty sure it should be right, sometimes ive had it cache on me (but its almost like its not my computer/software, but my ISP or something). Cheers, -Nic
Users
Wejście
RE: B-frame woes...
