Thomas Roell
Forum Replies Created
-
I’d suggest going with a DV7t instead. You’d get a larger LCD, but more importantly, it has a 2nd drive bay. That way you could have 2 drives, one for the OS, and one for your media.
The 9 cell big battery is a MUST, for the simple reason that it raises the laptop a tad and allows for better cooling.
Also the DV7t comes right now with a free upgrade to 8GB memory, and a Blu-Ray reader. The Blu-Ray writer is avalable for I think $75 extra, so IMHO a sweet deal.
One thing to be aware of with the AMD graphics options is that from my understanding, while running on battery, you’d only use the embedded intel graphics, while when running off external charger you’d get the full horse power. NVIDIA has something similar that they call Optimus. I do have no idea how that would affect Vegas Pro 11 and GPU rendering / video processing.
-
The interlacing effects. Is there a recommendation what should be used if there is some slow moving action intermixed with some fast moving action ?
-
Well, the audio on youtube was missing. And since I did save the project with Vegas Pro 11, I could not go back to 10 …
My only way to go was to use MainConcept with a 14/20 Mbps setting. Since youtube recodes anyway, I don’t think jaking up the filesize would hurt this workflow.
-
Ok, I was too early to say “all good”. Rendering with “Sony AVC” and uploading to Youtube punts me back with: “The video you uploaded may have audio/video sync issues …” “We did not recognize the audio format for this file …”
-
One thing I just found out, maybe work sharing …
I deinstalled all Sony Products, delete all app data, nuked all “Sony” entries in the registry, and then reinstalled Vegas Pro 11 again … well, now my “Sony AVC” codec works with 720p. Looks like part of my problems are solved.
-
Cineform. As I’m here the noobie, this advise might be worthless, but try this:
(1) Pick a “Video for Windows” template (say HD 720-60p YUV)
(2) Select “Customize Template”
(3) Pick “CineForm Codec” in the “Video format” dropdown”
(4) Click in “Configure” to select your Edcoded format/quality
-
How cool is that, Sony 😉 I could swear up and down that the web-page said GT2xx on the weekend. I just checked the manual, and on page 19 it says GT2xx …
Also I disagree that saying GTX 460 is good enough. There is the GT 440, which is a total lowend card, but still would work with Vegas … Or how does a Quadro 2000 correlate there ?
What’s even more frustrating is that the NVIDIA web page is in a few cases wrong as well, where a card is listed with 2.0, but is only 1.2 … Quite a mess I’d say.
-
Very frustrating … here is the info for NVIDIA Cards (if this is wrong, and somebody from Sony wants to jump in …).
It appears that Vegas Pro 11 wants to have CUDA Compute Capability 2.0. If I fake that out on my Quadro FX2700M, playback doesn’t work. So Vegas does require something that’s only in CUDA Compute Capability 2.0. I had tried 280 and 285 drivers from NVIDIA. Works fine with a Quadro 5000.
There is the wiki that tells you which GPU hence is supported: https://developer.nvidia.com/cuda-gpus. So in a nutshell unless you have a FERMI type GPU this is not gonna work, despite Sony claiming otherwise …
Hope that helps. Hope that Sony fixes this and allows CUDA Compute Capability 1.1 …
Couple of other observations. I did a trial run with the MainConcept MP4 code of a short 720p clip, 1:13 in length, no effects just a few cuts. Anyway, on a Quadro FX2700M it takes 2:17, on a Quadro 5000 it takes 1:35. CPU only MainConcept takes for the same clip on the CPU took 9:03, while SonyAVC took 3:35. The host was kind of slow, either a 2.8GHz Core2 for the FX2700M or a 2.66GHz Core for the Quadro 5000. Video playback on the Quadro 5000 was somewhat stuttery as compared to the FX2700M, which I’d attribute to the GPU usage …
– Thomas
-
Late response here.
The Sony Website is of no big help … It would be nice to have an explanation somewhere, why some older or newer cards are not supported and others are.
I’m somewhat ticked off as I got a Laptop specifically based upon the OpenCL 1.1 requirement, and now half a year later it turns out that it’s not supported by Vegas, but works quite nice with the Adobe Mercury engine.
Reading over all the posts, it seems that vegas110.exe has hardcoded some device id list somewhere, or some OpenCL requirement. It would just be nice to expose this externally so that one could use say “GPU Caps Viewer” and then see why their GPU won’t work.
-
You have “Match Project settings” checked. Uncheck this, and there is the Sony SVC coded. Then you can create your custom template …
Why not use the MainConcept AVC codec ?