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 :)

Public Beta of STORM Released

Managing Communication

Managing Communication

Hey James,

Might I make a suggestion?

This thread is kind of all over the place.

It would likely be a lot easier on you and your team if you closed this thread and opened a couple others to replace it.

Something like:

Storm Feature Requests
Storm Bugs
Storm Updates (no responses, just news from The Foundry like Jim's Thoughts and Tips)
A separate comments thread for each storm update

Storm Bugs should be closed and a new thread opened for each new build released. (ala RedCine-X)

That way you could track bugs easier and we who are finding bugs would be able to more readily determine if they were already addressed rather than plow through a lot of congrats and it would be nice if posts.

Further you customer feedback would be easier to consume as it wouldn't be commingled with bugs and questions.

Having said all that, congratulations, I'm loving the real time histogram and monitor updating, the product shows a lot of promise. You and the team should be proud of your work thus far.

I've got some bugs to file, and I'll get to those in the next day or so.

Thanks for your hard work, and for your presence here on the board,

Steve
 
Stephen Lovett said:
Hey James,

Might I make a suggestion?

This thread is kind of all over the place.

It would likely be a lot easier on you and your team if you closed this thread and opened a couple others to replace it.

Something like:

Storm Feature Requests
Storm Bugs
Storm Updates (no responses, just news from The Foundry like Jim's Thoughts and Tips)
A separate comments thread for each storm update

Storm Bugs should be closed and a new thread opened for each new build released. (ala RedCine-X)

That way you could track bugs easier and we who are finding bugs would be able to more readily determine if they were already addressed rather than plow through a lot of congrats and it would be nice if posts.

Further you customer feedback would be easier to consume as it wouldn't be commingled with bugs and questions.

Having said all that, congratulations, I'm loving the real time histogram and monitor updating, the product shows a lot of promise. You and the team should be proud of your work thus far.

I've got some bugs to file, and I'll get to those in the next day or so.

Thanks for your hard work, and for your presence here on the board,

Steve
Click to expand...

Please see the other Sticky Threads for Guidelines:

http://reduser.net/forum/showthread.php?t=52498

http://reduser.net/forum/showthread.php?t=52495

:smile:
 
HD Hildebrand said:
A storm is coming - looks like we ain't in Kansas any more Toto.
Click to expand...

Maybe that should be "...any more Tatoo"

Seriously this looks like its going to be a great tool for RED users - and open up the naysayers minds as to RED being a useable production tool with a viable workflow.
In true Foundry fashion this is great work!
 
All in all - STORM is looking very promising!

I would recommend you guys make it super easy for all beta testers to report bugs and feature requests inside the app and submit it to a bugs & report system that will allow me to follow any updates to my bugs when they're available and have been squashed or otherwise "handled" by your software engineers. If the app isn't online then it would obviously store my reports locally and submit them when there was an active internet connection.

I already have a ton of feature requests.
 
Stephen Gentle said:
Hmmm... It's just crashing on startup for me...

Code: 
1/12/10 11:12:38 PM    Storm1.0v1b1[3279]    *** __NSAutoreleaseNoPool(): Object 0x2138eb0 of class NSConcreteMapTable autoreleased with no pool in place - just leaking
1/12/10 11:12:48 PM    com.apple.launchd.peruser.501[302]    ([0x0-0xdf0df].uk.co.thefoundry.Storm[3279]) Exited with exit code: 1
Click to expand...

Hi Stephen, the new 1.0v1b2 build should also rectify this issue. Details are here for the download:

http://reduser.net/forum/showthread.php?t=52680

Let us know how you get on and apologies for the inconvenience.


many thanks,
Dan
 
Hi Richard.

Wow - it looks really good. Can't wait to use this more.

I very much like the XML, and the easy "from/to" FCP part. Makes a good workflow!

Am a bit curious on a few things.

What are the foundrys hopes for it to work with avid?

STORM would obviously be the heart of a post house if you could load in the RED footage, and output either a XML for final cut, OR a ALE for avid. Like REDrushes did.
And like it is now when you input a "FINAL EDIT" XML from FCP, to link to the original R3Ds, and then render DPXs and such to grade, it would be very handy indeed also to be able to input a CMX3600 or RED16 EDL to online from.

What thoughts have you done regarding that?

Will it in time be able to look on other files then RED, like DPXs and such?

Will there be some link between NUKE and STORM, to keep track on vfx renders?

Thanks you very much.

Looking forward to here from you.

Best,

Daniel

daniel@baconcph.com
www.baconcph.com
 
I love Storm so far... but one thing that's bothering me is when I transcode from R3D to ProRes (or any codec) the quality isn't that great ? I'm not using a rocket... just testing small clips on a laptop (using storm version 2).
Debayer setting is on best.. and I'm going to 1080p ProRes HQ (but the image quality is nowhere near what RCX does).
Is this just me?
 
Michael Totten said:
I love Storm so far... but one thing that's bothering me is when I transcode from R3D to ProRes (or any codec) the quality isn't that great ? I'm not using a rocket... just testing small clips on a laptop (using storm version 2).
Debayer setting is on best.. and I'm going to 1080p ProRes HQ (but the image quality is nowhere near what RCX does).
Is this just me?
Click to expand...

Hi Michael, we will certainly check into this. Can you start a new thread so that we can track this issue? :smiley:

many thanks,
Dan
 
You must log in or register to reply here.
Back
Top