.
.
LarsHD
wrote on 2/10/2010, 11:59 AM
Comments
PerroneFord
wrote on 2/10/2010, 12:39 PM
You use a tool until that tool no longer meets your needs. How many years have you used Vegas where you didn't feel this was an issue? But now, it is for you. So you move to something where it is no longer a problem.
No point in ranting about it. It just creates ill will as it did toward me when I highlighted why Vegas was no longer a tool that worked for my needs.
Just move it along and buy what you need. FCP is good. I prefer Avid. Maybe Canopus would work for you and it's much cheaper than both. Whatever works.
No point in ranting about it. It just creates ill will as it did toward me when I highlighted why Vegas was no longer a tool that worked for my needs.
Just move it along and buy what you need. FCP is good. I prefer Avid. Maybe Canopus would work for you and it's much cheaper than both. Whatever works.
Jay Gladwell
wrote on 2/10/2010, 12:50 PM
Perrone, did I read somewhere that Avid only works in the 24fps format?
LarsHD
wrote on 2/10/2010, 1:13 PM
.
farss
wrote on 2/10/2010, 1:13 PM
I had a phone call from another Vegas user yesterday and he is having the same kind of problem working with 4:2:2 SD on his external monitor. As you rightly say clients expect to see their video before it goes to air and despite upgrading his PC thinking that was the problem he is unable to show them the results of their considerable expenditure on crew, talent and Sony cameras and VCRs.
This goes beyond the question of users simply jumping ship. If Sony's broadcast division sees Vegas as having a negative impact on the considerable value of the brand name in the industry something is going to have to happen.
Bob.
This goes beyond the question of users simply jumping ship. If Sony's broadcast division sees Vegas as having a negative impact on the considerable value of the brand name in the industry something is going to have to happen.
Bob.
LarsHD
wrote on 2/10/2010, 1:17 PM
.
Yoyodyne
wrote on 2/10/2010, 1:19 PM
Lars I feel your pain but I think Perrone makes a good point. Vegas preview issues are kind of built in - it's a trade off. I've had to adjust my workflow a bit because of the preview quality and it is frustrating that other products offer a road to bombproof full framerate/full res preview monitoring. By the time Vegas can preview smooth HD everything will be 4k, then 8k...
I've had a few posts venting my frustration but I can see the upside too. I do a fair bit of work at really odd frame sizes (like 2500 by 720) and Vegas can handle it. It can play and preview damn near anything. This makes my life a lot easier.
When previewing I usually use the video preview monitor and it gives acceptable playback on auto. Clients are cool with it and I give them the "nothing is rendered so this will stutter/not be full res" spiel. I make sure to do a bunch of ram preview full res stuff for them. They do like how fast Vegas works, they are always amazed I can do stuff on the timeline while it's still playing.
If it's starting to be a deal breaker and is costing you money then it's time to think about adding a tool that fits your needs.
I've had a few posts venting my frustration but I can see the upside too. I do a fair bit of work at really odd frame sizes (like 2500 by 720) and Vegas can handle it. It can play and preview damn near anything. This makes my life a lot easier.
When previewing I usually use the video preview monitor and it gives acceptable playback on auto. Clients are cool with it and I give them the "nothing is rendered so this will stutter/not be full res" spiel. I make sure to do a bunch of ram preview full res stuff for them. They do like how fast Vegas works, they are always amazed I can do stuff on the timeline while it's still playing.
If it's starting to be a deal breaker and is costing you money then it's time to think about adding a tool that fits your needs.
Jay Gladwell
wrote on 2/10/2010, 1:35 PM
Okay, here's a thought...
Why doesn't Sony spin Vegas Studio off as a high-end prosumer NLE that works with everything but a peanutbutter sandwich and focus on building Vegas Pro as just that--a professional NLE that focuses on pro formats (and please don't start the flames about "professional" and what it means. Been there, done that, got the T-shirt).
Things are changing. It's time to move forward and upward. I want to see Vegas succeed!
LarsHD
wrote on 2/10/2010, 1:37 PM
.
farss
wrote on 2/10/2010, 1:41 PM
"Or they are wise and do *not* show this in action of fairs...?"
You got it.
Vegas is rarely mentioned by the Sony guys at their roadshows. Avid, Apple Adobe and Grass Valley are there to show how well Sony cameras work with their NLEs.
I only once saw a Sony AU presenter find Vegas mentioned on his Powerpoint slides and he looked lost as to what it was doing there.
Bob.
You got it.
Vegas is rarely mentioned by the Sony guys at their roadshows. Avid, Apple Adobe and Grass Valley are there to show how well Sony cameras work with their NLEs.
I only once saw a Sony AU presenter find Vegas mentioned on his Powerpoint slides and he looked lost as to what it was doing there.
Bob.
LarsHD
wrote on 2/10/2010, 1:48 PM
.
megabit
wrote on 2/10/2010, 1:52 PM
"( "Lars... what was that? In the middle of that panning it jumped and looked strange! Oh, that's just Sony Creative Software problem, the footage itself is fine, don't worry! "No, no - I want to see that the footage is OK! OK, let's exit Sony and play the footage "
The fragment I bolded out in the above excerpt of your post makes it clear that you're not talking about the 24/25/30p "inherent" stutter, but something caused by how Vegas Pro plays back its timeline.
Well, even though my recent experience with some other (very particular) Vegas issues are not positive, I must say I don't share your findings. On my system, playback of mxf Vegas timeline is as fluent as in VLC, WMP or whatever.
And I also did give AMC a try, and it wasn't any better (yes - it could hold the quality/speed with FXs and CC added, but that's probably thanks to the CUDA-GPU on the Tesla coprocessor I was testing at the same time).
Bottom line is:
We're talking software / hardware installations, which can differ dramatically between one particular user and another. In my case, stuttering of Vegas preview is not a problem at all.
The fragment I bolded out in the above excerpt of your post makes it clear that you're not talking about the 24/25/30p "inherent" stutter, but something caused by how Vegas Pro plays back its timeline.
Well, even though my recent experience with some other (very particular) Vegas issues are not positive, I must say I don't share your findings. On my system, playback of mxf Vegas timeline is as fluent as in VLC, WMP or whatever.
And I also did give AMC a try, and it wasn't any better (yes - it could hold the quality/speed with FXs and CC added, but that's probably thanks to the CUDA-GPU on the Tesla coprocessor I was testing at the same time).
Bottom line is:
We're talking software / hardware installations, which can differ dramatically between one particular user and another. In my case, stuttering of Vegas preview is not a problem at all.
Jay Gladwell
wrote on 2/10/2010, 1:56 PM
Piotr, I'm not sure I understand...
If the video clip stutters on system "A" in Vegas but does not stutter on system "A" in XDCAM Viewer, then what is causing the variation?
Why can one app show it smoothly and another not?
megabit
wrote on 2/10/2010, 2:39 PM
Jay, if only I knew the answer !
Let me answer your question with another one (I'm sure you will know what I mean):
- if a 5 mins long mxf clip can be played back right till the end with Edius or AMC, why does the same clip cause Vegas to eat some 24 GB of the virtual memory, on the same system A? While on another system B - also in Vegas - it doesn't consume too much memory, but stutters instead?!
All I know is that programming and implementing software is an art as much as it is a science....
Let me answer your question with another one (I'm sure you will know what I mean):
- if a 5 mins long mxf clip can be played back right till the end with Edius or AMC, why does the same clip cause Vegas to eat some 24 GB of the virtual memory, on the same system A? While on another system B - also in Vegas - it doesn't consume too much memory, but stutters instead?!
All I know is that programming and implementing software is an art as much as it is a science....
Jay Gladwell
wrote on 2/10/2010, 3:02 PM
Well, in your scenario all I can do is guess--because no two systems are alike? That much I understand (and that's all).
If we had the answers, I guess we'd be making the big bucks like the guys at SCS! ;o)
Based on my extraordinarily limited knowledge of these things, this is why I don't understand the reason computers and the like (in such instances) haven't moved toward a more uniform, standardization like broadcast TV did.