Forum Replies Created

Page 1 of 5
  • Bill Burnette

    February 25, 2020 at 12:34 am in reply to: veg files say files are not available

    If you can find them with search, you can compare where Vegas expected to find them and where they are now. Then maybe you can determine who or what might have moved them. After you go through the relinking process, if you don’t save the veg file, you will have to search again next time you open it.

  • Bill Burnette

    February 6, 2020 at 6:34 am in reply to: Effects on tracks vs clips

    Hi Graham, You’re most likely right the OP meant video noise reduction. I immediately thought of Sonic Foundry’s Noise Reduction audio plugin from way back.

    Media level sounds right, Graham. I think video noise reduction might be one of those “self -analyzing” effects, unless it just does mindless blurring, IDK. For another example, the legacy video stabilization was required to be applied at the media level. If the media contained multiple scenes, or if it took too long to analyze the motion, it was a good idea to create subclips to apply the effect and run the analyzing. Then events made from those would actually run the final stabilizing.

  • Bill Burnette

    February 5, 2020 at 10:18 pm in reply to: Effects on tracks vs clips

    It depends on which audio denoiser you use. Some of them need to run an analyzer in order to set ideal parameters. That means every time the audio scene changes, the denoiser needs different parameters. By “audio scene” I mean e.g. a change in locale, a change in background noise activity, etc. So definitely not denoising at the track level. Most likely at the “clip” (or “event” in Vegas-speak) level, just as Steve says. At the media level, audio scene characteristics might change; but if they don’t, and you are cutting up that file to use in multiple events, it may be more convenient to apply at the media level.

    Some of the same principles apply to other effects. The “analysis” for applying an audio or video effect might not be automatic, but depends on your eyes and ears, so e.g. setting color correction (with constant parameters) at the track or timeline level wouldn’t make sense. But some effects are “self-analyzing”, such as audio compressors, so it’s OK to apply at the track or timeline level.

    For your general question involving performance: I don’t know. Does anyone know the performance ramifications of applying a CPU-gobbling effect at the track level when there are only a few events and the rest of the track is empty? Can Vegas skip applying track effects when there is blank space on the track?

  • Bill Burnette

    January 13, 2020 at 9:17 pm in reply to: Pro 17 can’t open a Pro 12 template project?

    Hi Randy,

    (Quote from Magix Vegas Pro forum:)
    From another thread:

    It is very possible that these files require QuickTime to load. The QuickTime plugin in VEGAS Pro 17 has been turned off as QuickTime is no longer supported on Windows. You may, however, reactivate the QuickTime plugin by going to Preferences and selecting the “Deprecated” tab. From there you can turn on the QuickTime plugin if you still need it.

  • Bill Burnette

    November 26, 2018 at 5:49 am in reply to: hellllllllppppppp lol

    .478 doesn’t sound right. 60/134 = .44776… call it .448, but then correct for some drift. Assuming no fades …

    Calculator problem?

  • Bill Burnette

    October 26, 2018 at 3:41 am in reply to: Additional DRAM

    Normally, 13G physical used of 16G seems to leave a lot unused (unneeded). But I’m wondering how much of that memory is “compressed” and what the complexity is as Windows moves memory to and from the compressed area.

    If your CPU never goes above 60% and your memory never goes above 13G, then it sounds like disk I/O, i.e. reading the source files and writing the output file (when rendering), could be a bottleneck when your preview doesn’t work well. Of course it sounds like it is working well in your present scenario. Your browser may use a little CPU, RAM, and network bandwidth, but probably not much disk I/O in your latest scenario. If some of your video source is on a networked drive, that could slow things down.

    Bottom line, although RAM is probably the cheapest and easiest upgrade, it isn’t often helpful above 16G with just video.

  • Bill Burnette

    October 23, 2018 at 5:44 pm in reply to: Additional DRAM

    Rich,
    For starters, you can look at system usage while your worst case Vegas activity is running (I assume render?).

    The way to do this is start task manager (CTRL-ALT-DEL) and look for the “Performance” display (In Windows 7 it is a tab). The performance display will show CPU usage and memory usage. If CPU is up near 80 to 90% or above, then that is your bottleneck. If CPU is lower, then the two possibilities are disk throughput or RAM. RAM is less likely since you have a fair amount.

    Task manager will show you a graph of RAM usage and also a text display of “Available” physical memory. If available RAM is well above 0 (say a gig or more), then more RAM won’t help. If you use W10, the task manager is reformatted, but you should be able to find CPU and RAM somewhere.

    Bill

  • The Best Buy store clerk should have mentioned that there are dual layer writable DVDs (capacity 8.5 G), and there are inexpensive consumer-level DVD writers that can write them.

  • Bill Burnette

    August 24, 2018 at 2:24 pm in reply to: using sony vegas 14 as a multi-track audio recorder

    Duane,
    The professional DAW software Sonar recently became rebranded and free. It’s Digital Audio Workstation software that is geared to multitrack recording, editing, mixing, effects application, and rendering for publication. Its new name is Cakewalk by Bandlab (https://www.bandlab.com/products/cakewalk).

  • Bill Burnette

    June 14, 2018 at 6:57 am in reply to: My footage has gone missing!

    Did Disk Cleanup run? It removes “old” stuff from the system temp folder, the one you mention.

Page 1 of 5

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