On Tue, Jul 04, 2017 at 03:54:46PM -0400, Trevor Childs wrote:
> I meant -- what hardware generates that signal?
>
>The Linux system is an Nvidia Jetson TX1 developer kit, running Ubuntu
>16.04. The output is done over the board's HDMI (2.1, type A) port, either
>direct into the
>
>
> I meant -- what hardware generates that signal?
>
> The Linux system is an Nvidia Jetson TX1 developer kit, running Ubuntu
16.04. The output is done over the board's HDMI (2.1, type A) port, either
direct into the recorder or through an AJA HA5-4K HDMI to SDI converter.
_
On Tue, Jul 04, 2017 at 01:42:16PM -0400, Trevor Childs wrote:
> And what is the hardware you are trying to setup?
>
> The recorder is an Atomos Shogun Inferno. It has HDMI 2.1 as well as quad
>SDI inputs.
I meant -- what hardware generates that signal?
__
>
> And what is the hardware you are trying to setup?
>
The recorder is an Atomos Shogun Inferno. It has HDMI 2.1 as well as quad
SDI inputs.
How pixel clock is defined there? With ~300 kHz steps?
>
Pixel clock is defined as a number of picoseconds.
> What modelines got you 60.02 and 59.98 H
On Tue, Jul 04, 2017 at 11:00:51AM -0400, Trevor Childs wrote:
>I've run into a problem setting display modes. I'm attempting to output
>3840x2160 @ 60Hz to a hardware recorder but the standard modes for 60Hz
>and 59.94Hz actually come out to 60.02Hz and 59.98Hz. EDID data has
>1080
I've run into a problem setting display modes. I'm attempting to output
3840x2160 @ 60Hz to a hardware recorder but the standard modes for 60Hz and
59.94Hz actually come out to 60.02Hz and 59.98Hz. EDID data has 1080p@60 as
it's preferred mode, and scaling the numbers up leads to the same rounding
