Forum Replies Created

Page 2 of 5
  • A problem I once had with canon .MOVs is that their durations would sometimes not be a whole number of frames. Perhaps the audio was recorded slightly in excess, causing the event duration to be not right for frames. Since I was importing at frame boundaries, this would sometimes leave tiny gaps I could see on the timeline if I zoomed up far enough.

  • If you aren’t editing audio, the setting won’t matter. If you ever time-stretch a video clip, the associated audio will be time-stretched also. Choices like “good, better, best” are usually performance vs quality trade-offs. Vegas had its origin in audio editing on slower computers, so that setting might have been more important at one time. Might as well choose “best” these days.

  • The .255 at the end means software is “broadcasting” on your local network, so maybe trying to contact some particular related program. The port number 9763 may be associated with quicktime streaming service. I saw a forum post that FCP is doing the same thing.

  • How about Sonar’s video view and the thumbnails in the video track?

    (from the Sonar manual) Open the Video view by using the Views > Video command or by pressing ALT+SHIFT+2. In addition to the Video
    view, there is also a Video Thumbnails pane in the Track view

    Sonar has limited video render capabilities, but you can build a score, export it, bring it back to vegas, then render it.

  • Bill Burnette

    September 27, 2016 at 4:55 am in reply to: Pro 13 progress box is wrong

    Can it ever report more than 23:59:59? Anyone ever see that? If not, could be wraparound error, a la Y2K

  • Bill Burnette

    August 31, 2016 at 3:24 pm in reply to: Vegas issues?

    Rough ideas:
    –see if fan or internal airway is dusty/clogged
    –see if clock speed or maximum processor state can be reduced (slower but more stable)

  • Bill Burnette

    August 31, 2016 at 3:37 am in reply to: Vegas issues?

    Laptop: “… cpu ramps up … fan goes crazy … computer shuts down …” Maybe overheating?

  • Bill Burnette

    May 1, 2016 at 7:59 pm in reply to: Render crash

    For the menu problem, possibly you have changed the display setting to make text and other items larger to make up for your higher laptop screen resolution. Possibly vegas doesn’t display so well with that setting.

  • Evidently the part of the encoding that optimizes quality is single threaded. It is not able to use more than one core, so it can’t use 100% of your multicore CPU.

  • Bill Burnette

    September 25, 2015 at 5:09 am in reply to: SonyVegas Doubts

    3. See if this is what you need: Look for the little lock icon in the pan/crop window. Click to lock. Then the time control in the pan crop window will lock to the time control on the main timeline, so the panned/cropped image will show in the main preview window as you operate in the pan/crop window.

Page 2 of 5

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