Direct to disk capture of SD material

[Jeremy Garchow]

YOU mean timecode, not rp188, right?

rp188 is variable frame rate flag info.

What do you mean it’s not working? What version of VTR Exchange do you have? Have you set up the prefs accordingly? With the currently released version, the tc will say –:–:–:– in the capture window but if you notice after you capture it, the correct tc will be in the file.

Jeremy

[Ramona Howard]

Boys,

Technically, RP188 is a SMPTE transmission standard

timecode can come via RP188 (embedded), you are correct. Most SD decks don’t support this, which is why I think the confusion is that it is just a HD thing.

Flagged frames are also passed via RP188, so yes it supports variable frame rates.

You both win a ribbon 🙂

Cheers,
Ramona

[Jeremy Garchow]

See I first thought the rp188 was embedded tc along with the flagged frame info, then I learned that Rp188 is it’s own tc of sorts and SMPTE timecode are two separate entities. Now I am confused.

Glad I have a ribbon though 😉

[Ramona Howard]

If it were easy, everyone would do it 🙂

Try giving the SMPTE RP188 doc a read, then you will surely be confused. After that tackle the RP215…..

Here is the tag line:
Transmission of Time Code and Control Code in the Ancillary Data Space of a Digital Television Data Stream

By the way there are numerous was to pass timecode and ancillary data or more than one way to skin a cat.

Cheers,
Ramona

[Jeremy Garchow]

I’ll take a look for it. Thanks, Ramona.

At any rate, Robert, it is possible to capture embedded tc via SD SDI. It works I’ve done it, but it was straight out of camera, not a deck.

Jeremy

[Robert Hutchings]

I tested directly out of our Varicam via HD-SDI and the AJA utility read the embedded timecode like a champ.

But no dice on an SDI delivered SD signal looped thru a digibeta deck.

Thanks to both of you for the education and suggested reading materials.

Robert Hutchings
Director/editor
Twin Cities Public Television

[Ramona Howard]

That is because more than likely the digibeta doesn’t support it.

I am sure there is information out there somewhere that states if it does/doesn’t.

Anytime on the help.

Cheers,
Ramona

[Jeremy Garchow]

I think Ramona’s got it.

What deck? A500?

[Robert Hutchings]

Yes. A500.

Our HDCam decks do recognize RP188 embedded timecode.

[Gary Adcock]

[Ramona Howard] “Try giving the SMPTE RP188 doc a read, then you will surely be confused. After that tackle the RP215….. Here is the tag line: Transmission of Time Code and Control Code in the Ancillary Data Space of a Digital Television Data Stream”

LOL….
Ramona- you bait the hook too well.

Remember that TC info in a modern world is not necessarily meant to be a string of sequential numbers and that ancillary data tracks also handle in the same space Ubit and metadata.

” There are drop-frame and color framing flags and three extra ‘binary group flag’ bits used for defining the use of the user bits.”

Where as RP188 in an FCP world is not usually meant for the” house TC signal” but more the Ubit info. In the Real world outside of FCP where Ramona lives -this data stream carries the vastly larger array of information not accessible to the Apple platform called Metadata.

Most people here on the Cow understand RP188 as the frame flagging info mainly used in 720p HD to attend to the Variable Frame Rate Data- in actuality other companies -Sony with the Ex1 and Xdcam lines, Thompson with the LDK and JVC’s 200 too. However now we are seeing this info from the Sony f23, panasonic 3700 and even prosumer camera coming out later this year will start supporting the RP188 flagging in the 1080 stream over HDSDI or fibre.

With Rave ( and correct me if I am wrong here) the use of RP188 tracks allow the cameras to add any myriad of data into the pipe during image acquisition, lens settings, aperture,focal length, even other things like programed crane data can be inserted in the data stream and then extracted by the RAVE tools- This is all about the future of film making.

gary adcock
Studio37
HD & Film Consultation
Post and Production Workflows
Inside look at the IoHD