PerfectPhase wrote:Is it really necessary for ES to have this functionality when you already have the likes of Premier etc out there? I would have thought that the workflow would be to edit video in an external application and then import into Expression to be encoded?
Yes, it makes sense if Microsoft wants to compete with Adobe. Microsoft should add a non-linear video editing application to the Expression Studio suite and integrate it with the rest of the applications in the product.
As things currently are, Microsoft has a long way to go to catch up with Adobe, and there isn't a compelling enough story for designers to pick up Expression Studio. Adobe is the incumbent. Microsoft is just getting started.
I currently use both Adobe Premiere Pro CS 3 and periodically Adobe After Effects.
Most people buy suites or studios of software not individual applications.
The web is more and more about video including Channel 9 and Youtube.
If Microsoft wants to capture the creative professional market, it has no choice but to have both a NLE and motion graphics applicatons as part of the Expression Studio.
This is a very glaring hole in Expression Studio that I am assuming the Expression team is working on. My guess is you may see it in version 2.0, but more likely 3.0. If they are not, forget the creative professional market.
Currently Adobe owns the creative professional market:
and several more but why rub it in.
Need I say more.
Microsoft has its work cut out for them.
Their key advantage is the .Net Framework, Visual Studio and SQL Server that they must leverage with the Expression Studio as the tool set for creative professionals and the developers that work with them.
I know our pre-release milestone naming is a little inconsistent and at times appears haphazard. We're working to standardize the naming and make it clear to testers that "Beta 1" means "this" while "RC1" means "that".
Regarding this specific milestone naming, there are a couple of reasons we named it RC0.
I know that the answer "because we've done it this way before" is lame, but it's the truth. We've named many first-RCs as "RC0" in the past, so we rolled with that name this time.
2. We're dorks.
...so we frequently start counting things starting with 0 instead of 1. We do this everyday in the 100's of lists we manage. In fact, our prioritizations even start with "Priority 0".
Thanks for drawing the distinction between Silverlight 1.0 and 1.1.
I already got it, but some people miss it.
Will Silverlight 1.1 be ready for Visual Studio 2008?
How much of the functionality in percentage terms of WPF will be in Silverlight 1.1? I have heard over 90%.
Since Tim is back from vacation, suggest a video and demo aimed at the "creative professionals"--web designers and Flash animators--that are not developers--using Blend to publish a Silverlight app or movie.