Skybuck
New Member
I was live streaming on youtuve via obs studio.
I encountered a very strange mouse icon which I wanted to report on textpad forum, I had to login with my password, for that reason I disabled the display capture and then I completely forget to turn it back on !
After which I made some batch files and I think maybe other people could have learned from what goes wrong with batch files, it's unfortunate that it did not capture this on video.
It would be nice if OBS Studio would issue a warning after X minutes. Default could be 15 minutes, could also be modified by the user, so that in-case the user forgets to re-enable it, OBS Studio warns about it !
I already had to do many display capture disablements earlier in the live stream for mobile phone pin access, I was streaming already for 4 hours, I guess fatigue kinda got to me and I forgot to re-anble it after the textpad forum visitation. It's kinda logical, because my mind drift off into the textpad forum post I had to make and thus I totally forgot about the display capture being off.
Another idea could be to somehow detect password fields, and when a password field is being displayed the live stream goes black, however I still need to retrieve the password from one of my local files, so this would not be sufficient unfortunately, unless I would use some kind of application which stores account names and passwords and communicates with obs studio that the user is about to do some kind of account login and login information should be blacked out, blurring would not be sufficient because anti-blur methods/algorithms exist.
I do run into this issue frequently where I have to login to something while live streaming, so it's a bit of a risk and a re-occuring issue.
For this I forgot to re-enable it.
However I also recently had a mic failure, where the mic was not properly recording my voice, but that was a different issue, I don't know what caused it, but re-selecting the logitech blue yeti microphone seemed to fix it. Another idea for this could be to detect if the mic is working during the first few minutes if not also issue a warning that no audio is being perceived from the microphone, that would also be a very cool feature !.
(This is my first post on this forum. I posted it and then I saw a tag capability, I would like to try and add a tag, I tried to click edit, but it won't let me add a tag after posting it ? Maybe something to look into... )
I encountered a very strange mouse icon which I wanted to report on textpad forum, I had to login with my password, for that reason I disabled the display capture and then I completely forget to turn it back on !
After which I made some batch files and I think maybe other people could have learned from what goes wrong with batch files, it's unfortunate that it did not capture this on video.
It would be nice if OBS Studio would issue a warning after X minutes. Default could be 15 minutes, could also be modified by the user, so that in-case the user forgets to re-enable it, OBS Studio warns about it !
I already had to do many display capture disablements earlier in the live stream for mobile phone pin access, I was streaming already for 4 hours, I guess fatigue kinda got to me and I forgot to re-anble it after the textpad forum visitation. It's kinda logical, because my mind drift off into the textpad forum post I had to make and thus I totally forgot about the display capture being off.
Another idea could be to somehow detect password fields, and when a password field is being displayed the live stream goes black, however I still need to retrieve the password from one of my local files, so this would not be sufficient unfortunately, unless I would use some kind of application which stores account names and passwords and communicates with obs studio that the user is about to do some kind of account login and login information should be blacked out, blurring would not be sufficient because anti-blur methods/algorithms exist.
I do run into this issue frequently where I have to login to something while live streaming, so it's a bit of a risk and a re-occuring issue.
For this I forgot to re-enable it.
However I also recently had a mic failure, where the mic was not properly recording my voice, but that was a different issue, I don't know what caused it, but re-selecting the logitech blue yeti microphone seemed to fix it. Another idea for this could be to detect if the mic is working during the first few minutes if not also issue a warning that no audio is being perceived from the microphone, that would also be a very cool feature !.
(This is my first post on this forum. I posted it and then I saw a tag capability, I would like to try and add a tag, I tried to click edit, but it won't let me add a tag after posting it ? Maybe something to look into... )