Tetsuo Milk (npub1g6x…4rvz) npub14ly3sdvez025eln623a3t35c0tc8vyset9sqg30ed2x6alvyuvvsxja6kq (npub14ly…a6kq)
forcing software encoding on the server fixed it
Probably because my crappy NAL parser is broken: it’s possible to have NALs beginning with either 00 00 00 01 or just 00 00 01. On software encoding, the setup packets always use 00 00 00 01, and the rest always use 00 00 01, so I didn’t bother handling the other cases.
https://github.com/zhuowei/VisionOSALVRClient/blob/34384e1e3d7d644dc473e2cf2a7bb5465c33f794/ALVRClient/ALVRClientApp.swift#L99
Fix is probably simple (check the first 4 bytes to see if they’re 00 00 00 01 or 00 00 01 xx; see NalParsing.cpp in Alvr). Do you happen to have a video capture from Nvenc (Alvr->Debug->Start Recording)?
though it appears to be rendering the same texture for both eyes
ugh, sigh. I’ll take a look. Is it showing the same eye on the video recording as well?
Zhuowei Zhang /
npub1cp…9e7uy
2024-02-05 04:44:43
in reply to nevent1q…077z
Author Public Key
npub1cppa6rw8av0n2zjc6yarum7k0nmtkka4d7qas3ndy0sqpjfz9u0sx9e7uySeen on
wss://relay.noswhere.comPublished at
2024-02-05 04:44:43Event JSON
{
"id": "32c70aa419f0b08bfe0ed9e8e72a0176430296b5e3c0859327bc4ba46afee81b",
"pubkey": "c043dd0dc7eb1f350a58d13a3e6fd67cf6bb5bb56f81d8466d23e000c9222f1f",
"created_at": 1707108283,
"kind": 1,
"tags": [
[
"p",
"468cd334b9541b551189215c4c31b0af3e2e45a24eae6d6977e0726dbb3cd455",
"wss://relay.mostr.pub"
],
[
"p",
"afc918359913d54cfe7a547b15c6987af076121959600445f96a8daefd84e319",
"wss://relay.mostr.pub"
],
[
"p",
"611c518b5ac7c2daa81c6dcc66b3e04a279b6524b28f8f72fac89e14538d8dac",
"wss://relay.mostr.pub"
],
[
"e",
"775248ee050acd4270ac0662f206383a909f4ea3bdb072cd4acf6bf31d0e4348",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://notnow.dev/objects/9b11ba11-8674-40d5-a16f-28c453983968",
"activitypub"
]
],
"content": "nostr:npub1g6xdxd9e2sd42yvfy9wycvds4ulzu3dzf6hx66thupexmweu632sy74rvz nostr:npub14ly3sdvez025eln623a3t35c0tc8vyset9sqg30ed2x6alvyuvvsxja6kq\n\nforcing software encoding on the server fixed it\n\nProbably because my crappy NAL parser is broken: it’s possible to have NALs beginning with either 00 00 00 01 or just 00 00 01. On software encoding, the setup packets always use 00 00 00 01, and the rest always use 00 00 01, so I didn’t bother handling the other cases.\nhttps://github.com/zhuowei/VisionOSALVRClient/blob/34384e1e3d7d644dc473e2cf2a7bb5465c33f794/ALVRClient/ALVRClientApp.swift#L99\nFix is probably simple (check the first 4 bytes to see if they’re 00 00 00 01 or 00 00 01 xx; see NalParsing.cpp in Alvr). Do you happen to have a video capture from Nvenc (Alvr-\u003eDebug-\u003eStart Recording)?\n\nthough it appears to be rendering the same texture for both eyes\n\nugh, sigh. I’ll take a look. Is it showing the same eye on the video recording as well?",
"sig": "e6b76c5ded5fb4e0a76c6533053244e10f9ab864955508de1e14c95cbad931af8fb422351b331c90385b099e7648ca075e55b761edbc897d37c49ddd55e9781b"
}