Welcome to our community

Be a part of something great, join today!

  • 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

Storm has WAV support but TC is not shown in the bin, hence I cannot sort R3Ds and WAV by TC and sync them accordingly. To have this would be very important. I'm sure that TC syncing is highly on your list.

Thanks Hans,

We added initial functionality to manually select WAVs and R3D files to perform an automatic sync based on Timecode. This option is available in the Mac menu bar (tools/sync audio) but we have plans to support further Audio functions shortly.

Thanks for your suggestions Hans, this will help us to plan further design work for additional features to Storms Audio syncing.

Cheers,

James.
 
After hours of playing with STORM (Beta) I'm totally impressed.

Finally I can check my files on set without any hassle.

It should be primary RED application bundled with upcoming Epic L, M, X, XL, S and Scarlet.

Also I would suggest to add "Film Look" with the most important film stock looks from Kodak and Fuji ASAP.

Then everything will be fine with RED future cameras on set just because every cinematographer/director/produced

can instantly have any desired film stock look at any calibrated monitor on set or projector in cine-video village.

That means also if RED could enable REDColor2 and REDlogFilm to be output via HD-SDI or HDMI

that you can get 1080p ProRes or Avid files for direct to edit and fast grade option.
 
Yahoo! This is rad!
It purrs like a kitten on my old MPB 15" 2.4GHz Core 2 Duo with 4GB RAM.
 
...We added initial functionality to manually select WAVs and R3D files to perform an automatic sync based on Timecode...

Cheers,

James.

Thanks for the explanation, but my issue is not solved this way.

The problem I have is how to know which sound file belongs to which R3D. If I can sort them in the bin by TC of the day the sound file is usually above the video file because the soundman is running mostly before the camera. This way it's pretty clear which WAV belongs to which R3D.

Because the TC in the sound files is not displayed in the bin and hence sorting by TC works only with R3Ds but not with WAVs it's very difficult to pic the right pair for synching. Did I make myself clear? Or did I miss something?

Thanks for listening.

Hans
 
James, I hope that feedback is welcome...?

One rarely has the chance to talk to the developers personally.

- Every now an then the TL becomes black. Restarting the application brings the TL back to life.

- Exporting a TL to ProRes crashes the application. A QT wrapper is written (4K light) to the right directory but then Storm quits.

Hans
 
Rendering Black

Rendering Black

Hi,

The interface looks awesome. I am really going to dig this when it is done. Unfortunately, everything I render is black.

Am I doing something wrong? I've tried to export Quicktime files from the clip and the timeline and I get the same result.

Thanks for the open dialogue with us users.

-Dave Dessel
 
Thanks Tim,
Yes, that should work right now, with one minor adjustment. Make your selects in Storm and output QT proxies to FCP. When the timeline comes back from FCP, Storm will recognise the clips and conform to the R3Ds
All the best,
Chris

Dear James

that's not the same at all. We don't want to select stuff and make new proxies etc, we want to edit away and do transcoding when we are finished. That would be a huge timesaver.
On a music video project, you load the whole footage in because you never know what you might use till the end. It's no fun to transcode 300 GB of data into new proxies or prores files. That's exactly nobody want's to do anymore.

Go out shoot 5 hours of footage, edit the hell out of it till you got 3 minutes left and then go right into Storm and do your RAW grading and output into the format you like.
That would be the killer, the game-changer. That's what I thought Storm is going to be.

So are you guys working on that too or do you think it won't be possible?

With best regards.

Tim
 
Thanks for the explanation, but my issue is not solved this way.

The problem I have is how to know which sound file belongs to which R3D. If I can sort them in the bin by TC of the day the sound file is usually above the video file because the soundman is running mostly before the camera. This way it's pretty clear which WAV belongs to which R3D.

Because the TC in the sound files is not displayed in the bin and hence sorting by TC works only with R3Ds but not with WAVs it's very difficult to pic the right pair for synching. Did I make myself clear? Or did I miss something?

Thanks for listening.

Hans

Hi Hans,

I understand what you need and we'll be able to implement this when we begin futher improvements to Audio functionality in Storm.

Thanks for the feedback,

Cheers
 
So far so great.

I LOVE:
-live updating histogram/waveform/vectorscope
-vectorscope that shows color when oversaturating
-region of interest tool (CRUCIAL)
-intensity sliders on all Look/Effects tools
-Separating out camera looks and RMD looks as 2 distinct things
-Effects Stack concept (i think in Photoshop layers still)
-RANGE GRAPHS in an easy-to-use R3D native tool!!! finally.

I would love to see:
-the white guide and black guide for "Out of Range" behave more like the goalposts in REDCine-X, w/ red bar growing larger as a greater %age of pixels are Out of Range

-a choice in the LiftGammaGain tool to have it "Pop out" horizontally, lining up the 3 "track ball" Wheels right to left: visual analog for surface controls in the real world

-the ability to have a "node-like" or flowchart-icon view of the Effects stack, and maybe the ability to click on each "node" and have it pop open in the Effects Stack. The Stack gets a little tall when everything's open, & a little tough to remember which you are using when you have multiples of the same Effect element going. Maybe a tall skinny window that always travels next to the Effects stack, with a little stack of icons in it?

I look forward to:
-RC2, RG2, etc. integrated

just scratching the surface. Great work guys.
 
James, I hope that feedback is welcome...?

One rarely has the chance to talk to the developers personally.

- Every now an then the TL becomes black. Restarting the application brings the TL back to life.

- Exporting a TL to ProRes crashes the application. A QT wrapper is written (4K light) to the right directory but then Storm quits.

Hans

Hi Hans,

Do you mean that the actual image in the Record viewer goes black? This might be because your clips are using Red Gamma2 or Red Color2 and we'll need to update to Reds new SDK to solve this. If it's not this then we'll have to investigate further to determine the issue here.

Not too sure what's happening with the export, if you could let us know your exact export settings then we'll try and repro this in the office, we'll be setting up a specific e-mail address soon where you can send crash reports directly to us, tomorrow we can post the e-mail address on the forums, then it'll be easier for you and everyone else to e-mail any crash reports to the Storm team.

Thanks again,

Cheers, J.
 
Hi Hans,

... we'll be setting up a specific e-mail address soon where you can send crash reports directly to us, tomorrow we can post the e-mail address on the forums, then it'll be easier for you and everyone else to e-mail any crash reports to the Storm team.

Thanks again,

Cheers, J.

James, good idea. Looking forward to your e-mail address. Then l'll gladly report the details to my issues.

Hans
 
For the people who have clips showing up all black, did you also delete any *RMD* files that are with the clip, besides RSX?

Or you could try changing REDcolor2 / REDgamma2 to REDcolor & REDgamma in RCX as well (if you're using auto saved RMD's)

p.s. back the RMD's up if you care about the grade / changes you did in RCX
 
I would love to see:
-the white guide and black guide for "Out of Range" behave more like the goalposts in REDCine-X, w/ red bar growing larger as a greater %age of pixels are Out of Range

-a choice in the LiftGammaGain tool to have it "Pop out" horizontally, lining up the 3 "track ball" Wheels right to left: visual analog for surface controls in the real world

-the ability to have a "node-like" or flowchart-icon view of the Effects stack, and maybe the ability to click on each "node" and have it pop open in the Effects Stack. The Stack gets a little tall when everything's open, & a little tough to remember which you are using when you have multiples of the same Effect element going. Maybe a tall skinny window that always travels next to the Effects stack, with a little stack of icons in it?

I look forward to:
-RC2, RG2, etc. integrated.

just scratching the surface. Great work guys.

Good Suggestions Eric, thanks! We almost implemented simular functionality to RC-X for warnings in the Waveform/Histogram which indicates the % of clipping and the LGG wheels spead out horizonitally (like typical grading applications) but we'll have to tackle this next time around.

We've had a few requests for a flow graph view in Storm for the effects stack, we'll see how it goes... ;-)

Thanks for you comments,

Cheers, J.
 
Last edited:
Excellent! I've used STORM on one job already. This will be a must-have tool. And it has the look and feel of my favorite software tool, NukeX.

Suggestion: Ability to animate settings. I just shot a clip, all available light, walking from bright airport terminal interior to night exterior that is lit primarily by sodium street lights. Would be nice to ramp exposure, color temp and tint as clip passes through sliding doors. I did the ramp in NukeX and it looks great. BTW, the RedMX at 1600 ISO looks terrific! 4KHD, 30FPS, 1/60th, Ultra Prime 14mm at T/1.9.
 
can you add visual burn-in to the output files? if so, what are the options?

ideally, you'd be able to select clipname and TC, (and later audio TC from WAV file), or other metadata, and then have the option of where and what size font to display it. you should be able to place the burn-in wherever you like, and also have an option to have it only display for the first XX frames of each clip being output (Eg. burn-in for first 5 frames only on output).

Not sure if this is done already or not, but thought I'd mention it as it is important.
 
Hi James, I'm unable to download the beta - after completing the form and clicking the 'Continue' button, I get a "QUERY FAILED" ... "MySQL server has gone away" message. Tried several times now... any ideas what's happening?

Hi Steven,

Sorry for the problem you had submitting your details.
I'm responsible for the Foundry's website. I had a quick check tonight and things were working normally, so I'll investigate properly in the morning. I see you managed to register a little later - please message me if you discovered what was causing the error (hopefully it'll be obvious from the logs anyway, but just in case...)

Cheers,
Andy Ballingall
 
Back
Top