-
7 gets the AVI, 9 does not
Why is Sony Vegas 7 able to recognize–i.e. ‘project’–video from a rendered AVI that Vegas 9 cannot?
I got this semi-cumbersome process of acquiring the media from my Panasonic HDD consumer camera:
–Import the file(s) into my consumer NLE (Magix Pro 14) on my OLD laptop, then render that video out as either an AVI or MPeg (depending on how ‘nice’ I want it to look).
–Use this rendered footage on Sony Vegas.NOW. . .
Keep in mind that it is my OLD laptop that has both ‘magix’ and Sony Vegas 7 installed on it; my new laptop has Vegas 9 64-bit at this moment.
I rendered some footage from my HDD cam as AVIs on my old laptop, then checked it out on Vegas 7 to make sure it’s good to go. I then took the external hard drive that the footage was rendered on, and began to try and edit on Vegas 9 on my new laptop, and all I get is the audio. No video recognized. . .nothing!
This turned out to be really surprising to me, because Vegas 9 is able to recognize AVIs from another, crappier video camera that 7 can not. Owing to this, I was under the impression that Vegas had expanded its list of recognizable codecs.
So, ultimately. . .what’s the deal? Why can 7 recognize the video, but 9 cannot?
I have found a way to remedy the matter (for the time-being) by taking the rendered AVI, importing it into 7, then RErendering it as an AVI that can be used with 9, but this is, uh, really, really cumbersome, a slow moving process, space and time consuming, and makes it difficult to keep track of files.To let you know: I have looked into downloadable freeware that transfers mod files–the kind my panasonic makes–into AVIs, but I’m not too trusting of any of that right now. (Unless someone has a good lead for me.)
Mostly, I’m just vexed on the issue, and am looking for ways that it can be fixed. . .I just purchased 9 not too long ago, but would’ve stuck with 7 if I could have run it on a 64-bit system. Now I’m wondering what’s going on with the good people at Sony.
-
7 Replies
-
My guess is that you are missing the codec that Magix installed. Get the free program “GSpot” (https://www.videohelp.com/tools/Gspot) and it will tell you what codec was used to encode the AVI file.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Thanks for the link to gspot. As for the codec from Magix, I doubt that’s entirely the case:
–First, I went ahead and installed Magix on my new laptop–the one with Vegas 9–a while back.
–And second, the AVIs on my old laptop–the one with Vegas 7–won’t play on the windows media player (only audio), while it all shows up on Vegas 7; also, AVI video from another camera–a crappy one–will show up on the local windows media player, but not Vegas 7 (but it DOES show up on Vegas 9).Will do some more snooping around to try and figure out what the deal is. . .try and make some sense of it all. Stupid codecs.
-
…also, AVI video from another camera–a crappy one–will show up on the local windows media player, but not Vegas 7 (but it DOES show up on Vegas 9).
Vegas Pro 9.0 added native support for MJPEG files and MJPEG is a favorite video format of still image cameras that also shoot video. I’m guessing these files use the MJPEG codec but you really need to use GSpot to solve this problem.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Ran the AVIs through gspot–sorry it took a while; I have trouble feeling comfortable downloading ANYTHING that sounds, uh, ‘sexual’–and found out that it’s an old codec called “indeo” which is not supported on any post-XP system. (And it is not guaranteed to work even if you purchase it.) So. . .c’est la vie, aside from the usual frustration I’ve encountered with codec issues.
As for the crappy camera I was talking about, it came as part of a “Digital Editing for Dummies” pack I bought a couple of summers ago at a Wal-Mart in Wiggins, Miss.
Check it out:
https://www.technooutlet.com/cx32390.html?source=GGAN
I’m not going to rave on and on about it, but it was what introduced me to the wonderful world of digital editing and media, and I still like the junky camera that came with it more than anything else I own.
Off/on the subject, is there any reputable freewares out there you can suggest for transferring MOD files to AVIs (compatible with Win 7 systems)?
-
–and found out that it’s an old codec called “indeo” which is not supported on any post-XP system. (And it is not guaranteed to work even if you purchase it.)
Your best option would be to find an XP system and convert these files to M-JPEG so you can edit them in Vegas.
I’m not going to rave on and on about it, but it was what introduced me to the wonderful world of digital editing and media, and I still like the junky camera that came with it more than anything else I own.
It sounds like you got your money’s worth from it. My first digital still camera was a JamCam. It took the most horrible 640×480 images but I was hooked on the idea of snapping away and immediately seeing the results on my PC without having to develop film. I don’t regret buying that JamCam one bit.
Off/on the subject, is there any reputable freewares out there you can suggest for transferring MOD files to AVIs (compatible with Win 7 systems)?
You don’t want to do that. MOD files are MPEG2. You just want to make them MPG files so that you don’t loose any quality. You can try renaming the extension or the camera might have come with a utility to convert them to MPG. The lesson learned here should be, “Don’t buy any camera from any manufacturer that uses a proprietary format!”
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Transferring the files to m-jpegs seems like a good idea, even though I’ve already transferred the files I need via Vegas 7 (on my old XP machine) for my current project to AVIs that are recognizable to Vegas 9.
But on the subject of M-jpegs, does that mean that Vegas 9 can also ‘natively’ work with video footage coming off of DSLRs?
As for other codec issues, I’m just going to have to meet them as they come. Although, I’m going to say, right now, that I think Sony is shooting itself in the foot in not accommodating P2 media. I originally was more enthusiastic about Vegas because it seemed to be more of a ‘workhorse’–more versatile and durable–than other NLEs; but now I’m beginning to get daunted by what seems to be its limitations, while other NLEs are making it a point to be compatible with other software(s). I recently had to forfeit a chance to edit a fairly ambitious project owing to the fact that it was shot on a Panasonic P2 camera. I know there’s a plug-in (or whatever) that can transfer the material to be compatible with Vegas, and the producer of the project still wants me to be involved. . .but that doesn’t negate the fact that things can be needlessly cumbersome.
Don’t get me wrong, because I’m still a Vegas enthusiast, definitely over FCP and Premiere. In fact, it’s still my ambition to try and edit an entire feature using Vegas. But until Sony resolves some of these issues, I can (almost) understand why people aren’t looking for Vegas editors. And that’s something I CHOKE on to admit (because I hate Apple).
I’m glad, though, to see that I’m not the only person who started with humble beginnings–i.e., with crappy little cameras. Wish I was only more of an editor/filmmaker/videographer to validate my enthusiasm for this approach. Not to wax nostalgic on your time, but I broke all the rules back then: editing (w/a consumer NLE until I bought Vegas 7) on a 1-Gb laptop, and rendering onto the 5400-rpm c-drive until I ran out of space. . .and I still can’t say those videos suffered as a result. In fact, I’d say that the creative freedom that not having to bug with technical issues allows adequately compensates for amateurish attributes. Or at least how cool it is to know that you can make a whole ‘movie’ simply with what you’re carrying on your back. . .which is, again, one of the reasons I wanted Vegas in the first place.
-
But on the subject of M-jpegs, does that mean that Vegas 9 can also ‘natively’ work with video footage coming off of DSLRs?
Vegas Pro 9.0 has native support for M-JPEG so any video that uses M-JPEG can now be edited in Vegas without the need for a 3rd part M-JPEG codec. You still need a 3rd part codec to write M-JPEG but they are pretty cheap.
Although, I’m going to say, right now, that I think Sony is shooting itself in the foot in not accommodating P2 media.
They do accommodate it with the RayLight plug-in that works perfectly fine. There are legal reasons why Sony cannot support P2 natively so it’s not a matter of shooting themselves in the foot. Sometimes companys just can’t get along.
~jr
http://www.johnrofrano.com
http://www.vasst.com
Reply to this Discussion! Login or Sign Up