Thomas Roell
Forum Replies Created
-
[John Rofrano] ” [Thomas Roell] “The 59.94fps is kind of important. It’s the only way I can come up with to deliver good quality 29.97fps progressive for the web, and 29.97fps interlaced for a DVD.”
It’s certainly becoming more and more popular. I don’t understand how throwing away every other frame could be better than shooting the correct number of frames in the first place but that’s just me. ;-)”
Well the rational is quite simple. The footage is fast moving sports footage. Shooting in 720p @59.94 progressive allows me to get high quality for online viewing by simply throwing away every other frame. That’s essentially the same as having shot in 29.97fps progressive to begin with. If I want to deliver content on DVD, then I get the best quality by using every other frame for an even field, and the next frame would be the odd field. This way I can get more temporal resolution.
-
No disagreement about standards there. It just seemed to be very non-intuitive that something simple as “throw away every other frame” would trigger “smart resampling” given how much attention vegas pays to the 3:2 pulldown.
The 59.94fps is kind of important. It’s the only way I can come up with to deliver good quality 29.97fps progressive for the web, and 29.97fps interlaced for a DVD.
-
I have not put this onto the suggestions page. Thanx for pointing out.
However I disagree with your 99% assessment. I have had now a lot of footage that was declared to be 29.97fps, but turned out to trigger resampling. Right now I am dealing with 720p @59.94fps that I need to get into the 29.97 format. That triggers resampling as well. To be honest, I have not seen any good logic behind when resampling was triggered vs. not. As a rule of thumb, if it goes to youtube (well, any form of online), I disable resampling resampling.
-
Turn off resampling by selecting all video events and then right-click, and via “switches -> resampling”.
It’s the single most anyoing feature in vegas that you cannot tell it to start up with resampling forced disabled for a project (or at least change the default).
[Edit] See page 295 on the Vegas 10.0d pdf manual.
-
I’d say the first thing you should do is to turn off resampling. The next thing you should do is to change the deinterlacing from “blend” to “interpolate”. Since you are downconverting to progressive anyway (and the GoPro is already progressive) that should take care of this.
-
Skeptic or not, I have to admit I gave up on Vegas Pro 11. All versions I had tried out are slower on my system than 10e, are crashing randomly, and have plenty of other issue. I had expected that the switch to OFX would bring some benefits, but up to now I am seeing only a messy nightmare, with crashes, functional regressions and a GUI that is less usable than the one before it. Given that there is, other than the GPU accelerated MainConcept AVC renderer, no real new desirable feature, I am at the point of “why bother”.
Maybe in summer/autumn Vegas Pro 11 will be stable enough for use.
-
I like this techie explanation. So here my two addons:
– what the heck does the “saturation” slider do then ? Is it the “saturation” from the HSL model, whereby the H & L parts are adjusted in the color wheels ? Or is this YCbCr rather than HSL and it’s the chrominance gain ?
– the tool says something about low/mid/high … what is the definition of whether a given color belongs to the low/mid/high part ?
-
Ok, here 2 other things you might want to look into before making the call:
(1) Is the accidental damage protection available, and for how much ?
(2) Can you download the repair manual, that tells you how disassemble the beast, and for example clean out the fan …
My wife and I have gone throu quite a few laptops over the years. Turns out that HP and Toshiba have always been the best choices in the higher end segment. I have been burned by a lot of brands that I’d rather not mention.
Now if you are going to the $1500 to $2000 segment, I’d recommend to you to also take a look at the HP 8560w.
-
Did you turn on the deblocking ? Mind also trying the “Sony AVC” codec with the same shots ?
There is also this intresting link which describes more of the Mainconcept CUDA AVC codec. Maybe those limitations cause this massive blocking effect. https://www.mainconcept.com/products/sdks/gpu-acceleration/cuda-h264avc.html
-
Regarding the size, I cannot help you other than to recommend to check it out at a local store. It seems that the difference between the DV6t and the DV7t isn’t all that big. Also consider that you’d still have to lug the 120W power brick around, and if you are like me, probably your external drive …
Regarding the horsepower, I suspect it does have enought of it. I am using here a HP 8730w, Core2 T9600 with a FX2700M GPU. Still does it’s job for 1080@24p and 720@30p reasonably well.