github.com/WebAssembly/wasm-c-api This is a relevant piece of info that I was missing. The C API is poorly documented, because it's just implementing a spec that's defined somewhere else. I haven't read it, but it feels like it's supposed to be really low level. My guess is that you could build a higher level API on top of this abstraction, and have it work with all wasm backends.
this is such a confusing library. when i saw this video I treid to complete it before you but after a couple days i just had to see how you did it in 2 hours. it was glad to find out you struggled in the exact same spots i did lol. every stupid goto definition lead to a macro and there was barely any documentation.
I think the recording only starts at the first I-frame after I hit record, so sometimes the "Yooooo, what's up what's up what's up" is fully there, and sometimes we only get the tail end of it
You're missing a few technologies in this project. What you need to add is a sqlite DB to store clip data, then I'd look at writing your own custom VM to interpret some scripting language of your own invention
I don't know how much processing you do on the vods. But it would be cool if you enabled 1080p30fps not just 60. It uses twice the bandwidth for no gain with programming content
just an artifact of recording at 60fps. Would need to re-encode the entire video down to 30fps because youtube doesnt provide that option. Agreed that 60fps is overkill for text based content
Imposter Syndrome fears this man
github.com/WebAssembly/wasm-c-api This is a relevant piece of info that I was missing. The C API is poorly documented, because it's just implementing a spec that's defined somewhere else. I haven't read it, but it feels like it's supposed to be really low level. My guess is that you could build a higher level API on top of this abstraction, and have it work with all wasm backends.
This channel is a blessing for learning more than just the basics of zig. Youre a legend @sphaerophoria
this is such a confusing library. when i saw this video I treid to complete it before you but after a couple days i just had to see how you did it in 2 hours. it was glad to find out you struggled in the exact same spots i did lol. every stupid goto definition lead to a macro and there was barely any documentation.
no whats up whats up whats up? 😢
I wish WASM could handle string arguments without the need for bindings or advanced memory copying.. it would make it so much easier to use.
okay, after looking into it again I found out it's actually not that advanced. I digress.
1:47:02 awesome haha
01:17:30 Funnily enough I could have cut this whole hour and been okay with it, but there is value in showing mistakes as well :)
This was amazing.
Some reddit thread recommended me to watch you and this is amazing.
Feels very much like watching a Tsoding video ❤
Tsoding that actually loves zig).
No what’s up what’s up what’s up today. Something feels off
I think the recording only starts at the first I-frame after I hit record, so sometimes the "Yooooo, what's up what's up what's up" is fully there, and sometimes we only get the tail end of it
You're missing a few technologies in this project. What you need to add is a sqlite DB to store clip data, then I'd look at writing your own custom VM to interpret some scripting language of your own invention
you're a madman... but you're also pretty good at what you do. Keep it up man
still much better than JavaScript
I don't know how much processing you do on the vods. But it would be cool if you enabled 1080p30fps not just 60. It uses twice the bandwidth for no gain with programming content
just an artifact of recording at 60fps. Would need to re-encode the entire video down to 30fps because youtube doesnt provide that option. Agreed that 60fps is overkill for text based content