5D2 footage in Vegas vs....

Comments

kkolbo wrote on 5/15/2010, 9:13 AM
I guess I should just archive my post and copy and paste my opinion, but here we go again.

Different NLE's and tools each have different strengths and weaknesses. There is a best tool for each task. Why can't we just post things like,
"Hey, I am getting great results in PPCS5 with my 5D footage. Isn't that great."

Instead we want to whine about how Vegas doesn't fit our needs today. I think it is professional to to say that I have found a better performing solution for condition X, but to whine that something doesn't do what you want it to just gets old.

Professionals who need to complete tasks in the best fashion and on-time tend to have a tool box and reach for the tool that does the task best. In software, that changes constantly. If performance with small file size and editing in a lossey native format is your priority, then use CS5. It is a capable and exciting tool. Some great new stuff came out with CS5. If you also like their workflow then there is no shame in using it. Honest, it is not an insult to the posters on this board.

It doesn't have to be framed as an insult to Vegas. There are many tasks that Vegas does better than CS5 and in the reverse. There are times when I use Vegas for a format or task where the playback performance sucks because I want something else that Vegas brings to the table. Other times I use one of the three other NLEs that are on this laptop.

Can we try to approach things with a little positive attitude and celebrate technology advancements without whining?
LarsHD wrote on 5/15/2010, 1:14 PM
?
rmack350 wrote on 5/15/2010, 3:55 PM
Well said, keith.

Lars, yes, Event Pan/Crop will let you zoom in on the clip, as well as pan across it. Track motion affects the track rather than the event and would be better for doing PIPs. The 3D mode would let you flip it around and move several around in 3D space. Track motion will not look good if used to zoom in on something, although it lets you do it.

This is a little inconvenient because sometimes you really would like to zoom in on a sequence of events, but that's the way it works.

Rob
FrigidNDEditing wrote on 5/16/2010, 2:22 PM
Lars,

Re: Epic only working in 32bit Vegas...

I would suggest installing the Epic software, and then opening your project file in Vegas 9 32 bit and see if it helps, because if the CPU doesn't have to work as hard decoding the h.264 mov files, then it can use more of its resources to get you better playback on the other stuff going on.

Also see my post in resolution bug, about 3D positioning consuming large amounts of resources in vegas for as long as the track runs (eg the entire length of the project), and the pan/crop method being much better, and my offer to look at a truncated version of your trouble project(s) to help you get some issues resolved.

Dave
FrigidNDEditing wrote on 5/17/2010, 2:13 PM
just bumping to make sure LARS sees this.
LarsHD wrote on 5/17/2010, 2:28 PM
1. So Epic plays 5D2 files 100% smooht and it does this even when running two video streams. like during dissolves?

2. I don't have the 32 bit version installed. is it a good idea to start working in 32 bit? I can't open all my previous projects? I can't use as much RAM. Is this the right way to go you think?

3. This Epic-thing: iit will not remove performance in Vegas in regards to moving text, 3D alpha etc will it?

4. *exactly* what is Epic doing?


Lars
FrigidNDEditing wrote on 5/17/2010, 4:49 PM
Lars, 9.0 32bit and 64bit are interchangeable so long as they're the same version eg. a, b, c, d, e, etc... . A veg that was used in 9-64bit, can open in 9-32bit. Unless you're saying that you're consuming so many resources with your projects that 9-32bit just can't handle it, and everything that 9-64 has, 9-32 has.

Whether it's a good idea or not is entirely dependent on whether you can get an adequate workflow going with the Epic trial.

I guess I think that with as much time as you have spent posting on the forums about the differences in the Vegas workflow and trying to find different workflows, you would have time to test out 9d/e 32bit Vegas with epic.

Dave
LReavis wrote on 5/17/2010, 4:55 PM
"2. I don't have the 32 bit version installed. is it a good idea to start working in 32 bit? I can't open all my previous projects?"

You'll be able to open all your 9.x 64-bit projects with, say, 9c-32 - and, presumably, 9e-32; and your V8-32 projects in, say, 8c-32 - IF you install the 32-bit versions of your plugins. I've been editing for quite some time now in 8c . . . but I never render in 8c because few of my complicated projects will render all the way through in 8c. Instead, I render in 9c-64 (maybe 9e, now), unless I need to deinterlace, in which case I use 9c-32 (because I don't have any good plug-in to deinterlace in 64-bit versions of Vegas).

I have consistently had 100% reliable performance from this approach - both for editing and rendering. You'll need to install 32-bit versions of your plugins, but after that one-time nuisance, then you can open whichever version of Vegas is needed for your current task, at will.

If you do use a 32-bit-only plugin that's needed for rendering (apparently that would not be the case for Epic, which I presume only works for smoothing out the editing problems), then at least render in 9c-32 or 9e-32 instead of 8c (I've had red frames, etc., while editing in 9c; maybe that's cured with 9e-32). If rendering stops, reboot, then uncheck everything in the view menu; go to Preferences and set RAM preview to 0 and Rendering threads to 1. It'll be slow rendering, but you'll have plenty of RAM and CPU cycles left over to work on other projects, including other Vegas projects.

Incidentally, I'm pretty sure that if you install your 32-bit plugins for 8c, they'll also show up in 9c-32 without further work on your part.
LarsHD wrote on 5/18/2010, 9:54 AM
It seems like getting Vegas to do things require a utility plug in here, a freeware there, and a workaround here and some patience there etc.

I can't justify the time it takes to deal with this. Parts of the interface is noce I suppose. Having spent more and more time with other NLE's lately I can't say that thiongs are faster in vegas or easier etc. Only thing I see is that Vegas is plagued by bugs, crashes and problems. It feels old and unreliable and there are no indications of anything getting better.

Again I think I'm leaving Vegas - this time with more thorough experience of the alternatives. Nobody can blame me for not having enough patience...


Lars
kkolbo wrote on 5/18/2010, 10:06 AM

I am surprised we have not seen this long before. Vegas is not working for you. In your workflow it is not the optimum. No shame in that. I think over time, you will discover that if your workflow changes, the other NLEs will expose as many needs for plug-ins untilities and work-arounds. Heck, you can't do much in some of them without plug-ins. It is from that experience that most of the older folks here derive their surprise that you haven't been using something that better suits you. They all have warts, but none of them does it all. You just use what works for what you are doing..

Do well and when you are doing something that Vegas fits better, come on back for that. In the mean time, make great video on whatever platform does it best for you. (we call that voting with your feet)
TheDingo wrote on 5/18/2010, 11:04 AM
Hi Lars,

I work on two different workstations, one uses a Q6600 CPU and the second uses an i920 CPU, and there is a huge difference in processing power.

The i920 CPU seems to process video at about 3 - 5 times the speed of the Q6600 for most of my projects, so you might want to look at a motherboard/CPU upgrade if your budget allows for it.
John_Cline wrote on 5/18/2010, 11:07 AM
Lars, are all of the Vegas "bugs, crashes and problems" you have experienced been on an installation of Vegas on one specific machine? Judging by the number of individual threads you have going on the forum, you seem to be having many more issues than any other forum user. I think you should at least consider that it could be an incompatibility with your specific hardware.

I'm sure you don't want to hear this but with the exception of a slow loading problem I'm having with Lagarith .AVI files, I'm in Vegas all day, every day editing HD video from a variety of sources (including video from Canon DSLR cameras) and Vegas just hums right along.
FrigidNDEditing wrote on 5/18/2010, 5:31 PM
I have to confess a certain amount of frustration in trying to help you lars, and with offering to even look at your project files and giving you a means of getting a working solution even if it's in 32bit. I am not entirely sorry to see you move on ( if you do indeed move on ). My offer still stands to look at a project and show you a correct workflow, but if you move on to another piece of software that you can do your style of workflows in, then that will be just fine with me.

Dave
farss wrote on 5/18/2010, 6:44 PM
After spending many hours talking to Lars into the small hours of the morning I can assure you his decisions are not taken lightly.

Everyone of his test case I've run produce the same conclusion, there's some serious issues inside of Vegas. These have been escalated as far as possible within SCS. Perhaps someday thanks to Lars, Vegas will become a better product. In the interim like the rest of us Lars has client's needs to meet.

One of the biggest issues I see facing Vegas going forward is there's a core of users, myself included, who've come to love the cute cuddly nature of Vegas. We see it like a mother sees her child. We make excuses for the bad behavior. We should be much more demanding that things just work, we could be loving Vegas to death by our spin doctoring, workarounds and excuses.

An observation occured to me. The average age of Vegas users seems to be somewhere in the 50s. Judging by the audience at the CS5 roadshow Adobe's client base would have an average age in the 30s. Many of us have come from decades of dealing with technical challenges in the video and audio world. We're used to patching things together. There's a very different ethos in the younger generation in our industry, they demand tools that just work, they want to take their creativity into video, print or the web. Regardless of how well Adobe may be doing things they are clearly focussed on meeting the needs of up and coming creative people rather than video engineers.

Bob.
Cliff Etzel wrote on 5/18/2010, 7:10 PM
Well said Bob.

Cliff Etzel
Solo Video Journalist | Micro Documentary Film Maker
bluprojekt | SoloVJ Blog
--------
Desktop: OS: Win7 x64 | CPU: Q9400 | Mobo: Intel DG33TL | 8GB G.Skill Dual Channel RAM | Boot/Apps Drive: Seagate 160GB 7200RPM | Audio Drive: Seagate 160GB 7200RPM | Video Source: WD Black 2x750GB RAID 0 | Video Card: nVidia GeForce GT 220 1GB

Laptop: Dell Latitude D620 | C2D 2.0Ghz | 4GB G.Skill RAM | OS: Win7 x64 | Primary HD: WD 320GB 7200RPM | Video HD: WD 250GB 5400RPM
Rob Franks wrote on 5/19/2010, 3:54 AM
"Everyone of his test case I've run produce the same conclusion, there's some serious issues inside of Vegas."

Well I would question the term "serious issues". As with any other NLE Vegas does have "issues", and a showstopper is what I would call "serious". But it seems to me that LARS problem may well be cleared up with this suggestion here:

"Hi Lars,

Lars is pushing some "serious" codecs and bitrates through his machine which needs "serious" power, and he's trying to do this in a native state. So while the Vegas preview system does need updating, I believe Lars himself needs to stand up and take a bit of responsibility for this.
farss wrote on 5/19/2010, 4:52 AM
"Well I would question the term "serious issues". "

OK, I'll escalate it to showstopper. I'm NOT talking about playback performance. I'm talking about Vegas duplicating frames in the rendered output. Not only was I able to duplicate Lars's tests I found the same issue in another users video a few weeks ago.

This issue usually gets dismissed as being the fault of the playback system. The other user was being told the same thing by others here, no one actually took the time to carefully compare his source and rendered output.

Bob.

CClub wrote on 5/19/2010, 5:51 AM
" There's a core of users, myself included, who've come to love the cute cuddly nature of Vegas. We see it like a mother sees her child. We make excuses for the bad behavior. We should be much more demanding that things just work, we could be loving Vegas to death by our spin doctoring, workarounds and excuses."

I have immense respect for your technical prowess, Bob, but I don't understand why professionals such as yourself allow yourselves to get so emotionally attached to one particular tool in your toolbox as if it's a child. And I think that's why you become apologetics for people like Lars, who has been threatening to leave Vegas for months now, and spends more time posting than rolling up his sleeves and editing already. So leave Vegas, who cares? If Vegas doesn't meet my needs, I'd do like some of the [very intelligent] Vegas users who also have other tools/NLE's in their toolbox. Lars is like my son who always gets upset when he can't fix something in his apartment... but he only has a flathead screwdriver. So buy another tool already and stop complaining. Who would be offended if Lars used PPro or FCP? Every so often someone comes along on the forum why posts like mad for a few months, draws attention to themselves, and threatens to leave Vegas, and wants us all to convince them to stay. You didn't give birth to or legally adopt Vegas, you bought it online. You don't have to go to court to legally emancipate yourself from Vegas... you just uninstall and move forward into the bright sunshine of a new day. Here's the procedure: Start, Control Panel, Uninstall. Type in keywords "download Premiere Pro" and you're free.
farss wrote on 5/19/2010, 6:31 AM
" I don't understand why professionals such as yourself allow yourselves to get so emotionally attached to one particular tool in your toolbox as if it's a child."

That's an interesting question that applies to users of every NLE. If you ever come up with an answer let me know because it's escaped me too.

Maybe it's because we probably spend more hours with our NLEs than we do with our family. Sad state of affairs.
I did have a conversation with a couple of ex editors. They agreed, being an editor is not an overly rewarding career, the burn out rate is very high. Divorce rates are high, stress levels are high, lifestyle related diseases are high. I think almost all of us here do more than just edit which is a good thing for our state of mind. I cannot imagine spending 8 hours per day, 40+ hours per week in an edit suite on a rotating roster. Mate of mine did it for a decade.

Bob.
CClub wrote on 5/19/2010, 6:43 AM
That's a fascinating answer, and I very much appreciate your candor. Wow. Those insights are worthy of a documentary of its own... although I'm not sure who would want to watch it without a large bottle next to them for Comfort!
Guy S. wrote on 5/19/2010, 11:22 AM
Hi Lars, I have noticed that Vegas dislikes anything in a QuickTime wrapper. We have a FireStore direct to disk recorder that can record miniDV files in the native format (.dv), or in the AVI or MOV wrappers. The underlying file and CODEC is the same regardless of the wrapper.

Vegas plays miniDV files in the AVI wrapper just fine. The unwrapped .dv files played somewhat poorly, and the .mov files barely played at all. Further, after using 60 or so of these files in a project, Vegas had a propensity to freeze.

It was suggested that I use a freeware program to re-wrap the files from .mov to .avi. Because there was nothing done to the actual video data (no transcoding), re-wrapping 100 files took just seconds. This turned out to be a fast, easy, effective solution and I am wondering if it might be possible to do this with your 5D footage as well.

I realize that Premiere doesn't need to do this, but merely re-wrapping the files shouldn't be burdensome, and I'm assuming that you'd prefer to use Vegas else you wouldn't be posting.

Does anyone know if this might work with 5D footage?

One other thing: I strongly suggest upgrading to a Corei7. My workstation is roughly equivalent to yours (2- dual core Xeons @2.66Ghz) and 64-bit OS. And while it's workable, the systems I saw at NAB were playing AVCHD from the timeline quite smoothly. NOT realtime like Edius or PP CS5, but at least 100% better than what I have now.

BTW, we will be upgrading from CS3 to CS5 and I'm interested in how PP CS5 is working out for you. Timeline performance aside, is the general workflow usable? Anything you particularly like? I still have some decidedly un-fond memories of Premiere...

Good luck,

Guy

Jeff9329 wrote on 5/21/2010, 11:52 AM
Hi Lars,

While there is a significant difference in CPU power between the 6600 and i920, it's not as large as you describe. In a case like that the Q6600 was probably on a poor motherboard/other issues. A high end motherboard is just as important as the CPU. Of course, Im not saying to change out a 775 MB.
mvb wrote on 5/28/2010, 10:50 AM
Lars,

The Vegas 9/64-bit version of Epic is in Beta right now, should be released next week, see http://twitter.com/dvfilm

MemoryvilleMan wrote on 5/28/2010, 4:38 PM
Hey all you gurus... long time no post. This is probably going to be long so I'll apologize now. I haven't posted in long time, because frankly, I only cruise forums, in general, when I have a problem. I'm still using Vegas 7, because the relatively few projects I've been doing over the past few years are shot in DV with my good ol VX2100 and PD170, and edited on my good ol Dual Xeon. It's all very "good ol" and I have a trouble-free workflow, no problems to speak of.

However! I'm considering (again) doing weddings on the side (which I actually love doing), but I've always said I will only pursue clients with a decent budget, and provide top notch production values... fewer gigs, but more $ per gig kind of paradigm. Well, today, that obviously means HD.

This thread has grabbed my attention, since I'm researching a new rig, and the AVCHD issue is part of the new landscape that I I need to consider at length. But in reading the thread, this general concept of how much Vegas is or is not "software that just works" really resonates with me.

When I got into video, it was late 90's-2000ish, Digital8 ruled the consumer arena, miniDV was coming on, NLEs were just becoming practical on the desktop (PC... I'm a PC guy and that's that). I got some Pinnacle crap, with a cheesy breakout box with a firewire port, and made my first vid. I was hooked, but hated the software. It was clunky, crashy, proprietary hardware locked up, terrible real-time capabilities, limited track count, fat... just lousy. I knew this, because I was coming from a DAW background, and had already been using SF SoundForge for all my stereo work, and knew how smooth, stable and fast SF products were compared to everything else. I immediately started reading about Vegas and Premiere, and whatever else was available, and it was obvious that SF was doing what they had always done: made uber-stable software that performed death-defying feats of editing that made other software on the same platform look like it was years behind. At the time, Premiere couldn't even do real-time transitions without prerendering, and I'm pretty sure had severe track count limitations, and all that.

I bought Vegas Movie Maker on sale (or whatever they called the consumer version of Vegas 2), and was astounded. I could just drag clips from any source onto the timeline, slip edit, make auto crossfades, lay on some titles, play with opacity and compositing, work with sound the way I was used to... It was heaven. It never crashed. It was real-time enough. I could monitor live via firewire through the cam back to TV. Wow...

I did one project and immediately went out and upgraded to Vegas 3, which had just come out, and I think introduced velocity envelopes for the first time. Are you kidding me? The filters and plug-ins that came with Vegas were great tools... stuff that users on other platforms were paying for separately. You could stack them with ease, and they always worked smoothly. The way Vegas handled audio compared to the competition was light years ahead... basically getting Sound Forge built into your NLE for free. But above all, in real-time, things were fast, fast, fast compared to pigs like Premiere.

On the (relatively few) DV related forums back then, folks were telling these crazy tales of woe trying to get Premiere and other solutions to work worth a damn, on computers that were 5 times as powerful as mine. On the SF forums, we were all one big happy family, gently scoffing at all those chumps out there struggling with their much more expensive, less effective workflows. Problems existed in Sonic Foundry Land, but it was always fringe behaviors, and SF quickly patched things that proved to be internal to the software.

By 2003 or so, I was starting to do the occasional commercial job. Always DV, always low or no budget. A lot of home videos, of course. But I've basically always been an advanced hobbyist... never much money in it for me. I've stuck with Vegas until my most recent license for Vegas 7 (as I said, haven't needed to move up since my whole DV setup is circa 2007, and I've seen little compelling reason to upgrade to Vegas 8--although that was when they FINALLY put in a a better titler, I understand... that I wanted).

But since the Sony acquisition, I have slowly become frustrated. I still love Vegas 7 for the reasons I've always loved Vegas. It's like a refined version of Vegas 3, but only a few core functionality changes appeared (like 3D track motion and subclips). But while I love USING Vegas, in recent years, it just seems like it's become kind of isolationist: it may as well not even exist, apparently, if you're a plug-in creator. And in the world of modern HD, although I admit I'm just now getting serious into the research, It doesn't seem to be keeping up with the Jones' in terms of it's famous speed, compatibility, and basically trouble-free operation. For a general example: I've always HATED the chroma key filter. I don't think it's changed one iota since Vegas 2. I've experimented, read countless how-to's relating to getting a good key, have figured out that Chroma Blur prior to keying works wonders, but can only do so much. Yes, I know that DV sucks for keying. But cripes! During the second half of this decade, when you talk about down and dirty commercial production work, green screen is implemented in half of what you see. It's just completely mainstream. You'd think in 10 years, such a critical tool for the average editor would have been enhanced a bit. When Serious Magic came out with their Ultra 2, I downloaded the demo and was blown away. It could produce fantastic finished keys with all it's fancy algorithms and knobs. I thought, "ok...either Sony or a third party is going to see the bar has been raised, and I'll get something that will fit right into my Vegas workflow any month now." Nuh-uh. To this day I don't see any way to get a clean key without buying something stand-alone, and actually, I'm not even sure what that would be (again, hobbyist - don't have a compete handle on what's out there). I guess Adobe gobbled up Serious Magic. In fact, I've become so jaded about almost any plug-in that I get wind of never being available for Vegas that I've pretty much stopped paying attention to any of them.

And After Effects... It seemed obvious to me years ago that all the post production trickery that we were starting to see on the tube, all the compositing, motion tracking-centric techniques that poeple were twisting out of conventional editors was becoming mainstream. When AE appeared, I just KNEW that Vegas would either develop their own stand-alone FX tool, or expand the Vegas built-in toolkit to address the modern techniques.

I guess what I'm saying is, once upon a time, the only way a casual (or pro) desktop DV enthusiast could get broadcast level product out of his PC by tossing stills, WMV MOV AVI files, MP3 audio tracks or "what have you", with fantastic features, lightning fast speed, and truly amazing stability, was to use Vegas (or spend thousands with the competition to achieve the same abilities). In a nutshell, "it just works". Nowadays, Vegas does seem a bit like an "old school" tool, to me -- kinda like what Bob is saying. I'm not the kind of person who wants to use what everyone else is using because it's cool... but I have found over the years that using the computer products that are "popular" can be a very good idea because of the resources that tend to be available for the "popular" stuff: more forums, add-ons, tweaks, and usually more reliability because of all that support and feedback. It just flat-out bugs me that Vegas has not become "The" tool that everyone is using and writing plug-ins for the way PP, AE and FCV seem to be, and the way I always thought Vegas would be. It bugs me that there seems to be a lot of chatter about it not playing well with this kind of file or that kind of codec or what ever.

ALL THAT BEING SAID... (and look at all that... jeez, sorry) I'm positive that I'll be upgrading Vegas when I setup the new rig, because A) I've "come to love the cute cuddly nature of Vegas". Yup, it's like going into the womb, it's so comfortable to me - again, just a hobbyist at this point - and I know Vegas inside and out after a decade. B) cheap to upgrade - out of pocket for me. C) I think jumping into the forums after all this time invariably makes one think that a product is just a train-wreck, since you basically are just seeing the gripes. But I can tell by the posts that many HD Vegas 9 users are cruising right along with a variety of source material, just as I always have in my DV world, without a hitch. And D) Really, the things I wish I could do in Vegas that I can't, are truly the domain of a program like AE, and I'm just going to have to go down that software path if and when I want to do more hip and happnin', motion trackin', super 3D commercial project work.

Sorry If I'm a bit out of date - trying to rectify as we speak - but I really wanted to let off a little steam and back bob up on a few of his sentiments.

I'll be researching the forums for a while, but if I can't find my all my answers regarding HD, I look forward to benefiting from the always sage advice from this crowd.

later
Graham