bluray | Automatic Blu-ray Disk Upload Toolkit | YAML Processing library

edit: actually, this seems more reliable. So far any file that mediainfo can read, this also works with.

You can use seekTo function to start the video on a specific time.

WORKING DEMO

So what happened is that the library in Debian providing support for live555 was removed in February of this year, this affects all downstream distros including but not limited to RPi OS and Ubuntu:

https://askubuntu.com/a/1363113

The 2 active versions were 2020.01.19-1 and 2018.11.26-1.1, Live555 has since added GPL license headers to the offending files, however the RFC issue remains.

Now you may be tempted to just download the latest Live555 source code and compile it... it does not work. There have been changes to function names and structures referenced by VLC, and as such VLC will not compile against the source. You need to get an older version, I specifically used this one, which is a tweaked snapshot from 2020 prior to the modifications that prevent VLC compilation:

https://github.com/rgaufman/live555

The configuration you want is ./genMakefiles linux-with-shared-libraries, I do not know if it is required but since my system is x86-64-bit I added -m64 to the compiler options first

After compilation and install, I went on to compile VLC, adding '--enable-live555' and '--with-live555-tree=extras/live555-master' after placing the root Live555 folder in the VLC extras folder, however VLC failed to compile, it turns out the Live555's make install does not copy all the header files needed to where VLC is looking. They were dropped as 4 subfolders into /usr/local/include/, and the actual libs into /usr/local/lib/. Adding the correct CXX/CPP flags will make it look where they were put, however I put them all in a single folder and used 1 flag.

I also had to '--disable-mod' to work around a dependency version issue that I had no interest in fixing, since I do not use modplug or any mod files.

50 minutes later... VLC successfully compiled! However it was expecting the libraries for Live555 to be in /usr/lib/ not /usr/local/lib/, since it took so long to compile I was just fine with linking or copying the libraries into the expected folder, and after that VLC works with RTSP when linked to the new file. Or you can choose to maintain the original VLC and run the new file directly if you need to load the camera feeds.

@CaiusJard I tried it with no luck data field and meta field still Null

You must have done something different to me then:

I took your json and saved it into a file called some.json and set it to copy to the output directory (so i can load it easily). I wrote a line of code that loads it

I went to quicktype.io as advised in the comments and pasted your json in there, it gave me some nice C# classes and a comment on how to use it; I literally just pasted this onto the end of my Program.cs

I added the using and the line of code in the comment to my program.

I didn't have Newtonsoft installed. The comment says to install newtonsoft. The simplest way to do this is scroll to the bottom and point to any of the errors under the class names from newtonsoft; it's so popular that Visual studio knows thenames of its classes and will offer to install for you as a "click the lightbulb for help fixing this error":

After installing I put a breakpoint on the code and ran it. I stepped over the line that loads the json and now you can see in the Locals window at the bottom someThing truly is populated with data, including the Data and Meta

All done, with just 3 lines of code, and only one of them I had to write - bonus! :D

Putting @Samwise's comment together with your code:

Ah, okay I found the solution. Looks like there was an error with some of the parameters. Here's a link to the documentation. Updated the data parameter of the post request to just include the file_id.

Note: The following assumes you're using GNU find, which since you mention Linux, is a safe bet.

The default regular expression syntax does not understand \d (Instead you'd use [0-9] or [[:digit:]]). Alternation is \|. I don't think it supports repetition ranges; they're not documented. POSIX Basic Regular Expression syntax also doesn't understand \d, or alternation (though some GNU implementations do as an extension using \|), and requires many other things like groups and repetition ranges to be escaped. And none of the supported flavors supports non-capturing grouping ((?:...)).

Since your alternating group tests for either two or three digits, it can be turned into a single range when using one of the RE flavors that supports them.

So, something like:

let evaluates arithmetic expressions. When you want to concatenate strings, you don't need arithmetic expressions, so drop the let.