The server flow starts with a linux lite computer and a Linux lite computer is running OBS software and VLC software, In addition it's using K alarm for its triggering on a clock and also VLC has a Lou extension that is designed to be the as run log. What else is going on on the server is it also has a separate one gigabyte video drive that is cloned to the workstation, the workstation has a 1 gigabyte video drive also and that's all they do and the workstation one is cloned to the Linux one so all the work is done on the workstation as far as generating the log and then it's cloned over on the server, there's seven playlists labeled one through 7, and those are the seven days and those are each playlist is 24 hours, Now K alarm right before midnight triggers a script over there that overwrites the next number, it keeps consecutive count of the numbers one through 7, and it overrides nightly the next number so let's say yesterday was two it will kick script that was overwrite 2 as 3 and it's overriding this on a playlist called 000, So the 000 playlist  is always played, but it's changing nightly, and so to clear VLC out also I do a kill command, with K alarm so that it starts the playlist after it's created and then it dumps all the playlists out of it that occurs at midnight

On the workstation side that's where all the ingesting and program acquisition is done and there's a separate drive multiple drives over there but there's a separate drive is a store room and when the file's ready then it's transferred to the video drive on the work station that in turn after one minute delay will be cloned over to the video server. Now the playlist builder which is below is A relative playlist Builder, so it doesn't really care what the drive letters are what it does is create a text file M 3U playlist file and that file then is also transferred to the video server so you can create a playlist on the work station, and since it's using relative file paths and as long as you keep it on the top of the video folder or the video drive, then it will work on either computer, so all the playlists are being built on the workstation and then they're just synced over. So  over on the video server side the main thing to do is reboot every few days, and to you know take manual control and so on and keep it going over there. But the majority of the work is done on the workstation side. So far it's been working fairly well You can only get 7 days ahead but if you don't keep changing it you'll just replay the old one list as its a 7 day rotation. But I do keep changing it.

Station Christ Video Channel software - Playlist & Logger

Software: the main version BB or X9 is REALITIVE FILE PATH ONLY for lists generated, absolute file path X10 coming soon if you see it, its done - Windows stand alone excutable no install needed

STATION LOGGER for VLC player

The Station Logger (by Vistronic) is a lightweight Lua extension designed to turn VLC into a professional broadcast monitoring tool by automatically generating a continuous "As-Air" log. Once installed, it silently tracks every track or clip played in VLC, timestamping each entry into a simple, permanent text file. This provides a reliable, chronological record for licensing compliance, advertiser verification, or internal archiving without requiring any manual input from the operator. It’s the essential set-it-and-forget-it solution for maintaining an accurate station history. As the logger requires the user to hit view and start it I wrote a script for Linux to do this AUTO as I change my playlists at midnight this is a separate file you will find in there. The same could be done for windows but my sever is Linux lite.

Video server. The video server is just a computer I built with newegg parts and a few Amazon parts but mainly I buy the current AMD motherboard and I use the AMD processor that doesn't have the built in graphics because I'm gonna rerun in a separate graphic card so that's gonna be irrelevant And let's see I put in I think 32 gig of RAM on that one and then I add the current NVIDIA card that I can afford There's lots of them out there but whatever one you can afford I think I spent almost 200 on a card maybe a little bit less than that And so then you add your video drives M2 drives you have your OS drive and then a separate video drive so I have 500 gigabyte OS drive and then I have a 1 terabyte gigabyte drive and so when you have that all set then I went through Windows 10 and it just didn't it was just not They had too many ghost things going on inside of it so I went to Linux Light and that has been working fine after setup and it takes a long time to set up that's the only problem but after after you get all the bugs out and the setup done it works fine.

 Mainly the problems were associated with mysterious glitches in OBS because when you're running VLC and OBS and then you see these mysterious glitches and pauses and then you have to track it down it could be the Nevada card doing power saving ramping and other I found that the best and easiest way to do it is to just set up a separate monitor use it full screen and use whatever current version of screen capture you can get away with in Linux the reason being is I wanted to show the metadata coming out of the VLC player so if you just capture the stream itself from VLC you won't see the metadata but if you capture the whole monitor then you get the metadata and I use the metadata display for arbitration and showing the show title and all that stuff so I was wanting that shown and that's how you get it to be shown So in general you have two monitors one is the on air monitor the screen capture monitor and then the other one is where you you know operate the OS and the various software So all the time what's running is OBS streaming and then you have VLC as the player It's pretty solid as long as you play MPEG 4 exclusively because when you mix 4 mats it will play it VLC will play anything But then your introducing yourself to mysterious glitches coming out of OBS the encoder So it's not just the player the encoder wants the constant signal .

So what I'm doing is most everything is captured at 1080 Yeah including an OBS everything is captured at 1080 but then the output is 720p at i'm running 3.9 KBS right now for for a variety of reasons It's just more more robust stream with less less glitches And so yeah I ran 1080 and I can run it and I can run higher bit rates But I'm looking for the sweet spot where the viewer on either the web stream or on Roku doesn't have any glitches or I'm on fiber here but even if I push it too high then the slightest glitch in the fiber here also causes a glitch and then you got to waste days and days tracking all this stuff down So running at about three I think I'm running at 3.9 right now has been working very well on this server The only other problems is it just runs better if you reboot it once in awhile I don't know what kind of buffering it's doing in so I just start the stream then on the workstation and then I just stop the stream there and started on the workstation so it's AI have a backup I can switch to