FCP vs Vegas

Spot|DSE wrote on 6/7/2004, 7:42 PM
Finally saw something that makes Vegas substantially superior to FCP on output....I know it's superior on workflow and capability, but output has always been arguable in DV whether one is better/different than the other.
Do slow mo at 20% in both. Vegas is WAY better at interpolating the additional frames. With one render, Vegas was clearly better than FCP doing the same video. I saw this with the same Artbeats clip in Vegas and FCP. Was at B&H today and had a challenge regarding Vegas vs FCP with a customer there. . The slow mo thing was something that the customer/client was totally sold on FCP being 'better than anyone's" and I didn't have a solid answer because I'd never compared them, so took the risk of seeing for myself with a bunch of people standing there looking on. (including all of the guys from Burning Spear) Was a little nervous. Vegas beat out FCP's interpolation, thank heaven.

Comments

busterkeaton wrote on 6/7/2004, 9:12 PM
How did everyone react?
JasonMurray wrote on 6/7/2004, 10:18 PM
I slowed a video down by a massive amount recently and was extremely impressed with Vegas' interpolation, too ... rock on Sony :)
briz_dad wrote on 6/7/2004, 10:51 PM
Now if they could just get that "stills" bug fixed!!
Spot|DSE wrote on 6/8/2004, 6:00 AM
What "stills" bug? If you are referring to the one in a very long thread....that's an intermittent that no one can pin down. I've got some 2500 x 2500 stills that I've thrown on the TL w/no problem....all bmp's, which are the reported problem format. All the beta testers were asked to look specifically for this problem. Whether it's been nailed down, I can't say.
Anyway...
The folks standing there were really surprised, and there was a general feeling of "DAMN!!" in the small area. (don't know if you've seen the B&H demo area, but it's quite small in the grand scheme. Add 10 guys standing there, it's jammed.)
Anyway, the other really cool thing Vegas does well is removing pulldown on the fly. Easiest way to demo that is to move frame by frame and show a new frame starting at 00:23. FCP can't do that, either. Nor can Premiere. Or Avid Express.
JJKizak wrote on 6/8/2004, 7:09 AM
My .02: I believe a lot of these problems are memory related using the newer dual buss setup. With memory that is not totally compatible anything can happen anywhere but but it will occurr at the same points every time. Problem is who can afford to keep changing brands of memory and messing with the voltages?

JJK
Spot|DSE wrote on 6/8/2004, 7:23 AM
I'm confused by your post?
daryl wrote on 6/8/2004, 7:29 AM
RE the still bug mentioned earlier in this thread, I'm getting confused now. I got an email from Sony with an updated .dl some time after reporting the same "still problem"l. I was told to replace the original dll with the new one and try my still again, it worked beautifully, problem disappeared. Someone was on the right track. My problem was with png instead of bmp, but the exact same error and behavior. I'll try to find that email.
Jay Gladwell wrote on 6/8/2004, 7:34 AM
Did that "fix" get sent to everyone? I've not received such an e-mail with any .dll attacked. Then again, I haven't had the reported "still bug" problem, either. Yet.

J--
JJKizak wrote on 6/8/2004, 7:35 AM
My reply was about the "still" problem.

JJK
DataMeister wrote on 6/8/2004, 9:39 AM
Can we get an explaination of the pull down demo? What's happening there that I might have been taking for granted? And what happens on the other brands?

JBJones
daryl wrote on 6/8/2004, 10:12 AM
Drat, I don't have the original email, but the dll was stl2plg.dll, it's in a subdirectory of vegas 5.0.

It fixed my still problem, and I do remember replying to Sony telling them that it worked. From that point on, mystery to me.
GmElliott wrote on 6/8/2004, 10:22 AM
Oh yes it's a very small area- like small cubicals.

I wish I was there today- I would have loved to see the look on the Mac Elitists faces. :)
BJ_M wrote on 6/8/2004, 10:51 AM
you could hit most of them in the head with a 2x4 and it wouldnt make much of an impact anyway .....

but to be fair -- fcp has some great features ... but vegas excels in many many areas ..
Steve672 wrote on 6/8/2004, 11:41 AM
Pardon for my ignorance but what is "pull down"?

Steve
BJ_M wrote on 6/8/2004, 12:06 PM
http://www.zerocut.com/tech/pulldown.html

or

http://www.dvdfile.com/news/special_report/production_a_z/3_2_pulldown.htm

pulldown explained
Joe White wrote on 6/8/2004, 12:42 PM
I got the .dll too but it did not solve my stills problem, which is ongoing. Havent been able to use 5.0 since i bought it on Release day.
Steve672 wrote on 6/8/2004, 1:37 PM
BJ M excellent sources, thank you.
I presume then that this pull down process takes place when you are converting 30fps video to 24fps since Vegas does not deal with "film" but with video i.e. you want the "film look". (or, can you record video at 24fps?)
I hope I got this right?

Steve
BJ_M wrote on 6/8/2004, 4:19 PM
pulldown is 24p (really 23.976) to 29.97i

Inverse Telecine is 29.97 to 24p (really 23.976)

vegas can edit directly in 24p

and can automaticly remove the pulldown (Inverse Telecine) where it has been applied -- only if it is the standard 3:2 pulldown (there are other patterns)...

vegas handles this perfectly ...... only thing it cant do (nit picking here) is create a 24p cut list for film from a 29.97 video ....

i.e. it doest handle the selection of BB or AA from first hole/mark in film and transribe the exact frames in the cut list ... well anyway the way i know how from avid film ... but it CAN generate a pretty close list anyway.... working in only frames and 30p or 24p source material (frames) helps a great deal and can produce exact cuts and frame numbers ..



RexA wrote on 6/9/2004, 12:54 AM
PEEVE POST

Could you people who do not view this forum with 'Threaded View' please try to remember to make your posts Only while you have the message that you are replying to active in your top message display window.

Threads often get hijacked this way and, if nothing else, it is confusing.

END OF PEEVE