Forum Replies Created

Page 39 of 88
  • Norman Black

    June 24, 2014 at 4:50 pm in reply to: Sony Vegas and GTX770M problem.

    You obviously have both the intel and nvidia graphics installed.
    Is the Intel graphics the selected device in your Vegas video prefs? With multiple video devices installed you can tell Vegas which one it should use.

  • Norman Black

    June 23, 2014 at 3:14 pm in reply to: Prevent slow mo lag with Motion Blur ?

    What you are calling “slow motion lag” sounds like the frame blending due to resampling the video to get your slow motion. You can turn off resampling on an event but your result may not look smooth since Vegas will be duplicating frames.

    There are third part resamplers like Respeedr and twixtor you can try if you do not like the results with resampling off.

    For ideal slow motion, you record at a higher frame rate than your playback.

    “Motion blur” in Vegas is an envelope on the video bus. Turn on viewing of the video bus and then add the motion blur envelope. Motion blur is not going to give you something you think. It only has effect on pan-crop and/or track motion movement. And then, it is not much of a blur effect but rather but more of offset fading echos of the image.

  • [John Rofrano] “I do the same thing for footage that needs to be stabilized. I stabilize it separately and place the clean video into my project. This way, the final render doesn’t have to involve stabilization, noise reduction, and other “clean up” activities”

    +1 on that.

  • [gary orish] “When I tried your solution, the image was cropped (great!) but then the ENTIRE TRACK was panned off to the side (and was hidden from view)”

    Of course. Reset the track motion at the end of the event so the next event is default or whatever you want to do with the next event.

    Since you want to crop into an event AND then move it around the screen you have no choice but to use pan/crop AND track motion in combination.

    If all you wanted to do was move the whole event around the screen you can do that with just pan/crop or even track motion, whichever you prefer.

  • Norman Black

    June 20, 2014 at 10:30 pm in reply to: Loudness Meter Levels for Feature Films

    Digital signals max out at 0dB. The THX 105dB spec is the theater sound system sound pressure level corresponding to a 0dB input signal. This is with a properly calibrated THX sound system setup. Obviously someone uses a reference signal to calibrate. They adjust the sound system amplifiers so that a -20dB test signal gives 85dB SPL to the audience ears. A theater could certainly turn the volume lower or higher if they want, but that would not be within THX spec.

    -25 to -30 are supposedly typical signal levels for average dialog in DTS and DD.

    On your TV, PC or phone you have a volume control. Not so in the theater and this is what THX is all about. It sets a spec such that you the author can get the volume you desire at all points of your material since there is a connection between your signal level and actual volume level in the theater.

    My local theater is either turning the volume above THX spec, and they claim to be THX certified, or the recent trend in movies that that they are encoding a higher dialog volume level and thus using less dynamic range.

  • Norman Black

    June 20, 2014 at 6:36 pm in reply to: Loudness Meter Levels for Feature Films

    Movies are their own thing and about freedom of artistic vision. If the movie producer wants the movie to be frickin loud then so be it.

    THX is the common standard there and THX is all about what the sound system can deliver. Knowing what the sound system can do then you can do your sound how you envision.

    THX says the speakers need to be able to attain 105dB with a 0dB signal. This means a -20dB signal should be 85dB at listening position. The LFE channel goes 10dB higher than the others.

    -25 to -30dB for average dialog is supposedly common for theater mixing. This leaves lots of room for REALLY loud stuff like explosions and such.

  • What type of MOV files? A dump from MediaInfo would help.

    Vegas bypasses Quicktime for MOV files which DSLRs and digicams typically produce. AVC/H.264 and PCM audio. You can right click a file in the project media tab and go to the general tab and scroll to the bottom. What plug-in is Vegas using. If the qt7plug then Vegas is using Quicktime. If compoundplug, then Vegas is handling the file(s) directly.

  • Norman Black

    June 17, 2014 at 1:46 am in reply to: Recovering a temp file

    It is in your temp folder, but Vegas deletes that file in favor of new one(s) to be created in the new session.

  • [Sean Toombs ReVz] “Again, the rendered video itself from Vegas has always been fantastic, but the Youtube video is just terrible. “

    Youtube re-encodes EVERYTHING you upload to them. If you do not like their result there is nothing you can do in Vegas to get Youtube to give you a better Youtube result. You just waste your time uploading higher quality video streams than necessary.

    Speed of movement and high frequency detail are always problems with Youtube/Vimeo encodes. Their encodes are low bitrate.

    The only things you need to do are make sure your upload file is 30fps or lower since your game capture source is likely well above 30. Make sure resampling is OFF since your are changing frame rates on high motion sources.

  • Norman Black

    June 16, 2014 at 4:06 am in reply to: sony vegas correcting the graphics look :/

    The unedited footage looks the same as edited. I am not sure how you uploaded the source footage to youtube. Did you bring it into Vegas and render the same as you did your edited footage? It looks likes you did.

    If Vegas input and/or render is the source of the issue then both would/could get the same issues.

    This video still has blurring of the text so it looks like it might still be the edited one. Your original screen shots had no blurring on the text so I do not think the original has blurring.

    It looks like some of the posterization is occurring on and around gunfire hits/effects.

    Since I am still a little short of information I can give you a couple of things to try of a general nature.

    IF the problem is with the Xvid source decoding. You might try uninstalling whatever Video for Windows codec you installed to get Xvid to work and reinstalling it or trying a different Xvid codec. Windows does not support Xvid by default and Vegas does not install any codecs into Video for Windows so something was installed. Maybe your game recorder. Your video driver may have installed something.

    Or transcode your AVI file to something Vegas can edit natively with Handbrake or cliptoolz convert or similar. Might be the simplest option.

Page 39 of 88

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