Information for AppData

[wippercnmfpc]

What items should and should not be placed within this file location within Windows? In the beginning, I placed some permenant sources in this location within a new folder to prevent movement and deletions. But this has caused some issues with others and I am concerned that someone might get access and delete core functions.

Should only plugins, profiles and such be the only information that remains and the other data be placed in a directory or folder and maybe backed up to a hidden folder?

 

[Lawrence_SoCal]

Unfortunately, that really isn't an OBS question... and it depends
Is your drive NTFS or FAT, etc (if you are thinking, what?.. sorry, but like asking for help with an engine and not knowing if it is gas, diesel or hydrogen. )

Personally, I've been using WinNT since the '90s (MCSE back in the day, etc) so I'm very familiar with file and Windows OS system security. So, I put plugins where they belong, I don't allow regular user accounts to have Admin rights (for well 20 yrs), etc

So, 1 I use different user profiles/logins
for ... 'permanent' sources... I'd put in them in \Public\Documents so readable by any user profile, and any references would work across different logins. Then adjust NTFS permissions accordingly (ex make Read-Only for all/given users, editable by Admin or specific user account .. one that won't make mistakes). FAT file system ... different approach required

 

[wippercnmfpc]

Some of the scene source are used and are permanent. To prevent the location from changing and created a missing source, I didn't know whether these items should be placed in a special folder in the appdata/obsstudio location. I didn't want to cause courption issues with that folder, plugins, collections and the like. Or should I just place them in a normal folder/location and just back them up to prevent total loss.

I have some helping with our video team that have little to no real technical knowledge and fear that they might no know the importance of these files. Hiding them within the computer to limit access and accidents is what my questions really was pointing to.

RIght now I have a box that comes up when OBS Studio loads with missing source files and references. I would not want this to happen to my team should I not be there and check things out early enough to make corrections.

 

[Lawrence_SoCal]

Understood, I'd follow the approach in the later portion of my earlier post.
For me to answer further, requires knowing your Operating System, user profile approach, and NTFS security settings. My approach requires understanding the difference between User Profiles in WinNT and NOT allowing default user accounts with local admin rights

 

[wippercnmfpc]

The operating system is Windows 10 Pro. We have one user profile that is set for the booth that is password protected for the AV team to access and prevent untrained and those who are curious restrictions entering the system. The main profile is an administrator .

I have thought about tagging the information to a hidden folder where the OBS sources could index. This would keep the items out of the APPDATA area. Most of those working with the system have little to no knowledge of OBS at all. I have produced a set of Scenes and Source with several different Scene Collections for the different services that would be used during Sunday streaming.

One Scene in the Collection is for regular Sundays and the other is for Communion Sunday. They follow a different order and this eliminates to much interaction with OBS to make mistakes. I have locked the Sources but understand that changes can still be make via the menus when an item is selected.

The idea is to train those who operate OBS to just follow the scene order along with the bulletin for that service. One or two members of the team will be tasked with taking the leader's guide issued late Thursday and making the changes to OBS to have the right scriptures and the title for the sermon.

Some of our sources include timed PowerPoint slides that have been converted to VLC Video Format. The Scriptures have been produced several months in advance from the PCUSA Lectionary and all had to be produced since we do not know which would be selected for a given Sunday.

I have saved each of these for future use to reduce the need to continue to produce more and more. Each year, we will survey the collection and make sure that all are included. Any that are not included would still require creating.

I have a PTZ Optics 30X Camera attached to OBS and in the sources, I have created prompts to instruct which preset should be selected to provide the proper camera coverage during that part of our Order of Worship. It also provides for the channel of the dedicated mini sound mixer that provides the audio from the main board and audio from another source due to internal pushback running music and choir through the PA speakers due to echo. This audio is captured by another microphone system and both systems feed the mini mixer and that audio is supplied directly to the computer and OBS.

I hope his gives you an overview of what I have created and the protections I hope to place on certain parts of the programming to prevent unwanted change.

Scott

 

[Lawrence_SoCal]

I thought along the same lines.
IN the end, OBS Studio is written presuming a trained/knowledgeable single user, essentially. It does not have a role-based access control config option. So, an OBS Studio operator can absolutely screw up a setup. And I'm not aware of a way to prevent such (as even I've made mistakes. Training is best defense, but with HoW volunteers, one can't always expect that much). I notice last week someone (a Mac user) accidentally dragged 'n dropped a Scene into a different place in the order. [the humor of watching a Mac user try and use a 2-botton or more mouse]
So.. what did I do? I backed up the OBS Settings (and I use Adv Scene Switcher, which has its own settings export option). That way, if anyone messes up, I can have them exit OBS Studio, run script to replace setup files, and restart OBS Studio. problem solved.
As for source files, I'd simply adjust NTFS permissions to allow OBS Studio/Regular User Profile to read source, and require Admin profile/rights to edit file. Now, no mistaken deletions, moves, etc. I'd create a User Profile folder, either under /userA(OBS)/Documents, or in our case I placed the media source files under /Public/Documents/Livestream, [I definitely would NOT place media sources under \AppData] and adjusted permissions for the Folder, with files inheriting NFTS permissions.

We use PowerPoint slide show to display service bulletin. To make it easier/quicker, and enable last-minute edits (often required), we leave the content in PPTx. I then use a windowed slide show (Portrait orientation) and an OBS Window Capture. With a small portion of slide show window visible, all we have to do is put mouse over slide show (don't have to make window active) and scroll wheel to advance slide. Typical slide desk is a little over 30 slides (liturgical service with words to most of service, music, copyright notice, etc) We don't always need full page with, so I use a another OBS Scene (I could also have used 3rd party plugin option, but I prefer KISS) to use more video camera image width (and less of PPTx window).
Our workflow is that the person creates the regular printed service bulletin (which is handed out to every in-person attendees), then copies the same content from the Word booklet document (I think it is) into PowerPoint. We then make final tweaks to PPTx slide an hour or so before service (formatting, alignment, hymn music image sizing and placement, etc). One thing I've contemplated, but not done due to KISS, is to configure OBS Studio with websockets, and use macros in the PPTX slide deck to send commands (via websocket listening service) to OBS Studio to change scenes (or ?? could get sophisticated including PTZ presets).. there is a thread on PPT macros commands to OBS). Such a change trade training and sophistication in OBS Studio operator, for much greater attention to detail in the creation/updates/edits to the PPT slide deck (which our person, already past retirement age, isn't really up for).
The challenge is that I could make a PPTx slide deck that fully automates OBS Studio and PTZ camera actions. But what happens when the inevitable off-script moment happens. OBS Studio operator has to be able to adjust accordingly, requiring adequate knowledge/training, OBS Studio setup to allow it, etc. so for the time being, our setup requires fairly well-trained OBS operators, and little effort into slide deck, sound system setup, etc

As for audio, we have a Presonus AR12 USB mixer. At the moment, I'm still using an analog sub-mix audio output for OBS livestream (looking to use USB interface, but gets tricky with Windows OS audio sub-system and OBS Studio). By using mixer's sub-mix capability, I can capture choir, pipe organ, piano, bell choir, etc without amplifying any of those mics for in-house speakers.