Forum Replies Created

Page 5 of 15
  • Rob Franks

    January 13, 2011 at 2:24 am in reply to: MainConcept AVC Render Issue

    You’re using 2 pass vbr. What is your low end bit rate setting. I’m thinking maybe it’s too low (motion takes a fair number of bits)

    I don’t use MC. Is there a CBR setting? If so try that at a relatively high bit rate on a short sample and see if that clears it

  • Rob Franks

    January 13, 2011 at 2:17 am in reply to: the sheer Power

    Again, more memory does not equate to speed. It equates to how much MORE of the time line you can load into preview memory for playback. Now running dual or triple channel (as opposed to single channel) or running faster memory at higher bus speeds *MIGHT* decrease render preview by a few milliseconds… in other words nothing substantial because it is not the main objective of more memory… it is the AMOUNT of time line (and its complexity) you can load during a single SHIFT-B session that will differ.

  • Rob Franks

    January 13, 2011 at 1:46 am in reply to: the sheer Power

    Sorry… forgot the rest.
    No. More memory does not equal speed. Rendering speed is more a function of cpu size(speed). Increased memory simply equates to ability to handle more on the time line and more in preview ram.

  • Rob Franks

    January 13, 2011 at 1:41 am in reply to: the sheer Power

    Well you didn’t exactly specify WHAT vegas you had now did you. I run both the 32 bit AND the 64. Many (including myself) still run the 32 bit version (even though we have a 64 bit os) because a lot of the 3rd party plugins still don’t work in 64

    At any rate, You’re doing something wrong then because Vegas 64 will see a lot more than 4 gig. The max in vegas 64 is 32,768MB.
    I have 6 gig ram and if I go to preferences to view my preview ram limit it says: 5118MB

  • Rob Franks

    January 13, 2011 at 12:46 am in reply to: the sheer Power

    I assume you’re using Vegas 32bit?

    In vegas 32 bit the maximum setting for preview ram is 1024. The is because it assumes you are running a 32 bit os which has a 4 gig limit (Vegas needs memory for other things… your os need memory …etc)

    Now you can cheat a little and bump this up as high as 3072… but that’s the max for Vegas 32

    How to cheat:
    Hold the shift key down while clicking on preferences. You will see an additional tab open up in the preferences settings called INTERNAL.
    Scroll down until you see “RAM PREVIEW LIMIT (MB)”. Now change this value from 1024 to 3072 and hit enter. Take note and make sure the change has been made. Close Vegas and restart.
    Now go to RAM PREVIEW in options and you will see the max limit at 3072. You are free to use all of this, but remember to turn it back down to a reasonable number before rendering (ie: 256 or similar) or your renders may be a bit slower.

    *NOTE*
    Be careful about screwing around with the settings under the internal tab. You can screw up vegas by changing things that you don’t know about!!!

  • I could be wrong but I’m pretty sure Vegas (or any other editor) will not open the audio in a container format when there are multiple audio tracks muxed in.

    Download TSmuxeR (free download), demux into separate audio/video streams. Choose the audio track you want, then remux to a M2TS file. Vegas SHOULD open that properly.

  • Rob Franks

    January 10, 2011 at 1:05 pm in reply to: inconsistent 3gp behavior

    3gp is a CONTAINER format. In other words you can use a number of different codecs in different arrangements, so you need to look INTO the container and see what codecs there are and what arrangements… then check with Vegas to see if it supports what you have found.

  • Rob Franks

    January 8, 2011 at 12:12 am in reply to: Do Sony Want Vegas to be taken seriously?

    I have Avid MC5 and while it edits video extremely well… that’s about all it does. Its input/output is hideous to say the best.

    There is a thread going on right now on the Avid forums on how to get avchd into MC. The thread is nothing short of comical. One suggestion in fact is to download the trial of Vegas, import your mts files then export as mxf for import to MC. They seem to be impressed with the fact that through a lot of trial and error they have narrowed the avchd import time down to 3 to 1. In other words 3 times real time… or 3 times SLOWER than capturing hdv. Now imagine that… a $2500 program and people are talking about picking up Vegas in order to complete MC.

    Did you know that you can’t even import a native mpeg without transcoding or running through AMA?

    MC’s audio section pales in comparison to Vegas’s

    Avid DVD which comes with MC is done by Sonic as is the same as Roxio’s DVDit Pro HD. Support has all but evaporated on it. It’s no where near as good as Sony’s DVDa either

    Don’t get me wrong…. MC is an excellent cutting tool… but that’s all you’re getting for your $2500.

    Now I sure do wish Sony would have added something like motion tracking long before they added 3D abilities but then on the other hand (and just for example), Vegas is the only NLE that comes with a CERTIFIED pro level Dolby Digital encoder right out of the box… and that’s not cheap.

    While MC can run circles around Vegas on the cutting field, Vegas outdoes MC on just about every other front. That’s pretty good for a program that’s 5 times as cheap.

  • If you want 19020*1080 then you will have to buy a Blu Ray player and start burning Blu Ray.

    If you want dvd at the same quality as a commercial dvd then I suggest you buy a movie studio…. because that’s the only way it will happen.

  • Rob Franks

    January 5, 2011 at 3:17 pm in reply to: Rendering doubt!

    It sounds like your rendering as uncompressed avi which is big.

    What codec/format are you rendering to?

Page 5 of 15

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