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

Crimson Workflow is available for download.

ibloom

I'm DIT'ing now and remembered that you said your goal was to have crimson on every set shooting Red. What features are you implementing for on-set workflows?
 
So what's in the fun box?


1. Backup automation with checksum controll
2. Preview "timeline" clip by clip via RA, before render in RL
3. Send DPX sequences to FCP, when gluetools is installed
4. Fix all the color/dpx bugs... :)! (LOL!)
5. Auto-cutter function for successfull movies
6. Reframe/focus/DOF knob that regenerates imagae outside the frame with the genious ™assumtiate technology. (Somhow all the hot babes are there...)
ANything else?
7. Build 17

Gunleik
 
Gunleik,
For various important reasons I have to keep a lid on what is happening with Crimson. What I can tell you is that there are two builds I'm working with, the radically different build, and the improvement on what you have.
I'm testing this second one now, and it has greatly improved control over the Redline render, in addition to some other positive tweaks.
The radical build is on lock-down. Sorry.
Cheers,
Ian
 
ibloom said:
Those messages are non-critical, they just have to do with things like audio not seeing all of the original proxies. It's something that I'm working on, but not mission critical.

You will need to change your sequence settings to match whatever codec you transcoded to.

I have an entire forum for this kind of help Shawn, http://www.crimsonworkflow.com/forum

Ian
Click to expand...

So I ran into a new problem this weekend and posted it over there back on Sunday. Basically I did my first real conform for a full project (~6min) and it fubar'd all the clips involving speed cranking and FCP fading (where you keyframe the black line)
 
Shawn Nelson said:
So I ran into a new problem this weekend and posted it over there back on Sunday. Basically I did my first real conform for a full project (~6min) and it fubar'd all the clips involving speed cranking and FCP fading (where you keyframe the black line)
Click to expand...

Yep,
I think I've been pretty clear Crimson can't handle speed changes... yet. This is just a larger engineering problem than it appears. Keyframes as well can be problematic depending on where they are. I think if you read the Crimson forum, you'll see this has been covered many times over. The solution is to seperate out speed changes, render those entire clips an do those changes after you conform. Not like butter, I realize, but doable unfortunately.
IBloom
 
ibloom said:
Gunleik,
For various important reasons I have to keep a lid on what is happening with Crimson. What I can tell you is that there are two builds I'm working with, the radically different build, and the improvement on what you have.
I'm testing this second one now, and it has greatly improved control over the Redline render, in addition to some other positive tweaks.
The radical build is on lock-down. Sorry.
Cheers,
Ian
Click to expand...

So.. does this mean we will have to buy another version of Crimson if we want the radically different build?
I would hate to have just bought a license for the original product only to see it sidelined. Will you offer a trade in / upgrade path if that is the case?
 
Ed Watkins said:
So.. does this mean we will have to buy another version of Crimson if we want the radically different build?
I would hate to have just bought a license for the original product only to see it sidelined. Will you offer a trade in / upgrade path if that is the case?
Click to expand...

Ed,
You bought 1.0.0
You have 0.9.2
In other words, existing customers can sit back and enjoy the ride including the eventual release of a radically different build.
Even after I get all the features I promised into 1.0.0 there will still be free bug fixes for life.
Cheers,
Ian
 
ibloom said:
Yep,
I think I've been pretty clear Crimson can't handle speed changes... yet. This is just a larger engineering problem than it appears. Keyframes as well can be problematic depending on where they are. I think if you read the Crimson forum, you'll see this has been covered many times over. The solution is to seperate out speed changes, render those entire clips an do those changes after you conform. Not like butter, I realize, but doable unfortunately.
IBloom
Click to expand...

I should have separated that out, the speed changes were a minor issue and I dont expect Crimson to handle it. I can definitely pull them out next time.

It's the fading keyframes that killed me, I had tons of them (nearly every cut keyframe fading, it's a certain type of piece) and they were all wrong. Is there some secret to getting Crimson to properly read them? I'll go read the Crimson forum to see if this is already answered.
 
Shawn Nelson said:
I should have separated that out, the speed changes were a minor issue and I dont expect Crimson to handle it. I can definitely pull them out next time.

It's the fading keyframes that killed me, I had tons of them (nearly every cut keyframe fading, it's a certain type of piece) and they were all wrong. Is there some secret to getting Crimson to properly read them? I'll go read the Crimson forum to see if this is already answered.
Click to expand...

The secret is to post your XML on the forum so that I can debug it ;) This one is a first.
 
Helping some friends do some post work and finally got to see Crimson in action... wow...such a massive time saver. If I had this program back in October when I did my first Red short, it would have saved me literally three-four weeks of work. Thanks Ian for creating such a great app!

This is a must have app for anyone shooting RED and working within FCP.
 
Hi Ian and fellow Crimson users,

I've done a number of tests with Crimson, the only problem I encountered was opacity keyframes not being on the right positions. However, I'm now conforming a short film, the first real world Red project I'm pulling through the Crimson workflow and I'm having a problem generating the roundtrip XML. When I clic "Generate" I get the following message : "IndexError: list assignment index out of range". Has anybody encountered this problem before and know of a solution ?

Cheers,
Damien
 
gunleik said:
ian, what is your build 16 schedule?
I guess we're waiting for redline and redcine, but are there other stuff needed to pull it off?

Gunleik
Click to expand...

Until I see the new Redcine I won't know the extent of the change and how it affects Crimson.
In terms of Redline I don't forsee any issues though there may be some updates as the Redline interface may change.

earthling said:
Hi Ian and fellow Crimson users,

I've done a number of tests with Crimson, the only problem I encountered was opacity keyframes not being on the right positions. However, I'm now conforming a short film, the first real world Red project I'm pulling through the Crimson workflow and I'm having a problem generating the roundtrip XML. When I clic "Generate" I get the following message : "IndexError: list assignment index out of range". Has anybody encountered this problem before and know of a solution ?

Cheers,
Damien
Click to expand...

Can you post your console log on my site http://www.crimsonworkflow.com/forum

IBloom
 
You must log in or register to reply here.
Back
Top