[Stephen Crye]

Lee, I thought I would jump in because your question has gone unanswered.

Although I’ll try to shed some light on it, I suspect it went unanswered because we can tell you have a lot to learn, and it is not possible or practical to write a zillion pages here on this thread to guide you.

That having been said, your question shows you are thinking. It is not a stupid question. The quick answer is – rendering at a higher rate with the h.264 encoder will not buy you anything.

Your camera shoots with the AVCHD 1.0 standard, using h.264 encoding with a max bit rate 0f 24 Mbps.

If you are just trying to render for YouTube, it would be pointless to shoot for 24 Mbps on the render, because YT is going to degrade it to far less than 24 Mbps. I suggest a more reasonable 8 Mbps CBR.

But, if you plan to render for something else – for example BluRay – or if you want to use a different encoder such as MPEG (which does not compress as efficiently as h.264), then a higher bit rate might produce better results.

Read, experiment, and don’t expect simple answers to very complicated things.

Here’s a link that might open your eyes a bit:
https://www.jazzythedog.com/testing/DNxHD/HD-Guide.aspx

If you are serious about videography, years from now you will come back and read your post with a smile and with appreciation of how far you have progressed!

Steve

Win7 Pro X64 on Dell T3400, MultiTB SATA, 8GB RAM, nVidea FX 570, Vegas 10e (and 11) x64 DVDA 5.2(build 133) Sony HDR-CX550V

[Stephen Crye]

Hi;

The sample does look purplish.

However, file types (i.e. the type of transport scheme) are not directly related to the encoding scheme, and that ought not have anything to do with color balance unless something else is happening.

More info would be helpful:

* what camera and settings were used on the shoot?
* what version of Vegas?
* Exactly what settings used for the render?

Perhaps after more details, one of the *true* gurus on this forum can help.

Steve

Win7 Pro X64 on Dell T3400, MultiTB SATA, 8GB RAM, nVidea FX 570, Vegas 10e (and 11) x64 DVDA 5.2(build 133) Sony HDR-CX550V

[Stephen Crye]

Had you just done that nVidia update that came down the pike from Microsoft? That update is bad news … it broke some stuff on my Win7 Pro 64 bit box, such as the nVidia control panel. I backed out of it. However, I did the nVidia update and backout before I installed Vegas 11 for the 1st time earlier today.

Steve

Win7 Pro X64 on Dell T3400, MultiTB SATA, 8GB RAM, nVidea FX 570, Vegas 10e (and 11) x64 DVDA 5.2(build 133) Sony HDR-CX550V

[Stephen Crye]

Thanks, Jeff;

Stand by, will test this!

Allowing myself a glimmer of hope.

One quick question – can this be isolated to a single track? Or must I have a separate project to prevent deadly unintended ripple?

Steve

Win7 Pro X64 on Dell T3400, MultiTB SATA, 8GB RAM, nVidea FX 570, Vegas 10e (and 11) x64 DVDA 5.2(build 133) Sony HDR-CX550V

[Stephen Crye]

Hi;

Xavier, this is the age-old question – how to get the smallest possible rendered video without sacrificing quality.

Many of us, including me, just pick one of the built-in Vegas codecs and let Vegas do it’s thing. NTSC, BluRay, h.264 for Youtube, etc.

There are others who disdain these easy methods and do more complicated things. The “Handbrake” methods come to mind. Nick Hope is a big proponent of them, and his vids looks amazing.

Some more info can be found here:

https://www.jazzythedog.com/testing/DNxHD/HD-Guide.aspx

https://www.youtube.com/watch?v=rWMX5lSvEgY

Have fun!

Steve

Win7 Pro X64 on Dell T3400, MultiTB SATA, 8GB RAM, nVidea FX 570, Vegas 10e (and 11) x64 DVDA 5.2(build 133) Sony HDR-CX550V

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Stephen Crye]

Ok people, on a more serious and less eczemic note – read below and please jump in where I have it wrong.

Footage shot at 60i means that we get 30 “full” frames a second, with each full frame consisting of two half frames, each 1/60th of second apart. These half frames are interlaced: one contains just the odd lines in the final frame, the other the even lines.

This scheme was devised by the broadcast TV geeks in primitive times. Broadcast TV still uses this, the theory being that our lowly eyeballs and brains blur the even/odd half frames together into a single frame every 1/30th of a second.

YouTube and other formats, on the other hand, want everything to be 30p. So, when we render for YT, we have to combine the two half-frames somehow. Complicating this is the fact that the two half frames are separated in time by a small amount, so a moving object will be offset in each half frame – and because they are on alternating lines, there will be jagginess. We get rid of the jagginess with one of two methods in Vegas – “blend” (which gives those ghostly edges in the direction of motion), or “interpolate”, which seems to have less ghosting but possibly only because 1/2 of the info has been thrown away and the full frame calculated via some kind of necromancy/voodoo that no one can explain?!?

So far, no big revelations here.

But – suppose I want to render for a format that is native 60i. (I see plenty of these options in Vegas, for example BlueRay 1920×1080 60i.

If my footage is 60i, and my target media is 60i, why would I not set Vegas to “none” in de-interlace? Just not mess with it and send it to my Samsung TV in full glorious interlaced format?

Help …

Steve

Win7 Pro X64 on Dell T3400, MultiTB SATA, 8GB RAM, nVidea FX 570, Vegas 10e (and 11) x64 DVDA 5.2(build 133) Sony HDR-CX550V

[Stephen Crye]

Hee hee!

I must LOL because that thread is one of many that I have been reading with much scratching of my head.

But I’m glad that I am not the only one with these itches …

Steve

Win7 Pro X64 on Dell T3400, MultiTB SATA, 8GB RAM, nVidea FX 570, Vegas 10e (and 11) x64 DVDA 5.2(build 133) Sony HDR-CX550V

[Stephen Crye]

Ahhh … I only now remembered that I have *always* used the “Legacy text” generator … it was of such second-nature that I never thought about it until now.

Thanks,

Steve

Win7 Pro X64 on Dell T3400, MultiTB SATA, 8GB RAM, nVidea FX 570, Vegas 10e (and 11) x64 DVDA 5.2(build 133) Sony HDR-CX550V

[Stephen Crye]

Ok, thanks John, good to know it was not just me.

Although I could tell pretty easily if the option was enabled in SVP 10, I can live with the new look.

Steve

Win7 Pro X64 on Dell T3400, MultiTB SATA, 8GB RAM, nVidea FX 570, Vegas 10e (and 11) x64 DVDA 5.2(build 133) Sony HDR-CX550V

[Stephen Crye]

Hmmmm…

Still confused.

Here’s a workflow that happens to me quite often, usually with audio tracks, but the same principal can apply to video tracks.

I have 30 minutes or so of audio, mostly quiet passages, but there are snatches of conversation or other sounds I want to keep. I look through the event, and when I see a little peak of sound, I split the event on either side of the peak, isolating it from the quiet bits to ether side. When I have found all the parts I want to keep, I then go back and delete all the “quiet” bits I want to throw away.

Now I have a bunch of events on the timeline that are separated by random lengths of nothingness. To get all the events to “touch”, what I have been doing is (starting from the far right side of the timeline):

grabbing an event, dragging it until it touches the next event to its left, then shift-selecting to get them to “stick” in a group, drag that group to the left, repeat … until I am ready to scream from the repetitive frustration!

I dream of a way to tell Vegas : ” Ok for this range of events in the timeline, get rid of any empty space and squeeze all the events together”.

Can ripple do this for me? If not, is there another method?

Thanks!

Steve

Win7 Pro X64 on Dell T3400, MultiTB SATA, 8GB RAM, nVidea FX 570, Vegas 10e (and 11) x64 DVDA 5.2(build 133) Sony HDR-CX550V