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

Prepare...

Jeff, I'm a small company so I understand the idea of keeping expenses down. I am not into throwing money around, so when I bring up the idea of charging for a "Digital Lab" app it's because I want the best tool I can get to handle this footage. Even if it's a $1000, if the app speeds up my workflow by 50% the ROI will be huge for me.

Steve, I have to admit that my post this morning was written in haste... I don't think I completely conveyed my thoughts. I completely agree with you, I'm just not sure why people are throwing random figures out there like $500 or $1000 to make it better. We don't know what's involved in developing REDCINE or how it factors into the overall picture, etc.. The other way I look at it is that not all problems can be solved by throwing money at them. I see RED's software tools as continuously evolving products, just like the camera. I guess I just thought it was odd that people are offering to pay for an application that is supposed to be free in order to make it better, but yet no one is discussing what they want for their money.
Personally, I'd like to see REDCINE continue to develop as a free tool. Let RED get it to be 100% stable and let RED concentrate resources on getting that SDK out the door. But perhaps a REDCINE Pro isn't a bad thing to want for as a future product. We have to wonder if the free REDCINE will ever understand EDLs natively or be a functional conform tool without resorting to XML translators like Crimson Workflow.

In my market, the post side of things is still a hard sell right now

I was worried that I would have this issue too. But I'm finding the general attitude to be positive, it's a new camera, there will be kinks to work out. The workflow isn't too much more demanding (or problematic) in relation to current computer and storage systems than DVCPROHD via P2 when I (and several of my clients) started shooting that. It's workable now and will only get better.

I'm going to hold off commenting any further on this though because quite honestly I think the Red team knows what they are doing and I'm not really contributing much useful info here.:)

Ah, come on... You normally have something constructive to say. :) But I think I'm done too.. we've derailed this thread enough.
 
REDCINE will always be free. We'll keep improving it as we go. Just like the camera upgrades.

Jim
 
I guess, no chances for REDCINE PRO?
1K-1.5K range, secondary color ?

Yes, at 3000 cameras sold the budged would be 450K not much to develop the whole package from SCRATCH:-) ?? is it?
 
I have one other question.

I love how stable RA is but I love the potential of RC, but i'd love to see a "killer app" that gives the best of both.

Is RED eventually moving towards one application for post?

Wouldn't that lessen the development workload?

David
 
it wouldn't make sense anyway because they'll need it for scarlet and epic and they are using the same technologies. what I do like about red's approach so far is each advance they are using to make all the products better and in the same way
 
Just a thought for all of you people asking for a PAID application.

Don't you think it is fair that if RED has created a BRAND NEW FORMAT in R3D files, that they should support that format for free?

What do you think competitors would say if RED forced you to pay for the only application that allowed you to access the footage you just shot?

Don't you think there would be a bit more than screaming going on in this thread?

I plan to patiently wait to see if anyone jumps on the SDK (which they will) and see how much they charge to access R3D files in their application. I suspect many apps will go the way of FCP and include access to r3d footage to their customer free of charge.

Just think about this before you rip me.

David
 
it wouldn't make sense anyway because they'll need it for scarlet and epic and they are using the same technologies. what I do like about red's approach so far is each advance they are using to make all the products better and in the same way

very good point!

david
 
I think the problem RED is having is that there is a small tight team of people. This is such a small group, I think, that many of the people on REDUSER have met most or all of them at NAB.

Small groups tend to be the most efficient ways to make projects like RED happen. They are agile and can move quickly. But even working 120 hour days like Jim, they have a limited amount of time they can work.

It's extremely difficult to start adding people to this team, because any new person has to get up to speed with how things work, and is unlikely to have the brilliance of the people who have carried the project this far. Getting people up to speed often disrupts the way people who are asked the questions are working and the result is that things actually get done slower.

This has all been covered in various management books and is a huge problem with any large software development project.

We know everyone is working very hard and we know they are the best people in the world at what they do. This means we'll get a great product, if we only have patience for it.

D
 
Patience... I think most have on Reduser and the "Red Team" I'm sure is working harder than we will ever know....even beyond the long hours stated.

Have I missed a post though that indicated any ETA for Beta Build16 Days,Weeks?

Just curious.
 
We have no idea what we are doing... how many other companies will admit that!???!!!

Jim

Jim,
As long as you are having " Fun, make $, change the world a little bit and finally make some good contributions " are good enough though in life.

Stew.
HKG
 
I expect the 'problem' in developing Redcine further is the licencing agreement between Red and Assimilate for Assimilate's code within Redcine.

Red will need to revise this agreement and recompense Assimilate accordingly so they can develop Redcine to a degree that other Assimilate products are even more impacted.
I expect Assimilate developers do most of the changes to RedCine anyway.

....I would of loved to negoitate (see....i can't even spell it) that original deal!!

Dave,
 
I expect the 'problem' in developing Redcine further is the licencing agreement between Red and Assimilate for Assimilate's code within Redcine.

Red will need to revise this agreement and recompense Assimilate accordingly so they can develop Redcine to a degree that other Assimilate products are even more impacted.
I expect Assimilate developers do most of the changes to RedCine anyway.

....I would of loved to negoitate (see....i can't even spell it) that original deal!!

Dave,

I agree.

If I were Assimilate I would have negotiated the original deal where RED would be required to have shipped X amount of cameras for specific amount of time before the agreement ends. This way Scratch would be the only native RD3 post solution for long enough to attract new sales. Because of delays in shipping the required number of RED cameras, the agreement had to be extended.
 
I'm curious as to how B16 handles anamorphic photography. Is there any way to properly unsqueezed footage natively in-camera for monitoring purposes? Will there be a preset in RedAlert or Redcine to crop and conform footage?

This is no in-camera unsqueeze for anamorphic. There are external monitors that do this however.

Jim
 
Back
Top