Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Foundry STORM - we're online

Richard Shackleton

Richard Shackleton

REDuser Sponsor
Joined
Sep 15, 2010
Messages
15
Reaction score
0
Points
0
Location
London
Hi everyone,

Thank you for all of the enthusiasm, feedback and questions so far - and welcome to the STORM section of the REDUSER.net forum!

We are working hard to get the first version of STORM ready for beta. Please do keep providing thoughts and questions through this forum (we're listening) and keep checking in on http://www.thefoundry.co.uk/products/storm/ for product news updates.

Richard
 
Hi Martin,

In the first instance, STORM aims to provide a familiar non-linear editing approach of a basic nature - suitable for experimenting with initial editorial intent (for example timing of shots, short-form cut-based sequences) and supporting conform of an edit performed externally in FCP (and later other editorially focused apps).

So, you will have a source and record monitor, multiple tracks and familiar trimming tools, but not the finesse of the UI or complete integration you would expect from something targeted at the editorial process proper.

As with many areas of STORM, we're starting basic but building a strong foundation - we're certainly excited and planning the potential of growing the editorial focus.


Martin Weiss said:
Thanks. V. excited about this.

There've been some rumors about storm becoming a NLE system. Can you comment?
Click to expand...
 
Nice to see you guys in Reduser! Really excited you guys are working with RED and looking forward to the release of Storm.
 
Richard Shackleton said:
In the first instance, STORM aims to provide a familiar non-linear editing approach of a basic nature - suitable for experimenting with initial editorial intent (for example timing of shots, short-form cut-based sequences) and supporting conform of an edit performed externally in FCP (and later other editorially focused apps).
Click to expand...

I'm more interested in the conform capabilities of Storm than the actual editing.

You know what would be really useful is a feature like Automatic Duck / Clipfinder. I want to be able to take a FCP timeline edited in ProRes, QT proxies, or "Native" L&T and replace it with .R3D. Then send to Premiere or Avid EDL. That would be awesome!
 
Curran Giddens said:
I want to be able to take a FCP timeline edited in ProRes, QT proxies, or "Native" L&T and replace it with .R3D. Then send to Premiere or Avid EDL.
Click to expand...

In the current alpha version you can already do the first half of that. Currently you then grade and render in STORM and send back to FCP.
 
I don't want to go back to FCP is the problem. I'm done with it. This is for when someone brings a project that was edited in FCP and I tell them: "FCP sucks for Red footage compared to Adobe, let's switch to Premiere."
 
Curran Giddens said:
I don't want to go back to FCP is the problem. I'm done with it. This is for when someone brings a project that was edited in FCP and I tell them: "FCP sucks for Red footage compared to Adobe, let's switch to Premiere."
Click to expand...

Premiere and Avid support are on the road-map.
 
Keylight. It would be AWESOME to be able to key the footage in something that allows the flexibility of the R3D media and would let you grade the 2 shots on top of eachother for colour matching, then export them seperately.
 
Ian Laurie said:
Keylight. It would be AWESOME to be able to key the footage in something that allows the flexibility of the R3D media and would let you grade the 2 shots on top of eachother for colour matching, then export them seperately.
Click to expand...

All in due time my friend .....:smile5:
 
A suggestion, if R3d files could work directly with the da Vinci Resolve, using the Unix System in a direct 16 GPUs, it would be the Ultimate. Just a thought.

Humberto Rivera
 
There are already some pretty good tools out there, and maybe Storm already addresses this, but a full-on dedicated ingest and archive system built right into Storm would be fantastic. Especially if you guys are working this closely with RED, and could integrate perfectly with RED Station and anything else they have coming down the pipe.

And once more, I will throw my hat in the "I want storm to replace my NLE completely" ring, just to let it be known. You are already on the right track, any good editing system should also be a great ingest, file management, workflow, and creative tool first and foremost.

As others have mentioned, a system that could build a direct link to Nuke and AE would be fantastic, and more new creative ways to look at and analyze footage would be great as well.
 
You guys make me very happy. Storm will catch us REDusers by storm I guess.
If that thing will work as promoted, you will have a huge hit.
Put some decent editing stuff in it and we wont use Final Cut for long now.
At least for comercials.

Damn, I've been looking for such a tool since the first RED ciné.
Bring it on guys.

Thanks
Tim
 
Tim - Storm concept was born from and the the entire R&D process is driven by us - RED users. This is why the feedback we got at IBC was so tremendous. The Foundry lives by the same vision as Jim's RED - listen to Your customer and design products that the customer wants to use. This is also why it is important for all of us to provide constructive feedback. Just as RED, The Foundry listens...

:devil: Peter
 
Just in case you guys at the foundry are out of the loop, NO ONE IS EDITING RED FOOTAGE TODAY IN FCP. Even the guy who invented Clipfinder has abandoned ship to Premiere and Smoke. With the level of technological expertise exuding from the Foundry, you might as well concentrate on the whole Red post workflow, cut, composite, color, conform, storm. you have the technology, the tools, plugins and know how. for everything you cant implement into the application right now make sure your plugin and scripting APi is open for it. I don't work at the foundry, but who ever came up with the pricing for Storm needs to rethink it. $375 is tooo low for a specialty software that works with only R3D to begin with. $750-$995 will make more sense to keep the R&D focused on making this a revolutionary application. Storm and Nuke together will ease up the current, 5 application conundrum we are faced with right now, edit>>clipfinder>>to RCX>>>>PPro CS5>>> to AE CS5/NUKE/COMPOSITOR,>>>>DAVINCI/SPEEDGRADE/BASELIGHT///>>>>>TO SCRATCH/SMOKE/DS/ conform etc etc. Tooo much time and money involved. Currently Smoke/Myst/DS are the go to systems.

MAKE SURE STORM IS A FULL BLOWN EDITING, COLOR AND CONFORM APP. for all other things there are AE/NUKE/PHOTOSHOP/PROTOOLS?LOGIC?AUDITION ETC ETC

Well CS5 is thanks to some Foundry plugins is currently kicking ass. We await Storm patiently
 
Limiting the STORM to R3D is what makes it easier to develop and therefore the lower cost. Other format cameras have a plenty of good workflows to choose from, but there is a huge gap in the market for the RED workflow. As many have said - there are plenty of SW doing parts of the workflow, but there's no app covering the whole workflow from start to finish (as far as image is concern). I was also surprised when I have first heard the price before IBC, but this was rather a pleasant surprise. The idea is that at this price point there really is no excuse to not to have it for anyone owning RED or working with R3D media. The more people adopt one tool, the more it can be used to standardize the workflow, while keeping it flexible to adopt to anyone's specific needs...

In my honest opinion Storm will become the benchmark by which all other workflow tools will be judged...

:devil: Peter
 
You must log in or register to reply here.
Back
Top