Quicktime Import Filter - Test Version, Still Buggy - 2006-01-09

[dr.schanker]

FFVideoSource should work, i just tested a Photo-JPEG .mov with a somewhat recent version of ffms2.dll (May 2012) under WinXP.

Alternatively you could remux your Photo-JPEG .mov's to another container (e.g. .avi) with ffmpeg, use the switches '-vcodec copy' and '-acodec copy' to keep the original streams (no reencoding). This will give you an .avi which can easily be decoded by a MJPEG VfW decoder, e.g. 'ffdshow VfW'.

[stoffal]

Thank you kolak and dr.schanker !
I will play around with a script to edit the 700 Quicktime files as mentioned by kolak. If this does not work, I will try out vvvideosource again. Good workarounds, thank you.

[tateu]

Use mode=2 or mode=3. And if it is avc/h264, definitely use FFMpegSource instead.

[stoffal]

Thank you , Tateu. "mode=2" helped and opens the video in its real size. Great help !

[buck-tick]

Hi tateu!

I noticed the QT plugin for VDub doesn't load multi track audio like the Plugin for AviSynth does. I have a 8 channel ProRes I use to test with and it loads as mono in VDub with latest QT plugin from your site.

<3 your AviSynth plugin

Man this would make my life easier in trying to see waveform at a glance without having to open up a heavy program like FCP or Premiere

[tateu]

Yeah, the Quicktime version has never really been updated like the AviSynth version.

I know there are probably lots of people who use VirtualDub but do not use AviSynth...I am not one of them. I also use a custom VirtualDub which automatically writes a temp AviSynth script when I open a Quicktime movie and I also use ASynther through the SendTo menu to quickly get my AviSynth scripts started...I just don't have a personal reason to keep the VirtualDub plugin updated since I don't ever use it so it's hard to get motivated to work on it.

And to be honest, they both need a complete rewrite to clean up the supreme mess they have become...Again, it's hard to get motivated to do it.

[buck-tick]

Originally Posted by tateu

Yeah, the Quicktime version has never really been updated like the AviSynth version.

I know there are probably lots of people who use VirtualDub but do not use AviSynth...I am not one of them. I also use a custom VirtualDub which automatically writes a temp AviSynth script when I open a Quicktime movie and I also use ASynther through the SendTo menu to quickly get my AviSynth scripts started...I just don't have a personal reason to keep the VirtualDub plugin updated since I don't ever use it so it's hard to get motivated to work on it.

And to be honest, they both need a complete rewrite to clean up the supreme mess they have become...Again, it's hard to get motivated to do it.

Np.

Thanks for the plugins as they are.

[hanfrunz]

Originally Posted by tateu

And to be honest, they both need a complete rewrite to clean up the supreme mess they have become...Again, it's hard to get motivated to do it.

Set up some kind of a donation or flattr button, maybe we can get you motivated
If you visit IBC in Amsterdam this year i'll get you some beers, too.

regards,
hanf "using qtinput everyday" runz

[kolak]

tateu can you port QTinput to vapoursynth and add 10bit+ color spaces (v210, b64a, v216 etc)?

[colinhunt]

tateu, what would it take to get you motivated about developing qtinput further? Perhaps a sizable donation?

[kolak]

+1

[astronob]

Yes, please add 10bit+ color spaces to QTinput. I'd like that too.

[LigH]

I doubt this filter will be developed any further. L-SMASH Works (LSMASHVideoSource supports the index chunk in MOV files, LwLibavVideoSource creates an own index) should have made it more or less obsolete.