How to control the KiPro via RS-422?

[Jeremy Garchow]

OK, I wasn’t able to totally recreate your situation, but I used a Kona 3 to KiPro as my ioHD isn’t connected to the machine room. I imagine the results between the two will be similar. When letting the Kona do the conversion, I found basically what you found and that is some weirdness with the first few frames or 4.

When setting the KiPro to do the down convert, everything was spot on.

Give that a shot and see if that works better.

Config > In Convert > SD in the KiPro.

Jeremy

[Torben Suhrke]

No luck, yet. The same duplicate frames show up when I let the KiPro do the conversion. I also played around with the “playback offset” parameter in the device control settings, but it is also ignored by the KiPro.

Thanks again for taking the time to set up your gear for recreating my problem. Much appreciated.

Torben

[Jeremy Garchow]

Hmm. Sorry Torben. I’ll hook up the ioHD tomorrow and see if I can recreate the issue.

What’s the first thing in your timeline? Meaning, describe what your timeline looks like.

Also, when you make changes in the device control preset, you are sure that’s the preset selected when performing the ETT?

And (sorry for the edits) what drivers are installed on your ioHD? What kind of system do you have (computer/hard drive/etc)?

[Torben Suhrke]

As soon as I realized there are duplicate frames at the beginnig, I superimposed some numbers at the start of the timeline to keep track of what is going on.

I renamed the copied device control preset to “KiPro”, so I can check in the ETT-dialog that I chose the correct one. Though I’m not quite sure if you have to restart final cut to make any changes come alive.

All drivers and software are up to date.

Today I tested a different setup: MacPro with internal Blackmagic Decklink HD Extreme connected to the KiPro.

Same result. 3 duplicate frames at the beginnig of the resulting file.
So it has to be a wrong setting in final cut or the kipro that is causing this behaviour.

Torben

[Jeremy Garchow]

[Torben Suhrke] “Though I’m not quite sure if you have to restart final cut to make any changes come alive.”

No, you just have to make sure that preset is selected in the ETT window.

[Torben Suhrke] “All drivers and software are up to date.”

Firmware is up to date on the ioHD?

[Torben Suhrke] “So it has to be a wrong setting in final cut or the kipro that is causing this behaviour.”

Can you please explain your timeline a bit? What is the first clip? Are you using the ETT window to layoff bars or black or anything? Is there a gap in your timeline near the beginning?

Jeremy

[Torben Suhrke]

Oh, it’s a very simple timeline. It consists of just one 30 second long clip. It’s only purpose is to test this workflow.
I unchecked everything in the mastering tab of the ETT-window, because what I really want is just a downconverted file that mirrors my timeline so that further processing can take place. (e.g. sending to compressor and combining with different audiomixes)
No spaces or anything in the timeline.

Torben

[Gabriele Turchi]

Guys sorry if I cannot help with your duplicated frames …
But I have a question regarding the RS422 and kipro:
Basically now the kipro act like a deck?
So tale the timecode over the 422?
Can it record for few few hours straight ?
Can it split the clip when the timecode break ?
The reason is because I am thinking to use it with SCRATCH for realtime dailies …
Thanks

G

[Torben Suhrke]

Hi Gabriele,

yes, the kipro acts like a deck and receives timecode via 422.
The recording duration depends on your chosen flavour of prores and the size of the hdd.
I’m not quite sure what happens on a timecode break during edit to tape, but theoretically you could work without deckcontrol and have the kipro start and stop recording whenever timecode is coming in. The parameter is called “arm recording” and can be set to tc. Then it should create a new clip whenever timecode is coming in. There might be a slight delay of a few frames before recording sets in.
I don’t know if this workflow is applicable to your situation, though.

Greetz,
Torben

[Gabriele Turchi]

Thanks Torben,

but SCRATCH can layoff timecode only over the RS422 (actually now even over teh SDI but the device should support VANC data on teh SDI (does the kipro accept VANC ?)),
so over the RS422 scratch can operate only as connected to a deck ,
and the use of the kipro for my need would justified only if i can record like 2 hours straight of material without stop -pause-or reinsert TC…

Thanks

g

[Torben Suhrke]

Hello Gabriele,

in your specific situation it might be best, if you rent a kipro to test your workflow.

Torben