Foundry's Storm - what does it make redundant?

[Karel Bata]

http://www.thefoundry.co.uk/products/storm/

Yes, I know, I should read all the zillion posts in the relevant threads...

Has any one figured out yet what the capabilities of this have made redundant? Clipfinder seems like the obvious one. What about the other RED software?

I ask because I'm still learning, and I don't want a repeat of what happened to me with Shake where the week after an expensive Shake course Apple bought it and announced the next version was Apple only - and I was on PCs at the time!

[M Most]

http://www.thefoundry.co.uk/products/storm/

Yes, I know, I should read all the zillion posts in the relevant threads...

Has any one figured out yet what the capabilities of this have made redundant? Clipfinder seems like the obvious one. What about the other RED software?

I ask because I'm still learning, and I don't want a repeat of what happened to me with Shake where the week after an expensive Shake course Apple bought it and announced the next version was Apple only - and I was on PCs at the time!

Since it only handles R3d files at the moment, it really doesn't make anything redundant for anyone who has to deal with footage from any other camera, even occasionally. As far as Red's own tools go, it's likely that Redcine X and it's eventual descendants will always be updated to the latest code faster than anything else. Because of this, they will not likely be redundant if you want to have access to the latest features at the earliest date.

[Karel Bata]

Hmm..

Good answer. But it assumes that the latest code gets installed by everyone the moment it's out. But is it? I'm not a RED owner, but I'd be inclined to see if any one reports bugs before going for any upgrade. Likewise any one used to using Storm would likely wait until The Foundry caught up (providing they're quick about it) before upgrading their camera.

Kind of depends on how close RED and The Foundry are. At the moment it looks like they're very close.

[Alexander Ibrahim]

Hmm..

Good answer. But it assumes that the latest code gets installed by everyone the moment it's out. But is it? I'm not a RED owner, but I'd be inclined to see if any one reports bugs before going for any upgrade. Likewise any one used to using Storm would likely wait until The Foundry caught up (providing they're quick about it) before upgrading their camera.

Kind of depends on how close RED and The Foundry are. At the moment it looks like they're very close.

Yes, people do install the latest RED software right away.

They don't get rid of their tested stable versions though- they just maintain multiple versions.

As far as camera firmware goes, I usually upgrade and test between productions- but during production I always stick with my last fully tested firmware. Most of the time you can downgrade firmware versions if needed.

[Mark L. Pederson]

Since it only handles R3d files at the moment

emphasis on .... moment.

[Jeff Kilgroe]

Post workflows are very diverse and not only differ from one production or post house to the next, but differ from one production or individual production task to another. That said, I don't think there's any tool out there right now that can render another obsolete.

The good news is that Storm will be available to everyone soon and you can decide for yourself then. All I can say is that you must get STORM.

[Peter Majtan]

As Mark have said - "at the moment" is the key part - and to add to this - it also supports QuickTime "at the moment". So until ARRI activates the RAW capture for the end users, Alexa's footage will work as well, and so will most of the DSLR's... :devil: But the key strength of Storm is the non-destructive workflow for RAW data (think Aperture/Lightroom for motion cinema) which You only get with the RED footage...

Peter

[Peter Majtan]

And to answer Karel's question:

In my opinion both REDcineX and Storm will coexist into the future. The main purpose of REDcineX is for RED to be able to immediately implement and test any new features of the cameras and color-science and to provide free tool for everyone working with RED RAW data. Storm on the other hand is meant to be production-oriented tool with full support and reliability associated with The Foundry. It also goes way beyond the scope of REDcineX to expand to a complete workflow tool to take You from start to finish. As Storm will shape up, expand and stabilize over the coming months You will see more and more people "dropping" the little assist apps. This was the main drive behind the Storm in the first place. There are many tools that take care of individual steps in our workflow, but the main "nightmare" was to make them "talk" to each other. The goal for Storm is to keep al the tools needed during the entire workflow within a single SW environment and if You do want to use other SW's - it will help to manage the communication in both directions...

As Jeff have said - You all will soon see the potential for yourselves. Keep in mind though that the Public Beta is not going to have all the features implemented right at the beginning. Things will be added as we progress down the line. The best part is that just like RED, The Foundry is listening to the end user and wants to work with us to design and develop a tool that we actually need and will use in the real world...

:sifone:

Peter

[Karel Bata]

I can't wait! I love The Foundry's other software. This has to be good.

I attended an Adobe presentation some years back where someone asked "Why can't we have all these tools in one package?" Everybody laughed. Adobe have come a long way since - like the degree to which AE and Premiere talk to each other, but it's still not quite there. Having different teams develop the different softwares probably didn't help. It's rather like Microsoft's dilema - if only they could just start again from scratch! Legacy issues. Which is what they're avoiding here, and it's very encouraging. As is The Foundry's relationship with RED. As is the price! Truly aggressive, without - er - being aggressive.

So - er - can we start a wish list..? :reddevil:

[Christoffer Glans]

No PC-support?

Since there's such a low focus on Macbook pros as a professional choice for heavy on-set and flexible post production work, there are a few really powerful choices on the PC market.
The Elitebook 8740w with dreamcolor display kicks the ass on any apple product.

So in seeing this current reality, is there any PC support for the Storm? Or is it mac only?

[Peter Majtan]

Mac for the Public Beta and first release. Windows and Linux will follow the next year's release...

:devil: Peter

[Richard Shackleton]

Steady there Peter (pulls on reigns) - QuickTime support for reading/playback you have seen in the STORM alpha and your eyes didn't deceive you, but it won't be enabled initially for the beta. Got to get R3D proven and solid first. Sorry.

Richard



As Mark have said - "at the moment" is the key part - and to add to this - it also supports QuickTime "at the moment". So until ARRI activates the RAW capture for the end users, Alexa's footage will work as well, and so will most of the DSLR's... :devil: But the key strength of Storm is the non-destructive workflow for RAW data (think Aperture/Lightroom for motion cinema) which You only get with the RED footage...

Peter

[roryhinds]

how far behind is the Linux version?
Apple have left the pro market... didn't you iHear

[Jim Geduldick]

how far behind is the Linux version?
Apple have left the pro market... didn't you iHear

When did Apple leave? Are you meaning because they have been more focused on other things currently then FCS?
I dont know any studio that isnt running Mac's as main stations even along side Linux machines.
Especially RED related Mac's have a extremely strong presence.

I am sure Richard can explain more why the choice for OSX/Mac support came 1st in the dev process.

[Uli Plank]

And then there is Smoke, Resolve … Even CS5 is available for OS X. Who says that FCP is the only important program on a Mac?