Xavier Dolz
Forum Replies Created
-
Again the money discussion. I would pay nothing, which is 329 million dollars. Yes, nothing = 329 million dollars. The same incomes from Mozilla. How much do you pay for Firefox? Nothing. Okay, nothing in the internet world, 329 million dollars.
Happy?
Or perhaps I would pay your price, if it is reasonable. Do it, and sell it. There is market for it.
This is only an opinion, but things are changing. Artist promote their own music, they share it for free, earn money with their merchandasing, their blogs, youtube, etc.
Selling a box with something inside, is cute, from the past.
A model to earn money would be offering this script for free, and creating a blog with publicity. Or asking for a donation, and removing publicity. Wikipedia works that way, you will earn less money, 77 million dollars.
But there is something even more important than money.
LOVE
And again, this is only an opinion. -
We need a script, it’s clear… 🙁
-
Do you think this could be solved with a Macro? really?
I’m open to everything, so please, tell me.
I don’t understand very well the TSC2 encoded Camtasia video export.
You mean, to edit the video in Camtasia Editor with the zoom, and now export it to mp4 or avi from the Camtasia Editor and then opening it in VEGAS?
That would be a painful job. Have in mind a video could take 3 hours rendering in Camtasia, and now you open it in VEGAS, it has the zooms, yes, now you apply titles, cool color efects, transitions, etc. and now re-render again in VEGAS, another 3 hours waiting… that’s a lot.
I’ve used Camtasia as en example of how zooms can be made for videotutorials and if we could have the same zooms in VEGAS.
Rendering the videos 2 times, one in Camtasia Editor, and the second in VEGAS would be terrible.
So… I think we only have the script solution, if someone is willing to help the community or the macro solution you suggested.
Cheers -
Hi Marco,
I think we have a missunderstood here about codecs, files, and so on.
.TREC file does not contian any information about zooms… what you have inside is an AVI, if I am not wrong…
okay… then we have a .CAMPROJ file… that yes, that have the zooms information, call outs, etc.
So basically, what you do is recording the screen.
Then you get a .TREC file.
Now you drag and drop that .TREC file in Camtasia.
You have the timeline, you edit the .TREC file (the video), you apply the zooms, etc. and now you can save your file.
The .CAMPROJ file have all the zooms information.
Opening a .TREC file in VEGAS won’t provide VEGAS the zoom information from the timeline. It is just a video file that need to be edited, and again, we have the problem of the zoom and the dual keyframe system.
If I re-edit my zooms in VEGAS, I should need the script with the double keyframe system, if not, it would take long time.
Even if I am able to open the .TREC file in VEGAS, we continue having the problem of the zooms.
The problem is not moving the .TREC file to VEGAS. The problem is creating the zooms in VEGAS in the same way you can do it with Camtasia, dual keyframe, saving time. For that reason the script.I’ve been watching BB FlashBack Pro 5 but again it’s the same. It is like a Camtasia, but a closed system.
The problem is that, with systems like Camtasia or BB FlashBack Pro, you will never have the same power you have with VEGAS.No NewBlue FX, no transitions packs, no professional titlers, etc.
For that reason is nice to have a the script for the zooms in VEGAS, because you can use it in this way, like a videolearning tool, to produce videos with a quality never seen before. -
I guess you mean to BB FlashBack Pro 5… it is a screen recorder utility, with an editor, in the Camtasia style, but again, a closed system. If you want to move the produced file to VEGAS, you have to render, and then, in VEGAS render again.
We can talk constantly about this, but it is doing circles about the same.
The only possible solution is a script in VEGAS that allow the pan zoom options you would find in Camtasia. -
Hi Marco, step by step okay?
I don’t know why this forum is posting all in italics I have the same problem ! I hope the solve it soon.
The script, okay, I missunderstood you. I though you were able to program it ok.
I am not able to explain the necessary steps clearer than I said before, however I can do some remarks.
Then pan / zoom window must be present always in the screen. You cannot be launching the pan zoom screen everytime you create a zoom, that involve the movement of your hand and 1 mouse click, 2 seconds or 3 seconds, everytime, again we are losing time.
With that screen present always, now, you should be able to apply the zoom, and then, inserting the two keyframes, in the way I’ve explained before, steps 5 to 8.
Things you must know about Camtasia, TSC2 codec and export.
1. TSC2 codec is to be used only with Techsmith products, you cannot use it with VEGAS or Premiere (closed system).
2. Extracting the .TREC file fail a lot. Techsmith gave the possibility to extract the recording AVI file inside the TREC file, because many people complained along the years. However, it is unstable and crash constantly. Extract the TREC content is not an option.
3. Even if you are able to extract it… you wouldn’t have the dual keyframe system, so you would have an AVI file that you can edit in VEGAS… but you won’t have zooms, so again, we need the script to make the zooms in VEGAS.I don’t know what is Flashback? is it a video editor? it works in the same way?
-
My God Marco, I’m reading you and I suspect what you want to do… you want to create a script that even open the pan Window in VEGAS and work like in Camtasia !!!!!!!!!!!
My God !!!!!!!!! that would be wow amazing 😀 !!!!!!
Okay, okay.
Let’s think about how to make it work fine.This is normally how you would work… doing a videotutorial that need lots of zooms.
1. You are in VEGAS taking a look to your movie… you have the timeline in front of you.
2. Now you decide you want to create a zoom
3. We must have a button in the VEGAS toolbar that when we click on it, launch the pan / zoom window. Then, we can dock this windo in any area of the screen. This way, you could attach the window somewhere in the screen, it would be fantastic… in that case you would have always that window in front of you (again, you save seconds editing and mouse clicks)
So it could be a good idea a button, I can press in the toolbar.
When I press the button, I get this pan / zoom window opened. Now I can attach this window in any area of the screen or dock it…Why having always the Window? because we don’t have to launch it everytime we want to create a zoom. It is always there, waiting for us. Again, we are saving mouse clicks, seconds and editing time…
4. The pan / crop window is opened, we have docked it, and it is ready for us.
5. We have the cursor in the timeline, in the position we want to add the zoom.
6. In the pan / zoom window we take one of the box corners and drag or move it to reduce or increase the zoom…
7. Then, automatically, two keyframes are inserted.
First keyframe A is a copy of the previous keyframe inserted in the timeline. In that way we won’t have any animation before keyframe A, because the first keyframe inserted, A, copy the information of the previous keyframe we could have in our timeline.
Second keyframe B have the zoom information.
In this way, the animation will take place from A to B in a specified period of time.
8. By the fault, the zoom animation time is 1 second.
9. In the pan / zoom window could be possible to have a box, in which we can add the animation time for zooms?
If so… in the pan / zoom window you should be able to configure how many seconds you want for the zoom. 1 sec, 2 sec. etc.This script would be perfect. It would be the best invention ever made, the saving time would be incredible.
😀 -
@George
It’s cool friends support each other in the forum. I don’t want to talk about different things about what is indicated in the topic. Reluctant (plus) telling I should learn scripting, (in my opinion) reveal the intention that is not interested to help, which is very legitimate. As I said, everyone help in the measure they consider in the forum, so anyone is obligated.
Let’s focus in the problem and the whole community, not me, you, waag, etc. The problem still open. It has been demonstrated that doing zoom for videotutorials (with a fixed time) in VEGAS involve 7 seconds or more, which takes a lot of time for large projects. It has been demonstrated with a video that inserting the keyframes manually is very slow and reduce dramatically the editing performance.
If someone want to help giving the whole community a script, it will be very welcome. I will be glad to use it, because I really need this script, but I suspect also, thousands and thousands of people using VEGAS and uploading videos to youtube, they, will also love this script and use it.
Unfortunately I am not so smart to code scripts and probably I would be lost starting to code one, for a specific task like this one.@Marco
Thanks for your support and sincerity. Yes, in fact, some additional seconds are involved. However, 7 seconds of delay, as it is demonstrated in your video, is enough to prove the tremendous amount of time, it is wasted. Again, thanks Marco. -
With your workflow, a timeline using 4000 zooms, would need 40 minutes.
With Camtasia, it would need only 400 seconds, which are 400 / 60 seconds (which are 1 minute) = 6 minutes.Sorry I meant…
With your workflow, a timeline using 400 zooms, would need 40 minutes.
With Camtasia, it would need only… 400 zooms, 400 zooms x 1 = 400, so 400 zooms take 400 seconds, which are 400 / 60 seconds (which are 1 minute) = 6 minutes. -
Do you see? and in your video you are placing the cursor position by clicking with your mouse, thing that is not always suitable. When you have a complex and big timeline you need to zoom or reduce the timeline (not the video) and then, moving the cursor just 1 second is not always so easy.
Anyway, we have 7 seconds.
In camtasia 1 second.
We have 6 extra seconds.
For a large project with 400 zooms, for example… 400 x 6 seconds = 2400 seconds / 60 second (which are 1 minute) = 40 minutes.
With your workflow, a timeline using 4000 zooms, would need 40 minutes.
With Camtasia, it would need only 400 seconds, which are 400 / 60 seconds (which are 1 minute) = 6 minutes.As a result:
A project in Camtasia with 400 zooms takes 6 minutes
A project in VEGAS with 400 zooms, take 40 minutes.
We have wasted 34 extra minutes (half an hour).I upload many videos to Youtube, and really, I suffer a lot this.
Thanks for doing the video 😉