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

Anyone regretted going for build 16?

I hear you guys but you should all know I upgraded for a 2 day commercial in green screen studio.

What could go wrong?

10 min into shooting I got my first codec error. It then continued for 2 whole days were it literally was codec error in every take.

Needless to say that I would strongly recommend to wait until they iron out the by now known issues with B16. A new build is supposedly to come within the next days.


Fredrik
 
weirdcrew said:
10 min into shooting I got my first codec error. It then continued for 2 whole days were it literally was codec error in every take.
Click to expand...



Fredrik,

How did you deal with the codec errors? Is it just a situation where you just have to try again? Does it make the shot unusable or is the footage fine up until the codec error?

Harky
 
Problems, yes. Regrets, no.

For me the advantages have outweighed the disadvantages for upgrading to B16.

-Thor
 
Harky said:
Fredrik,

How did you deal with the codec errors? Is it just a situation where you just have to try again? Does it make the shot unusable or is the footage fine up until the codec error?

Harky
Click to expand...

The thing tht happens is that it stops the take when it happens. Footage is fine up until that moment (at least most of the time).

It was hard because ours had it after 15 secs or so. So we had to just shoot and shoot and shoot and shoot.

We turned off the camera in between. It seemed to help a little. Not that the camera was over heating, it was far from it, but for some reason it was easier to shoot in the beginning of starting it up.

I've never had any real problems with my camera until now and it wasn't a camera stress related shoot. Green screen hahahahaa

We're looking into what could be potentially wrong. So hopefully it'll be fixed.

But to get in that situation is tough, because it was impossible to figure out why it was behaving as it was.


Fredrik Callinggard
 
twlim said:
David, have not tried yet, I presumed these 6 + minutes clips can be rendered out by RedAlert and not VIA Compressor - Lim
Click to expand...

Sure,

Have any suggestions for getting the sound that I recorded with the clip?

David

PS: This is not directed at you Lim, but can people please refrain from the "double system" BS that I will get from this post. The camera has four channels of audio in, IT IS NOT AN MOS camera, nor was it designed to be.
 
battistella said:
Sure,

Have any suggestions for getting the sound that I recorded with the clip?

David

PS: This is not directed at you Lim, but can people please refrain from the "double system" BS that I will get from this post. The camera has four channels of audio in, IT IS NOT AN MOS camera, nor was it designed to be.
Click to expand...

You might use your proxies to cut with then use media manager and recompress.
 
Files for you

Files for you

gunleik said:
Anyone got a B16 (short) 3rd for me to do some workflow tests?

Gunleik
Click to expand...

No problems here. Have upgraded to Build 16, version 3.1.5. Shot today for 7 hours in 115 degree weather in the desert about 20 miles outside of Vegas. Had one power failure during playback, but then covered the camera with a white towel and didn't have further problems. I had never seen the warning on the back menu, but it was there all day (BODY HOT).

I haven't been able to link my 1080p Samsung TV to HDMI output for playback, camera locks up. This has always been this way, so it's not a build 16 problem. My TV is just not compatible.

Gunleik, I do have Build 16 .r3d files if you'd like to work on your workflow. How do I get them to you?
 
weirdcrew said:
I hear you guys but you should all know I upgraded for a 2 day commercial in green screen studio.

What could go wrong?

10 min into shooting I got my first codec error. It then continued for 2 whole days were it literally was codec error in every take.

Needless to say that I would strongly recommend to wait until they iron out the by now known issues with B16. A new build is supposedly to come within the next days.


Fredrik
Click to expand...

Sorry to hear that Fredrick.. Stuart should have a surprise for you guys having Codec troubles shortly.

Just a reminder for you guys reporting camera errors to support.. if you could send along your camera log files it helps us tremendously.
 
Russ Fill said:
Hey Battistela? What work flow are you using. I know when I turn in some of my time lapse work using Digital stills the QT files are around 500mb to 1gb at time and the post department called me up and said that their older Avid software could not handle any clips over about 3 or 400mb. Just wondering.
Click to expand...

Russ,

Just trying to use compressor to encode to ProRes because you can not use Log and transfer on B16 footage as the tools have not been released yet.

I want to use Prores for this interview I shot and the sound is in the file. I need to create the Prores files with the sound from the proxies so at this moment with build 16 Compressor is the ONLY way to get sound out of the files unless I cut proxies (which I do not want to do).

Does this help?

David
 
phaz said:
You might use your proxies to cut with then use media manager and recompress.
Click to expand...

I'm not to comfortable with the proxies yet. A 1K is OK but I feel better with created media. This stuff will be resolved soon. I am just trying to se if this is a problem other people are having so that we can troubleshoot it.

Thanks for your input.

David
 
battistella said:
Russ,

Just trying to use compressor to encode to ProRes because you can not use Log and transfer on B16 footage as the tools have not been released yet.

I want to use Prores for this interview I shot and the sound is in the file. I need to create the Prores files with the sound from the proxies so at this moment with build 16 Compressor is the ONLY way to get sound out of the files unless I cut proxies (which I do not want to do).

Does this help?

David
Click to expand...

David,

You can pull the sound from the proxies, either in QuickTime, or by putting them on a timeline in Final Cut, unlinking audio and video, and removing the video data. Once you've done that, drop in video made from RedCine or RedAlert (you might need to use uncompressed if they don't export ProRes) and then export the timeline to QuickTime ProRes. That should get you by until the problem is ironed out.

Damon
 
dmeledon said:
David,

You can pull the sound from the proxies, either in QuickTime, or by putting them on a timeline in Final Cut, unlinking audio and video, and removing the video data. Once you've done that, drop in video made from RedCine or RedAlert (you might need to use uncompressed if they don't export ProRes) and then export the timeline to QuickTime ProRes. That should get you by until the problem is ironed out.

Damon
Click to expand...

Yep,

That is what I did. Rendered in RED ALERT and relinked in FCP, just not the easiest way to the finish line. Have to keep those R3D files on line as well.



David
 
weirdcrew said:
There's a lot of codec error out there which is because of high contrast in the frame. That means that backlight in frame is not really working. Until RED has solved that problem I consider it to be very BETA. I jumped on 15 for professional work when it came, with only minor problems, but the problems I came across with 16 are severe.


Fredrik
Click to expand...

Agreed. I have had similar problems with 16, and a better experience with the terabyte or so of build 15 material that we have shot.

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