Sony Vegas Platinum and Pro

Discussion in 'Professional Video Production' started by Mxsmanic, Apr 30, 2011.

  1. Mxsmanic

    Mxsmanic Guest

    I'm a bit confused about Sony Vegas.

    I see there's a Pro version for about $600, and a Platinum-something version
    for ten times less. Do both products have the same code base, and if so, what
    does the Pro version provide that the Platinum version doesn't have, in
    exchange for the extra $530?

    Also, do the Vegas products install rootkits or other squirrely "protection"
    mechanisms? (I haven't trusted Sony software since it put rootkits on its
    Mxsmanic, Apr 30, 2011
    1. Advertisements

  2. The various versions of Vegas are described here --
    and compared here --
    The "little secret" is that for most work, the cheap version works
    just fine for most people (and it is cheap at;-).
    The Platinum 10 "consumer $129.95" version is worth the bit
    extra to get the extra transitions, filters, and sounds. If you are
    doing 3D, subtitles, crawls, sub-edits, multi-camera, etc., the
    Pro 10 version may be worth the money, but otherwise, they
    all look and work like the others. You can see "how-to" videos
    for these programs here -- programs also have built-in tutorials).> Also, do the Vegas products install rootkits or other squirrely"protection"> mechanisms? (I haven't trusted Sony software since it put rootkits on its> CDs.)Dunno. I've had no problems that I may associate with anythinglike this...--DR
    David Ruether, Apr 30, 2011
    1. Advertisements

  3. Mxsmanic

    Ptas Guest


    I have tested both using files coming from Canon 5Dkm2 (without conversion).
    Platinum does not support those files well and programme crashes after
    adding 15-20 short clips. Pro version works very well, simple i3 is enough,
    I faced no problems.

    I have asked Sony for support and explanation. After few emails Sony
    explained that Platinum is not based on the same code as Pro. After 30 day
    testing of both products it looks very like it. for me no way to buy cheap
    this nice software .....

    Best regards,

    Ptas, May 4, 2011
  4. Thanks for the information. While working with Platinum 10 on a friend's
    computer, I did find it quite useable with more "normal" source material,
    but even with that, the track ordering and naming needs to be reset in
    order to work as easily and in as straight-forward a way as with the
    "Pro" version - but for most, editing most material, this may be a minor
    inconvenience compared with the huge difference in price between the
    two programs. The Pro version does seem to handle almost any format
    easily (I was able to edit the new 60p TM700 footage on an older version
    of Vegas Pro while Adobe and FCP users were still waiting for updates
    for their programes to do the same thing - and the now one-version-older
    Vegas 9 can edit 4096x4096 RED video, which I may find useful for
    "roaming" around inside of high-resolution stills while maintaining full
    1920x1080-60p output characteristics).
    David Ruether, May 4, 2011
  5. Mxsmanic

    Ptas Guest

    Just found comments from Sony:

    The Vegas Movie Studio HD Platinum 10 is a native 32-bit application, which
    means that it can only access up to 2GB of memory. Vegas Pro 10 is a native
    64-bit application, which means that it can access up to 8TB of memory. This
    is why are will likely see better HD file handling within the Vegas Pro 10
    program. I understand if you do not wish to upgrade at this time. However if
    you don't upgrade, the best option would be to try splitting your video into
    sections, editing each section, then importing the edited sections into
    Vegas Movie Studio HD Platinum 10 to render the project as one file.

    By the way have tested both on very average desktop i3, 4GB RAM, GForce 240.
    For me the only way is to buy Pro version .....

    Ptas, May 4, 2011
  6. Likely true, given what you pointed out earlier, and the "PITA" aspect of
    editing sections and combining them later (although I used to need to do
    with even Mini-DV in the very early days, and more recently, with different
    file types on the timeline at the same time which caused problems). As for
    the above, I think 64-bit Pro must run on a 64-bit OS, but in practice I saw
    little difference in the two Pro versions (which are sold together) except
    that I can make longer RAM previews in the 64-bit version where I can
    assign 3-4 gigs of RAM for previewing with 6 gigs in the computer (this is
    very useful). If not for this, I would return to 32-bit XP and get back some
    programs I lost with Win 7 64-bit - and not need to deal with a dual-boot
    system or a virtual XP within Win 7 to use the "lost" programs.
    David Ruether, May 4, 2011
  7. Mxsmanic

    Aretwodeetwo Guest

    That explains why Vegas Platinum 10 installed in Program Files(386)
    I thought it was 64bit. Bummer. Still works great!
    Aretwodeetwo, May 4, 2011
  8. I just installed the trial edition of Vegas Pro 10 last night (64bit).
    It had taken me about 3 weeks of wrestling with Vista's "Windows Update"
    and various other issues before I could get Vista's SP2 installed, and
    it took many hours of help from Microsoft, but eventually I met the
    prerequisite for installing Vegas Pro 10.

    I especially wanted to get a feel for multi-camera editing. And I liked
    how Vegas does it. Until it froze.

    Last time I tried Vegas was at version 9, and it would freeze when I
    just tried panning the cursor around in an HDV clip, within a minute
    of starting it up. I had hoped 10 would be better. And I guess it is,
    because I ran it for more like 15 or 20 minutes this time before it

    I had loaded 1 cameraA clip, about 8 cameraB clips, 2 cameraC (HD) clips
    preprocessed with avisynth and virtual dub and now in Lagarith 24p avi's,
    and about 8 more close-up clips derived from cameraC with some earlier
    processing (ditto, but in SD format). This gave me 4 cameras, plus I
    had one master pre-mixed audio track. I didn't bother to try to get
    everything synced correctly yet -- I just wanted to try the editor, you
    know? And it was working fine for a while. I was switching between
    cameras, etc. Cool stuff. But then, it just froze, never to come back.

    This tells me that Vegas has a very nice design, a good inteface, but
    it just doesn't work well enough to trust it.

    I also got the trial of Edius, and it is confusing me rather greatly.
    It appears to take a very different approach from Vegas, Premiere, and
    various other programs I've seen or tried. Maybe it just takes some
    getting used to. I should try some tutorials, I guess. But for the
    moment, I'm left thinking that I might be better off with Premiere than
    these other two choices. Edius's trial period may not last long enough
    for me to really have time to evaluate it.
    Keith W. Blackwell, May 4, 2011
  9. Mxsmanic

    J. Clarke Guest

    If you're getting freezing, check your cooling very carefully. It might
    not be a software problem at all.
    J. Clarke, May 4, 2011
  10. Mxsmanic

    Frank Guest

    Good point, but if it was only Vegas that froze and the system itself
    continued operating, then it wasn't a thermal problem.
    Frank, May 4, 2011
  11. Mxsmanic

    J. Clarke Guest

    J. Clarke, May 5, 2011
  12. Mxsmanic

    Ptas Guest


    My experience was much better. Loaded just two video lines but both fullHD,
    25fps mov from Canon 5Dmk2. About 50 short takes per line, most of takes
    with color correction, gamma modified, some transparency added, etc. One
    audio line.

    Was quite surpeised it worked quite smooth, preview was very acceptable,
    almost smooth. No crashes of Vegas at all. Rendering was working fine.

    Ptas, May 5, 2011
  13. Mxsmanic

    Mxsmanic Guest

    Large volumes of video content were already being handled successfully by
    editing software before the advent of 64-bit hardware, so that's probably not
    the reason. It's harder to write software that handles large amounts of data
    (gigabytes) in a 32-bit environment, but it's certainly not impossible.

    I wonder if there are other differences in the code base besides this. Does
    the 32-bit version of Vegas Pro also perform better than the HD Platinum
    Mxsmanic, May 5, 2011
  14. Mxsmanic

    Mxsmanic Guest

    Actually, I just remembered that both Platinum and Pro require Microsoft .NET,
    which is a very bad sign for any application. Anything that uses .NET will
    require significantly more resources and run significantly slower than
    programs that don't use it, and with 300 million bytes of code, .NET itself is
    a rat's nest of bugs.
    Mxsmanic, May 5, 2011
  15. Mxsmanic

    Ptas Guest

    You are right. Handling loads of video data is not a result of 64bit systems
    coming to the market. Looking at this from different angle: I like Vegas but
    they have problems do deal with 32bit systems ... I guess .....
    No idea, never tried. My 30 days trial expired so cannot really continue and
    not sure I want to spend all that moeny for Pro 10.

    Ptas, May 5, 2011
  16. I'm going to give it another try, this time getting everything sync'ed up
    first. Who knows -- maybe Sony will have some patch or update or something
    that fixes the problem.
    Keith W. Blackwell, May 5, 2011
  17. Since a bug fix appeared for Vegas Pro 8, I've had *NO* crashes with
    either Pro 8 or Pro 9 *at all*, *ever*, **UNLESS** I mixed file types
    on the same timeline (using XP with 32-bit Vegas Pro 8 and Win 7 with
    64-bit Vegas Pro 9). So, the problems with crashes *may* be related
    to mixing file types...;-)
    David Ruether, May 5, 2011
  18. Mxsmanic

    Mxsmanic Guest

    It seems that you only get a few extra features with Sony Vegas Pro, as
    compared to the HD Platinum version. However, those features are apparently
    carefully chosen so that many professionals will need the Pro version to
    handle specific file formats or other special requirements.

    My guess is that the code base is the same. It's economically very unfeasible
    to maintain two completely different code bases that provide virtually
    identical functionality. The usual procedure is to either write one product
    and then selectively disable certain features internally for the cheaper
    versions, or rebuild the product for cheaper versions with the code for
    advanced features removed from the build by switches.

    However, when you go from 32-bit to 64-bit (or any time you change address
    spaces or hardware platforms), there is a tendency for the code bases to

    Anyway, 64-bit does not necessarily equate to better performance. It usually
    does equate to more wasted memory and disk, though.
    Mxsmanic, May 8, 2011
  19. Mxsmanic

    ushere Guest

    balderdash! you have no idea what you're talking about....
    ushere, May 8, 2011
  20. Mxsmanic

    Mxsmanic Guest

    I was measuring system performance before PCs existed. I know exactly what I'm
    talking about.
    Mxsmanic, May 8, 2011
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.