#timvideos

nueces: ping?

mithro, hi!

nueces: Did you see my reply to your email?

mithro, I see your mail and I really like your idea

nueces: Now I've forgotten what my idea was :P

but I don't have time this week

clone the EDID using the opsis

really interesting bug with the atlys today - my laptop -> atlys, getting this: https://corelli.tumbleweed.org.za/stefanor/tmp/...

it's correct on the HDMI outputs, but wrapped on the encoder

I'm outputting https://elegua.za.net/~froztbyte/pyconza/sponso...

tumbleweed: okay I've just looked at that more. WAT.

that's like 2x-shifted

tumbleweed: Something weird is going on with your vsync signal in that

mithro: yeah

but I thought hdmi2usb was buffered through the rham

ram

so, why were the HDMI outputs fine?

also, just couldn't get it to work :P

fuck, it's doing it with the next speaker

swapped the atlys out

new one works

tumbleweed: It's just bytes

mithro: so, in DVI hsync is just a packet?

err vsync

tumbleweed: No, the hsync/vsync is just tells it when to start copying bytes

right, and that was clearly getting thruogh to the outputs

but not the encoder

gah, don't think I actually power cycled it. Probably should have tried that

tumbleweed: What do you mean? The output hsync/vsync signal is generated internally and doesn't actually have any relationship to the input hsync/vsync

that's the problem with having the odroid powered from the atlys - I'm wary of power cycling

mithro: right, that's what I was assuming

mithro: so, then why would only the encoder be affected?

tumbleweed: You mean you aren't getting it on the screen too?

correct

06:51 < tumbleweed> it's correct on the HDMI outputs, but wrapped on the encoder

tumbleweed: The encoder doesn't really just have a hsync/vsync - it just takes what ever buffer is avaliable at the time

yep, hard power cycle fixed it