3ivx Splitter Breaks FFDShow support for QuickTime

[Blight]

Just a note to either Milan or the 3ivx people.

Once installed, the v4.5 version of the splitter won't connect anymore with ffdshow. The 4.04 worked with quite a few Sorenson v1/v3 clips.

[shitowax]

I've just (re)tested the sorenson matrix trailer with a fresh 3ivx 4.5 install and, exactly like in the 4.04 version, you just have to set the "allow unsupported decoder" check box in the directshow property page, and that simply works. So, either your ffdshow version is broken or your forgot to set the checkbox. 4.5 doesn't break anything, it's the opposite: it fixes tons of bugs (really).

Originally posted by Blight
Just a note to either Milan or the 3ivx people.

Once installed, the v4.5 version of the splitter won't connect anymore with ffdshow. The 4.04 worked with quite a few Sorenson v1/v3 clips.

[SeeMoreDigital]

I would like to download the '3ivx for QuickTime' component. The GUI looks great!

Is it available?

Cheers

[shitowax]

Yeah, nice GUI can be done with MacOSX ... ;)
Seriously, the Quicktime component is in the 4.5 Windows package with the VfW codec and all the DirectShow filters. The 3ivx win QT component shares almost all its resources with the VfW codec ;)

[SeeMoreDigital]

Originally posted by shitowax
Yeah, nice GUI can be done with MacOSX ... ;)
Seriously, the Quicktime component is in the 4.5 Windows package with the VfW codec and all the DirectShow filters. The 3ivx win QT component shares almost all its resources with the VfW codec ;) Oh well, never mind!

I was hoping that your codec might have interfaced somehow with QuickTimePro when it was opened.

I quite like QuickTimePro because it's able to generate Mpeg4/AAC (MP4) encodes. However, you don't get very much in the way of options. 2pass being the main one!

Your GUI showed many useful options. Shame it's only available to MAC users!

Cheers anyway.

[shitowax]

Our windows package is only 1 MB but it contains a lot of interesting things :
- the 3ivx component for quicktime on Windows that let you decode and encode using the MPEG-4 compliant 3ivx core from quicktime(pro) or any application using quicktime on Windows (premiere for example).
- the well-known VfW codec
- the DirectShow filter suite ( AAC encoder, (HE)AAC decoder, mp4 splitter, mp4 muxer and video decoder).

To be clear, the 3ivx core has exactly the same quality on Windows and on Mac, only vectorized functions are different (MMX/SSE/SSE2 on Windows and Altivec on the Mac). The quicktime frontends are a bit different (http://www.3ivx.com/support/mac/encoding/quicktime.html#advanced):
- the mac qt frontend let you deactivate NVop coding because the quicktime hinter is buggy and cannot hint NVop. All the windows frontends use NVop coding. If you want to use the quicktime hinter on windows, just use the 3ivx mp4 muxer before with the NVop annihilation activated.
- the mac qt frontend let you produce "pure MP4 stream". As those stream cannot be stored in .avi, the windows frontend won't let you produce "pure MP4 streams" directly. But you will obtain them if you use our muxer to produce .mp4 files ...

So, basically, Windows users have no reason to be jalous of the Mac ones. Indeed it's the opposite, we have a lot of Mac users jalous of the Windows ones because 3ivx on Windows is much more powerful than on Mac ... =)

[Blight]

shitowax:
Wasn't aware you had to enable that checkbox, I didn't enable it in the previous version.

Also, any idea why the frame rate is reported so high?

[Stux]

Originally posted by Blight
shitowax:
Wasn't aware you had to enable that checkbox, I didn't enable it in the previous version.


You must've, or its because the priority was raised on the splitter in 4.5, mainly to overcome problems where MS's old splitter would override the 3ivx splitter


Also, any idea why the frame rate is reported so high?

There is a funny issue which happens when the audio is neither MP4 nor AAC, its possible this could result in too fast framerates (as well as static coming out of speakers)

Other quicktime clips often use QDesign audio (which I think can not be decoded in the DS architecture anywho)

[Stux]

Regarding 3ivx<->quicktime interaction

you can encode with 3ivx into a qt mov using qt

you can then use plain qt to play those movs (no need for 3ivx)

you can also use qt to pass-through the mov video into an mp4

you can also use the 3ivx DS Filter Suite to play these movs, convert them to MP4, or play the MP4s, etc etc etc

you can encode 3ivx avis, and play them with QT+3ivx on mac or windows, etc

if you convert the 3ivx.avis to mp4 with the 3ivx DS Filters, then plain qt can play them, as well as many other MP4 decoders

etc

3ivx for Mac = 3ivx for QT for Mac OS

3ivx for Windows = 3ivx for QT for Windows + 3ivx for VfW + 3ivx DirectShow Filter Suite

[Blight]

Stux:
I meant the framerate reported by DirectShow to be about 1000000fps. Doesn't effect playback, just wondering why it was this way. Perhaps it's FFDShow.

[Atamido]

1,000,000 fps is about 1,000ns per frame. I think that the resolution allowed by DirectShow is only 100ns. That is a strange number indeed. (Matroska uses 1ns because it was a nice number)

[Stux]

Originally posted by Blight
Stux:
I meant the framerate reported by DirectShow to be about 1000000fps. Doesn't effect playback, just wondering why it was this way. Perhaps it's FFDShow.

Another possibility is that the broken frame-based seeking which snuck into the 4.5 release seems to do that too