MetroEast

The emedia1 subdomain is working. I'm with my specialist now, we're discovering that Rocky 9.5 is not supported by the storage packages and we're rebuilding a Rocky 9 instance at 9.3 which is commpatible. I'll be working with them to ensure we have a working container and work to migrating our emedia1 instance via snapshots and the CLI scripts. We're closed through Jan 2. I'll report back on our status, and we can move forward with further dev and tests.

Apparently the issues were local DNS related... ssh and the site "just worked" today when I went to try them.

Oh, ok, sounds good

I was in the call if it was required, but if not we can take it back after Jan 2 then.

Sorry Cristobal, I disconnected early. There's not much for us to do until after the new Rocky build is completed later today or tomorrow, and I'm on holiday for a bit. Thank you for being available. I've been stretched pretty thin, and haven't been able to coordinate the server business as effectively as I'd like.

Actually, I'm still in the Zoom... so that's weird. I'm disconnecting now.

No prob! Happy holidays and we will talk on January!

❄️☃️

I'm about half way done with the rebuild on Rocky 9.3. One thing that surprised me is a prompt during the execution of the script to setup the instance, which asked me to select the image. There were 3 options, and I chose the last item noted as "docker.io/entermediadb/entermedia10:latest" which seemed the most likely choice. This seemed to go as expected, but ended with the following notice: Error: statfs /media/emsites/emworkspace/190/tmp: no such file or directory

Hi David, we can go over this coming thursday!

Hey David, sorry I lost power at the end of our call. I see the site is responding ok in the browser now.. I think last step is to update to newest version, for that you will need to update the update.sh script to run entermediadb-update-em11.sh instead of the 10' version. And that's it. If the mounts are right I think next week we can bring an Snapshot and start again testing the Elemental process.

David, the missing link was we need to create a Hotfolder that will make the input file path correct. Now we are sending the right <uri>: /mnt/Meld/DAM/originals/Programs/2024/Started Record/Stairway To Gilligan's Island - Led Zeppelin - Classic TV theme-K4MKQMTHplI.mp4 I see it in the Elemental portal, now you need to be sure that Tool can also read that path the same way "/mnt/Meld/DAM/originals" Anyways we can take a look on it next week.

Thanks for the update! I'm surfing a municipal studio install today and tomorrow. I need to push this to next week, but I can work on sorting the above in the next few days.

All right, sounds good to me, let talk next week

I believe I've resolved permissions. I'll want to add another preset for the elemental, to generate the "broadcast ready" file format where we want to call a post processor script on the elemental to move the file to the automation system.

The conversion succeeds, but the conversions status is still sowing "processing" ... One thing I'm unclear on is how we might include a unique formatted file name for the output file we want to push to automation.

hello, it is very easy to set the output filename in the Preset Config in our side, what format you want?

Lost track of the morning... apparently snow/winter closure things do that to me. The output file we need for broadcast is currently based on 2 fields: Program number and episode number. When not an episode (null value) we want only the program number. Currently the format is 5 character, zero padded integer, for the program number. When episode is not null, a delimiter character is next, an underscore "_" Then a 4 digit, zero padded, integer for the episode number. My next item is working with our playback folks to try out the workflow and note anything we need to address. I'm not sure that will happen before the end of the month. The winter closure is upsetting the schedule a bit.

The file formatting could be handled elsewhere in the chain of handoff. Right now, that starts with our operator renaming any source files they receive to the formatted program/episode number. The file is placed in a watched folder, the elemental has a profile which defines the output file format, and copies the original file into an archive directory. The output file is copied by a post execution script on the elemental, to the file share of the automation system's import watch folder. The automation, makes a copy of that "broadcast" file into a similar archive folder. original and broadcast files are copied to LTO, by the storage system policy.

I'm unsure about how much I want to change the way archiving works. My main concern is the files are truncated to zero bytes after being copied to LTO. I'd like to also back up the entire DAM directory on the storage system. We could call a post execution script, similar to our current config... which could handle file naming and copying, presuming the program and episode numbers are somehow included in the JSON that the script receives from the Elemental processor.