Pride month means I get to post the gay oscilloscope

Here's the VOD of my stream for #SynthOn 5 year GSG Legends celebration in case you missed it =)

https://www.twitch.tv/videos/2461414789

#Synth #musodon @synths

More vampire therapist on my stream shortly #twitch https://twitch.tv/litui

Streaming some Vampire Therapist on #twitch for #TDoV. Come say hi! https://www.twitch.tv/litui

First I'm going to have to figure out how to get some of the udp network code working over interrupts. AES67 has some pretty tight timings.

My goal is to see if I can get multiple teensy 4.1 boards streaming to pipewire on my linux music system decently.

So I kinda got the Teensy4.1 AES67 code semi-working today after much rewriting and mangling. It's not great yet but actually getting sound between systems on my LAN at L16/44100Hz (with major stuttering) and all the PTP code appears to be working.

preempt=full is love, preempt=full is life

Okay, had to work out some glitches.

The above works because my TV doesn't announce its "off" status via dpm/dpms but something fails to fix the output when turning the TV on again. This script monitors i2c for the TV being on or off and cycles the dpms status.

https://gist.github.com/litui/0e7287881d70f8e014d173a1d62b7fea

@jordan there, did it. Works dandy 😂. Maybe it'll provide a starting point for your setup too.

https://gist.github.com/litui/0e7287881d70f8e014d173a1d62b7fea

@jordan lol... not sure it's the best approach but i2c device detection changes depending if the TV is on/off. I might try watching a byte on one of the transient addresses and triggering `kscreen-doctor --dpms` off or on depending on results.

@jordan I'm testing some commands to see if I can automate somehow... looks like remotely-run `kscreen-doctor --dpms off` followed after a pause by `kscreen-doctor --dpms on` restores the display without the same breakage as changing ttys.

@jordan might work for you still if you're not using qt/plasma on your basement PC.

I may have spoken too soon regarding getting rid of the dongle. Seems like qt/plasma receives a wake message of some sort when the TV turns on that still borks it (creates a fake display to render to and doesn't restore to the real display).

When the EDID dongle is plugged in and mirroring is set up, qt doesn't freak out and my display is restored properly.

So weird.

@jordan wayland doesn't seem to be disturbed, just the qt/plasma session atop it.

@jordan seems like a kde/plasma problem here. The static EDID seems to have fixed the disappearing TV problem, but when I turn the TV on again, KDE is getting some kind of signal that the power cycled and messes up after that point.

@jordan I still seem to be having issues with wayland coming back after turning my TV on again, but switching to a different TTY and back seems to fix it.

I've been dealing with it for years using an HDMI HDR-capable EDID emulator dongle set as my secondary, mirrored monitor. This worked great in Windows.

It also (mostly) worked in Linux, but for a current nvidia driver bug affecting multi-monitor setups in wayland.

In any case, I dumped my TV's EDID eeprom and told the Linux kernel to always use it for that HDMI port and it seems to have solved everything.

Reason for needing to do this is the TV eventually cuts power to its EDID eeprom after being turned off. That forces the OS into a display reconfiguration as it's as though a monitor just disappeared. If no other monitor is attached that will wreak havoc with games, prevent there from being a valid display for Sunshine to attach to, etc.