00:15 haasn: JEEB: what do you mean by ipt then
09:09 pq: JEEB, if it touches H.273, this channel is not completely off-topic either. :-)
09:26 JEEB: pq: sure :)
09:26 JEEB: also I had forgotten how nice it is that JVT docs are public
09:26 JEEB: I could see that Apple would like the H.273/CICP process less rigid
09:26 JEEB: https://jvet-experts.org/doc_end_user/documents/29_Teleconference/wg11/JVET-AC0317-v1.zip
09:26 JEEB: they want to make a registration authority a la mp4ra
09:27 JEEB: which would be nice since I think mp4ra accepts github PRs?
09:38 pq: docx...
09:40 pq: good thing we expected H.273 to get more entries in Wayland design
09:42 pq: JEEB, did the FourCC/MP4RA... um... is it a complete mess of confusing pixel formats, image layouts, and colorimetry information?
09:43 pq: as opposed to drm_fourcc.h which is a completely separate "standard" and strictly limited to pixel formats only
10:07 JEEB: pq: it is separate for essentially codec identifiers and otherwise metadata boxes etc
10:08 JEEB: f.ex. https://mp4ra.org/#/codecs
10:11 pq: JEEB, I was thinking of e.g. MatrixCoefficients, transfer function, or primaries.
10:14 pq: JEEB, looks like I guessed wrong: FourCC/MP4RA does not include pixel format definitions at all, does it?
10:24 JEEB: pq: yea. and they just want to make another registration authority for CICP
10:24 JEEB: not include it in mp4ra
10:24 pq: right
10:26 JEEB: thankfully these docx generally open up nicely in libreoffice so it's not too much of a PITA to work with them :)
10:27 JEEB: I expect the next draft for CICP to appear in https://jvet-experts.org/doc_end_user/current_document.php?id=12568
15:26 naveenk2: HI anyone experiencing gitlab.freedestop.org to be very slow than usual browsing!!
15:27 naveenk2: it takes more than ~2mins to open this CM&HDR implementation roadmap (#467) · Issues · wayland / weston · GitLab
15:27 naveenk2: https://gitlab.freedesktop.org/wayland/weston/-/issues/467
15:28 daniels: it loads in a few seconds for me here, including scrolling down to page all the comments in
15:28 bl4ckb0ne: same, loads in the usual gitlab time
15:28 daniels: apparently Firefox is pathologically slow with GitLab loads sometimes
15:33 naveenk2: disconnecting vpn also does not help, and youtube plays videos very smooth. so do know what is culprit here
15:34 naveenk2: changed browser too
15:34 naveenk2: but its fine as long as it works fine for others :)
15:48 naveenk2: pq: I remember weston does have manual color space conversion (using some sort of formula/c program) for color values comparison with equivalent shaders conversion, can you help me point to that
15:55 pq: naveenk2, yeah, grep for opaque_pixel_conversion or output_icc_alpha_blend
15:58 pq: those give you the entry points to such tests
15:59 pq: they're in tests/color-icc-output-test.c
15:59 pq: till tomorrow .o/
16:00 naveenk2: okay thanks :)
19:12 aaron465: (please redirect me if there is a better place to ask this...) What is the general status of nvidia drivers + wayland? Things are mostly working with kernel modesetting + the "actually restore the video memory when coming back from sleep" stuff... however I still get a lot of weird graphical glitches. I think things with hardware acceleration like vscode are particularly good at triggering it. Even just typing on the keyboard does weird shit,
19:12 aaron465: when typing a new character the previous one disappears for a moment so it feels really janky and you can't see where you are up to.
19:13 aaron465: Had considered just giving up and selling my 3070 for some AMD card if it's gonna work loads better. I finally just nuked my Windows install last week and been playing games under steam proton for a while now in Linux.
19:18 bl4ckb0ne: it "should just work"™ but you're on your own when you hit a driver issue
19:26 aaron465: I haven't been able to find much/any evidence of other people having similar issues so there must be something weird about my specific combination of hardware or just my GPU maybe... I don't know much about graphics card hardware but variants from gigabyte/asus etc are just different packaging (cooler / maybe a bit of overclocking) afaik so shouldn't make any difference to basic desktop operation right?
19:27 aaron465: this stuff happens even on a fresh install so my pc is just cursed for linux I guess
19:30 bl4ckb0ne:points at proprietary drivers
19:30 kennylevinsen: aaron465: refer to your gpu and Wayland server vendor (sway, gnome/mutter, keep/kwin, ...) for support - Wayland is just a protocol, not an implementation. :)
21:12 DemiMarie: <aaron465> "(please redirect me if there..." <- Is there an iGPU as well? If so, and the problem goes away when it is used, then contact Nvidia.
22:57 wlb: wayland Merge request !292 opened by yshui (yshui) protocol: clarify when wl_surface.enter events are sent https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/292