Welcome to our community

Be a part of something great, join today!

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

CineForm NEO 4K Beta, RedCine compatible, and available for trial.

CineForm ConForm...thats what you need to call it
 
Jannard said:
....RED has agreements in place, at least for a certain time period, that would prohibit this type of native support.....
Jim
Click to expand...

Hi Jim (or anyone else willing to answer)

I heard about this from a high end software/hardware manufacturer. They mentioned/mumbled 2years? Is this correct/way off? I realise that agreements get made to aid development so I'm not complaining at all. Just trying to get as much info as possible to support any post purchasing decisions I make to work with our 2 red cameras.

thanks for any more info (if possible)..

Michael Lindsay
 
Adobe can say no, but do they (red) control all 3rd parties?
 
And on a related note, there is no way to trim a Cineform RAW file without "developing" it to Cinefrom444 or 422, right? If there is, how do you do it?
Click to expand...

They can be trimmed . . . I typically use the free Virtual Dub utility in it's "Stream Copy" mode.
 
CineForm NEO 4K, build 143

CineForm NEO 4K, build 143

A new build of NEO 4K has been created to work around the RedCine 4096 export issue. With this new build you can set your project and export resolution 4095, and internally the codec will treat the image as 4096. This way you get your full image out of RedCine (minus 1 pixel on the edge) to a 12-bit CineForm 444 MOV master. When RedCine is fixed for 4096 16-bit QT exports, the projects can be set back to the default resolution.

Improvements have also been made to the AVI 4K importer for After Effects and Premiere Pro, plus there will be a new version of Prospect 2K tomorrow that supports 4K RT playback on a 2K project timeline. We would till recommend re-wrapping the MOVs as AVIs (very fast and lossless) for Premiere Pro work, but the AE will work fines in 16-bit per channel RGBA from MOV files.

New NEO 4K 3.2.0.143 : http://www.cineform.com/downloads/NEO4Kv320b143-071119.zip

Please offer any feedback from your testing.

Thanks.
 
If only I had my RED camera to test with!
I guess framerates are a non issue as Redcine just exports "frames" and you guys transcode to "video" files right? your not looking at extra frames etc like dvcproHD right?

Hey David! nice to see you 'round here! I am sure you can't say they same for me hehehhe :) I will FIND your weirdest bugs while you sleep!!! LOL

Really though your latest builds are getting better and better. thanks for that you know I am the biggest fan of your workflow :)
 
David Newman said:
A new build of NEO 4K has been created to work around the RedCine 4096 export issue. With this new build you can set your project and export resolution 4095, and internally the codec will treat the image as 4096. This way you get your full image out of RedCine (minus 1 pixel on the edge) to a 12-bit CineForm 444 MOV master. When RedCine is fixed for 4096 16-bit QT exports, the projects can be set back to the default resolution.

Improvements have also been made to the AVI 4K importer for After Effects and Premiere Pro, plus there will be a new version of Prospect 2K tomorrow that supports 4K RT playback on a 2K project timeline. We would till recommend re-wrapping the MOVs as AVIs (very fast and lossless) for Premiere Pro work, but the AE will work fines in 16-bit per channel RGBA from MOV files.

New NEO 4K 3.2.0.143 : http://www.cineform.com/downloads/NEO4Kv320b143-071119.zip

Please offer any feedback from your testing.

Thanks.
Click to expand...

Let me make sure I have this straight: I set my REDCINE project to 4095 and export at 4095, and Neo4K will automatically add an extra line to the edge, and then I setup a PREMIERE project at full 4096, for my "4095" wide file? (Or more likely a 2K project)
 
David Newman said:
No worries there Jim, we're only interested in transcoding, nothing else was being implied. Transcoding everyone's camera format to CineForm
Click to expand...

Well David - if Apple doesn't step up I think you're going to make some sales. Sure looks like you may be the conduit to the best post solution for a lot of us.

Does your codec work in FCP and Color well? Or are you really optimized more for Premiere? And what about Premiere on the Mac?

I'm getting a brain cramp...
 
The Cineform codec works in Premiere on a Mac, and should work in FCP as well, but there are major advantages to using Cineform with Premiere on a PC. Prospect's Cineform RT engine allows realtime effects and editing in Premiere, with realtime SDI Monitoring if desired, from the XenaLHe.
 
stupid question but is the codec working in compositing/vfx software like Nuke ?
 
i'ts just an AVI codec like the rest. can you open others in Nuke? it works in Fusion...
 
It opened in FCP for me, but not in Color or Nuke. I may have done something wrong though.
 
McCarthyTech said:
Let me make sure I have this straight: I set my REDCINE project to 4095 and export at 4095, and Neo4K will automatically add an extra line to the edge, and then I setup a PREMIERE project at full 4096, for my "4095" wide file? (Or more likely a 2K project)
Click to expand...

That is correct, either a 4096 wide project in AE, or Prospect 4K (coming soon, in private beta) or a standard 2048 wide project in Prospect 2K. In Premiere set it to default to scale to frame size. This way 4K and 2K can used interchangably. You can zoom around in 4K up to 200% without losing resolution, which is pretty nice.
 
Irri said:
It opened in FCP for me, but not in Color or Nuke. I may have done something wrong though.
Click to expand...

Currently Color support no third party codecs, only very particular codecs or file formats (in does support generic QuickTime.) This is a limitation Apple is looking into. It impacts Redcode as well.

Nuke, shouldn't have this limitation. Does it open ProRes, DNxHD or Sheer? All of these codec should support 16-bits per channel, like CineForm. If CineForm has an issue with Nuke we will happily address that.
 
obin said:
i'ts just an AVI codec like the rest. can you open others in Nuke? it works in Fusion...
Click to expand...

AVI vs MOV also a factor. Many applications will work fine with AVI or MOV, but not the other (particularly on the PC.) Some applications are only 8-bit with AVI and 16-bit MOV (Combustion) or visa versa. To help overcome this limitation, we support rewrapping MOVs out of RedCine to AVIs for the applications that prefer that.
 
Hi David

I might have been a little quick to post that result. I just exported a file in Redcine then asked a compositor to see if it would open in Nuke. Nuke came up with a lengthy error message that I didn't read. There has also been an update to Nuke which we haven't installed. I'm out of the office now so I can't check ProRes etc.
 
i'll try with the newest version of nuke tonight, i ll tell you.
 
You must log in or register to reply here.
Back
Top