Genlock and/or timecode experts..?
- Thread starter ^faldo^
- Start date
ProfessorU
Veteran
We need an engineer up in here.
There's a basic blurb on black burst for genlock here
http://www.tek.com/Measurement/App_Notes/NTSC_Video_Msmt/genlock.html
Does that help?
There's a basic blurb on black burst for genlock here
http://www.tek.com/Measurement/App_Notes/NTSC_Video_Msmt/genlock.html
Does that help?
^faldo^
Member
Update:
In short:
*WAH*
(C# != C)
NTSC drop frame timecode is a dicey hack
Bluetooth stack is opaque
Assignments
*WAH*
In long:
I started learning C# about a week and a bit ago for this project, and it's less C-like than you'd think. Getting there though, but struggling with streamWriter stuff.
Being a PAL boy, NTSC is weird. I need to devote some deep thought time to how drop frame works. The rule is drop frames 00:00 and 00:01 every minute but the tenth, but I keep worrying that this will throw everything out of sync relative to a global clock, which it shouldn't. Implementing strange functions instead of a simple millisecond divisor is on the to do list, and so the first alpha might not do drop frame numbering.
Bluetooth stack and working out how devices pair and talk is just messed up. More on this when alpha is released.
I've got a fairly major Uni analysis due in 24 hours, so priorities have changed. Say Wednesday.
In brief, FTR:
Genlock is a voltage pulse that does coordination. I need more info. Expect full support in the beta.
Timecode is binary coded decimal number that represents the actual timecode, user bits and certain flags that can be recorded as an audio track or in a scan line. I suspect (but am not certain yet) that it's just a square wave pulse that hits your camera through BNC, and the camera deals with it from there. Expect full support in the beta.
Uni libraries are awesome.
In short:
*WAH*
(C# != C)
NTSC drop frame timecode is a dicey hack
Bluetooth stack is opaque
Assignments
*WAH*
In long:
I started learning C# about a week and a bit ago for this project, and it's less C-like than you'd think. Getting there though, but struggling with streamWriter stuff.
Being a PAL boy, NTSC is weird. I need to devote some deep thought time to how drop frame works. The rule is drop frames 00:00 and 00:01 every minute but the tenth, but I keep worrying that this will throw everything out of sync relative to a global clock, which it shouldn't. Implementing strange functions instead of a simple millisecond divisor is on the to do list, and so the first alpha might not do drop frame numbering.
Bluetooth stack and working out how devices pair and talk is just messed up. More on this when alpha is released.
I've got a fairly major Uni analysis due in 24 hours, so priorities have changed. Say Wednesday.
In brief, FTR:
Genlock is a voltage pulse that does coordination. I need more info. Expect full support in the beta.
Timecode is binary coded decimal number that represents the actual timecode, user bits and certain flags that can be recorded as an audio track or in a scan line. I suspect (but am not certain yet) that it's just a square wave pulse that hits your camera through BNC, and the camera deals with it from there. Expect full support in the beta.
Uni libraries are awesome.