VT3 Problems Already !

[wtdedula]

Hello All;
I have am having a problem with VT3 that I hope is due to operator error rather than a bug. I started working with VT-3 this weekend. For my first project, I brought in ToasterEdit project that I started working on in VT-2. I only used Photos since I am building a slide show. Like the one gentlemen said, I discovered that the cropping of the clips was all messed up and I had to fix them all in VT3.

I went on to work on the proect where I modified many properties of the clips such as cropping, borders, colors, etc ... ! When I saved this project as BOTH a VT3 Project and a VT-Edit Project (Which one should I save as ?), and then opened it up again, these properties were all messed up and I had to redo each and every clip. Also, the positioning got messed up, and the color as well. In fact, I don't think any of the clips properties that I changed got saved - I had to redo this again. I will no longer use VT3 until I figure out why this is happening of I will have to redo the entire proejct before I begin each session which of course isn't practical.

How do I get the clip's properties to be saved with the project ? I hope I'm just forgetting something because others would surely complain if this were a problem.

I have another question too - how do I copy a clip's properties to another clip without copying the actual content ? I tried Inherit but it copies the actual photo as well - is it possible to ONLY copy the properties without the content (Photo or Video, etc ...) ?

Tim

[Paul Lara]

Originally posted by wtdedula
how do I copy a clip's properties to another clip without copying the actual content ? I tried Inherit but it copies the actual photo as well - is it possible to ONLY copy the properties without the content (Photo or Video, etc ...) ?


Oh, absolutely! Not only can you copy the property (motion, color correction, cropping, sizining, etc.), but in VT[3] you can now go to Tool Shed | Presets | User Presets | and click on the create button, give it a descriptive name, and then it's saved for one-click recall to apply to any clip any time in the future!

[slacker]

I had the same problem with settings not saving when I saved a project and it was driving me crazy. Paul solved that trouble by pointing out that simply setting the value of your size, color, etc. isn't enough. You need to set the value and then add a keyframe. That is the only way it will save properly. It's worked fine since then.

Regards,

Joel Slack
Media Department, New Life Christian Fellowship
Jacksonville, FL

[wtdedula]

Thanks Joel;
It sounds like your message is the first I received that may possibly hold the key to getting this to work.

Tim

[wvp]

Originally posted by wtdedula
...may possibly hold the key ... Tim
Key, funny!

actually while this is not a big deal to do, it does sound like it it a bit more of a pain than it should be. It also sounds like something a lot of people are going to overlook & get screwed up on.
Thanks for the heads up, I would love it if more people could chime in on if this is how it has to be though.:confused:

[SBowie]

Originally posted by wvp
actually while this is not a big deal to do, it does sound like it it a bit more of a pain than it should be... I would love it if more people could chime in on if this is how it has to be though.:confused: I imagine the 'autoscale/don't scale' decision will ultimately go back to being a Prefs option. It's a bit more confusing when loading up an old project than when working with a new one.

I think more might have chimed in were the matter not being discussed in another thread or two already? :)

[vip3dran]

In the first message posted to this area,
Tim asked a question that I was hoping to hear
an answer to.
I'm wondering about the same thing.

Originally posted by wtdedula
When I saved this project as BOTH a VT3 Project and a VT-Edit Project (Which one should I save as ?)

What is the difference between the two?

[ted]

Currently the options are there to be backwards compatible.
"I think", the "VT3 Project" would be the recommended choice.

[vip3dran]

Any recommendations from Newtek? Paul?

what's the difference between the two?

[SBowie]

I asked this, too. I was told (not verified) that the the VT-Edit type was a remnant of Beta filetype included for those who had used it then.

[wtdedula]

I think slacker had the key a few messages back in his thread. I called Newtek Tech. Support today and they were able to reproduce my problem. Just setting a keyframe the first time all of the edit properties for each clip will cause them to be saved correctly. I tried this and I think it worked but the true test will be when I edit my big file with a few associates.

This is not intuitive and I don't think it's explained in the manual (or atleast I didn't see it) so hopefully this requirement will be eliminated in the next released build of the VT3 software.

Tim

[SBowie]

I tedn to agree that I would prefer there be some change or addtion to the way this works - perhaps either an 'implied key' at frame 0 of all newly added clips, or a Preference setting to allow the user to designate whether there was always a keyframe at 0 or not.

[ScorpioProd]

That's a great idea Steve!

I totally agree, there should be an implied keyframe at 0, that's what T[2] did.

[JReble]

I haven't even installed the upgrade yet and I'd definitely vouch for that as well.

[bradl]

Originally posted by wtdedula
I have another question too - how do I copy a clip's properties to another clip without copying the actual content ? I tried Inherit but it copies the actual photo as well - is it possible to ONLY copy the properties without the content (Photo or Video, etc ...) ?


I think you may be confused on how inherit works. Inherit lets you change the content (clip, still, audio) but retain all attributes. So to "copy a clip's properties to another clip" using inherit, make a copy of the original clip (CNTL+DRAG), then deposit new content on the top of the copy while holding the ALT key. Now you have a new clip with the properties of the original.

As Paul mentioned the toolshed presets could do this, but I find for a quick one-off, Inherit is still faster.