Davd Keator
Forum Replies Created
-
Sony avc internet 720p everytime… just select your proper frame rate. 1080p. Toooooo slow even with broadband Turbo :-/
President: http://www.VertexMedia.com
-
I just decided to give 10d a try, thinking you know fourth time is a charm….
Any way, your solution:
Update to the newest Directx 10: there is an updtae that came out last month… Should fix your problem.
President: http://www.VertexMedia.com
-
Davd Keator
May 4, 2011 at 10:49 pm in reply to: m2ts – which format to render to to keep resolution in Vegas 9.0?Oy Vey – This is a big can….
Lets see: Codec: A program and algorithm that is used to encode and compress media data. Certain codecs are fast and dirty. Such as Mpeg1. Mpeg2, M2ts, etc…
Throughout the years, processors have gotten faster and along with innovation we have benefited from faster more efficient codecs to compress our video. As time went on we have evolved to what is known as wavelet codecs such as Cineform.
Quick brief:
Long Group of Pictures is a format that bunches individual pictures of the video and massively compresses the areas of the image that don’t move very much, and a little compression on the parts that do move. This is processor intensive and when you as an editor cuts in the middle of the group of pictures, your computer and editing software needs to recalculate the new stream and then re-compress a new group of pictures. When this occurs you get compression errors and blocking artifacts, not to mention just a bit muddier image.
This type of compression falls apart right after the second generation of rendering. That is if you were to make a few cuts render it out then go back add some effects and cuts then render it again.
You will see blocks, lines, off colors and graduations in the colors as well
This is simplistic as Vegas does have no-re-compress on their H264, however overall, it still falls apart.
GOP is known as lossy compression
Longer part of the brief:
Bit-rate: this is how many bits of data are used to save the information for the computer to reconstruct the image. The less data, the more compression, the more the computer gets to guess what the image looks like. The higher the bit rate – the better. However, there is a point of diminishing returns.
Too much bit-rate and you are wasting processing power trying to keep information and you see stuttering and other playback issues. Simply your computer can’t keep up with the data stream.
Also, the codec in general only allows for so much information to pass through at a tine.
Look at wikipedia: H264 codec specs. There you can see the data rate & resolution specifications. If you exceed the bit-rate, you simply waste power, not to mention a possible break of the codec and you can no longer play it back or edit it properly.
Sony gives you great defaults per codec of choice. If you lower the bit-rate you get more rendering errors / compression artifacts etc…
M2ts is a glorified codec like MP4. Looks good as a blu-ray, not good as an editing codec.
What do we do?
We get a codec that is the most modern and as lossless as possible that my computer can edit.
Enter Cineform, Mjpeg2000, Huffy, etc…
I have played with many codecs and struggled and prodded my way through to just realize. Just get the best and pay for it.
Therefore I use cineform.
This is a wavelet codec, it compresses each frame individually and uses advanced mathematics to keep the frequencies of light and color space more accurate each and every time you re-render the video.
The bit-rate is extremely high as well, however, the math behind the codec is great and most computers can handle it with ease. Even Apple and it’s touted “Prores” is getting replaced with this form of codec for their next Final cut release.
This digital intermediate is pricey yet well worth the cost if you do composting and other complicated effects.
Thats about it:
For further reading look up:
Bit-rate
Codec: H264, Mpeg2, Lossy & Lossless
Wapper: AVI, MP4, MOV
Bit depth – 8, 10, 12, 16 & 32float
Wavelet
de-blocking
TranscodeSimple point of view:
Take captured footage, transcode into Cineform ‘filmscan1’, edit, render out to codec needed, blue-ray, Mpeg2 for DVD, or MP4 for internet upload & or sharing. Be happy, this is the best you can get, now you just need practice making your footage look better and hone your editing skills.
Don’t forget, learn how to edit audio as well. Sound Forge or Adobe Audition / Sound booth.
Good luck.
-
Only when we have to… LOL
-
Well, something changed, I ran into this issue years ago, I think when I first went V8.1…
You are going to need some diagnostic help…
When this happens to me I usually do a fresh install of Windows and go from there, newest drivers and updates for all…
Lets see:
Tell me all your computer specs…
Also in the meantime run resource monitor while rendering to see whats happening…
CPU load.
Disk IO.
Memory – especially the Hard faults per second… & used phsyical memory…Also do the other vegas tricks as well, set dynamic preview to 0 etc…
Just a thought, how much room do you have on your C drive and your render drive?
Also: what codec are you reading and what is your output settings?
thanx
-
Davd Keator
May 1, 2011 at 7:15 pm in reply to: m2ts – which format to render to to keep resolution in Vegas 9.0?This really all depends on your level of Edititing…
Simple cuts – use the blu-ray codec…
If however you are using transitions, fades, green screen etc..
Then you must, absolutely must transcode to a good Wavelet interframe codec first before you start editing. Otherwise you will see codec errors left and right. Most people don’t notice these but editors and other film critics do…
Cineform = rockin solid
Morgan Jpeg = great in 32bit world
Lagarith 32 bit world good too… -
Yes, Vegas 8,9, & 10 must have 2 gigs ram per core available. If not you will see your rendering going to the swap file. This will literally kill your rendering times and at many times drop you to ONE cpu during rendering!
Win 7 x64
8 gigs of Ram
Quadcore cpu
16 gig swap file – but you won’t hit it….
2 hard drivespartition your boot drive to something small like 64 to 120 gigs…
this is great, you get really fast boots and app load speed.Good luck…
-
Jim,
Just for the heck of it, I installed Vegas 10 their lates iteration just give it a lookover one more time.
Vegas 10 does do a nicer job of video preview due to the gpu access. I have noticed my Red .3rd files much better looking in preview mode which makes lining up effects better over all.
I am running the I7-2600k OC: 4.2GHZ.
I noticed a very slight decrease in performance with Hyperthread off… Like 1.3% I decided that 1% wasn’t worth turning off due to other apps that I use actually work just a hair better.
For your rig: the I5-2500 sound interesting, you only seem to loose 2megs of cpu cache, however, 2 megs might be a critical level of info you may be missing out on. If your CPU needs input, you will be slowing down the cpu as it has to wait for your ram or worse your HD to give it the data it so desperately needs.
But then again, my 980x has 12 megs and I noticed no diference dropping to 8 megs cache, but both cpu are at 2 megs per core. Your i5 is at 1.5 megs per cpu. My thoughts are it will be measurable yet negligable.
My thoughts for your rig:
1: i5-2500k OC-3.8 to 4.2ghz with Hyper212 CPU cooler.
1b: H67 or better p67 pro from asus
2: Nvidia GTX 450 stock clock.
3: 8 gigs o ram – 16 if you like over kill.
3: 2 Harddrives| 1 or 2 TB drives
C: Sytem Boot partition at 80 gigs.
D: Backiup appz / files Partition – 150 gigs
E: Library copy of all your media, clips, music etc…
—–
F: Work drive – full 1 or 2 tb drive for work.
(keep less than 50% full)This is about as fast of a system you can get…
Don’t count on Vegas incorporating Intel tech anytime soom…
Also if you use integrated graphics, you share your system ram with your apps and video. Your video preview and over all system will be laggy and just plain not fun…
-
Davd Keator
April 7, 2011 at 11:14 pm in reply to: Sony Vegas Pro 10 GPU ..What, where, when….No Way!Hey guys,
Thought I’d try Vegas 10 again now that I have the Sandy Bridge I7 2600k CPU & GTX 560 Ti & 16gig. I love this computer it’s actually faster than my 980x and way less expensive. Anyway:
Vegas 10:
RED footage 19 second clip – 4k raw
Color correction
Chroma key
Film grainSony AVC at default 1280x720x30p setting:
GPU Enable:
GPU: 22%
CPU: 62%
Time:0:28 secondsCPU only:
GPU:6%
CPU:92%
Time: 0:24 seconds
——————————————–
Well, I guess it is still things that make you go HMMM…
Nearly the fastest GPU on the market is worthless for rendering in VEGAS!I can’t wait when they advertise that they support red rocket! 0_o
-
Positive: SSD’s are great for loading apps that’s it. Vegas in .5 seconds windows in 10 seconds etc…
We are running an entire infomercial series on 4 computers each with 1 hd. No saturation issues at all. Pull up your resource monitor. You will see that your Hd rarely surpasses 20 megs a second hardly a sweat for any hd of today….
Here is a link to the show…
https://www.youtube.com/user/TheOCspotlightEach episode is rendered by segments and then put together with the final fillers to complete the show.
The only bottle neck I have seen is pulling the segments off the network…too much lag on the gigabit network. If we copy all segments to the finalizing computer, no issues at all…
Take it easy,
Dave