Custom Query (13624 matches)

Utilize Schedules Direct metadata if grabber makes it available

Schedules Direct provides some additional metadata that at least one upstream XMLTV grabber now optionally makes available.  Use that metadata if it is provided by the grabber (typically the grabber will need to be told to provide the additional information via a grabber --configure).

In particular, with this patch, the original air date and a new episode flag is available and can be useful to better schedule recordings.

The (real soon now) next XMLTV release will include the new grabber, and one can obtain the upstream master code now.

If the additional metadata information is not available (or not configured in the grabber to be made available) the results are the same as today.

FWIW, I have been using this patch (and the upstream grabber updates) for a couple of months now.

Patch will be attached.

​https://github.com/MythTV/mythtv/pull/200

The zoneminder database includes a column named function, which is a reserved word in mysql v8.x, so the SQl statements needed to be updated. The shared memory data structure for zoneminder 1.34.x also changed and had not been added to zmserver code. The code was none functional because of these errors. With correction the code works again.

Initial support for enabling the building of MythTV with LTO.

LTO may be (or may not be, your experience will vary) beneficial to systems which are on the low end of performance.

While FFmpeg itself has support for LTO builds in the latest version(s) using the --enable-lto configure option, the MythTV build process did not support the necessary options and code requirements.

These patches are intended to get the compile to properly work if one wishes to test a LTO build, although I have been running a LTO build on my "production" system. It seems to operationally work for my use cases.

The patches are provided in smaller sections so that a developer can more easily review them.

The first set of four patches are to address the requirement for an LTO build to have consistent definitions of all names and structures for a compilation unit.  The next set of two patches (also required for the consistent definitions) remove the local videodev2.h include, as the original requirement was for an older kernel which is no longer supported by the project (2.6.something).  The last patch updates configure to properly pass along the necessary options to QMAKE and FFmpeg that can be set during configure.

Note: The resulting set has been compile tested on Fedora, EL, Debian and FreeBSD 11/12 using a standard configure to verify nothing breaks with these patches on those platforms.

For individual LTO testing purposes, and depending on whether your disto has changed the default ar/ranlib/nm commands to be the gcc enabled variants, you make need explicitly specify those in your configure, as in:

   make distclean
   ./configure --cc=gcc --cxx=g++ --enable-lto --ar=gcc-ar --ranlib=gcc-ranlib --nm="gcc-nm -g"
   make

or for the equivalent for clang of the form (alternative is to use gold rather than lld, but the gold linker seems to be mostly dead upstream, so we use the llvm linker):

   make distclean
   ./configure --cc=clang --cxx=clang --enable-lto --ar=llvm-ar --ranlib=llvm-ranlib --nm="llvm-nm -g" --extra-ldflags="-fuse-ld=lld"
   make

Note: lld creates 8 byte build-ids by default, and some post processing/debugging utilities were/are known to have challenges with those build-ids, so you may need to include -Wl,--build-id=sha1 in the extra-ldflags.

Note:  If you are using --extra-cflags, you may need to add --extra-ldflags (with equivalent flags) to avoid certain flag merging artifacts during the link stage compilation as the linker will use the flags in the first object files, which might not be ideal for your use case.

Patches will be attached.