ExKode Forum

Dxtory => Help & Support => Topic started by: Zalerinian on January 27, 2014, 07:16:14 am

Title: AVIMux Builder.Init error 0x8000FFFF
Post by: Zalerinian on January 27, 2014, 07:16:14 am

When trying to use AVIMux to make all the audistreams in my recorded file into one, I get a Builder.Init error if I choose a video codec. It doesn't matter which one I choose, they all have this issue. I am useing Version 2.0.125

Environment Data (http://pastebin.com/LRr91BwH)
Error Screenshot (http://i.imgur.com/4ozdurj.png)

Is there any way I'll be able to fix this, or is it a software issue that requires an update?

Title: Re: AVIMux Builder.Init error 0x8000FFFF
Post by: ExKoder on January 27, 2014, 12:59:42 pm

Currently, cause is unknown.

Title: Re: AVIMux Builder.Init error 0x8000FFFF
Post by: Zalerinian on January 28, 2014, 05:29:21 am

I should also note (silly me) that this occurred on Windows 8 and 8.1 machines, no compatibility mode selected. I have not tested with compatibility mode or with anything other than 8/8.1, so it's possible it's only on those two Operating Systems.

Title: Re: AVIMux Builder.Init error 0x8000FFFF
Post by: needhelpnoww on February 05, 2014, 02:14:05 pm

win8 is fine

Title: Re: AVIMux Builder.Init error 0x8000FFFF
Post by: Zalerinian on March 08, 2014, 09:28:41 am

Just a little update:

It seems this only occurs when trying to mux video files that are recorded with the x264vfw codec. When I tested by recording from the DXTory codec and muxing it into x264, it worked fine. I don't know if this entirely rules out the issue being DXTory's fault or not, but at least there's a workaround.

Title: Re: AVIMux Builder.Init error 0x8000FFFF
Post by: iNSANiTY on March 08, 2014, 08:41:35 pm

Zalerinian,

I see your using Windows 8 and 8.1, assuming these are 64bit computers could you test something for me? Read my post under the support section about DirectShow Output and let me know if you have the same issue as me. It will be appreciated a lot :D

As for your problem, I think it does have something to do with the codec, but knowing if dxtory is the cause of the codec malfunction is another story. Glad you found a work around though.  8)