I did not remove anything yet, it is a clean install.
Can I stream 3 AXIS IP Cameras to 3 Live Streams on YouTube at the same time.
- Thread starter John Zapf
- Start date
Well... Okay.
*Something* is definitely broken. Never had it do that for me. Did you update as soon as it ran on its own for the first time? I always do that, because the image that you download really *can't* be up to date. Run the commands to do that, reboot, and try again.
OK I did a fresh install the driver installed that time and said reboot and I rebooted and now it won't boot back up it's stuck here.
I've been just trying to do one thing since 2:00. It's 518 now. This is how linux always is with me. You gotta fight with everything I could have installed windows and had all this done in about 10 minutes and even had the remote software going. I don't know how to get the remote software in there now it's still not working either. To me windows is so easy and so stable and I can uninstall anything reinstall anything and it always just works but I do want the low overhead and speed of Linux is just always a struggle.
I've been just trying to do one thing since 2:00. It's 518 now. This is how linux always is with me. You gotta fight with everything I could have installed windows and had all this done in about 10 minutes and even had the remote software going. I don't know how to get the remote software in there now it's still not working either. To me windows is so easy and so stable and I can uninstall anything reinstall anything and it always just works but I do want the low overhead and speed of Linux is just always a struggle.
Attachments
From most of this thread, I gather that you can't help messing with it, and you forget easily. I still think you're doing this to yourself.
If you take all of the defaults on a fresh install and don't mess with it, and update as the first thing you do, then it generally does "just work". It's when you customize it prematurely or get too aggressive with the management, that it becomes hell. It'll happily let you do that, on the assumption that you know it better than it knows itself, and you know all of exactly what you're doing.
I'm not customizing anything. once i get it to work and the video driver installed and workingI just need to set the static IP and install my screen connect software so I can remote into it. ( ScreenConnect.ClientSetup.sh ) and honestly, I don't know how to get that file to run right? Like I say I've been a windows system engineer for 32 years there's nothing I can't do with the Windows Server or network or firewall or anything. But when it comes to linux it's like so archaic to me I can't even double click on a file and install something
I grew up on Windows too. But I'm not *that* old yet. It's definitely different under the hood, but no better or worse overall. Someone who grew up on Linux and made a career out of maintaining it exclusively, would probably have the same trouble with Windows as you're having here. Basic Linux things "just don't work" on Windows, and they can't understand why.
Maybe for this rig, you do it the way you know, AND get a machine that you can play with Linux on. Break it, ask for help, fix it, etc.
For general help with Ubuntu Linux and its derivatives, like Ubuntu Studio:
OK for the update. I got the Linux all set up and working fine.
The only thing I couldn't get to work right was my remote desktop software I use the screen connect. So you're used to using this flavor of Linux what's the best way to allow remote desktop to this box? I googled it and there's twenty different ways.
So I also installed windows on the box and uh that all set up and I did apples to apples testing on both versions so here's my results.
I had 3 streams running in OBD all were using hardware:
Ubuntu Studio
CPU 6.9 - 7.3 %
GPU 9-17 %
Windows 11
CPU 2.2 - 3.4 %
GPU 17 - 27 %
The only thing I couldn't get to work right was my remote desktop software I use the screen connect. So you're used to using this flavor of Linux what's the best way to allow remote desktop to this box? I googled it and there's twenty different ways.
So I also installed windows on the box and uh that all set up and I did apples to apples testing on both versions so here's my results.
I had 3 streams running in OBD all were using hardware:
Ubuntu Studio
CPU 6.9 - 7.3 %
GPU 9-17 %
Windows 11
CPU 2.2 - 3.4 %
GPU 17 - 27 %
this looks like the easiest way for RDP?
OK so where I'm at. I just did a fresh install of Ubuntu studio all the updates, the video driver, static IP, and the updates to obs studio that you sent. Everything went smooth as silk. So the install is perfect.
The only things I need help with now before I can start moving the streams and using this is:
1. The best way to do RDP, windows remote desktop, to the Ubuntu Studio box.
2. Could you use these names and wright the best .sh script for me to use to start the 3 different sessions?
obs --profile "Olive" --collection "Olive Cam" &
obs --profile "Fountain" --collection "Fountain Cam" &
obs --profile "Feeder" --collection "Feeder Cam" &
And 3rd is there a way to open the konsole window as root, sudo -i?
The only things I need help with now before I can start moving the streams and using this is:
1. The best way to do RDP, windows remote desktop, to the Ubuntu Studio box.
2. Could you use these names and wright the best .sh script for me to use to start the 3 different sessions?
obs --profile "Olive" --collection "Olive Cam" &
obs --profile "Fountain" --collection "Fountain Cam" &
obs --profile "Feeder" --collection "Feeder Cam" &
And 3rd is there a way to open the konsole window as root, sudo -i?
Woohoo!
Yeah, there's a bajillion ways to do almost everything. Most of them work, as long as you actually understand the one that you chose and what quirks it has. Depending on what you're doing, the same quirk could either be a must-have feature or a deal-killing bug, or anything in between.
See this question, for example, that I posted yesterday:
x11vnc causes KDE Plasma to reset when the screen is off
When the screen is on, it works perfectly. When the screen is off - via the timeout that I set in the power settings, or manually - the VNC client appears to no longer receive updates. When I wiggl...
askubuntu.com
I'd call that far enough down in the noise to be practically equal.
Copy/paste:
Bash:
#!/bin/bash
obs --profile "Olive" --collection "Olive Cam" &
obs --profile "Fountain" --collection "Fountain Cam" &
obs --profile "Feeder" --collection "Feeder Cam" &Running things as admin as a matter of course, is not something you do in Linux. Windows needs that to make some permissions work, with no real way around that, but Linux has the detailed permission structure to *always* have a way around it. (you might need some googling and forums to find that way, but there's always a way)
So you don't run things as root. Ever. Except for very specific things that change how the system itself works, like updates, and for things that manage system resources. Those things, specifically, run with root permissions, and nothing else does. Not even the things that talk to them and use what they do, but otherwise don't need it. In the Linux mindset, running too many things as root is asking to get hacked.
So, getting root permissions is intentionally an extra step, just to keep it in your mind that this is something special that you don't normally do.
sudo in front of everything that actually needs it, or sudo -s to start a root session in that terminal. exit to close that root session and go back to the normal user, then exit again to close the terminal itself.I hardly ever use
sudo -s though. Had to look it up even, just to finish this answer. Just put sudo in front of everything that needs it in the regular session, and nothing else.OK so yes the RDP is very flaky on a lot of them. I tried a couple and it definitely has its limitations. So because of that I'm going to put windows on it that way I can have it listed in my screen connect server and then I can do everything from one place anywhere in the world.
And the "headless "computer so it's called without the monitor is an issue also and I just ordered this it seems to be an easy fix for that. https://www.amazon.com/gp/product/B09GKB1R9D/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
but I would like to say that that version of Ubuntu, ubuntu studio, is really nice. I like that a lot. I like the look and the feel of it and I tried for a couple days to make it work and it came down to the lack RDP. I have lots of monitors and I have KVM'S and all kinds of things, but I really don't wanna go down that road it's not something that I'm going to have to get into very often--I hope.
And the "headless "computer so it's called without the monitor is an issue also and I just ordered this it seems to be an easy fix for that. https://www.amazon.com/gp/product/B09GKB1R9D/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
but I would like to say that that version of Ubuntu, ubuntu studio, is really nice. I like that a lot. I like the look and the feel of it and I tried for a couple days to make it work and it came down to the lack RDP. I have lots of monitors and I have KVM'S and all kinds of things, but I really don't wanna go down that road it's not something that I'm going to have to get into very often--I hope.
Oh, I'm sure there's a way to make both of those work too, without buying the easy $5 plug. I'm actually surprised that the display doesn't already. I'd think it would at least keep a *logical* desktop, if it didn't detect anything physical, which would be enough to VNC or RDP into.
Of course, you need a way to see it anyway, and see that it does, and there's probably *someone* that says you should have tried the one that *they* use, because it does exactly what you want, perfectly. There often is, if you ask in the right place, give them the right details, and wait for them to come back from vacation to see it.
:-)
The RDP software that I use. Connectwise/Screenconnect, works really well. You can cut and paste from it you can drag and drop files back and forth so it's really handy.
And yes, there is some code that is able to do what that $5 dongle does. But I would rather just be able to plug the dongle in and be done with it.
I have a lot on my plate with work kids and my channel seems to be taking a lot of my time also, so sometimes simpler is better.
And yes, there is some code that is able to do what that $5 dongle does. But I would rather just be able to plug the dongle in and be done with it.
I have a lot on my plate with work kids and my channel seems to be taking a lot of my time also, so sometimes simpler is better.
So does most other things. My VNC connection can do all of that, even with different software on each end. x11vnc for the server on Ubuntu Studio and RealVNC for the client on a Raspberry Pi, for just one present example. Or RealVNC for the server on a different RPi and KRDC for the client on UStudio, for another one. A previous connection used UltraVNC as the server on Windows and Remmina as the client on Lubuntu (resource-light version of Ubuntu). Mix and match all you want: as long as they all use the same standard, they work. I have a VNC client on my phone too; and it also works with everything else...
If you use proprietary stuff, you're stuck.
That was supposed to be a joke. It's hard to beat $5. :-)
So can you remote to x11 (on ubuntu studio) with the default windows RDP or what do you need to use?
I see x11 supports headless connections.
And once your remoted in do you get the exact ubuntu screen or do you get that screen with the mouse on it?.
The windows remote software use you can see the exact screen you can actually see it doing the pre boot and shutting down almost everything almost a full boot cycle and it comes right back up in the remote software stays on the whole time.
My screen connect is supposed to work with Linux and I had it running one time and I don't remember what I did but I tried for probably three more hours to get it running on Linux again and it never ran so I don't know what the problem is their support for Linux is dying off and I couldn't find any how to get it to work again on Linux I don't know what I installed or what I did the first time I installed it and it worked but it needs something I think it has something to do with Java I don't know.
I see x11 supports headless connections.
And once your remoted in do you get the exact ubuntu screen or do you get that screen with the mouse on it?.
The windows remote software use you can see the exact screen you can actually see it doing the pre boot and shutting down almost everything almost a full boot cycle and it comes right back up in the remote software stays on the whole time.
My screen connect is supposed to work with Linux and I had it running one time and I don't remember what I did but I tried for probably three more hours to get it running on Linux again and it never ran so I don't know what the problem is their support for Linux is dying off and I couldn't find any how to get it to work again on Linux I don't know what I installed or what I did the first time I installed it and it worked but it needs something I think it has something to do with Java I don't know.
Attachments
Last edited:
This is what I did to install and it installs but wont run. https://blog.brettstudios.com/?p=34
I've never used Windows RDP. Didn't have a need to when it first came out with a big splash, then I forgot about it, then someone showed me VNC. That "just works" everywhere, and so I've been there ever since.
Ah, yes! I remember now. My first attempt at VNC on Linux used a server (forgot which one) that creates its own virtual desktop by default, when I really wanted the physical one. For you, I think that virtual desktop is exactly what you want!
After some more googling, I did get that same server to connect to the physical one instead, and then that worked too.
For the virtual desktop, it's what you get after a cold boot, simply because you haven't done anything with it since the server started. For the physical one, it's whatever's on-screen at the time. The mouse pointer, I believe, is not part of the image, but a glyph/sprite and a set of coordinates. So the client can have an option to show or hide it, and the pointer still changes based on what the server is doing.
Physical and virtual desktops are in the same list: :0, :1, :2, etc. Linux is a true multi-user system, somewhat like the old single-mainframe-and-many-terminal idea, and it even has several layers of that idea. If you end up playing multiple users at one level or another, you might wonder why something else you did doesn't seem to have an effect. For casual use, it's hard to get into that situation, but remoting in is one way to do it, unless you make sure that it really *is* the same user at all levels.
That depends on where in the process the server is started and stopped. It's just another app in that sense. While it's running, you get whatever's on the screen, physical or virtual.
My present system has it starting 10 seconds after login, which doesn't help at all if you need a password to log in. But since I'm the only user here and I directly control physical access, I have it log in automatically. There are also lots of questions and answers about starting it early enough to show and use the login prompt. You can google those as well as I can.
A lot of companies seem to not take Linux seriously. I don't use them, even if they do make something else that *exactly* fits another project in all of its detail. There's always another way to make a given *concept* work, and I'm not married to any of them. If something I've standardized on turns out to have a hole in it, I'll seriously consider changing that standard, which effectively means setting up new rigs differently, and I'll eventually change over as the old rigs retire.
There are several big names on my blacklist now, because they refuse to support Linux...which really means that they refuse to follow existing open standards, because Linux does support almost all of those, either natively or with apps that are easy to get and "just work". If they have a Linux driver that installs using a *normal* process (see the next section), I'll accept that too.
That is NOT a normal way to install stuff on Linux!
apt --fix-broken is NOT a normal thing to have to do!Looks to me like the same "don't care, just force it to work" mindset that a lot of shadier Windows stuff has. I would not be surprised at all if a security patch broke that site's process.
On Debian Linux - which Ubuntu and its derivatives are based on - the preferred way to install stuff is
sudo apt install <package-name>. That goes to the repositories that the apt package manager is already set up for, downloads everything from there, including dependencies, and sets it all up correctly. If that set of repos doesn't have what you're looking for, you can add one that does, like for the current version of OBS, for example:sudo apt-add-repository ppa:obsproject/obs-studioWhen you
sudo apt update && sudo apt upgrade, it looks at those same repos for a newer version of each package, then downloads and installs them the same way, over top of the old ones.There are a few other "okay" ways to install things, like downloading an orphaned package file directly, and using the package manager to read and install it, or a set of source code that uses the already-installed build process. (I have a capture card in one of my rigs, that comes with a source-code driver, and a script to build and install it) But breaking things and calling it "normal", is NOT AT ALL NORMAL!
Last edited: