?? upgrade cheesehole

KPITRL wrote on 8/14/2002, 10:23 PM
I just istalled the latest patch (VV3c)
because I started experiencing jittery
playback in some of my video.

I just read on another post, that you should
un-install your earlier version before in-
stalling the patch, is this the case?

This is the 2nd. upgrade I've installed for vegas,
without un-installing the earlier version.
could this have been what started the jitter?

I never had that problem before. I did see some
of the earlier posts on stutter, but i'm still
trying to solve it.

The only other thing I do different than before,
is I've been shooting with a canon GL1, which I
thought might have been the cause.
anybody use the GL1, and vegas?

Any input is mucho apprecciato :o)


kpitrl







Comments

Cheesehole wrote on 8/14/2002, 11:22 PM
>>>anybody use the GL1, and vegas?

lots of people do. I do too. works fine except for the annoying black vertical bars on either side of your video :) but editing progressive video is much more fun for me so it's worth all the shortcomings.

just install VV30c right over your old version of Vegas. that's the way the upgrades are intended to work.
KPITRL wrote on 8/22/2002, 5:59 PM
[but editing progressive video is much more fun for me so it's worth all the shortcomings.}

Do you have to edit (progressive video) when
using the GL1?, if so, could you give me a
little insight on this matter, and could this
be why I,m getting jittery video?

Also, have you ever used a sony camera to
capture footage shot with a canon, or vise
versa, and is there any known problems doing
so?

I use a canon Gl1, and also a sony trv20
should I not mix, and match?

any help would be very much appricated.

Thanks in advance,

kpitrl
Cheesehole wrote on 8/22/2002, 6:26 PM
>>>Do you have to edit (progressive video) when
using the GL1?, if so, could you give me a
little insight on this matter, and could this
be why I,m getting jittery video?

whether you shoot in Frame (progressive) or Normal (interlaced) mode with the GL-1, the key for editing the footage is to make sure Vegas is interpretting it correctly. After you capture footage and bring it into Vegas, right click the media in the media pool and go to properties. make sure the Field order is set to 'None(Progressive scan)' or 'Lower Field first' depending on whether you shot that clip in Frame or Normal mode. sometimes VV mis-interprets Progressive footage as Lower Field First and you can switch it back right in that dialog.

>>>Also, have you ever used a sony camera to
capture footage shot with a canon, or vise
versa, and is there any known problems doing
so?

I have used a Sony DVCAM Deck (DSR-11) to capture footage recorded with a GL-1. a sony camcorder should have no trouble either.

>>>I use a canon Gl1, and also a sony trv20
should I not mix, and match?

if you want to achieve the closest match you should shoot in Normal mode (interlaced) on the GL-1. progressive will look way different from any interlaced footage, especially if your final destination for your project is back to tape or DVD for playback on a TV.

if you were shooting for internet video or some other PC based medium, I wouldn't worry about the difference. I would use progressive when possible in that case since the destination playback device is progressive (PC monitor).
BillyBoy wrote on 8/22/2002, 11:14 PM
Anytime you upgrade you're getting the full application, not just a patch. The newer version should ask if you want to overwrite the old version. At least I think it does, its been awhile I forgot. :-(
gnfoster wrote on 8/22/2002, 11:53 PM
I'm running VV3.0a bld 107 and don't have any problems (that I know of). Should I upgrade or should I not... that is the question. The old "If it ain't broke, don't fix it" addage comes to mind, but... am I missing something good?

What do you guys think?



cheesehole?... I don't EVEN want to know where that name came from!
KPITRL wrote on 8/23/2002, 6:34 PM
Thanks Guys,

For all the tips, and comments.
Again this forum is the best!

Regards,

kpitrl
riredale wrote on 8/23/2002, 7:09 PM
Qnfoster, here's some text from the 3.0c update readme file. It's your option, of course, but I haven't heard anyone complain about new bugs introduced by the 3.0c version. One thing to note, however: veg files created by 3.0c can't be opened by earlier versions (not that you'd ever need to)...


From the readme:

"An a/v sychronization bug in MPEG encodes has been fixed.

A bug has been fixed that caused print-to-tape operations to fail when markers with no text were present.

In Vegas 3.0a and 3.0b, choosing None from the Time stretch / pitch shift Method drop-down list in the Audio Event Properties dialog had no effect on time-stretched audio events. This bug has been resolved.

Notable changes/fixes from 3.0b

A Vegas project saved in version 3.0b will not open in any previous version of Vegas. Project structure had to be changed to address bugs and there was no way to avoid this project versioning incompatibility.

Text command markers now embed captions in QuickTime streaming files for viewing in the QuickTime player.

RealMedia 9 video codecs are now available on the Advanced Video tab in the Custom Settings dialog. Standard templates continue to use RealMedia version 8 video codecs.

A bug that caused some color curves settings to display inaccurrate color values has been corrected.

Autonamed CD extraction now correctly saves files to the Recorded Files folder.

Regions and markers and regions created in .w64 files using Sound Forge 6 now correctly display in the Vegas trimmer window.

PAL Widescreen DV renders now use correctly auto-switching format flag.

A bug that prevented some resampled events from resampling when using the best render quality has been fixed.

A bug that caused play/pause in the Trimmer to revert to timeline focus has been corrected.

A bug that caused Vegas to crash during project loading when transitions were missing has been corrected.

A bug that caused disk-at-once CDs to cause problems with some third-party verification software has been corrected.

The Main Concept MPEG-2 DVD templates now have an average bitrate of 6,000,000.
Numerous Video Capture changes have also been implemented. Please see your Video Capture readme.

A bug that caused normalize to fail on looped clips has been corrected.
Vegas will use SoundForge 6.0 as its default audio editor if SoundForge 6.0 is installed on the system.

A bug that caused the Main Concept plug-in to crash when using K6 processors has been corrected."