Am I missing a CODEC?

Dabitz · Post by **Dabitz** » Mon Sep 29, 2008 5:16 pm

When I convert an AVCHD file to MPEG2, the window screen shows grayed out when playing on Windows Media Player (latest version/Vista Home Premium). However, this same MPEG file does play on VS 12.

Another thing I noticed when down-converting to WMV or FLV is that the pictures and titles on the video do not retain the 16:9 ratio, so the video shows wide screen but the titles and pictures show 4:3 (sample at: http://www.youtube.com/watch?v=dFeRfFyC21A)

Thanks so much in advance...

Post by **Ken Berry** » Mon Sep 29, 2008 9:28 pm

I can't help with the second half of your question. However, as far as I am aware Windows Media Player will only play AVCHD if it does not have the .m2ts or .mts extension. If you change the extension to .mpg, I think you will find that WMP can then 'see' the file and play it...

Dabitz · Post by **Dabitz** » Mon Sep 29, 2008 9:36 pm

Hi there Ken...

No, WMV is having trouble playing the MPEG files that I converted out of the AVCHD. They play on VS12, but can't see them on WMV. I wanted to make a file I can play over the PS3 (HD).

Post by **Ken Berry** » Mon Sep 29, 2008 9:51 pm

Whoops!

Sorry -- I read your original post too quickly. What are the properties of the mpeg-2 you created? I have converted quite a few AVCHD clips to standard definition mpeg-2 and they play fine. In fact, there were a couple in the folder I checked before to test the AVCHD playing in WMP and they played with no trouble. So potentially, there might be a codec problem... WMP seems to prefer codecs from only one or two sources. On mine, its preferred mpeg-2 codec believe it or not is from PowerDVD. IIRC, the VS codec does not get a mention. But then again, WMP using that Cyberlink codec has no trouble playing mpeg-2 encoded in a Corel product...

Post by **lancecarr** » Tue Sep 30, 2008 6:42 am

Windows Media Player does not come with it's own MPEG2 decoder. As Ken already said WMP is also quite snobbish about which decoder it will deign to work with.
They do offer the rare priviledge of going online to the Windows site and purchasing an overpriced decoder from them. However,
there is a free Windows utility called (something like) Windows Video decoder Checkup utility.
Try to search for it on the net. Run it and it will tell you what, if any, MPEG2 decoders you have on your system already that WMP will play with. If you have one that is acceptable it will give you the choice to associate the decoder with WMP.

Dabitz · Post by **Dabitz** » Tue Sep 30, 2008 4:37 pm

Last night I was playing with it. This is the AVCHD workflow that works for me:

1. Add individual AVCHD files to the library and let the system create Proxy Files. Then edit my project in the time line as usual and save my project. Proxy files work flawlessly for me.
2. Create/render an MPG2 file using the HDV settings and save to my harddrive (same file I CANNOT see with WMP). Next time I'll create a file using AVCHD settings, but this worked as well.
3. Create a new blank project in VS12 and insert the file I just created (again, it doesn't play with WMP but it does with VS12)
4. Create an AVCHD Disc on a regular DVD by using the share option create AVCHD.

My only complain is that at some point I dropped Dolby Digital 5.1, but I can figure that out later. So far this is what works for me. I wanted to be able to create MPG files I could play over my media server and read on my PS3, but I think this will have to do by now. The avchd dvd I created looked amazing when played on the PS3 with the exception of some banding in white areas. I should've bought an HDV camera...

This AVCHD editing stuff is very frustrating, so I wanted to share what works for me.

I would appreciate any suggestions to further improve my workflow. I am no expert by any means, but came up with this after reading posts from etech and Ken.

Post by **Ken Berry** » Tue Sep 30, 2008 9:48 pm

In point of fact you *can* use Make Movie Templates Manager to make your own AVCHD template with your own preferred properties including the original 5.1 audio! It just happens to be undocumented (and who knows if Corel is even aware of it?!) It also only works if you want a template using the same properties exactly as one of your AVCHD files straight out of the camera e.g. using Dolby 5.1 audio. You can of course achieve this anyway by using Share > Create Video File > Same as first clip, as long as your first video clip is in fact an AVCHD clip with your preferred properties. Otherwise, you can do the following.

Click on Tools > Make Movie Templates Manager, then instead of the normal 'New', you click the bottom button 'ADD'. A new dialogue box appears. In the bottom line, give a logical name to the new template (e.g. AVCHD Dolby 5_1). Then in the line above, click on the Path 'Browse' button (with ' ... ' on it) and browse to where you have stored an original AVCHD clip with 5.1 audio. Click on the file so that the path appears in the dialogue box. Click OK to get out of that dialogue box. Check in the original dialogue box to make sure the properties down below match those you are after. Do NOT try to edit those properties as that will just reset everything to default properties. Then close that dialogue box. The new template should now appear down towards the bottom next time you choose Share > Create Video File. Again, you must remember never to try editing that template as it will just reset everything and you will have to start over again.

Now that all being said (again!), you can also, I have found, edit your AVCHD and jump straight to the burning module (Share > Create Disc) rather than first rendering your project to a new AVCHD (or whatever) file. Doing it this way goes against years of my own preferred workflow with standard definition, but it seems to work -- at least for me. This workflow inserts the project file (.vsp) into the burning timeline. Then when you click on the middle of the three icons in the bottom left of the burning screen, you can change the burning properties to whatever you want. It doesn't matter whether or not the 'Do not convert compliant mpeg files' is ticked or not since in this case you have a project file, and not an mpeg-4, in the burning timeline. But you could uncheck this box to be on the safe side.

These hybrid discs work fine in my PS3 -- I am not sure about the banding your experience, though. Does it appear only in white areas, or in white areas when you are panning horizontally?

I have my my PS3 out in my lounge room connected via HDMI to my 46 inch HDTV. And the PS3 is networked via cable to my computer. Using either Nero MediaHome or WMP in server mode, I can play my edited high definition videos direct on the HDTV. It's truly great. My only annoyance is that Sony just brought out a new PS3 model with an 80 GB hard disk AND wireless connectivity, for the same price I paid for my lesser model 4 months ago!

Dabitz · Post by **Dabitz** » Wed Oct 01, 2008 1:23 am

Oh wow, that AVCHD template is awsome. Next time I'll create my file using those settings. The banding only appears on very white clouds taken from an airplane. I'll see if it happens when I render my file next time using my AVCHD template I just created.

Regarding codecs, I found the program that checks your computer for what codec you have installed, but it only works for XP and I have Vista. I think I'll have to fix my codec problem before I can play files over to the PS3 wireless. Yes I have the 80G wireless

My Sony Vegas crashes every time I try to render an MPG file, so I am positive I need to find a way to install another codec.

Thanks so much Ken... I'll post back once I try to render again using this new setting.

Post by **Ken Berry** » Wed Oct 01, 2008 2:27 am

If the banding only occurs in that specific circumstance (i.e. white clouds through a plane window, it is highly possible that it is there on the original video, though not particularly visible in the small camera and VS preview screens. In other words, it could be a spectrum effect caused by diffraction of the light through the plane window. And as you would have found, with high definition, it can be pretty unforgiving in highlighting any fault in the filming!!