Forum Replies Created

Page 14 of 16
  • Marco Baer

    August 3, 2016 at 9:33 am in reply to: Vegas pro 13 – track glow bad (buggy) behavior

    Did you try turning GPU support off in “Options/Preferences/Video”?

  • Yes, TSC2 encoding would mean rendering and waiting all the time until render process completed.

    A macro at least should be able to emulate anything you elsewhere doing by mouse-clicks or key-presses. But a macro does not know which event you selected or where your timeline cursor stays, where your next keyframe is, etc.

    If the steps we described are scriptable, a script solution would be much smarter than using a “dump” macro. But if there will be no script then a macro at least could help saving some time.

  • I didn’t mean or talk about the TREC files but the TSC2 encoded Camtasia video export files only, which would contain zooms made in Camtasia.

    If you would not re-edit your zooms made in the screen recording software (no matter if you use Camtasia or FlashBack Pro which both use double-keyframe zooming), I’d thought it might be an acceptable solution doing the zooms in the screen recording app and any further editing (except zooms) in Vegas Pro.

    So now I assume you won’t do that because even if you’d apply your zooms in Camtasia there would be a need to re-edit the zooms in Vegas Pro. I just wanted to be clear we didn’t miss anything which could help you. You only took Camtasia as an example of how a zoom workflow could be optimized, right?

    As I cannot code such a script, I also think about a more simple macro solution. At least main parts of desired workflow maybe could be done by a macro. But before dumping into a macro solution I now wait if not a script coder could use the inputs given in this thread.

  • Yes, of course them are closed systems in the way you could not share its projects files with Vegas Pro but its rendered video output only. Would you re-edit your zooms you already applied in Camtasia?

  • Camtasia’s TSC2 encoded video definetely can be used in Vegas Pro and other kind of video editing software. I just does at the moment. But I was wrong about encoding to TSC2 from within Vegas Pro. The codec is listed and can be selected (which made me think you could use it) but encocding won’t work then. Instead I could use TSC (the prior version) for encoding from within Vegas Pro. But TSC2 decoder works pretty well in any of my editing apps here.
    So TSC2 codec can be used in Vegas Pro but other than TSC only the decoder part of TSCS2, not the encoder part.

    If I apply zooming in Camtasia and export to TSC2, I will get a regular AVI video file including all effects done in Camtasia (of course I cannot re-edit the effects because it is a video file, not a project file) which can be used in Vegas Pro.

    FlashBack is another screen recording software. I use it for about 10 years now because I prefere FlashBack’s GUI and responsiveness.

  • That said – you should be able to use Camtasia exported video encoded by TSC2 in any software which decodes AVI files. If it is a separate system you only need to install TSC2 separately. Vegas Pro and other softwares even can encode to TSC2.

    Though Camtasia isn’t the only software using this double-keyframe method for zooming. FlashBack also does same way.

  • By the way – I just tested Camtasia 8.6. I could export the Camtasia timeline including its zoom effects using the TSC2 codec. Vegas Pro could also import and edit this AVI file without problem. Though I prefer using FlashBack Pro for screen recordings (and some kind of editing of screen recordings).

    So in case nobody could code such a script, at least you should be able to do the zooming in Camtasia, export to one of the given codecs (just like TSC2) and do further editing in Vegas Pro.

  • Why the heck is this forum software using italic typo suddenly???

  • Just to avoid a misunderstanding: I’m not able to code such a script. I only drop some ideas about how the steps taken in such a script could be simplified without losing desired functionality.

    Not sure about your steps 1. to 3. If you dock Pan/Crop window in Vegas Pro, it will stay there. All it needs is to refresh the docked window for the current event which needs to click onto the Pan/Crop button again.
    Now if you either click onto the Pan/Crop button or click onto a script button for refreshing the window doesn’t make a difference. Though having said this – if refreshing the window is combined with the steps following, it would save time again.

    Your steps 6. to 8. should be fulfilled by the steps I described above.
    If Pan/Crop timeline cursor is set back 1 second first to add a keyframe, this is just like having copied last keyframe. It requires there are not yet any further Pan/Crop keyframes used to the right of the timeline though.

  • I’m now thinking about the most effectiv steps to take for a script.

    Assumed you let timeline synch enabled, wouldn’t it be:

    – Open Pan/Crop window.
    – Set cursor of Pan/Crop timeline back 1 second first.
    – Create a keyframe.
    – Go forth 1 second.

    When you now do your cropping you’re done because this will automatically add your second keyframe.
    And you needn’t copy keyframes or restoring a keyframe this way.

Page 14 of 16

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy