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

Beta REDCINE for Build 16...

Hey. Quicktimes now render as individual clips without "seperate folders". Now we're talking. Hard to do anything but rendering though as Redcine locks up the computer. Pressed F11 and tried to do something else but that crashed Redcine. Hoping for a send to redline/copy to clipboard button like in Redalert.

RedCine has always crashed for us when trying to render in the background (8 core Mac Pro, 8800GT, 10.5.3). Pretty annoying. Really wish there was a way to grade in RedCine (with instant feedback, etc.) and then kick rendering out to RedLine.
 
Some problems:

Can't re-render multiple versions of a clip. After the first render as a TIFF, the output buttons are disabled. The file must be closed and opened again.

Cannot output QuickTime. QuickTime Animation, ProRes HQ, Uncompressed 10bit and 8bit give "failed to write frame" errors. I haven't tried them all but I suspect I won't be able to write any QT movies. I have this issue with multiple Mac stations in my studio (all high end updated hardware, etc. QT 7.4.5.
-Wait! It appears to render QT's fine to my local drives. Is there a problem when rendering QTs over a network? That's where all my server space is. Rendering TIFFs to a network works fine.

I suspect that the histogram is not reading correctly (highlights as effected by exposure) any chance it could be off?

When trimming the length of a clip, the trim is not saved when closing and re-opening the file.

Thanks,
Phil

http://www.artbeats.com
 
1: Use the "invalidate" button to render multiple versions of one clip. BEWARE you can overwrite your originals if you don't change the name.

2: APPLE file shares have an issue writing files over 2gb. After effects suffers the same deal.



Some problems:

Can't re-render multiple versions of a clip. After the first render as a TIFF, the output buttons are disabled. The file must be closed and opened again.

Cannot output QuickTime. QuickTime Animation, ProRes HQ, Uncompressed 10bit and 8bit give "failed to write frame" errors. I haven't tried them all but I suspect I won't be able to write any QT movies. I have this issue with multiple Mac stations in my studio (all high end updated hardware, etc. QT 7.4.5.
-Wait! It appears to render QT's fine to my local drives. Is there a problem when rendering QTs over a network? That's where all my server space is. Rendering TIFFs to a network works fine.

I suspect that the histogram is not reading correctly (highlights as effected by exposure) any chance it could be off?

When trimming the length of a clip, the trim is not saved when closing and re-opening the file.

Thanks,
Phil

http://www.artbeats.com
 
Cineform renders now work quite well.. Just be sure to stay in 2:1 for the time being.

There are a lot of improvements in this build!

Jay

Yes.....!!!!!:love: Also remember to use 4095 as opposed to 4096!:construction:
 
Somebody asked if the new Redcine works with Crimson. YES!!! To my surprise, it works perfectly. I've just opened a 92 clip sequence, using FCP, Crimson and the Redcine beta. It works perfectly.

It doesn't appear to work with B16 proxy file names (for me at least)

I still get full conforming and round-trip with XMLs made from B15 media names.
 
Library feature question???

Library feature question???

How do we active the adding/deleting the columns on this build (Mac version)? It seems that now I cannot make that pop-up/pull down menu to show up?:bye2:
 
It doesn't appear to work with B16 proxy file names (for me at least)

I still get full conforming and round-trip with XMLs made from B15 media names.

Ah, just checked and my "working perfectly" test was done with Build-15 clips. I tested Build 16, and as everybody else probably knows already, Crimson doesn't seem to work with Build 16 clips. (I've been off-forum for a while). Still, at least this means the new Redcine doesn't cripple Crimson completely, which was always a fear.
 
1: Use the "invalidate" button to render multiple versions of one clip. BEWARE you can overwrite your originals if you don't change the name.

2: APPLE file shares have an issue writing files over 2gb. After effects suffers the same deal.

Hi Mike,

Thanks for the reply and the "Invalidate" button tip. However, regarding the second problem, I was purposfully writing a small file of 50 frames, so I didn't get close to the 2GB limit. Something else is afoot...

Phil
http://www.artbeats.com
 
it wont tell me the ISO... they are all 320 for everything.

oh yeah.. and my favourite bug is gone.... i can make jpeg snapshots... uber cool.

just installed build 16.

WOAH..

Redspace...

WOAH...
 
Crimson doesn't seem to work with Build 16 clips. (I've been off-forum for a while). Still, at least this means the new Redcine doesn't cripple Crimson completely, which was always a fear.

thanks a lot for the test, Christopher.

Ian is it something that can be quickly solved? If not (and taking out Scratch on that equation) how are we going to conform from FCP offline edit?

thanks,
antoine.
 
there is a new TAG in the XML file named "media length". what is for sure useful, but I think the crimson converter don't know this TAG at the moment and get confused... that my 5 cents to this.....

best regards
rainer
 
Yes... I requested a <media_length> tag in the file in order to make the subclip workflow work form RedCine into Avid since there was no way to determine the output of a clip when shorter spans of the file were exported. Both handles are actually offsets from the start, and not offsets from start and end as expected. Thanks to Assimilate for getting that in! Just have to work on getting the choice of DNxHD formats into the export next. :)

But with XML, the idea is that new tags should not bother exisiting workflows, so it may well be something different.

Michael
 
HDMI freezes RED

HDMI freezes RED

I've noticed when plugging in a "hot" HDMI source to a RED that is up and running, it sometimes freezes the camera - on, but frozen. Has this been fixed in Build 16? Is there a workaround?

David
 
Latest REDCINE runs great on Linux under Wine (perhaps better than build 90?).

I can finally upgrade my camera to B16 now! WoohooOO!

Now I just need to get that SDK in my hands, ASAP! (Wow, I'm needy).

Thanks Jim, Deanan, Stuart, and everyone else!
 
I've noticed when plugging in a "hot" HDMI source to a RED that is up and running, it sometimes freezes the camera - on, but frozen. Has this been fixed in Build 16? Is there a workaround?

David

i'm doing a timelapse right now as we speak.. got a "hot" HDMI and plugged it into Red... the screens were on when the hdmi cable was plugged into red.

no freezes so far.
 
Cineform renders now work quite well.. Just be sure to stay in 2:1 for the time being.

There are a lot of improvements in this build!

Jay

Jay,

Just to clarify...

You're able to export Cineform .avi's directly from RedCine on a Windows machine?

If that is the case... happy day!

Also, which version of Windows are you running? I assume you're editing in XP64 since that works the best for Cineform. Are you running a dual boot system? If so, which version of Windows did you use to install Redcine?

How fast is it converting Redcode to Cineform? How many cores are you running?

Is it converting to Cineform RAW or Cineform 444? Or both?

Did you render to 4095 or 4096?

If this version of RedCine gives the Windows guys a Cineform workflow, then I am one happy camper!

-Thor

EDIT FOR THE MODERATORS: Please let Jay answer these questions here. I will move all further questions to another thread in the Worflow section. Promise!
 
So is the new Redcine update coming out today still? Is it going to have the ISO fix?
 
Back
Top