Welcome to our community

Be a part of something great, join today!

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

MX ..... A suggestion

J

Jeff Brown

Well-known member
Joined
Dec 28, 2006
Messages
477
Reaction score
0
Points
16
Location
London, UK
Not a complaint as such just a suggestion:

Put a sheet of paper in every MX box shipping back to it's owner stating staying what QT plugins/ Red post software/3rd Party software has correct color science support for MX/Build 30. Not everyone reads firmware release notes so keep it simple.

The yellow/ green issue is springing up across all the forums. Owners aren't even getting this right so what chance have clients got? There are already too many dry hire companies (in the UK at least) renting MX with no post advice at all.

Let's not have the "red is difficult in post" scenario again that we had two years ago...

Just a thought.
 
There definitely needs to be at least a sticky up here with the latest workflow because, yes, the buzz right now is that there is no MX workflow solution and I honestly don't kow the proper solution at the moment myself. I feel like I hacked my way through it the last time, but it was more of a design than editing project so it was possible. Is there a link to the latest workflow with MX using Apple? I looked in that forum, no stickies.
 
RED has to do a better job of centralizing such information. Sometimes just finding the latest REDCine-X version can be a pain. It's posted somewhere on here but not on the red.com support site. Go figure...
 
It's a problem because the lack of organized information and centralized downloads fosters a lot of misinformation. I've spoken up about this on several threads. The only reply I've gotten amounts to the software is seeded in the threads so people who are testing it, the "hard core redusers", find it and once it's release ready, it gets posted to the red.com/support page.

I think this approach needs some evolution. Anyone who needs to work with MX footage needs this software, regardless if they own a camera or spend 10 hours a day on reduser. The codec and software releases are so quiet and their location rather opaque, it wastes a lot of my time playing catch up instead of using the tools.

I read on a post yesterday someone talking about build 247. Can't find it anywhere on the site. Was the person misinformed? Typo? With the way the software and information are provided, it's anyones guess. :banghead:


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

http://reduser.net/forum/showthread.php?t=43841&page=2
 
I agree with everything written above.
I'm an MX owner -received no notification of any Qtime Codec for MX sensor.

One Post guy last week jokingly called me a selfish b*&^ard for shooting on an MX because he didn't believe there is a post path available to him.

I was talking with some ACs this morning about to start an MX shoot with an Academy Award - winning DP, who believed there was no such thing as a QT codec for MX.

It's incomprehensible to me how the communication is so poor right now on this issue. Seems to be getting worse.
Why is this new codec not available, and even highlighted, on the downloads page at Red.com? Unbelievable...
 
My camera's currently at RED getting the sensor upgraded, and I had no idea I needed a new codec until someone on RedUser complained about a green tint to their footage. I agree with putting some simple instructions in the box.
 
There is already another thread on this subject so I will not belabor the point. We post pre-beta builds here on REDUSER for initial testing and immediate feedback with collaborative communication between RED and testers. Then, if and when, we feel we have a build ready for wider, general release on RED.com (which also includes an email blast announcement), we post there.

The other option is for us to not post these pre-beta builds and only email to a select few alpha testers to test for us. We feel that is less productive so we take the former route. But, if you all feel you do not want builds posted here before official beta versions on RED.com and us to be less transparent with builds as we develop them, I will certainly discuss with the team here. Please note that no builds on REDUSER means less feedback to us and, in turn, means greener builds when released on RED.com.

BC

FWIW, since we HAVE been able to have some solid feedback on a few pre-beta builds, we expect to release additional workflow support soon on RED.com.
 
Brent,
I think a link/page on red support page to ALPHA builds would be a great idea and one place to find those builds. with some rather large warnings about the builds being ALPHA builds, not to be used for production; use at your own risk; failure/crashing is eminent and so on. This way, those of us alpha testing the new RCX for example don't have to go back to our subscriptions listings to find those builds again when they are updated to the next build. RCX being the primary example of course. Or if you don't want it on RED support site....how about something completely unrelated like www.redalphabuilds.com
but don't take those alpha builds out of the mix.....
 
Or if someone here wants to create a build sticky with builds as they are released, I think everyone would be satisfied.

BC
 
Brent@RED said:
But, if you all feel you do not want builds posted here before official beta versions on RED.com and us to be less transparent with builds as we develop them, I will certainly discuss with the team here.
Click to expand...

That is not what we are asking for at all, I think you understand that, so some middle ground is what we are asking for. Without MX builds and codecs we can't work with the footage.

A builds sticky would be a welcome compromise. Is that a reduser mod's job to do?
 
Brent@RED said:
Or if someone here wants to create a build sticky with builds as they are released, I think everyone would be satisfied.

BC
Click to expand...

If there was a clear, official, and up-to-date description of the workflow situation at the Red Support page, specific to the sensor they are working with, I think everyone would be satisfied.
 
Well I think I hit a nerve....

A bit of clarification though I wasn't suggesting we don't alpha/beta test Brent - and yes that discussion has been had and it's great that there's a community here to help test and develop.

But I'm not talking about testing.

Build 30.5.0 is a release build.

MX cameras are released and growing in number every week.

There is no MX Quicktime codec on the Red.com support page or a comprehensive list of FLUT supporting software (Red and 3rd party).

I've now got 2 MX cameras and demand is high from DPs but at the moment I'm often having to shoot with my non MX cameras on Build 21 because of lack of native support for finishing. I'd love to say yes to the DP but it's the Producer who pays and he has 3 day post delivery on this commercial etc etc etc....I'll always make sure the route is clear and hold the hands as I've always done but too many people won't. At this stage in the game when everyone seems pretty happy with their established workflows there will be many who get burnt (again).

It seems like such a simple fix.

Please don't take this as a flame - more a dispatch from the front line.
 
No worries, Jeff. We hear everyone's comments on everything - we live in a glass house here. I honestly do not know what more to say. I understand people want to be able to have the builds on RED.com. And, conversely, we put them on RED.com when they are ready for public beta. When we launched M-X sensors, we provided support in REDCINE-X. And we are working on development of additional workflow solutions that support M-X. We provide pre-beta peeks here of both newer versions of REDCINE-X and other types of software support. We are not being secretive or trying to have poor communication. We simply are trying to be transparent to REDUSERS of our development on those projects and will post them when we feel they are ready. No one wins if we post something prematurely on RED.com.

Note we also have a new version of RED.com under development that will also provide a better presentation of support topics.

BC
 
Brent@RED said:
Note we also have a new version of RED.com under development that will also provide a better presentation of support topics.

BC
Click to expand...

That's what everyone's wanting, I think.

Can't see why the whole website needs to be overhauled to provide what people are asking here. A page could be written and posted right now, surely.

... but that's good news.
 
NEW - FCS users - Package with RED QuickTime Codec (v4.2), Log and Transfer (Build 30), REDCODE plug-in for Color (v4.2): http://reduser.net/forum/showthread.php?p=615896#post615896

REDCINE-X B247: http://www.reduser.net/forum/showpost.php?p=610777&postcount=1

The above are PRE-BETA, testing versions. There you go, info in one spot.

BC

PS,

Mark Pugh said:
Can't see why the whole website needs to be overhauled to provide what people are asking here. A page could be written and posted right now, surely.
Click to expand...

Yes, if we wanted to post on RED.com with these pre-beta builds, sure. But, again, first on REDUSER, then on RED.com when ready. Even with a new website, I can tell you right now that Deanan, Rob, Jim, etc will still post on REDUSER first for testing and feedback. What the new website will provide (hopefully) is an overall improvement on user online experience - incl information presentation.

BC
 
Last edited:
I wanted to add that I understand everyone's frustration with this. We've hired more people and will do better.

Thanks for the feedback!
 
You must log in or register to reply here.
Back
Top