Matt Carlson
Forum Replies Created
-
David is right here… let’s sum up.
1) The 600 cards are crippled without licensing the new SDK. To my knowledge only GAME developers are even allowed to do so right now. Even if Sony wanted to implement the 600 series Nvidia may refuse to let them (welcome to the new world where lawyers rule.) A 500 series card runs slightly better than a crippled 600 series card.
2) OpenCL and Cuda are not interchangeable they just coexist because developers implement both. In the case of Vegas OpenCL is used for preview acceleration only. Cuda is the only implementation that uses render acceleration (and that is limited to the Sony avc codecs.)
-
Main Concept also has the same problem. I ran several tests and here are the interesting results.
Quicktime duration of a 25.00 region Media Info 24s 982ms Vegas Properties 25.00
Sony AVC duration of same region Media Info 24s 960ms Vegas Properties 24.23 (missing frame)Sony AVC duration with Quantize OFF Media Info 24s 983ms Vegas Properties 24.23
The durations become almost the same in Media Info but the frame is still missing in Vegas.Sony AVC with Adjust To Frame Rate checked Media Info Frame Rate 11.988 Duration 25s 25ms (one frame over and frame rate messed up.)
There is definitely something going on with the source which is a lecture burned to Bluray (through DVD architect I believe but I should check) but the source stats seem fine: AVC High 4.1 Reference Frames 3 progressive. The source is demuxed with TSMuxer and the audio is converted to M4a for editing. The renders come back Reference Frames 2 for AVC but that is the only inconsistency I can find. I can’t find a reason for the Adjust To Frame Rate to think the source is 11 since Quicktime comes back fine.
-
Quantize to Frames is enabled. Rendering the regions with a Quicktime template creates clips of the proper size but the clips are being sent to several different applications (AE, Resolve, etc) and AVC was the best choice to play well with all of them on a windows machine (and I noticed a drop in quality with fast movement from Quicktime at the same bitrate.) The footage is 23.976 progressive so I tried a render at straight 24 and the clips ran over. It just seems to be a quirk with Sony AVC although I vaguely remember having a similar problem with ASF many years ago.
-
“there are some hardware capabilities that the gaming cards don’t have”
This was the problem Nvidia ran in to. The versatility of CUDA and the sheer power of the 600 series would be greater than what makes Quadro such a good thing (which I agree is/was a valid market .) The dedicated architecture of workstation cards was going to be eclipsed by the sheer power (even if technically that power was not as efficient.) I am not quite sure why they just don’t start making the Quadro series that much better but I am guessing that they don’t see the cost benefit of changing that side of the manufacturing process which is the root of the trouble. Their gaming cards are now so good that they have to cripple them. That is just a little bit on the insane side.
-
Well I know you are a Quadro user and the new 600 series was about to be an incredible beast. Would you spend 3 times on a Quadro if you can get a “gaming” card that just by the sheer nature of its design made the idea of Quadros obsolete? I agree with you that it is a pretty ballsy move to start such practices with hardware but software has done this for a decade now. It is not like Vegas Platinum took any less resources to make. In fact it takes more resources to repackage and diminish Pro to make Platinum. They can’t just reduce their price on Pro to get people to buy (there is sarcasm dripping from that sentence.) The idea that hardware developers are getting in to this practice by crippling performance without even making a show of removing actual hardware such as cache memory etc is troubling.
-
The new Nvidia Keppler cards (i.e. the 600 series) changed their architecture and divided the CUDA cores in to four banks. This change is rumored to be intentional in order to limit performance to specific SDK licensing. The effect of the architecture change for Vegas is this… only the first CUDA bank is recognized. Your 570 had 480 cores. Your 660ti has 1344 cores but Vegas only sees 336 of them which makes it a step down. Once again the rumor is that this was intentional meaning that we will not see a driver update that fixes this as it is not a “problem.”
-
M2TS is a newer version of the MTS container that allows for advanced features (such as encrypting data) and is partly a product of (useless to us) patent revisions. MTS is solely a Sony endeavor, however, where M2TS is not quite restricted to Sony conventions. Whether any of these container revisions or codec enhancements can trip up Vegas Pro will likely depend on the source. M2TS was designed specifically for Bluray streaming but now is used as the end result of codec conversions while MTS is still used (most probably for patent reasons) as a camera raw footage codec. The M2TS video codec is described as “more advanced” mpeg-2 while MTS is described as proprietary AVCHD. All this is to say they will probably function exactly the same in Vegas but considering all the lawyerly crap explained above you never know if the patent restrictions plus hardware/software combination will suddenly end in some interaction that coughs up a furball.
-
When this has happened to me the glitches came from third party OFX plugins that did not like running concurrently (for which there was no solution.) What kind of effects do you have on the two projects?
-
Your conclusion is pretty much correct. Your video card will help with the preview a bit but it will be hard pressed to give any support to your i3770 during rendering. Your render times being halved are completely due to your processor upgrade. The GT640m is a fairly capable card outside of video editing but it is a second tier card and 10 fps in the preview is what you will average with second tier cards. The “X” cards are far better for getting your video preview up to 24 or 30 fps except the fact that your previous gtx 260 card was a bit old and the 640 despite its architecture limitations is newer and compensates a little for that lack of the “X” factor. With an i3770 a gtx 460 will probably let your reach 24 fps or higher. Anything less (that is budget cards that are less than about $160 US) will struggle to keep the preview running in real time and will do very little to get better AVC rendering times. With newer gtx first tier cards you would probably see about a ten percent (maybe less) performance boost in rendering coupled with the i3770.
-
How are you monitoring the situation yourself during the recording (if at all)? If you have a boom box or something with rca inputs you could use it as a headphone station that takes your computer output and just use the Tascam as the input device.