obs-ndi VS obs_blade

I using OBS Newtek NDI https://github.com/obs-ndi/obs-ndi to send the screen over network (without capture card).

For receiving NDI in Streamlabs; https://streamlabs.com/content-hub/post/ndi-receiving-setup-in-streamlabs-desktop OBS NDI plugin for use with OBS. OBS-NDI: https://github.com/obs-ndi/obs-ndi

For NDI use a gigabit connection or there will be issues. I run Vseeface on my streaming rig while I run my games in my own pc, you can see an example here: https://youtu.be/5xq3p8QvWxQ For NDI: https://github.com/obs-ndi/obs-ndi/releases

Do you have the OBS NDI Plugin installed? It's not a default media source. https://github.com/obs-ndi/obs-ndi/releases

Current OBS plugin. https://github.com/obs-ndi/obs-ndi/releases/tag/4.11.0

For controlling OBS, you can control it several ways. If you have a stream deck, you can use OBS web socket. Or if it works, you could just use google chrome Remote Desktop. Might be choppy video though. Also look at obs blade. https://github.com/Kounex/obs_blade

OBS Blade: Make use of the OBS WebSocket Plugin and control your stream

OBS -- I use OBS when I am streaming Graduation/Board Meetings/etc. I use OBS Blade to control it from a tablet.

I'm the author of OBS Blade, an open source mobile app to remotely control OBS (Open Broadcaster Software) which is mainly used for streaming content to platforms like Twitch or YouTube and recording stuff for videos etc!

Just Download the Icon pack as a font (.ttf), include it in your pubspec (take a look here at the bottom: https://github.com/Kounex/obs_blade/blob/master/pubspec.yaml) and create wrapper to use it in a type safe way in your project (https://github.com/Kounex/obs_blade/blob/master/lib/utils/icons/jam_icons.dart)

A general approach is the view / feature driven project structure where the main goal is to separate code / concerns into view / feature specific files / folders. You will usually have some „main“ folders like: utils, types / classes, models, states / stores, widgets / shared etc. But all in all a more freestyle aspect. You can take a look into my open source project for this kind of approach: https://github.com/Kounex/obs_blade but be aware that this is does not guarantee to be a good approach for everyone (or specifically your project). I nested view folders to reflect the way views are direct children (routing wise) and try to extract a lot of stuff into own widgets to keep every widget small and also keep the actual „view widget“ to only serve as laying out the screen.