The fact that Supermicro is involved is extremely interesting.

Well, a bit over my pay-grade/budget but... if they decide to launch a "Win a New Vegas Pro Master Suite!" sweepstakes ad campaign, please let me know.
Just kidding--no, actually I'm not kidding.
DO let me know :)

Speculate... speculate...

... but if 2 x Xeons at 2,63 GHZ is the top model, then there must be some heavy en/decoding etc. planned in the Nvidia® Quadro® FX580 graphic card.

I already have 2 x Xeon quads at 2,8 GHz.
It works - Ok - sure - but it is at the lower limit for i.e. previewing some AVCHD 1080i 25 Mbps *) -- meaning that just a little x-fading or color correction or some 2-3 active tracks make the Fps go down - and which you certainly would not expect from a 7 K$ professional NLE system.

)* from SONY's own cameras.

It would be extra-interesting if Sony offers a Suite upgrade deal for existing license holders.

ritsmer,

Those cpu's are quad's with 8 threads each. So I am assumeing they are the same as yours just a little less megahertz.

I am running the same setup- a dual quad xeon setup with intel board. It works very well for me, but I have yet to touch avchd from a camera to test... I hope I never have to unless some major changes come forth.

I would dare say that my system is very comparable to theirs but mine only cost me around 2,000 to build.

j razz

When Peronne says "interesting . . " - I'm very attentive to what comes next . . . .

Grazie

"Interesting," some people may say, "the king is naked."

The Supermicro stuff I have had reminds me of the old Western Electric no holds barred reliability and quality. The old Western Electric shipping crates and oak ladders are worth more than todays Cadillacs.
JJK

And then you look at the new Adobe Mercury Playback Technology demo at http://cs5launch.adobe.com/ and bemoan why not for us?

I wonder what happened to the SCS and AMD partnership from a couple years ago?

kairosmatt

It's about time SONY realized they needed to come up with standardized hardware known to work as trouble free as possible. This listing of hardware now provides a shopping list by which others who choose to piece their computers together can compare to.

Now they need to do the same thing with pre-configured laptops and then SCS can be looked upon at a similar level as AVID who has always spec'd machines known to work from the go-get.

SCS is getting my attention with this announcement

Cliff Etzel
Solo VJ : Web Designer
bluprojekt | SoloVJ Blog
--------
Desktop: OS: Win7 x64 | CPU: Q6600 | Mobo: Intel DG33TL | 8GB G.Skill Dual Channel RAM | Boot/Apps Drive: Seagate 160GB 7200RPM | Audio Drive: Seagate 160GB 7200RPM | Video: WD Black 2x750GB (1.5TB) Raid 0 | Render Drive: WD Black 640GB 7200RPM | Vid Card: nVidia GeForce GT 220 1GB

Laptop: Dell Latitude D620 | C2D 2.0Ghz | 4GB G.Skill RAM | OS: Win7 x64 | Primary HD: WD 320GB 7200RPM | Video HD: WD 250GB 7200RPM

As said above the Supermicro kit is top shelf. The level of support I was able to get with my old system was excellent. Called support and there was a man at the door in 15 minutes and the problem fixed in 30 minutes.

The real problem though was that Vegas ran faster but with exactly the same bugs as everyone else was having. Users buying this level of equipment will have the reasonable expectation that the preloaded software is of the same quality as the hardware. I fear they will be dissapointed and will become the touchstone for negative publicity . SCS needs to get the serious bugs out of their code before they go chasing high end users. Piss them off and they will not come back and will take a lot of users with them.

Bob.

You nailed it, Bob.

farss said:

SCS needs to get the serious bugs out of their code before they go chasing high end users. Piss them off and they will not come back and will take a lot of users with them.

Well said Bob

Cliff Etzel
Solo VJ : Web Designer
bluprojekt | SoloVJ Blog
--------
Desktop: OS: Win7 x64 | CPU: Q6600 | Mobo: Intel DG33TL | 8GB G.Skill Dual Channel RAM | Boot/Apps Drive: Seagate 160GB 7200RPM | Audio Drive: Seagate 160GB 7200RPM | Video: WD Black 2x750GB (1.5TB) Raid 0 | Render Drive: WD Black 640GB 7200RPM | Vid Card: nVidia GeForce GT 220 1GB

Laptop: Dell Latitude D620 | C2D 2.0Ghz | 4GB G.Skill RAM | OS: Win7 x64 | Primary HD: WD 320GB 7200RPM | Video HD: WD 250GB 7200RPM

What, specifically, are these "serious bugs in their code?" I mean actual bugs that anyone can reproduce on any machine. I'm not being sarcastic or flip, let's list the actual known bugs.

I may not use every obscure feature in Vegas all the time, but I work in Vegas for hours each day doing primarily HD from HDV, XDCAM and some AVCHD sources and Vegas works as advertised, always has.

John, there must be some bugs in Vegas 9 since the engineers have been working with Vegas 9d for five months now.

But the biggest shortcoming as I see it, is the existing plug-in interface (API) - if that's the correct term, but you understand what I mean. This is probably ONE reason that there are so few plug-ins for Vegas, and some plug-ins does not function well (Boris as an example). I think pro editors also looks at the available plug-ins when they consider which NLE to purchase.

Jøran

Really?

We just had a single user leave this forum after pointing out 4-5 of them. I consider running out of memory on a render a bug. And that is reproduceable by a LOT of folks.

Bob hit the nail on the head. The group of users dropping $7 on an editing suite could buy ANY system they want. They are not going to want unknown render issues, preview problems, inability to rotate stills, etc. That's just not acceptable at that level.

I don't think so. Boris has an error message that stops the user from appling to many effects because it will crash Vegas. The message states to render in the Boris app because it can get the job done there so to speak.

Therefore, if people put too many filters on a clip and crash a render it is their fault for putting on to many filters. It's up to the user to do multiple renders and to not stack effects and filters so as to not crash Vegas.

Vegas is not After Effects, it's not made for tons of effects. Its for quick edits with a little polish.

HD just exacerbates the issue.

I agree with John, vegas has been good on my systems and laptops. The mysterious red frames did appear about two months ago, but that appeared to be related to disk io problems, 1 year old drive was not responding well. I've sure that Farss comments have real meaning but I have not directly experienced all of them, so I consider them issues to keep an eye on! But the real fact is both John and Farss probably use vegas for video editing a lot--lot more than I do, so my feed back has limited value---- but I do push vegas hard with 4K projects, with a lot if mjpegs,... ;-)

FishEyes, I'm not talking about error messages. I'm talking about the plug-in interface that makes it compleatly impossible to use Boris FX inside Vegas. I'm talkning about these NOTE's in the BORIS FX9 User guide:

Applying a Boris Effect as a Video Effect
Boris appears in the list of available video effects in the Video FX window and can be applied as a video effect the same way you apply any native video effects in Vegas.

NOTE: The Boris timeline will not display updated video frames while launched inside Vegas. Only the video frame at the cursor location displays in the Boris timeline. This limitation of Vegas’s architecture does not impact rendering effects.

1. Drag the Boris video effect from the Video FX window to an empty event or video clip. The Event Effects window opens.
2. Click the Launch Boris FX Button to open the Boris user interface and create your effect.

NOTE: Place the Vegas cursor on the first frame of the effect to display the first frame in the Boris timeline. Otherwise the frame at the Vegas cursor location displays in the Boris timeline.

3. In the Boris Timeline window, set the effect duration to match the duration of your Vegas effect by typing a new value in the Duration field and pressing Enter.

NOTE: If the Boris effect duration does not match the Vegas effect duration, the rendered effect in Vegas appears differently than when you preview it in the Boris user interface.

4. Choose Edit > Preferences to open the Preferences window. In the General tab in the Preferences window, set the Project Options to match the project size, FPS and aspect ratio that you are using in Vegas. Click OK to close the Preferences window.

5. You can now open settings from the Keyframe Library or create your own custom effect. When you finish creating your effect, press the Apply button or Cancel button to either apply the effect to Vegas or cancel and leave the event or track unchanged.

Jøran Toresen

So, here's me sticking my head above the parapet, we have 2 Camps (?):-

Camp-1: We have Bugs and they still need to be rectified and that a more powerful PC will EITHER uncover those bugs faster OR that these same bugs will be dealt with (squashed) by faster processing.

Camp-2: We don't have bugs and have always needed a more powerful PC to do the job.

If I have understood this, in which Camp is the King not Wearing Clothes?

How's that from a non-IT specialist?

"Interesting . . . " - very.

Grazie

J0ran, Boris fx9 and RED are nice but very difficult to use inside vegas vs other more simpler plug-ins. I wish it was a lot smoother, it would "feel" more PRO.