Fourth Beta Release

v4.0.0beta3 -- 13 Oct 2021

Fourth beta release of Rivendell v4.x. Be sure to read the INSTALL
document, as major changes in software dependencies have occurred.

Major Changes Between v3.x and v4.x:
Qt Toolkit. Rivendell v4.x uses and is fully compatibile with major
version 5 of Qt (Qt5). See the INSTALL documents for specifics.

Date/Time Customizability. Date/Time presentation formats can now be
customized on the basis of site perferences.

MySQL Compatibility. Rivendell v4.x aims for full compatibility with
MySQL 8.0 and earlier versions in their default installation
configurations.

RDAirPlay. The rdairplay(1) has been completely overhauled, and now
supports dynamic resizeability as well as a revamped level metering
system.

RDPanel. The rdpanel(1) now supports dynamic resizing.

Many bug and regression fixes. See the 'ChangeLog' for details.

Database Update:
This version of Rivendell uses database schema version 355, and will
automatically upgrade any earlier versions. To see the current schema
version prior to upgrade, see RDAdmin->SystemInfo.

Be sure to run 'rddbmgr --modify' (as root) immediately after upgrading
to allow any necessary changes to the database schema to be applied.

Beta Release

Third beta release of Rivendell v4.x. Be sure to read the INSTALL
document, as major changes in software dependencies have occurred.

Major Changes Between v3.x and v4.x:
Qt Toolkit. Rivendell v4.x uses and is fully compatibile with major
version 5 of Qt (Qt5). See the INSTALL documents for specifics.

MySQL Compatibility. Rivendell v4.x aims for full compatibility with
MySQL 8.0 and earlier versions in their default installation
configurations.

RDAirPlay. The rdairplay(1) has been completely overhauled, and now
supports dynamic resizeability as well as a revamped level metering
system.

RDPanel. The rdpanel(1) now supports dynamic resizing.

Database Update:
This version of Rivendell uses database schema version 350, and will
automatically upgrade any earlier versions. To see the current schema
version prior to upgrade, see RDAdmin->SystemInfo.

Be sure to run 'rddbmgr --modify' (as root) immediately after upgrading
to allow any necessary changes to the database schema to be applied.

Production Release

Changes:
RDImport. Fixed a bug that could generat an erroneous
'Title already exists' error.

RDLogEdit. Fixed a bug in the voice trcker that could cause a
segfault.

RDAirPlay. Tweaked support for dark themes.

Database Update:
This version of Rivendell uses database schema version 347, and will
automatically upgrade any earlier versions. To see the current schema
version prior to upgrade, see RDAdmin->SystemInfo.

Be sure to run 'rddbmgr --modify' (as root) immediately after upgrading
to allow any necessary changes to the database schema to be applied.

Beta Release

Second beta release of Rivendell v4.x. Be sure to read the INSTALL
document, as major changes in software dependencies have occurred.

WARNING: This BETA version of Rivendell is intended for testing purposes
only. As such, it is quite likely to contain bugs, including serious ones
that could lead to LOSS OF DATA! DO NOT put it on production systems!

Major Changes Between v3.x and v4.x:
Qt Toolkit. Rivendell v4.x uses and is fully compatibile with major
version 5 of Qt (Qt5). See the INSTALL documents for specifics.

MySQL Compatibility. Rivendell v4.x aims for full compatibility with
MySQL 8.0 and earlier versions in their default installation
configurations.

Database Update:
This version of Rivendell uses database schema version 349, and will
automatically upgrade any earlier versions. To see the current schema
version prior to upgrade, see RDAdmin->SystemInfo.

Be sure to run 'rddbmgr --modify' (as root) immediately after upgrading
to allow any necessary changes to the database schema to be applied.

Production Release

Changes:
RDImport. Fixed a bug that could cause a segfault when used with the
'--fix-broken-formats' switch.

Rivendell Service. Fixed a bug that could cause resource leaks on
systems performing system maintenance.

Database Update:
This version of Rivendell uses database schema version 347, and will
automatically upgrade any earlier versions. To see the current schema
version prior to upgrade, see RDAdmin->SystemInfo.

Be sure to run 'rddbmgr --modify' (as root) immediately after upgrading
to allow any necessary changes to the database schema to be applied.

Production Release

Changes:
RDImport. Added the user's e-mail address to the set of addressees used
when the '--send-mail' switch is used.

New PyPAD Scripts. Added the following PyPAD scripts.
'pypad_ino713_tcp' - Supports Innovonics RDS/RDBS encoders via TCP.

 'pypad_nautel' - Supports Nautel 'VS' series transmitters.

Reconciliation Reports. Fixed a formatting bug in the
'RadioTraffic.com Traffic Reconciliation' report type, while retaining
the original format in a report type called
'Original RadioTraffic.com Traffic Reconciliation (DEPRECATED)'.

Various bug fixes. See the ChangeLog for details.

Database Update:
This version of Rivendell uses database schema version 347, and will
automatically upgrade any earlier versions. To see the current schema
version prior to upgrade, see RDAdmin->SystemInfo.

Be sure to run 'rddbmgr --modify' (as root) immediately after upgrading
to allow any necessary changes to the database schema to be applied.

First Beta Release

Changes:
First beta release of Rivendell v4.x. Be sure to read the INSTALL
document, as major changes in software dependencies have occurred.

Database Update:
This version of Rivendell uses database schema version 349, and will
automatically upgrade any earlier versions. To see the current schema
version prior to upgrade, see RDAdmin->SystemInfo.

Be sure to run 'rddbmgr --modify' (as root) immediately after upgrading
to allow any necessary changes to the database schema to be applied.

Production Release

Changes:
Podcasting Subsystem. Major refactoring, with explicit support of
iTunes and Superfeed DTDs added. All feed elements, including XML elements,
are now statically served rather than dynamically generated.

RDLogManager. Added control to specify explicitly how Start
Times/Lengths are derived for Inline Events (traffic, markers and
voice tracks).

Dropboxes. Added the ability to generate e-mail reports for each
attempted file import.

GVC7000 Switcher Driver. Modified the 'GVC7000 Protocol' switcher
driver to better handle stacked commands.

WebGet. Modified the WebGet service to offer audio profiles when
exporting audio rather than having the user set individual export
parameters. Added the ability to upload audio files into specified
Rivendell groups.

Audio Library. Deprecated the ability to enforce unique cart titles.

Various bugfixes. See 'ChangeLog' for details.

Database Update:
This version of Rivendell uses database schema version 346, and will
automatically upgrade any earlier versions. To see the current schema
version prior to upgrade, see RDAdmin->SystemInfo.

Be sure to run 'rddbmgr --modify' (as root) immediately after upgrading
to allow any necessary changes to the database schema to be applied.

Production Release

Changes:
As-played Reports. Added a 'Results Report'.

Various Bugfixes. See 'ChangeLog' for details.

Database Update:
This version of Rivendell uses database schema version 317, and will
automatically upgrade any earlier versions. To see the current schema
version prior to upgrade, see RDAdmin->SystemInfo.

Be sure to run 'rddbmgr --modify' (as root) immediately after upgrading
to allow any necessary changes to the database schema to be applied.

Production Release

Changes:
Edit Event dialog in rdlogmanager(1) - Cleaned up the layout of the
'Edit Event' dialog in rdlogmanager(1) to better reflect operational
flow.

Multiple Bugfixes. See 'ChangeLog' for details.

Database Update:
This version of Rivendell uses database schema version 317, and will
automatically upgrade any earlier versions. To see the current schema
version prior to upgrade, see RDAdmin->SystemInfo.

Be sure to run 'rddbmgr --modify' (as root) immediately after upgrading
to allow any necessary changes to the database schema to be applied.