Mjpeg AVI woes

I am trying to import Matrox MJPEG AVIs into Premiere Pro CS5. I have the codecs installed on the computer (confirmed through G-Spot), but Premiere does not recognize them. It lists them as an unsupported format.
Any hints on what I need to do? I expect its a reg edit I need, but without some guidance on exactly where to look, I am more than a bit lost. All of our file video is in this format, as well as video we capture and use on a daily basis - so not having it is not an option. Needless to say this is very frustrating.

Do you have the more recent 64-bit versions of the codecs installed? Since CS5 is a 64-bit application, the codecs must likewise be 64-bit--even if the files were originally encoded on a 32-bit system.
I believe that this package has both the 32-bit and 64-bit versions. Do note that a few of us have had issues with stability and other broken features once these codecs were installed.

Similar Messages

Premiere CC 2014 MJPEG AVI displays incorrectly

I'm running Premiere CS6 and CC 2014 on Windows 7. In a project last opened on a Mac running CC 2014, there are MJPEG AVI files that are not displaying correctly.
When opening the file in Windows Media Player, the video displays like this:
Premiere CS6 and CC 2014 are displaying it like this:
Any ideas why this might be occurring?

It should be noted, however, that you need to be very careful when installing these codec packs because they often contain malware.

Creating MJPEG AVI

Hello,
I want to create a MJPEG AVI from single JPEG pictures. Ok, I have done all the AVI stuff but for using the images I must use a special Hufmann table. How can I set this table via                                    //
JPEGEncodeParam param = encoder.getDefaultJPEGEncodeParam(bi);
param.setACHuffmanTable();
param.setDCHuffmanTable();
the Hufmantable I need looks like this
/* JPEG DHT Segment for YCrCb omitted from MJPG data */
private static byte[] MJPGDHTSeg = new byte[]
          (byte)0xFF,(byte)0xC4,(byte)0x01,(byte)0xA2,
          (byte)0x00,(byte)0x00,(byte)0x01,(byte)0x05,(byte)0x01,(byte)0x01,(byte)0x01,(byte)0x01,(byte)0x01,(byte)0x01,(byte)0x00,(byte)0x00,(byte)0x00,(byte)0x00,(byte)0x00,
          (byte)0x00,(byte)0x00,(byte)0x00,(byte)0x01,(byte)0x02,(byte)0x03,(byte)0x04,(byte)0x05,(byte)0x06,(byte)0x07,(byte)0x08,(byte)0x09,(byte)0x0A,(byte)0x0B,(byte)0x01,
          (byte)0x00,(byte)0x03,(byte)0x01,(byte)0x01,(byte)0x01,(byte)0x01,(byte)0x01,(byte)0x01,(byte)0x01,(byte)0x01,(byte)0x01,(byte)0x00,(byte)0x00,(byte)0x00,(byte)0x00,
          (byte)0x00,(byte)0x00,(byte)0x01,(byte)0x02,(byte)0x03,(byte)0x04,(byte)0x05,(byte)0x06,(byte)0x07,(byte)0x08,(byte)0x09,(byte)0x0A,(byte)0x0B,(byte)0x10,(byte)0x00,
          (byte)0x02,(byte)0x01,(byte)0x03,(byte)0x03,(byte)0x02,(byte)0x04,(byte)0x03,(byte)0x05,(byte)0x05,(byte)0x04,(byte)0x04,(byte)0x00,(byte)0x00,(byte)0x01,(byte)0x7D,
          (byte)0x01,(byte)0x02,(byte)0x03,(byte)0x00,(byte)0x04,(byte)0x11,(byte)0x05,(byte)0x12,(byte)0x21,(byte)0x31,(byte)0x41,(byte)0x06,(byte)0x13,(byte)0x51,(byte)0x61,
          (byte)0x07,(byte)0x22,(byte)0x71,(byte)0x14,(byte)0x32,(byte)0x81,(byte)0x91,(byte)0xA1,(byte)0x08,(byte)0x23,(byte)0x42,(byte)0xB1,(byte)0xC1,(byte)0x15,(byte)0x52,
          (byte)0xD1,(byte)0xF0,(byte)0x24,(byte)0x33,(byte)0x62,(byte)0x72,(byte)0x82,(byte)0x09,(byte)0x0A,(byte)0x16,(byte)0x17,(byte)0x18,(byte)0x19,(byte)0x1A,(byte)0x25,
          (byte)0x26,(byte)0x27,(byte)0x28,(byte)0x29,(byte)0x2A,(byte)0x34,(byte)0x35,(byte)0x36,(byte)0x37,(byte)0x38,(byte)0x39,(byte)0x3A,(byte)0x43,(byte)0x44,(byte)0x45,
          (byte)0x46,(byte)0x47,(byte)0x48,(byte)0x49,(byte)0x4A,(byte)0x53,(byte)0x54,(byte)0x55,(byte)0x56,(byte)0x57,(byte)0x58,(byte)0x59,(byte)0x5A,(byte)0x63,(byte)0x64,
          (byte)0x65,(byte)0x66,(byte)0x67,(byte)0x68,(byte)0x69,(byte)0x6A,(byte)0x73,(byte)0x74,(byte)0x75,(byte)0x76,(byte)0x77,(byte)0x78,(byte)0x79,(byte)0x7A,(byte)0x83,
          (byte)0x84,(byte)0x85,(byte)0x86,(byte)0x87,(byte)0x88,(byte)0x89,(byte)0x8A,(byte)0x92,(byte)0x93,(byte)0x94,(byte)0x95,(byte)0x96,(byte)0x97,(byte)0x98,(byte)0x99,
          (byte)0x9A,(byte)0xA2,(byte)0xA3,(byte)0xA4,(byte)0xA5,(byte)0xA6,(byte)0xA7,(byte)0xA8,(byte)0xA9,(byte)0xAA,(byte)0xB2,(byte)0xB3,(byte)0xB4,(byte)0xB5,(byte)0xB6,
          (byte)0xB7,(byte)0xB8,(byte)0xB9,(byte)0xBA,(byte)0xC2,(byte)0xC3,(byte)0xC4,(byte)0xC5,(byte)0xC6,(byte)0xC7,(byte)0xC8,(byte)0xC9,(byte)0xCA,(byte)0xD2,(byte)0xD3,
          (byte)0xD4,(byte)0xD5,(byte)0xD6,(byte)0xD7,(byte)0xD8,(byte)0xD9,(byte)0xDA,(byte)0xE1,(byte)0xE2,(byte)0xE3,(byte)0xE4,(byte)0xE5,(byte)0xE6,(byte)0xE7,(byte)0xE8,
          (byte)0xE9,(byte)0xEA,(byte)0xF1,(byte)0xF2,(byte)0xF3,(byte)0xF4,(byte)0xF5,(byte)0xF6,(byte)0xF7,(byte)0xF8,(byte)0xF9,(byte)0xFA,(byte)0x11,(byte)0x00,(byte)0x02,
          (byte)0x01,(byte)0x02,(byte)0x04,(byte)0x04,(byte)0x03,(byte)0x04,(byte)0x07,(byte)0x05,(byte)0x04,(byte)0x04,(byte)0x00,(byte)0x01,(byte)0x02,(byte)0x77,(byte)0x00,
          (byte)0x01,(byte)0x02,(byte)0x03,(byte)0x11,(byte)0x04,(byte)0x05,(byte)0x21,(byte)0x31,(byte)0x06,(byte)0x12,(byte)0x41,(byte)0x51,(byte)0x07,(byte)0x61,(byte)0x71,
          (byte)0x13,(byte)0x22,(byte)0x32,(byte)0x81,(byte)0x08,(byte)0x14,(byte)0x42,(byte)0x91,(byte)0xA1,(byte)0xB1,(byte)0xC1,(byte)0x09,(byte)0x23,(byte)0x33,(byte)0x52,
          (byte)0xF0,(byte)0x15,(byte)0x62,(byte)0x72,(byte)0xD1,(byte)0x0A,(byte)0x16,(byte)0x24,(byte)0x34,(byte)0xE1,(byte)0x25,(byte)0xF1,(byte)0x17,(byte)0x18,(byte)0x19,
          (byte)0x1A,(byte)0x26,(byte)0x27,(byte)0x28,(byte)0x29,(byte)0x2A,(byte)0x35,(byte)0x36,(byte)0x37,(byte)0x38,(byte)0x39,(byte)0x3A,(byte)0x43,(byte)0x44,(byte)0x45,
          (byte)0x46,(byte)0x47,(byte)0x48,(byte)0x49,(byte)0x4A,(byte)0x53,(byte)0x54,(byte)0x55,(byte)0x56,(byte)0x57,(byte)0x58,(byte)0x59,(byte)0x5A,(byte)0x63,(byte)0x64,
          (byte)0x65,(byte)0x66,(byte)0x67,(byte)0x68,(byte)0x69,(byte)0x6A,(byte)0x73,(byte)0x74,(byte)0x75,(byte)0x76,(byte)0x77,(byte)0x78,(byte)0x79,(byte)0x7A,(byte)0x82,
          (byte)0x83,(byte)0x84,(byte)0x85,(byte)0x86,(byte)0x87,(byte)0x88,(byte)0x89,(byte)0x8A,(byte)0x92,(byte)0x93,(byte)0x94,(byte)0x95,(byte)0x96,(byte)0x97,(byte)0x98,
          (byte)0x99,(byte)0x9A,(byte)0xA2,(byte)0xA3,(byte)0xA4,(byte)0xA5,(byte)0xA6,(byte)0xA7,(byte)0xA8,(byte)0xA9,(byte)0xAA,(byte)0xB2,(byte)0xB3,(byte)0xB4,(byte)0xB5,
          (byte)0xB6,(byte)0xB7,(byte)0xB8,(byte)0xB9,(byte)0xBA,(byte)0xC2,(byte)0xC3,(byte)0xC4,(byte)0xC5,(byte)0xC6,(byte)0xC7,(byte)0xC8,(byte)0xC9,(byte)0xCA,(byte)0xD2,
          (byte)0xD3,(byte)0xD4,(byte)0xD5,(byte)0xD6,(byte)0xD7,(byte)0xD8,(byte)0xD9,(byte)0xDA,(byte)0xE2,(byte)0xE3,(byte)0xE4,(byte)0xE5,(byte)0xE6,(byte)0xE7,(byte)0xE8,
          (byte)0xE9,(byte)0xEA,(byte)0xF2,(byte)0xF3,(byte)0xF4,(byte)0xF5,(byte)0xF6,(byte)0xF7,(byte)0xF8,(byte)0xF9,(byte)0xFA
Thanks for your help
R

I downloaded the trial and found the clips would not even load. Then I discovered that if I changed the clip extension from .mpg to .avi they loaded fine. I have been able to edit and apply transitions and effects with no problems. Accordingly, I purchased PrE 10.
Both of Adobe's NLE (Non Linear Editor) programs look for common CODEC's, in common "wrappers," i.e. the file format, like MOV, MP4, AVI, MPEG, WMV, etc.. When one wraps a common CODEC in a wrapper, where the program expects something else, it can get very confused.
This has been happening with some regularity, where some camera mfgrs. are choosing to wrap H.264 (common CODEC) in the AVI wrapper (un-common combo). To date, PrPro has addressed this CODEC/wrapper issue w/ a recent update. I anticipate that we might see similar with PrE 11, but do not kow that it will happen.
When camera mfgrs. "stray off the ranch," it takes companies, like Adobe, some time to catch up. In the case of PrPro, there are historically updates during its 18 mos. +/- life cycle. As PrE is on a 12 mo. life span cycle, not so often, though there HAVE been updates, like with PrE 3.0, when Vista was released just after PrE 3.0 was, and caused many issues. Same with some issues with PrE 8. When that does happen, there are often little "goodies" added in, that might have been sitting on the shelf, waiting for the next big upgrade - though not always.
As per another thread, we are seeing more and more still cameras, that shoot Video as 640 x 480 w/ PAR = 1.0 (square pixels), which is uncommon, by the general Video standards. However, as more mfgrs. do such things, Adobe will need to adapt, and at some point, adopt.
Good luck,
Hunt

No Thumnails for MJPEG AVIs in PSE 11 Organizer

My AVI Video clips are not showing thumbnails in the PSE 11 Orgazizer.
Here is what I have observed as I have been troubleshooting this:
The files are MJPEG.
When I double click on it in the organizer window, I get audio, but no video.
If I open the file for edit in Premier Elements, the video thumbnail shows up in project assests and the video correctly plays in the Premier Elements editor.
If I double click on the files in Windows Explorer they open up in Quicktime Version 7.
The thumbnails for the files show in up windows explorer when I browse to the folder they are in.
I selected a file in PSE, chose 'Export to New File" and the file that I created by doing that showed a generic Quicktime icon without the thumbnail in windows explorer. When I double click on that file it correctly plays in Quicktime.
Selecting "Update Thumbnail" has no effect.
Any one have any ideas what is going on with the organizer that might be causing this beavior or is this a know limitation of PSE Organizer. What is the point of having the organizer supporting video If I can't see the video without opening it in the Premier Elements Editor?
Message title was edited by: Brett N

You may have missed the comment that I tried that and it did not work. I am providing the "Systems Info" if that helps anyone.
Elements Organizer 11.0.0.0
Core Version: 11.0 (20120923.r.32287)
Language Version: 11.0 (20120923.r.32287)
Current Catalog:
Catalog Name: My Catalog
Catalog Location: C:\ProgramData\Adobe\Elements Organizer\Catalogs\My Catalog\
Catalog Size: 49.1MB
Catalog Cache Size: 578.7MB
System:
Operating System Name: Vista
Operating System Version: 6.0 Service Pack 2
System Architecture: Intel CPU Family:6 Model:7 Stepping:7 with MMX, SSE Integer, SSE FP
Built-in Memory: 3.9GB
Free Memory: 905.8MB
Important Drivers / Plug-ins / Libraries:
Microsoft DirectX Version: 9.0
Apple QuickTime Version: 7.73
Adobe Reader Version: 10.1
Adobe Acrobat Version: Not installed
CD and DVD drives:
E: (HL-DT-ST DVDRAM BUS: 1 ID: 1 Firmware: GH24LS50)

MJPEG AVI issues, gspot codec appliance lying to me?

I have two types of videos. One is 1080p from my goggles, one is from my Canon point and shoot.
Goggle 1080p .mov video: Premiere Elements 10 and Windows Movie Maker can import and edit, but gspot codec appliance says it is undetermined.
Crummy Canon .avi MJPEG video: Everything can play it, Windows Movie Maker can edit it no problem, Elements 10 cannot import it, and gspot tells me it is an MJPEG and the codec is installed and fine.
What the heck is going on??
Do I need to export these MJPEGs from Windows Movie Maker and feed them into Elements 10? I can't afford to lose any video quality on those files...
I r dissapoint.
Help!
Thanks,
Brad

I downloaded the trial and found the clips would not even load. Then I discovered that if I changed the clip extension from .mpg to .avi they loaded fine. I have been able to edit and apply transitions and effects with no problems. Accordingly, I purchased PrE 10.
Both of Adobe's NLE (Non Linear Editor) programs look for common CODEC's, in common "wrappers," i.e. the file format, like MOV, MP4, AVI, MPEG, WMV, etc.. When one wraps a common CODEC in a wrapper, where the program expects something else, it can get very confused.
This has been happening with some regularity, where some camera mfgrs. are choosing to wrap H.264 (common CODEC) in the AVI wrapper (un-common combo). To date, PrPro has addressed this CODEC/wrapper issue w/ a recent update. I anticipate that we might see similar with PrE 11, but do not kow that it will happen.
When camera mfgrs. "stray off the ranch," it takes companies, like Adobe, some time to catch up. In the case of PrPro, there are historically updates during its 18 mos. +/- life cycle. As PrE is on a 12 mo. life span cycle, not so often, though there HAVE been updates, like with PrE 3.0, when Vista was released just after PrE 3.0 was, and caused many issues. Same with some issues with PrE 8. When that does happen, there are often little "goodies" added in, that might have been sitting on the shelf, waiting for the next big upgrade - though not always.
As per another thread, we are seeing more and more still cameras, that shoot Video as 640 x 480 w/ PAR = 1.0 (square pixels), which is uncommon, by the general Video standards. However, as more mfgrs. do such things, Adobe will need to adapt, and at some point, adopt.
Good luck,
Hunt

.AVI Woes

P4 3GHz Windows XP
Hi All I am trying to put .AVI files into itunes the metod I am using works fine on my powerbook but will not work on my PC. I save the file as a reference movie in quicktime 7 Pro and drop that into iTunes, on windows the movie shows as if there is not a compatible codec available. I am using Divx on the mac and PC.
So is Divx compatible with quicktime on the PC or is there a way the get quicktime to use Divx?
TIA

Yes there is a way to get divX encoded AVI's to work with quicktime, but it is extremely involved
1) Use a program called [url="http://www.virtualdub.org/"]virtualdub[/url] to decode the mp3 audio layer found in most AVI's. The codec mentioned in the next step does not work with mp3 audio layers. To convert the audio track you must open the audio tab, look down and select full processing mode. Then use the file menu and select "save as AVI". It will now make a file whose audio will work in quicktime
2) Download a codec called [url="http://www.3ivx.com/"]3ivx[/url] to enable AVI playback in quicktime
NOTE: if your AVI doesn't have an mp3 audio layer you do not need to use virtualdub on the audio layer
Windows XP

.avi files no longer importing (86 :: 1)

Recently, After Effects CS5.5 has simply stopped importing .avi files. It's very frustrating sense I was in the middle of a project and it's just stopped reading my main video file.
I've tried everything from completly uninstalling and reinstalling CS5, to updating my codecs, but I always get:
After Effects Error: File "X.avi" cannot be opened, it may be in an unsupported format. (86 :: 1)
I've searched everywhere, but I can't seem to find a solution. I'm running it on a PC and it's not having any trouble with .mp4 files. I also use Divx if that's any help.
Any assistance would greatly be apreciated.

themanofvideo wrote:
Are you sure total reinstallation is the only alternative?
Pretty much.
You can confirm by doing TWO searches in this forum: one using the term Klite or K-Lite and one for AVI. The first search will reveal others' experiences with K-Lite, and the second should reveal Todd Kopriva's recent post on AVI woes like yours. You'll find the search window in the upper right the page.
Looking over your specs, I'd also double check AE 10's (or 10.5's) System Requirements. I'm not certain if Vista 64-bit is up to snuff. You might need Win 7 for best results.
Now here's something I AM certain about: you're way low on memory for AE work. 4 gigs is almost nothing. There's no way you can use multiprocessing. I would say that 8 gigs is the minimum to run AE effectively. 16 gigs lets you use a couple of cores for multiprocessing. 24 gigs is good for multiprocessing. More memory than that lets you leave other applications open with no worries.

My avi video files are no longer supported in PRE9? Help!

I created a movie in premiere elements 9 several months ago. My video was imported from avi files on my computer. The avi files were originally downloaded from my camera. Everything was fine and I even burned a near finished copy of my project on a DVD. Now, several months later, I open up the project to put my final touches on it and notice that all the avi video files are red in the timeline. On the organizer tab for my project under media type, it says, "offline". So, I clicked on the avi file and it asks me to find it. I find it (the files have not moved) and click on it and I get this error, "Error Message. This type of file is not supported, or the required codec is not installed." This is very strange. Do you have any ideas? My operating system is Windows 7.

I kind of suspected MJPEG (just a hunch, as two other CODEC's, commonly wrapped in an AVI, DivX and Xvid, seldom every play correctly to start with).
Now, there are many "flavors" of MJPEG. It is an older CODEC (or really type of CODEC, as there are so many versions), that was ressurected for use in mostly (then) stills cameras, with video capabilities added. It is not a bad CODEC, but each camera mfgr. has tweaked it for their purposes. This can create issues. MJPEG is not the "universal," that say DV-AVI Type II is. Canon will have a version, Nikon another and Panasonic yet another. They all show as MJPEG, but will be a bit different. A similar analogy can be drawn with Camer RAW files - Canon's differ from Nikon's, which differ from Panasonic's, though they are all Camera RAW. Also, Nikon, for instance, is constantly changing what is in their NEF (Camera RAW) files, so that the newest will require the latest release of Adobe Camer RAW (ACR), to be processed in Photoshop. MJPEG is similar to that, with fewer variations - but still individual variations.
Now, there could well be reasons that things have changed. The first one to strike me would be that you installed the software that came with that camera, and included its specific version of the MJPEG CODEC, then later removed say the camera's utility, taking that specific version of MJPEG away. You might well have others, but PrE is having a hard time matching them up.
In that article I linked to on MJPEG, I mention two popular MJPEG CODEC's, Morgan and MainConcept. Both are rather generic MJPEG CODEC's, and when MJPEG resurfaced, they worked fine for most such files. However, as time has elapsed, and camera mfgrs. tweaked and tweaked, they are less likely to work 100%. Once, they were the "silver bullet" for MJPEG - but not so much any more.We began seeing more users, with either, or even both, still having issues with newer MJPEG CODEC's. As most camera mfgrs. ship a copy of their specific version, somewhere along with the camera, it became common practice to recommend installing that specific version from the specific camera's utility disc. Unfortunately, that was not always easy to do. Some included their version of MJPEG as a separate installation (best way, IMHO), but many incorporated it into the camera's driver installation (still good), and then there are those instances, where the specific version of the MJPEG CODEC is installed along with other utilities on the disc, such as maybe a little editing program, or a file cataloging utility. Scant mention is ever made of the specific MJPEG CODEC, and how it is installed on one's system. The latter method seems to be the most common now. I have the full utilities, including the camera's own editing programs, installed for my Canon, my Nikon and my wife's Panasonic. That means that I have at least five (think that the total count is eight on my workstation) MJPEG CODEC's: one for Canon, one for Nikon, one for Panny, one Morgan and one MainConcept.
What camera produced those MJPEG AVI files?
Do you have that camera's editing and cataloging utility installed?
Do you have the utility disc for that camera?
Have you removed any such editing, or cataloging utility, between the time that the files worked, and when they did not?
I do not believe that any version of PrE actually installs any version of MJPEG (could be wrong here), though they work with, and include various other MainConcept (mostly MPEG) CODEC's. That means that one will need to install an MJPEG CODEC, and the one specific to that camera, might be required.
You obviously do have an MJPEG CODEC (or more), installed in your OS. As there is a vast difference between playback of an AV file, and editing that same file, it could be that PrE is just not able to use the installed version, with those files. As it once was able to edit them, I am guessing that something has changed, and it could be as simple as cleaning out one of the supplied utilities for the camera, that also removed its specific version of the MJPEG CODEC.
As PrE does not install the specific version of the MJPEG CODEC, many recommend not trying to edit such material. I am not of that mindset, but do allow that one might have to do some extra work (and work that is NEVER outlined in the camera mfgr's literature - unfortunately), to get things to work. I had to install a bunch of programs, that I will never directly use, just to be able to edit the MJPEG AVI's from my family's cameras, in both PrE and PrPro. I hate having to do that, as it fills up my HDD with stuff, that will otherwise never be used - but I need the specific CODEC, and it's only available to be installed WITH other software - all too common nowadays, and a mistake on the part of the camera mfgrs. IMO.
Good luck, and I hope that with the specific MJPEG CODEC, you will be back up and editing your footage, as you were once able to do.
Hunt
PS - sorry for writing an entire encyclopedia there, but MJPEG is not as simple as it could be.

Export from QT Pro as AVI reduces quality of video drastically

I need AVI for poor PC users in family.
Original video is AVI from a Samsung digital still camera, saved and edited in QTPro 7.2 on iMac.
Export as AVI using Default or Highest Quality Settings, results in a severe degradation of colour tonal gradation - which was OK in the original AVis (viewable in Quicktime), and in QT.
It looks like the number of colours has been reduced from thousands to hundreds ( ? 256)
Filesize is similar- MOV 41.6 MB, AVI 39.5 MB.

The only detail given in the Samsung Pro 815 manual is "file type .avi (MJPEG)". I used default Cinepak compression to export as .avi
Now we're getting somewhere. Motion JPEG is a common video codec used by certain digital camera manufacturers in the AVI container. It is a moderate compression/higher quality codec. Cinepak is an older, high efficiency video codec probably better suited to smaller resolution use. Comparing CinePak to MJPEG would, in some ways, be like comparing MPEG-4 to H.264. In both cases the video data rate of your final "Cinepak" AVI needs to be on the order of 2.0-2.5 times the data rate of your original "MJPEG" AVI file for equivalent quality. While I do not normally deal with such files, a previous poster ask for help in converting his Casio (MJPEG/DVI ADPCM) files for use in iMovi '08. Wile the original file is not of the highest quality, I prepared a clip to compare the original "MJPEG" AVI video track with the final "Cinepak" AVI track. (For comparison purposes, these two tracks were stored in an MOV file container so they could be compared on a "frame-to-frame" basis.) If interested, here is the URL for this comparison.
http://homepage.mac.com/jrwalker4/.Public/CIMG8145Comp.mov
For QT7 Pro to edit the original .avi clips, they have to be saved as .mov.
Strange. I can convert directly from the "MJPEG" AVI to "Cinepak" AVI file.
This is instantaneous, and causes no quality loss. No file conversion or re/de/compression seems to occur.
Correct.
Exporting Cinepak .avi obviously requires considerable processing, so it seems that the codec used in the Samsung .avi is native to QT
This codec basically sequences a series of still JPEG photos in either the AVI or MOV file container. As such it is compatible with probably any system capable of viewing JPEG photos and opening either file container. This compatibility is probably the reason this codec was selected in the first place by the camera manufacturer.
The issue is clearly that the QT7 >Cinepak .avi export process (?deliberately) degrades video quality, without reducing file size, even though it claims to be using "Best" quality and "millions" of colours.
Each codec has its own characteristics. If a small file is what you want, then reduce the resolution of your movie or accept the reduction in quality at its current resolution. If quality is your main concern, then increase your video data rate so it can store as much of the original quality as it can at the current resolution or simply switch to a more modern codec, Microsoft ended support for the AVI file container a decade ago.
Is there a secret QT setting, or plug-in, which will do the export without loss of quality, to an .avi or other format which bog-standard WMP on XP will play?
As demonstrated in the sample file above, the only setting that needs to be changed is the data rate. As to other possible compression formats, you could use more modern codecs like WMV 9 (Flip4Mac) or DivX 6.

FCP X: DV AVI import fails

Hello forum,
I have DV AVIs which were captured on a Windows XP PC with the Miro DV500 capture card. When trying to import a given AVI file into Final Cut Pro X 10.0.1 (latest available update) I get an error message:
"No importable media - None of the selected files or folders could be imported. Change your selection and try again"
(I have the german version, so the above is just a rough translation)
I tried also with unchecking all import dialog checkboxes, to no avail. The same import failure happens on an iMac running 10.6.8 Snow Leopard and FCP X 10.0.1 (latest update) and on a MacBook Pro running 10.7.1 Lion with the original FCP X 10.0.
I copied the files onto the Mac harddisk. The size is nothing extraordinary, the smallest file is just about 172 MBytes.
The files import just fine into my Final Cut Express 4.0 version! They also play fine with QuickTime or any other application such as VLC on my Mac.
I found this entry here: https://discussions.apple.com/thread/3152268?start=0&tstart=0 which talks about (large) MJPEG AVIS from a Pentax K-7 camera. The same workaround described there works with my DV AVI files as well: I open the AVI with Quick Time 7 Player (on my Snow Leopard), "Save as" and then "Save as reference" ("Als Referenz sichern" in my german QT). This produces a very small *.mov file which I then can import into FCP X!
(Unfortunatelly I haven't figured out yet how that works on Lion with QT 10.1, since the "Save as" has gone (bummer!) and the Export doesn't seem to provide a "Save as reference" anymore - unlike the original post claims: "...and save the file as a movie with the media in the same format." - how?)
Anyone else is having trouble importing DV AVIs into FCP X?

Ops, sorry, yeah, wanted to post this to Final Cut Pro (X) forum! Sorry about the noise!
Anyway, thanks for your reply: I consider this a bug in FCP X and if possible would like to avoid to transcode the movie (I could live with copying the streams 1:1 and simply re-writing the AVI header, or copying it into a MOV container, without any re-compression loss - any such program known? Tried quickly VLC, but that only seems to support transcoding into MPEG etc., not copying the content 1:1...).
Anyway, will re-post this into the proper Final Cut Pro forum... if you're interested, please continue there.

Import of PAL DV AVI fails

Hello forum,
I have DV AVIs which were captured on a Windows XP PC with the Miro DV500 capture card (with OpenDML option, PAL format, interlaced). When trying to import a given AVI file into Final Cut Pro X 10.0.1 (latest available update) I get an error message:
"No importable media - None of the selected files or folders could be imported. Change your selection and try again"
(I have the german version, so the above is just a rough translation)
I tried also with unchecking all import dialog checkboxes, to no avail. The same import failure happens on an iMac running 10.6.8 Snow Leopard and FCP X 10.0.1 (latest update) and on a MacBook Pro running 10.7.1 Lion with the original FCP X 10.0.
I copied the files onto the Mac harddisk. The size is nothing extraordinary, the smallest file is just about 172 MBytes.
The files import just fine into my Final Cut Express 4.0 version! They also play fine with QuickTime or any other application such as VLC on my Mac.
I found this entry here: https://discussions.apple.com/thread/3152268?start=0&tstart=0 which talks about (large) MJPEG AVIS from a Pentax K-7 camera. The same workaround described there works with my DV AVI files as well: I open the AVI with Quick Time 7 Player (on my Snow Leopard), "Save as" and then "Save as reference" ("Als Referenz sichern" in my german QT). This produces a very small *.mov file which I then can import into FCP X!
(Unfortunatelly I haven't figured out yet how that works on Lion with QT 10.1, since the "Save as" has gone (bummer!) and the Export doesn't seem to provide a "Save as reference" anymore - unlike the original post claims: "...and save the file as a movie with the media in the same format." - how?)
Anyone else is having trouble importing DV AVIs into FCP X?

Now, Tom and Ron, you two seem to be very on the bright side of life: just accepting the fact that there are bugs and just put up with them by "Thinking different" - or you're just accepting the fact that "You're holding it wrong" or whatever.
It's funny, this seems to be a very common attitude among some Apple "lovers".
@Tom: Now your statement is wrong in at least a couple of things: first DV AVI actually is on the list of supported import formats. Second, "no previous version did" is clearly disproven by the very fact that even FCP Express 4 is able to import this very same AVI clip. Let alone QuickTime being able to play it and iMovie also imports it just fine.
Now I cannot talk about FCP before FCP X as I have never used those, but FCP Express being a downsized version of the very same product and being able to import DV AVI I can't believe FCP would not.
Finally your statement that the new "AV Foundation" doesn't import (DV) AVI clips is also wrong: again as disproven by the fact that the very same DV video clip, with a modified/corrected AVI header by MPEG StreamClip (a simple "Save-As" does it!), is successfully imported into FCP X!
So yes, it's most probably an AVI header bug, and that bug is in the new AV Foundation.
And there's something else you get confused about: AVI is NOT a video format! It is a container! So even if that is not the native (or preferred) container for FCP X there would be absolutely no reason why FCP X should do any other thing than decompress the format (DV in this case, which is a very common format!) and convert it to my target format (H264 or whatever, and into whatever container I would choose, say MP4). There would be absolutely no rendering involved (assuming off ourse that the only editing would be cuts and no fades or the like), except maybe converting DV into the "native" format which would be used internally. But that would be comparable effort to converting any other format into the FCP internal format. So I don't see your "endlessly rendering in FCP" (compared to when I would import say a DV video clip in a QuickTime container).
And to Tom: No, this is not a viable solution for me to use a converter to work around a bug! And I don't understand why you insist on your suggestion being a genuine solution, as I already wrote in the first 3 posts or so that I figured out that myself already (and actually without converting to any "FCPX codec" - whatever that would be, but I figure you mean something like "ProRes 422"). But it's just no fun to first copy hours of digitised VHS tapes into almost identical files, just to be able to import them! Yes, it would work, yes I might even have to revert to that "solution" - but I still consider it not a real solution.
And again, I am not saying that Apple cares enough about eventually fixing that issue, but they did get in contact in me after me sending an issue. Also just recently after I complained that 10.0.2 did not fix it (uh well, yes, with no concrete indications of whether that would get fixed, just along the lines like "I have to get in contact with our engineers again")...
So no, 10.0.2 did not fix it - so I'm still holding my breath...
Thanks anyway for your help so far - just don't try to convince me of what I'm trying to do is wrong (as I get the feeling).
Cheers, Oliver

Journe air 1000 - video playback lags after converting to mjpeg

Hello,
i have bought 2 journe air 1000 photo frames, and i'm trying to play video on them.
To convert the video files i'm using the provided software that was in CD that came with the frame - ArcSoft video converter 2.5, which converts the video to a MJPEG avi file with quite poor sound quality.
And the main problem is that, video starts to lag after some time, there is no sync between sound and video, and eventually it crashes.
Also some video track just crash straight away..
I have 2 files, one is 30 mins long and the other is 10 min long, both experience the same symptoms, on both frames.
I have tried to use newer arcsoft converter software, different converters, tried splitting the files to smaller segments but to no avail...
It just like there's some buffer in the frames that fill's up and the video starts to lag.. anyone experienced that?
Maybe there's some other codec that this frame supports except mjepg? i have tried some (mpeg4, divx, xvid) but it didnt work, it doesn't even play mjpeg mov's, just avi's...
Any ideas how to fix it?
thanks.

yes i have tried loads of other formats: with mjpeg movs i get some flickering sound and black screen, and with all the others (h264, mp4 and so on) - "decode failed" and i haven't found anywhere in specs that it supports anything else except mjpeg avi..
maybe some specific setting need to be applied to other formats? has anyone else succeeded in playing other formats? what settings did you use?
thanks

Intermittent Problem with MJPEG Files

Hello, all-
I've been having some real trouble lately with files that have been captured or rendered using the Blackmagic MJPEG codec. I do most of my work at 1080 (both i&p) and render effects and After Effects graphics to BM MJPEG AVIs. On occasion (and the occasions are becoming more frequent), Premiere will render these files as a solid green frame. The odd thing is, it's very intermittent. Sometimes even within the file itself (i.e., only some frames will show up as green). The files play fine in any other application (media player, for example). Often times, the problem won't become apparant until I'm exporting to a file for client review through AME (very conevenient).
I'm assuming that the files are fine, and it's some sort of media database problem. I've tried deleting all of the database files and the problem persists, so it could be that it's embedded in the project somehow. Starting a new project and importing sequences does not solve the problem. Also, the files will sometimes show frames (with the green/pink effect) from completely different clips, which again makes me think of some sort of database problem. If I re-import the same clip as a new clip in the project, it still does not display properly.
The weird thing is, it only seems to happen with these MJPEG files which are essential to my workflow. Most of my source footage is XDCAM-EX and DVCPro HD which both work flawlessly. I'd purchase a copy of CineForm, but I can't seem to render effects to the CineForm codec if I'm working on a Blackmagic timeline and CineForm timelines won't display on my Blackmagic hardware (Multibridge Pro).
Computer is up to specs, Tyan S5396, Dual Quad ES5410s, 16GB RAM, fast raid array for storage.
Ideas?

I just tried the command you mentioned to start OC4J but I still get that problem.
It's really weird because I have had this process of deployments working for months with no problem, then all of a sudden it started acting up.
I don't think anything has changed but there must be something. I just don't know where to look.
any other suggestions?
-Isaac

Cannot open .avi files imported from Nikon d90 in Adobe Premiere 6.0.

Cannot open .avi files imported from Nikon d90 in Adobe Premiere 6.0.
When I try to open the file I get the following error message:
"cannot open that file
the file uses an unsupported file compression format"
I really need urgent help with this so if you know a soloution, please post it!

I don't do mjpeg so you will have to search the forum for advice
But... having a playback codec installed does not ALWAYS mean the codec will work for Premiere editing
After you search the forum and find the (I think free) codec vendors, you will need to install fresh so Premiere will "see" the codec for editing
Or, Google
convert mjpeg avi
To convert to DV AVI type 2 with 48khz sound so the files will "natively" edit in Premiere
My GUESS (you didn't say) is the d90 is a STILL camera that has a video function, not a true camcorder
If you plan to do much video work, you need a tape-based DV camcorder so you use Firewire to do a digital transfer as a "real" AVI that Premiere may edit without conversion or extra software
For a Firewire DV Camera - look at Panasonic PV-GS320 or GS500 (Note that I have not used either, but they have good reviews)
http://reviews.cnet.com/Panasonic_PV_GS320/4505-6500_7-32330317.html
http://reviews.cnet.com/digital-camcorders/panasonic-pv-gs500/4505-6500_7-31660646.html

AVI to ProRes has problems

Two interesting issues I came across today with QT/FCP. While I just the problems are just bugs, I'd like to see what others think.
A friend of mine has some SD video he shot in MJPEG AVI's. When trying to convert them with QT to ProRes 422 (HQ and regular), the frame rate of the resulting clip is only 15 fps. The original is 30. What's strange is that if I hard set it to something like 29.97, or 60, it still comes out 15 fps, and just gets artificially boosted to whatever I set. Very annoying!
So, I used VLC to convert this AVI to H264/AAC .MP4, opened THAT in QT, and converted it to ProRes. Now its still 30 fps. Great!
BUT... when I try to drag that clip into FCP, it says the file is invalid, even though QT MADE IT! Again, this clip is ProRes 422 HQ with Linear PCM audio!

Turns out ffmpeg does something wrong to MooV atoms, rendering files unreadable by FCP.

Mjpeg AVI woes

Similar Messages

Maybe you are looking for