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

REDCINE-X Build 487...

I've been scouring this forum looking for an answer, so please excuse me if this info is readily available somewhere...

Does REDCINE-X support the Avid/Euphonix MC Color control surface under Windows 7 64-bit?

Thanks.
 
It seems like a lot of the HDRx examples I've been seeing didn't really need hdrx, such as landscapes with bright skies, etc. I think a main use of HDRx will be shooting inside and looking out a window, or other extreme contrast situations, not really for normal high contrast scenes. Careful exposure and redlogfilm have generally taken care of these pretty well for me...
 
Hello; a great day to all. I have a RED am am trying to get a monitor for clients to watch,to function. I have atached a cable to the 720 output on the camera and then run to a converter to hdma on a hi def flat screen tv. Looks fine but it keeps blinking. It seems like it is refreshing image or??? But it is very annoying to watch. How do I get the monitor to stop blinking? What is causing it?
Thank you, Michael
 
25p Avid MXF with Audio Rendering problem

25p Avid MXF with Audio Rendering problem

Hi Guys,

for everyone in PAL World, before you might run in the same problem:

There is a little 25p bug in Rendering with Audio attached to Avid, just submitted this to RED Support too:

its been there since RCX 470, i think even 454, but definitley not Build 356:

Rendering a R3D File ( Happens both with RED MX 30.6.0 and EPIC M 1.6.19 Firmware) 4K 16:9 / 5K 2:1 with 25 fps Timebase in REDCINE-X Out to Avid MXF&AAF results in the AAF not being created and the Files still stuck in the "Clipname" Folder with MXFs and an XML, as soon as the Enable Audio Option is on. (there is actually an BWF Audio File synced to the clip)

With the Audio Option off it works flawlessly, well of course no audio so there we have an important feature in our workflow missing.

Rocket or Software is the same.

Interesting: it doesn't matter which target Avid MXF Framerate or Bitrate it is ( tried framerates 24,25,29.97, 720p 25, and bitrates 185x, 120, 26) it is just with the Camera Recording Time Base being 25.

everything we shoot with 24 fps Time Base renders flawlessly, even with audio.

it would be awesome to have this resolved since it is an important part of our workflow...and it just happens to be we live in an 25p world - at least for TV Broadcast - here :)


Thanks and Greetings from Berlin,

Alex
 
Hi Guys,

for everyone in PAL World, before you might run in the same problem:

There is a little 25p bug in Rendering with Audio attached to Avid, just submitted this to RED Support too:

its been there since RCX 470, i think even 454, but definitley not 356:

Rendering a R3D File ( Happens both with RED MX 30.6.0 and EPIC M 1.6.19 Firmware) 4K 16:9 / 5K 2:1 with 25 fps Timebase in REDCINE-X Out to Avid MXF&AAF results in the AAF not being created and the Files still stuck in the "Clipname" Folder with MXFs and an XML, as soon as the Enable Audio Option is on. (there is actually an BWF Audio File synced to the clip)

With the Audio Option off it works flawlessly, well of course no audio so there we have an important feature in our workflow missing.

Rocket or Software is the same.

Interesting: it doesn't matter which target Avid MXF Framerate or Bitrate it is ( tried framerates 24,25,29.97, 720p 25, and bitrates 185x, 120, 26) it is just with the Camera Recording Time Base being 25.

everything we shoot with 24 fps Time Base renders flawlessly, even with audio.

it would be awesome to have this resolved since it is an important part of our workflow...and it just happens to be we live in an 25p world - at least for TV Broadcast - here :)


Thanks and Greetings from Berlin,

Alex

Thanks Alex. We're working with Avid to get this fixed. Should be present in the next release.

David
 
Have you seen an audio synch issue when shot with the Epic in 25p?
Do you use external synch or internal?

Thanks

Patrick

Can you send me the log file for your camera so I can try to replicate the settings?
I just ran a 2 hour 25p test on Epic to check this and it was locked to the slate and sound recorder the whole way through.
 
I shot a 25p project yesterday with an Ambient LockIt box attached to the Epic. Auto Sync in RedcineX was flawless. No issues whatsoever.
 
Hello Deanan,

I have the R3D file, does it help?
I shot it with build 1.4.9 and 1.6.12 back in june 15th 2011, it's difficult for me to do a logfile...
Alexander Christ from Octamas spoke with you about this trouble.

Pat
 
Hi Guys,

since we didn't have the TC Cable yet, we shot with no TC Sync, so i can't tell if Epic has this issue in 25p or not.... RED MX definitley not - other than the still big mystery why about 90% of the Shots the Audio is about 1 frame ahead of the Video when synced with ambient loockit to an sound device recorder also with ambient tc.



--> weird thing is: The Alexa seems to have the exact same "Problem"

It might have something to do with the image being "processed/encoded first, and then after this, that the TC is grabbed from the external source and stamped to the frame?

Which could lead to 1 frame of "encoding lag" ?

Deanan ?

(The 10% that match could be because in these cases encoding was a bit faster and therefore the TC just match barely over the frame boundary)

It seems a lot of people i have spoken to have the same issues, but either it is technically just not more accurately possible and we have to live with it, or there could be a future fix to this.

One thing that would definitely help, i don't know if requested already, so that goes out to the RCX Developers:


Since we have to manually Adjust offset each single clip this is very timeconsuming.

A Feature: Adjust all Selected Clips offset would be a Dream, and save so much work, we'll send a case of best German beer for that ;)

And a Keyboard Shortcut to Access the Adjust offset directly would also help tremendously for the rest of the manual fixes.

Right now it is a lot of Mouse aiming and Moving

Also: in 356 it used to be that you could click adjust offset, then press down or up on the keyboard for one frame forward or backward, hit enter and then go with the down key on keyboard to the next key. now it doesnt work anywhere because program focus seems to lay somewhere else.

What i want to say is: a decent way to navigate quickly through a lot of files and quickly trim offsets based on the visual information we get from picture and audio waveform would be a killer feature :)

So long and Greetings from Germany
 
Hello Deanan,

I have the R3D file, does it help?
I shot it with build 1.4.9 and 1.6.12 back in june 15th 2011, it's difficult for me to do a logfile...
Alexander Christ from Octamas spoke with you about this trouble.

Pat

Sure, please send me a clip.
I couldn't find anything from Alexander on this. Unless we are talking about something different.
 
Hi Guys,

since we didn't have the TC Cable yet, we shot with no TC Sync, so i can't tell if Epic has this issue in 25p or not.... RED MX definitley not - other than the still big mystery why about 90% of the Shots the Audio is about 1 frame ahead of the Video when synced with ambient loockit to an sound device recorder also with ambient tc.



--> weird thing is: The Alexa seems to have the exact same "Problem"

It might have something to do with the image being "processed/encoded first, and then after this, that the TC is grabbed from the external source and stamped to the frame?

Which could lead to 1 frame of "encoding lag" ?

Deanan ?

(The 10% that match could be because in these cases encoding was a bit faster and therefore the TC just match barely over the frame boundary)

It seems a lot of people i have spoken to have the same issues, but either it is technically just not more accurately possible and we have to live with it, or there could be a future fix to this.

One thing that would definitely help, i don't know if requested already, so that goes out to the RCX Developers:


Since we have to manually Adjust offset each single clip this is very timeconsuming.

A Feature: Adjust all Selected Clips offset would be a Dream, and save so much work, we'll send a case of best German beer for that ;)

And a Keyboard Shortcut to Access the Adjust offset directly would also help tremendously for the rest of the manual fixes.

Right now it is a lot of Mouse aiming and Moving

Also: in 356 it used to be that you could click adjust offset, then press down or up on the keyboard for one frame forward or backward, hit enter and then go with the down key on keyboard to the next key. now it doesnt work anywhere because program focus seems to lay somewhere else.

What i want to say is: a decent way to navigate quickly through a lot of files and quickly trim offsets based on the visual information we get from picture and audio waveform would be a killer feature :)

So long and Greetings from Germany


Two things:
1. Make sure your sound devices and ambient are calibrated to each other with a master clockit.

2. Timecode by itself does not have a phase or relationship to shutter closed/open.
Therefore there can be a mismatch that stems from this lack of phase because
timecode can fall out of phase with the the shutter. Using a source that has
both genlock and timecode together helps with this.

The phase issue as well as the calibration play a big part in how well syncing
works because unless everything is fed the same tc and genlock, there can
be cascading mismatches that can add up or cancel each other out.
 
Sure, please send me a clip.
I couldn't find anything from Alexander on this. Unless we are talking about something different.

Hello Deanan,

Could you PM me the ftp server where I could upload the files? HDRx clip is 42GB, 6 min. RC 1:8 2:1

Pat
 
Two things:
1. Make sure your sound devices and ambient are calibrated to each other with a master clockit.

2. Timecode by itself does not have a phase or relationship to shutter closed/open.
Therefore there can be a mismatch that stems from this lack of phase because
timecode can fall out of phase with the the shutter. Using a source that has
both genlock and timecode together helps with this.

The phase issue as well as the calibration play a big part in how well syncing
works because unless everything is fed the same tc and genlock, there can
be cascading mismatches that can add up or cancel each other out.

Deanan,

thanks so much for this precise and valuable answer, we appreciate that a lot it could save lots of work!

Just two Details about that, sorry about being so specific and accurate, but i guess in the Sync world it is all about the last bit of Accuracy ;):

1. Calibrating: By Master Clockit do you mean this works only with the ACC 501 (or old ACC101) Clockit Controller http://ambient.de/produkte/timecode/controller/controller_e.html or would a Second ACL 203 TRILEVEL SYNC LOCKIT http://ambient.de/produkte/timecode/lockit/lockit_e.html that acts as a "Master" and then once or twice feeds the first Lockit ACL 203 attached to the RED/EPIC and also the Sound Devices Recorder ?
(would probably not make a lot of difference than having just the first ACL 203 Lockit on the Camera also jam syncing the Sound Device once or twice a day i guess?)

-> Whats your expericence in how often you have to calibrate to stay frame accurate?


2. So since the ACL 203 Clockit has a Genlock Output, basically connecting that Output to the Camera and of course turning GENLOCK Sync on in Camera should be sufficient? Or should the Sound Device Genlock IN be also connected to the Lockit GENLOCK OUT when we connect the Lockit TC OUT to the Sound Devices TC IN temporarly when jamming 1/2 times a day ?


Even though considering there can be working ways to get frame accuracy, when in the real world there still sometimes you will get Material that was not carefully synced enough, what do the RCX Developers think about the Adjust Offset Features?

Another Point: Right now it seems that pretty much all BWF Metadata like Track Names and so on is lost after Rendering in RCX... is there a future plan to pass that BWF Metadata through to the MXF Video / Audio Pair, or is this just an Avid Limitation we have to live with?

Thanks for your time and support!
 
Does anybody else have this ?

Sometimes when switching to Fullscreen Mode (Zoom Setting set to Fit Both) the Image is zoomed in a lot, something like 100 or 200 % and sometimes also distorted. Switching back and forth between GUI View and Fullscreen again a couple of times and it is gone.

all with Rocket in the Mac Pro 5,1 , Snow Leopard 10.6.6
 
Back
Top