TC error after embedder
Posted: Tue Jul 04, 2017 9:15 am
Hi.
We have a strange behavior of the embedded timecode from our Atem 2me 4K switcher.
We are feeding a ltc timecode to our switcher and if I send the program out (1080i50) it to our recorder (Atomos Samurai Blade) the embedded timecode are displayed correctly.
If the same signal are going thru a Black Magic Audio to SDI embedder the timecode on the Blade starts to change rapidly (looks like its more than one timecode) and every time you start a recording the TC starts randomly on one of up to three timecodes. I had to start recording and if it was the wrong TC stop and start all over again until it started with the right TC. I have no idea where the other two timecodes comes from. I have tested two embedder, one using analog audio and the other aes/ebu both give me the same problem. It must be the embedding process that messing with TC and since we are using 2 embedders to be able to embed 12 channels of audio, each embedder make another timecode giving me a total of 3.
Have anybody experienced the same problem.
We have a strange behavior of the embedded timecode from our Atem 2me 4K switcher.
We are feeding a ltc timecode to our switcher and if I send the program out (1080i50) it to our recorder (Atomos Samurai Blade) the embedded timecode are displayed correctly.
If the same signal are going thru a Black Magic Audio to SDI embedder the timecode on the Blade starts to change rapidly (looks like its more than one timecode) and every time you start a recording the TC starts randomly on one of up to three timecodes. I had to start recording and if it was the wrong TC stop and start all over again until it started with the right TC. I have no idea where the other two timecodes comes from. I have tested two embedder, one using analog audio and the other aes/ebu both give me the same problem. It must be the embedding process that messing with TC and since we are using 2 embedders to be able to embed 12 channels of audio, each embedder make another timecode giving me a total of 3.
Have anybody experienced the same problem.