Forum Replies Created

  • Mike Silberstein

    December 19, 2011 at 11:28 pm in reply to: No AAC audio using Sony AVC (.mp4) SVP11.
  • Mike Silberstein

    December 19, 2011 at 3:16 am in reply to: No AAC audio using Sony AVC (.mp4) SVP11.

    I just repeated Sony GPU benchmark test with footage tracks muted leaving only generated media in the project. No sound in Sony avc mp4 render. When I unmute all tracks same project renders ok. Weird.

  • Mike Silberstein

    December 18, 2011 at 1:03 pm in reply to: No AAC audio using Sony AVC (.mp4) SVP11.

    This problem seems to be hardware and content dependent. I’m having no audio track in mp4 sony AVC renders on a Win 7 x64 machine with AMD 6770 GPU in a simple test projects where only media generators and a wav file are used. But Sony’s GPU vp11_benchmark project renders flawlessly. Mainconcept gives me “The reason for the error could not be determined” upon render attempt with “GPU if availavle” but render is fine when “CPU only” is selected.

    Any render is fine on a Win7 x32 laptop with NVIDIA card that is simply not compatible with Vegas 11, it’s not visible in prefs, Vegas only utilizes CPU to render.

  • Mike Silberstein

    January 17, 2010 at 2:32 pm in reply to: Jagged lines in Vegas

    Thanks for the hints. I’ve figured that out. It definitely has to do with deinterlacing.

    If I drop the test file on the timeline and look in the clip properties I can see that Vegas interprets it as “interlaced upper field first” for some reason.

    Without changing that, if the project settings have deinterlace method set to “None” or “Blend fields” it renders a nice and smooth image. Perhaps you had your project set to one of these.

    If deinterlacing is set to “Interpolate fields” – here come the jaggies.

    If I switch the clip’s field order to “None (progressive scan)” Vegas renders it all nice and clean with ANY of the project’s deinterlace options.

    As I have learned Vegas does not recognize the field order of a progressive scan AVI thinking that it’s interlaced – that happens even if I drop the AVI just rendered by Vegas with progressive scan option. And if the project settings are set to “interpolate fields” Vegas tries to do some weird stuff.

    Gotta be careful to match clips and projects interlace settings in the future.

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