OK so my new dedicated box should be here in a few days and I'm gonna try setting up Linux first and just see if I can do three sessions with Linux and keep them fairly separated so I never make a mistake regarding each stream. So with that said what is the easiest way and best way to open three sessions on Linux and for this let's just say, Profile - Cam 1, Cam 2 and Cam 3, and Collection can be Stream 1, Stream 2 and Stream 3.
As I said before:
And you can see the options in the script that I posted. You don't necessarily need all of that logic; I left some remnants of some conditional logic in there, for different uses of the same script. You might just get away with 4 lines: 1 at the top to say it's a bash script (
#!/bin/bash), and the other 3 to start each instance of obs.Graphics can be transparent too. Regardless of how they do it, I'd use Photoshop. Or a free equivalent that already comes preinstalled with Ubuntu Studio (not the regular Ubuntu, but Studio specifically, which is based on it):
That I don't know. Maybe someone else will have that answer.
Bash is a command-line interpreter. Stands for Bourne-Again SHell, after the guy that started that particular branch of it. There are others, but that's by far the most popular and therefore widely supported.
#!/bin/bash - and make the file executable in its properties. The #! up front is called a shebang (! is sometimes called a "bang"), and whatever comes after it is the absolute path to whatever is supposed to execute this file. In this case, it's the path to where Bash is actually installed. I'd be VERY surprised if you don't have Bash in that exact path; almost every Linux system does.# that it starts with, also makes it a comment, which the interpreter itself simply ignores. So if you want to document your script, within the script itself (a VERY good idea!), just start every line of the documentation with a #.crontab -e in a terminal, choose the nano option, and add a line at the bottom like @reboot /path/to/script. Because this is a terminal application and not a graphical one, the paste function is Ctrl-SHIFT-V, because Ctrl-V is already taken by something else. Or you can right-click and paste from there. Also because it's a terminal app and not graphical, the mouse has (almost) no other meaning, so the cursor must be moved with the arrow keys.obs --profile "Stream_1" --collection "Camera_1" && on the end makes it continue without waiting to finish. So if all 3 of your obs lines have that, then they all start and run simultaneously, and the script exits immediately, having run out of things to do. If one doesn't have the & on the end, it'll wait for that process to finish. For a graphical application, "finishing" doesn't happen until you close it.Thank you for all the info. I'm just gonna use regular Ubuntu. I just want the most stripped-down box possible to run this, I don't need any bells and whistles. Like I said I bought another box just to put the minimum needed on it to run these three streams reliably.Bash is a command-line interpreter. Stands for Bourne-Again SHell, after the guy that started that particular branch of it. There are others, but that's by far the most popular and therefore widely supported.
A bash script is simply a text file that has commands in it that Bash can interpret. All that's required to make it one is to put the line at the top that says so -#!/bin/bash- and make the file executable in its properties. The#!up front is called a shebang (!is sometimes called a "bang"), and whatever comes after it is the absolute path to whatever is supposed to execute this file. In this case, it's the path to where Bash is actually installed. I'd be VERY surprised if you don't have Bash in that exact path; almost every Linux system does.
The shebang is also handy because the#that it starts with, also makes it a comment, which the interpreter itself simply ignores. So if you want to document your script, within the script itself (a VERY good idea!), just start every line of the documentation with a#.
---
The file itself can go anywhere. No restrictions on that. I have a folder called Scripts, with a few subfolders under it, just to keep things organized, but there's nothing special about that at all. When you set it to run on startup, you go to the scheduler's settings, and give it the absolute path to wherever you decided to put it. You can (usually) right-click the file and copy that path instead of the file itself, and then you can paste it to avoid typing errors.
---
That scheduler could be cron, as I mentioned above:crontab -ein a terminal, choose thenanooption, and add a line at the bottom like@reboot /path/to/script. Because this is a terminal application and not a graphical one, the paste function is Ctrl-SHIFT-V, because Ctrl-V is already taken by something else. Or you can right-click and paste from there. Also because it's a terminal app and not graphical, the mouse has (almost) no other meaning, so the cursor must be moved with the arrow keys.
(Ctrl-<something> in a terminal is a whole list of quick signals that *always* have their designated functions. That list came about before the familiar interface that we have today, so the assignments that you're used to have to go somewhere else, but that remapping only applies in a terminal.)
Nano's functions are listed at the bottom of the terminal, but the important one is Ctrl-X to exit. If you've changed something, it'll ask to save. Answer Y, and then Enter. And then the schedule is updated.
---
Or the scheduler could be your desktop manager's login settings, however the one that came with your chosen flavor of Linux does it. Each different flavor seems to have a different one of those, but this part of them all does the same thing...if you can find it. Pretty much every Linux system has cron, and it always works the same way.
If you use Ubuntu Studio like I do:
then the graphical login settings are here:
View attachment 96472
As you can see, I have one each on login and logout. They're actually in the same folder, next to each other; the login one just doesn't show the absolute path like the logout one does.
---
<string> is a placeholder for whatever you end up putting there. So if you have a profile called "Stream_1" and a scene collection called "Camera_1" ('cause that's where each of those things is stored), then to start OBS with those settings, you'd do:
obs --profile "Stream_1" --collection "Camera_1" &
The order of options doesn't matter, except for the ones that expect a <string> immediately following. Organize them however it works for you to read it, add and remove options as fits your needs, etc.
As I also said above, the&on the end makes it continue without waiting to finish. So if all 3 of your obs lines have that, then they all start and run simultaneously, and the script exits immediately, having run out of things to do. If one doesn't have the&on the end, it'll wait for that process to finish. For a graphical application, "finishing" doesn't happen until you close it.
You're probably going to give yourself some headaches to install for yourself, what already exists and works in UStudio.
Yep! Rumor has it that an early Bill Gates saw what Unix was doing with its terminal (Linux = Linus's Unix, named for Linus Torvalds, whose hobby at the time turned into what we know today), liked it, and changed just enough to avoid a lawsuit. So the basic idea is similar, but a lot of things are just messed up and more convoluted in Windoze than they have to be, coming from someone who's used both.
:-)
Don't know if it's the low-latency kernel in Ubuntu Studio specifically (regular Ubuntu doesn't have that either - it has to do with how long it takes to call on something after it's "raised its hand" for attention, which directly translates to a smooth stream with higher settings), or something to do with Ubuntu in general or Linux in general, compared to Windows, but several of my rigs have done much better on Ubuntu Studio than they did on Windoze. Same hardware, same sources, producing another of the same event.
ok, I can install Ubuntu studio that's not a problem I will go with your experience. Just as long as all that extra stuff that comes with it isn't running in the background are going to slow anything down.
The existence of a bunch of pre-installed apps makes no difference to performance. Only storage space. It doesn't run in the background. If that even remotely hurts for you, then you can't record either.
So far so good. Don't forget the shebang at the top, and to make it executable. And since you only have to type it once, you might as well include a bunch of other options if they make things easier later.
I don't. Modern devices are reliable enough that it's not really a problem for me. My working system is not backed up at all, and I just know what I like from having set up a bunch of different systems for different purposes. Only ever had one hard drive failure, and that was Windows 98. (unprovoked head crash) Never had debilitating malware at all. Long-term storage is simply two individual external drives that I manually put the same stuff on.
Because of some licensing details, you'll have to install the GPU driver yourself:
sudo apt-add-repository ppa:obsproject/obs-studio
sudo apt update
sudo apt full-upgrade -y
sudo apt autoremove -y
sudo snap refreshsudo, or have it scheduled as root (sudo crontab -e), then you don't need sudo in the script itself.OK thank you again for all the great info.
having a couple issues. see pictures. one is with my ConnectWise ScreenConnect remote client. I use this for all my clients all their servers all their workstations I can remote in at anytime very easily I've used my connect wise server for 15 years now. I've never installed it on Linux before man it's giving me a headache. And then there's an error with the video driver?
That can break things too...unless you want to completely understand the complex web of interdependencies. Otherwise things that are supposed to "just work" will break for reasons that no one can help you with. It's really not a problem to have stuff sit there unused.
See above. Wipe and reinstall fresh, DO NOT REMOVE ANYTHING, and just hit the points that I mentioned.
