[James m. Sheats iii]

From everything I’ve read I have to agree with you that there are definitely a variety of Motion Jpeg codecs out there. I originally thought I was on to something when I found the enable legacy codecs switch in Quicktime and it opened up the option to either MJPG A or MJPG B but of course they didn’t output for me in .AVI format. There is also MJPG 2000, Morgan MJPG on the list goes on. Then I got turned onto G-spot and saw just how many MJPG codecs there seemed to be on my system though most were apparently for decompression and didn’t include compression functionality.

Finally I found that ffdshow would work in MJPG mode, but without audio – I believe this is because its a video only codec but I’m a noobie so don’t hold me to that.

I really appreciate all your help and input — I am defintely learning alot about codecs as I go along.

[James m. Sheats iii]

These are the details on the codec that works from Accusoft, Pegasus Imaging PICVideo setup.

– – Type VFW
– – Function Decoder
DSH 4CC MJPG
DSH Friendly Name PICVideo M-JPEG 4 32-bit VfW Codec
DSH DirectShow CLSID CLSID_AVIDec {CF49D4E0-1115-11CE-B03A-0020AF0BA770}
REG Driver File C:\PROGRA~2\COMMON~1\PEGASU~1\pvmjpg40.dll
REG Merit 0x00200000
VFW Name PVMJPG40
VFW Description PICVideo M-JPEG 4 32-bit VfW Codec

This one was pre-existing on my system which meant I could play in WMP but it didn’t allow for import into AE, Prem Pro etc.

MJPG Motion JPEG – It lists no vendor or other details, though the info below might be the more complete info

– – Type DSH
– – Function Decoder
DSH 4CC MJPG
DSH Friendly Name MJPEG Decompressor
DSH DirectShow CLSID CLSID_MjpegDec {301056D0-6DFF-11D2-9EEB-006008039E37}
FIL File Description DirectShow Runtime.
FIL Company Name Microsoft Corporation
FIL File Version 6.6.6000.16386 (vista_rtm.061101-2205)
FIL Internal Name Quartz.dll
FIL Legal Copyright © Microsoft Corporation. All rights reserved.
FIL Original Filename Quartz.dll.mui
FIL Product Name Microsoft® Windows® Operating System
FIL Product Version 6.6.6000.16386
REG Driver File quartz.dll
REG Merit 0x00600000

I was able to choose this codec to output to the DPF (I had to select MJPG in the settings under configure options) and this works but without audio 🙁

– – Type DSH
– – Function Decoder
DSH 4CC MPEG2_VIDEO
DSH Friendly Name ffdshow Video Decoder
DSH DirectShow CLSID {04FE9017-F873-410E-871E-AB91661A4EF7}
FIL File Description DirectShow and VFW video and audio decoding/encoding/processing filter
FIL File Version 1.0.7.3095
FIL Internal Name ffdshow
FIL Legal Copyright Copyright © 2002-2008
FIL Original Filename ffdshow.ax
FIL Product Name ffdshow
FIL Product Version 1.0.7.3095
FIL Legal Trademarks GNU GPL
REG Driver File C:\Program Files (x86)\K-Lite Codec Pack\ffdshow\ffdshow.ax
REG Merit 0xff800001

Seems I am getting closer…

[James m. Sheats iii]

I understand what you are saying, theoretically AE should import these .AVI files from my digital camera, but it will not. I get an error telling me that the file is damaged or in an unsupported format. I am thinking it has to do with the odd 20fps frame rate that my camera puts out. Just to be clear I am talking about an inexpensive point and shoot model that happens to record low quality 320×240 videos as well as take still shots. I know the codec is installed because the videos play in WMP fine, just cannot import into AE or Premiere Pro etc.

I downloaded a trial from Accusoft of a codec called PICVideo 4 and now I can drag and drop into AE. Unfortunately the license is a little expensive — $179 for the 64bit compress/decompress version which is justifiable expense for me to play around with getting my videos onto my DPF after editing.

At least I know that it is possible now and that the problem is codec related. I have to believe that I have the appropriate codec already (since I can view the videos inside of WMP etc) and that it is just not registered or recognized within AE. Possibly it is just the decompress version for viewing and that is why I cannot ouput using the codec.

[James m. Sheats iii]

Thanks — I had a feeling my workflow was flawed or my understanding of the different types of markers at least.