[RDD] Rivendell v4.0.2

[Fred Gleason]

On behalf of the entire Rivendell development team, I'm pleased to announce the 
availability of the next production release of Rivendell, 4.0.2. Rivendell is a 
full-featured radio automation system targeted for use in professional 
broadcast and media environments. It is available under the GNU General Public 
License version 2.

From the 'NEWS' file:
*** snip snip ***
Changes:
   RDCatch Subsystem. Fixed a bug that would cause subsequent catch events
   to fail after processing a 'Start Record Deck' ['RS'] RML.

   Voicetracker. Streamlined the workflow when inserting new track markers.

Database Update:
   This version of Rivendell uses database schema version 370, and will
   automatically upgrade any earlier versions. To see the current schema
   version prior to upgrade, do 'sudo rddbmgr'.

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

*** snip snip ***

Details and source code are available at 
https://github.com/ElvishArtisan/rivendell/releases 
.


Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Rivendell v3.6.7

[Fred Gleason]

On behalf of the entire Rivendell development team, I'm pleased to announce the 
availability of the next production release of Rivendell, 3.6.7. Rivendell is a 
full-featured radio automation system targeted for use in professional 
broadcast environments. It is available under the GNU General Public License 
version 2.

From the 'NEWS' file:
*** snip snip ***
Changes:
   Podcasting Subsystem. Fixed a bug that caused superfeeds to fail
   validation against the 'direct' name space.

   RDCatch. Fixed a bug in rdcatchd(8) that caused record events to be
   captured with the incorrect sampling rate.

   RDLibrary. Fixed a bug that caused waveform generation to break on ARM
   architectures.

   RDLogManager. Fixed a bug that caused inline traffic events to be imported
   without regard for slop factor settings.

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.
*** snip snip ***

Details and source code are available at 
https://github.com/ElvishArtisan/rivendell/releases 
.


Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell v3.6.6

[Fred Gleason]

On Oct 11, 2022, at 11:27, Gavin Stephens  wrote:
> Will this be available for doing an upgrade by yum by any chance?
> 
Should be there now. You may have to do ‘yum clean expire-cache’ to update your 
local repo cache.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] VNC problem revisited

[Fred Gleason]

> On Oct 9, 2022, at 07:35, Rob Landry <41001...@interpring.com> wrote:
> 
> I've  had my share of difficulties running Xvnc on Rivendell systems lately. 
> The VNC service will crash; or it will stop responding to mouse clicks or 
> keystrokes; and in some cases even the keyboard and mouse attached to the 
> physical machine will become unusable.
> 
> Some machines never experience problems; others experience them frequently. 
> In some cases, killing and restarting Xvnc will resolve the problems, but in 
> others, I have to reboot the machine.
> 
> The problem has been encountered on machines running CentOS 7, with Rivendell 
> installed via the Paravel install script. I've encountered the problem with 
> both Rivendell V2 and Rivendell V3. I don't remember seeing the problem on my 
> older Debian-based Rivendell machies.
> 
> Has anyone else but me encountered this sort of problem?

Never anything of that intensity (where it affects the local X server), but I 
haven’t run Xvnc in ages. You might want to try out our x11vnc-based setup, 
which uses Systemd socket-activation to start up an x11vnc session on demand. 
To get it, do:

On RedHat-ish setups:   sudo yum install x11vnc-auto

On Ubuntu-ish setups:   sudo apt install x11vnc-auto

After installing, then set it up:

sudo systemctl start x11vnc-auto.socket
sudo systemctl enable x11vnc-auto.socket
vncpasswd

N.B. - no ’sudo’ on the last command!

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] [Rivendell] Mailing list - future directions

[Fred Gleason]

On Oct 3, 2022, at 14:13, Jim W7RY via groups.io 
 wrote:

> I can moderate for a while. Until it gets out of hand. :)  As long as it 
> doesn't take much time, I'm good with it.

Happily, in the 20 years I’ve run Rivendell-dev, I’ve had to put a user on 
‘moderate’ only once. It is a great community.

Ok, let’s do this! I will generate a formal announcement to get things started.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| Easiest Color to Solve on a Rubik's Cube: Black. Simply remove all  |
| the little colored stickers on the cube, and each of side of the|
| cube will now be the original color of the plastic underneath --|
| black. According to the instructions, this means the puzzle is  |
| solved. |
| |
|   -- Steve Rubenstein   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] [Rivendell] Mailing list - future directions

[Fred Gleason]

On Oct 3, 2022, at 10:45, Jim W7RY via groups.io 
 wrote:

> You are welcome here!

Thank you James!


> I can make someone that you think should be a moderator an admin on this list.

Any volunteers? (I’d be happy to undertake it, but time spent doing “admin 
stuff” is time spent *not* working on Rivendell code).

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| Ninety-Ninety Rule of Project Schedules: The first ninety percent   |
| of the task takes ninety percent of time, and the last ten percent  |
| take the other ninety percent.  |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Mailing list - future directions

[Fred Gleason]

On Oct 2, 2022, at 22:41, David Klann  wrote:

> +1 for groups.io . I would contribute actual money for a 
> paid subscription to groups.io . Oh! I just checked my 
> groups.io account -- I am (and 4 other users are) already 
> subscribed to "Rivendell". List owner appears to be someone named "Jim W7RY". 
> Jim are you listening here?

‘Kay, I just joined that list and sent them a copy of my original post from 
yesterday (cross-posted here as well). Let’s see what happens…

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
|  Nothing is ever accomplished by a reasonable man.  |
| |
| -- Bucy's Law   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Mailing list - future directions

[Fred Gleason]

Greetings Rivendell Folks!

My apologies for the cross-posting and repetition. Those of us the 
Rivendell-Dev listserv has been having some discussions about possible 
replacements for our GNU Mailman-based system (for reasons that will be obvious 
in the appended message), and the ‘rivend...@groups.io’ list came up. Might you 
folks be interested in taking on the role? Appended is the original post that 
got the discussion rolling:

*** snip snip ***
Howdy Folks:

Many of you here (especially those whose e-mail is delivered by via accounts 
hosted by Google) have likely noticed that the reliability of messages from 
this listserv has taken a significant nosedive over the past several months. 
After ~20 years of self-hosting this list and (for the past several months) 
spending many, many hours wrestling with obscure and intermittent bounces 
generated by Google’s MTAs, I’ve come to the conclusion that it’s time to move 
this service to a provider that has the requisite skills and resources to 
manage it in the “Google age”. Our options appear to be:

1) Host the existing list with a commercial company. 

2) Move to a “non-commercial" existing listserv that has the available capacity 
and would be willing to take it on —e.g. an ‘edu’ type institution.

3) Move to some other, non-email based service (the FB Rivendell group is one 
that has come up as a possibility).

WRT option 1), I’ve done some shopping around and found none with the needed 
functionality that would at the same time be affordable (really trying to avoid 
advertisement-based models).

I’m open to ideas regarding the possibilities.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|——|
*** snip snip *** ___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Mailing list - future directions

[Fred Gleason]

Howdy Folks:

Many of you here (especially those whose e-mail is delivered by via accounts 
hosted by Google) have likely noticed that the reliability of messages from 
this listserv has taken a significant nosedive over the past several months. 
After ~20 years of self-hosting this list and (for the past several months) 
spending many, many hours wrestling with obscure and intermittent bounces 
generated by Google’s MTAs, I’ve come to the conclusion that it’s time to move 
this service to a provider that has the requisite skills and resources to 
manage it in the “Google age”. Our options appear to be:

1) Host the existing list with a commercial company. 

2) Move to a “non-commercial" existing listserv that has the available capacity 
and would be willing to take it on —e.g. an ‘edu’ type institution.

3) Move to some other, non-email based service (the FB Rivendell group is one 
that has come up as a possibility).

WRT option 1), I’ve done some shopping around and found none with the needed 
functionality that would at the same time be affordable (really trying to avoid 
advertisement-based models).

I’m open to ideas regarding the possibilities.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Rivendell v3.6.6

[Fred Gleason]

On behalf of the entire Rivendell development team, I'm pleased to
announce the availability of the next production release of the next
major version of Rivendell, 3.6.6. Rivendell is a full-featured radio
automation system targeted for use in professional broadcast
environments. It is available under the GNU General Public License
version 2.

From the 'NEWS' file:
*** snip snip ***
Changes:
   RDCastManager. Added an Online Feed Report that displays a bulleted list
   of items for a feed on the basis of the actual posted feed XML.

   RDImport. Added the ability to load copy-split audio sets (generic and
   regional) by means of ISCI-code named files. See the '--by-isci' option
   in the rdimport(1) man page.

   RDLibrary. Restored support for CD-Text for reading CD metadata.

   Fixed a bug in the podcasting subsystem that caused episodes to be
   automatically deleted immediately after being made active if the
   'Air Date/Time' was set for the future and 'Item Expires' was set to 'No'
   in the 'Editing Item' dialog.

   Various bugfixes. 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.
*** snip snip ***

Details and source code are available at 
https://github.com/ElvishArtisan/rivendell/releases 
.


Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] How close is Rivendell 4?

[Fred Gleason]

On Jul 13, 2022, at 14:30, David Klann  wrote:
> 
> Just tossing out my $0.02-worth of an opinion. I question whether Rivendell 4 
> is ready for release candidate status. There are several pull requests and 
> issues at GitHub, and I'm noticing lots of "rough around the edges" things 
> that are, in Rivendell 3, stable and "sensible".
> 
> On the other hand, Rivendell 4 is certainly stable enough, and publishing a 
> release candidate will motivate more people to try it out and reveal more 
> issues.

Good questions! They summarize well the dilemmas involved.


> Fred, what's your suggested process for getting attention to pull requests 
> and issues?

Well, now that I’m back after a month+ of various distractions, I’m hoping to 
be able to spent some time with those outstanding issues and PRs. And after 
that, we’ll see.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Compiling problem

[Fred Gleason]

On Jun 16, 2022, at 06:56, Rob Landry <41001...@interpring.com> wrote:

> I'm trying to install Rivendell on a Dell Inspiron 3910.
> 
> I couldn't get CentOS 7 to install on this machine; it can't find any disk 
> drives.
> 
> Rocky Linux 8 (= CentOS 8) does install, so I set about trying to compile 
> Rivendell from source.

Just be sure you’re using Rivendell v4.x. Earlier versions won’t work there.


> The problem is that libcoverart won't compile; I get the following:

There are packages available in the Paravel repo for RHEL8. See:

https://software.paravelsystems.com/rhel/8rd4/

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] How close is Rivendell 4?

[Fred Gleason]

On Jun 8, 2022, at 17:14, James Greenlee  wrote:

> Just curious if there's a time-table on the release of Rivendell 4.

There is, it’s just that the date keeps slipping. Suffice to say that it’s been 
an ‘interesting’ past few weeks here.

If all goes well (ha!), I hope to have a release candidate out the door next 
week. We’ll see…

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Old Rivendell, new system, multibyte string problem (I think)

[Fred Gleason]

On Jun 29, 2022, at 13:20, Rob Landry <41001...@interpring.com> wrote:

> Could this be a UTF-8 issue? Unless I misremember, Rivendell versions befor 
> 3.x don't fully support UTF-8. A client of mine who used to run a Brazilian 
> format on Rivendell had a lot of problems with Portuguese-language song 
> titles.

Correct. v2.x is basically limited the Latin character set. v3.x and later has 
proper UTF-8 support.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Supporting old AudioScience cards [WAS: RD & ASI6122...]

[Fred Gleason]

On May 29, 2022, at 01:27, Timothy Elwell  wrote:

> Finally getting some time to play with RD again. Had built a box with a 6122 
> card a while back and had to just leave it alone for a while because of my 
> real job. I'm running CentOS7 via Fred's awesome install scripts. Everything 
> works except the 6122 card doesn't show anywhere. If I do asihpitest on the 
> command line, it finds the card, runs the tests and finishes up. However, the 
> card doesn't show in RDalsaconfig (and my brain may be way outdated as to 
> whether it should) nor anywhere else in RD. In RDAdmin, under "Audio 
> Resources" for the correct machine, the "Supported Audio Drivers" sections 
> shows "AudioScience HPI [not active]". I've googled everything I can think of 
> as well as trying to search the wiki, but seem to be at a dead end.

The ASI6122 was officially ‘end of lifed’ by AudioScience a number of years 
ago, which means that support for it is not included in their current driver. 
However, all is not lost! You can downgrade the driver that was installed by 
default to a version that will recognize that card. The procedure is:

1) Download an RPM for the replacement driver. Available at:


http://static.paravelsystems.com/audioscience/centos/7/4.13.00-3/hpklinux-4.13.00-3.el7.centos.x86_64.rpm

2) Open a Terminal and do ’su -‘ to get a shell with root permissions.

3) Remove the old driver by doing ‘yum remove hpklinux’. This will want to 
remove some additional packages, including Rivendell itself. Go ahead and let 
it do it.

4) Install the replacement driver by doing ‘yum install 
’.

5) Reinstall the Rivendell RPMs by doing ‘yum install rivendell’.

6) Reboot.

Your ASI6122 card should now be recognized and usable in Rivendell.

NOTE: Uninstalling the Rivendell RPMs will not touch your *data* —i.e. the 
Rivendell database and audio store— at all. We remove those RPMs and then put 
them right back in the above procedure because they list the ‘hpklinux’ package 
(the AudioScience driver) as a dependency and yum(8) has no direct method for 
‘downgrading’ a package in place.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] MainLog gets fadded down upon tracks segueing

[Fred Gleason]

On May 11, 2022, at 10:29, Alejandro olivan Alvarez 
 wrote:
> Have you opened an issue on the Github repo for this?
> 
I’ve marked #806 as a bug; no need for a new issue.

> (I guess that this may probably be considered a quite ugly bug!)
> 

Certainly a glaring one! Hopefully not too bad to fix though.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] MainLog gets fadded down upon tracks segueing

[Fred Gleason]

On May 11, 2022, at 10:11, Bemis, Andru  wrote:

> I'm not at my RD4 computer right now, but I have a hunch that the Fade-Up & 
> Fade-Down markers have been accidently switched somewhere in the RD4 
> programming. I know for a fact that cuts exported from RD4 and imported to 
> RD3 have Fade-Ups where I set Fade--Downs, and vise versa. This leads to very 
> similar results as you're describing. There's definitely a bug of some sort 
> in the way RD4 deals with fade markers.

That’s exactly right. Good call! See:

https://github.com/ElvishArtisan/rivendell/issues/806 


Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Getting Notices of bounces from mailing list

[Fred Gleason]

On May 6, 2022, at 08:06, Rich Gattie  wrote:

> So I have been getting these messages from the mailing list that I am being 
> disabled because of excessive bounces. 
> I am using Gmail, and I checked my filters and don't see any blocking the 
> mailing list. 
> 
> Is there anyone else on Gmail seeing this as well?

We have been experiencing cases where a particular post will generate bounces. 
It’s been very intermittent, and seems to primarily affect recipients at 
gmail.com . It appears to be related to intermittent outages 
of the DNS system at the location that hosts the server. Investigation is 
ongoing.

In the meantime, I’ve disabled the bounce processing on the listserv, which 
means that no further accounts should be disabled automatically on the basis of 
a bounce. This of course is merely a band-aid; the real resolution will depend 
on getting to the bottom of the DNS problem. We apologize for the problems.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Reading RDAirPlay status after sending RML

[Fred Gleason]

On May 4, 2022, at 11:42, Nick Andre  wrote:

> tldr: is there any way to tell what cart RDAirPlay is currently playing? It 
> seems like I can grep the syslog, but just wondering if there's some other 
> more expedient way.
> 
> We implemented remote broadcasting for our radio station using some basic 
> bash and MySQL procedures. Essentially after all is said and done, the script 
> will send RML to Rivendell 
> 
>  to load a particular cart to the queue along with a certain announcement and 
> then start the show. Looks like this:
> 
> rmlsend PX\ 1\ 3004\! #This is the WMFO shows pre-recorded announcement, will 
> push to top
> sleep 1
> rmlsend PN\ 1\! #press play next (second track in queue or first if not 
> running), which should fade out existing track
> sleep 1
> rmlsend PX\ 1\ 96\!
> sleep 1
> rmlsend PX\ 1\ $cart\! # queue up specified show
> 
> Sometimes a live DJ will ignore instructions and load a new log, canceling 
> playback. I would like to programmatically illuminate if this has happened.

Sounds like you need a PyPAD script.

http://opsguide.rivendellaudio.org/html/chapter.pad.html#sect.pad.pypad 


These can be used to send notifications whenever the state of a log changes in 
RDAirPlay.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
|  Life would be so much easier if we could just look at the source   |
|  code.  |
| |
|  -- Anonymous   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Compatible Soundcards

[Fred Gleason]

On Apr 29, 2022, at 11:35, Joe Panarello  wrote:

> In this vain, Is there any virtual sound card software that will work with
> Rivendell? I'm fairly sure that there is not any DANTE support for CENTOS
> (LINUX) at this moment.

Axia Livewire is the only one that comes to mind right now (which Paravel sells 
as an add-on).

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Compatible Soundcards

[Fred Gleason]

On Apr 29, 2022, at 10:38, David Henderson  wrote:

> This one is a bit outdated and with all newer PCs having PCIe slots, finding 
> a machine with the older PCI slots is becoming harder and harder.

Unfortunately, the ‘prosumer’ sound card market for PCs has radically shrunk 
over the past few years, with most current offerings being either USB-based or 
full-on pro-grade —e.g. AudioScience, which does offer a full line of products 
with PCI/e interfaces.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Nautel RBDS Pypad script question

[Fred Gleason]

On Apr 26, 2022, at 09:10, Rob Landry <41001...@interpring.com> wrote:

> The solution: hard-code the IP address and port number into the Python 
> script. Works like a charm.
> 
> I still have no idea why it's not reading these things from the config file. 
> Comparing this script with the others, they all get these thinsg though the 
> same mechanism. Sauce for the goose ought to be sauce for the gander, but for 
> some reason it's not.

Are you launching this via RDAdmin->ManageHosts->host_entry->PyPADInstances? If 
so, then there is no actual ‘config file’, just an entry in the 
‘PYPAD_INSTANCES’ table in the DB (the configuration data lives in the ‘CONFIG’ 
field).

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Nautel RBDS Pypad script question

[Fred Gleason]

On Apr 24, 2022, at 01:09, le père Léon  wrote:

> Le 23/04/2022 à 05:05, Rob Landry a écrit :
>> [...] I have a funny feeling the script is never reading the config file. 
>> Where is the config file stored?
> 
> In the database.

It depends on how the script is being instantiated. If you’re running it 
“embedded”, where the Rivendell service starts it, the config is indeed pulled 
from the database. However, it’s often convenient to be able to run a pypad 
script directly from the command line, in which case you can provide the config 
filename as one of the command line arguments. See

http://opsguide.rivendellaudio.org/html/chapter.pad.html#sect.pad.pypad 


for the details.

WRT the Nautel script: that script was contributed by a Rivendell user; I’ve 
never been able to actually test it as I lack the required hardware. I’d 
welcome any feedback on it.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] fetching rdlibrary reports from terminal

[Fred Gleason]

On Apr 23, 2022, at 07:17, Peter Claes  wrote:

> Is there a way for me to start a 'Cart Data Dump (CSV)' from the command line 
> ? 
> 
> I did man rdlibrary, but it seems not possible via there.

Not supported at present. One of the things the would make it slightly tricky 
to do is be the fact that the contents of a given support are determined by the 
set of carts returned by the current search criteria. I suppose a way to 
specify those via command line could found.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

[Fred Gleason]

On Apr 19, 2022, at 17:15, Rob Landry <41001...@interpring.com> wrote:

> When I run rdlogin, it says "Current user: unknown".
> 
> If I select a user, or press the Default User button, the program immediately 
> quits.
> 
> If I run it again, it still says "Current user: unknown".
> 
> So, the problem appears to be some database value that isn't letting it set 
> the user.

Sounds like a reasonable diagnosis.


> This Rivendell installation was done under CentOS 7, following the Paravel 
> Web site instructions. Since I followed the same procedure for two other 
> machines, neither of which have the problem, it must be something in this 
> database rather than a software issue. If I were to do a table-by-table 
> comparison with one of the other machines, which table should I start with?

I’d start by taking a look in RDAdmin->ManageUsers. Are all of the expected 
users there? Does the data look sane? (The data in those dialogs mostly live in 
a table called ‘USERS’, but looking directly at that won’t be particularly 
helpful without a good understanding of the schema design. And, remember, the 
schema has changed quite a bit between v2.1x and v2.19.x)!

And then, take a look at the Station entry in RDAdmin. Does the default user 
exist?

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

[Fred Gleason]

On Apr 19, 2022, at 14:34, Rob Landry <41001...@interpring.com> wrote:

> It says "User: " with nothing after it, and then "Log: wcvr-tuesday”.

There’s your problem with sound panel play-out then (and a slew of other stuff 
not working as well).

Can you use RDLogin to log in as other users? How about the default user? The 
titlebar displays should update in real time as the users change.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

[Fred Gleason]

On Apr 19, 2022, at 10:29, Rob Landry <41001...@interpring.com> wrote:

> Unfortunately, upgrading the old database to 2.19.3 and then upgrading it to 
> 3.6.5 didn't solve the problem. I am still experiencing the same symptoms.
> 
> If I start rdairplay in a terminal window, select Sound Panel. click on Setup 
> to start it slashing, and then click on [S:1] Panel S:1 to change its name, 
> the following message appears in the terminal window:
> 
> QSqlQuery::value: not positioned on a valid record
> for query: select `CONFIG_PANELS_PRIV` from `USERS` where `LOGIN_NAME`=""
> 
> LOGIN_NAME = ""? Shouldn't it default to 'user’?


Do you have a valid user context? Look on the titlebar of RDAirPlay; you should 
see something like ‘User: user’.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

[Fred Gleason]

On Apr 18, 2022, at 16:12, Rob Landry <41001...@interpring.com> wrote:

> I have an old machine installed at WCVR running RD 2.1.5 under Centos 6. It 
> was built in 2017.
> 
> I want to replace it with a new machine I've just built that runs RD 3.6.5 
> under CentOS 7. Both machines have the same name 
> ("farancia.sugarrivermedia.com ") but 
> different IP addresses.
> 
> In pursuit of that goal, I backed up the old RD 2.1.5 database, copied it to 
> the new system, imnported it with rddbmgr, and converted it to the current 
> database version.
> 
> I'm finding that some things don't work; in particular, rdlibrary sees no 
> groups and no carts.
> 
> The SoundPanel buttons in rdairplay don't work properly. The System panel 
> buttons are all blank, and cannot be modified from rdairplay. The User panels 
> are likewise blank, but can be modified.
> 
> Has anyone else experienced these issues?

Sounds like something got borked in the database conversion. That’s a very old 
Rivendell version that you upgraded from (schema version 205). The DB converter 
routines in v3.x (and v4.x, for that matter) support schema versions all the 
way back to 159 [v1.0.x], but only schema versions 242 [v2.10.x] and later are 
really well tested. If possible, I would try converting that DB using the 
latest v2.x version (v2.19.3), *then* use v3.6.5 to convert it to ‘current’.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Restart subservices (rdcatchd) selectively

[Fred Gleason]

On Apr 5, 2022, at 10:13, Florent Peyraud  wrote:

> I'm facing some issues with rdcathd putting itself in a state where it does 
> not perform scheduled tasks until I restart it. The problem with the current 
> implementation of rdservice and systemd, I need to restart the complete 
> rivendell service set, which cuts audio during the startup and the relaunch 
> of rdairplay. For the time being, I was not able to debug rdcatchd when this 
> issue occurs.
> 
> Is there a way to restart rdcatchd only with the current implementation ?

I’d be more interested in getting to the bottom of the problems with 
rdcatchd(8). Please consider opening a bug report for it at 
https://github.com/ElvishArtisan/rivendell/issues.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] RDlibrary opening delay on rd3

[Fred Gleason]

On Apr 1, 2022, at 09:56, Tom Van Gorkom  wrote:

> We are helping a small FM station update from rd2.19 to 3.6 and are concerned 
> that something in the database isn't right. When we prepare a fresh install 
> of server and client on CentOS 7 and Riv 3.6.5, it all works great. Then when 
> we load and convert the database, at least the library becomes sluggish. The 
> CPU load is fine. The library click to open delays about 1 sec on the server 
> but around 5 seconds on the client before it is populated. He has about 10K 
> of carts/cuts. Is this normal? It's not normal on our 2.19 clients with 17K 
> of carts/cuts. Any ideas of what could cause this?  We have tried different 
> hard drives and computers and all behave the same. Using Dell 9th gen i5. 

I’d be looking at network configuration. An incorrect DNS configuration often 
turns out to be the culprit with startup delay issues like this.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rendering logs / Segue issues

[Fred Gleason]

On Mar 31, 2022, at 21:14, Bemis, Andru  wrote:

> Using RD 3.6.5 on CentOS 7, I'm having unexpected difficulty with the 
> "Render" function in RDLogEdit. If I create a one-hour program log with voice 
> tracks, and try to render it to FLAC for archival purposes, the segues do the 
> opposite of what they do in RDAirplay; music tracks start at full volume 
> under the voice tracks, and voice tracks subsequently fade to zero. What's 
> going on? Is there a way to render a log without fading out voice tracks 
> during segues? Has anyone else run into this issue?

Is it a function of rendering to FLAC? Or do you see this behavior with other 
formats?

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Odd issue with rdcatch

[Fred Gleason]

On Mar 30, 2022, at 14:34, Rob Landry <41001...@interpring.com> wrote:

> For now, I've got it recording analog audio. They are recording a four-hour 
> live show Saturday morning and playing it back Sunday evening, and I won't be 
> back there again until Monday. I'll take a look at it when I'm next there.
> 
> What's interesting is that if I launch the rdcatch program and watch while 
> it's recording, I don't see anything on the level indicators when I'm 
> recording from the AES3 input, but if I've got normalization turned on, there 
> will be audio recorded. If I'm recording from the analog input, I do see 
> level indications during the recording.

I suspect that the card is just an oddball. There is special code in Rivendell 
to handle the ‘non-standard’ input routing in the ASI5111; I’ve a hunch that 
something similar will be needed for the ASI5810. Going to be hard to suss out 
without a sample card in hand though.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Importing audio on new drive

[Fred Gleason]

On Mar 31, 2022, at 09:47, David Klann  wrote:

> For the record, the "Fred Gleason recommended way(tm)" to attach remote file 
> systems uses the autofs[1] subsystem. Autofs causes remote file systems to be 
> attached at the time they are accessed and are detached when unused for a 
> specified period of time.

Yup. :)

The beauty of autofs is that it can automatically ‘heal’ situations that 
otherwise can cause major grief. A classic one is recovery from a facility-wide 
power failure. It’s not uncommon for the Rivendell server to take significantly 
longer to finish rebooting than many workstations; with the result that 
fstab(5) based setups end up with ‘/var/snd’ not being mounted from the server. 
If you’re “lucky”, this will show up right away when audio doesn’t play. The 
really invidious case though is with dedicated net catchers, which will happily 
record audio to the machine's local drive rather than the server. This 
sometimes doesn’t get caught until hours (or days!) later, when incorrect/dated 
material hits the air.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Odd issue with rdcatch

[Fred Gleason]

On Mar 29, 2022, at 09:48, Rob Landry <41001...@interpring.com> wrote:

> I recently installed an ASI5810 sound card in a Rivendell machine at WUMB 
> (Boston, MA). We are using the AES3 input and output of this card.
> 
> rdcatch appears to record only sometimes from the AES3 input.
> 
> In particular, if normalization is selected, we get a recording with audio, 
> but if no normalization is selected, we get silence. The problem does not 
> occur if we record from the analog input.
> 
> WUMB runs an older version of Rivendell (2.19.3), so if this problem has been 
> fixed in newer versions, I'll make the case to management that we need to 
> upgrade.
> 
> In the meantime, I think we'll be recording ffrom the analog input.

I’ve never tested with an ASI5810, but in looking at the mixer layout 
[https://www.audioscience.com/internet/products/sound_cards/asi581x.htm 
], that 
card has a decidedly ‘unusual’ layout on the capture side. There are two 
physical inputs (one analog and one AES3), but the accompanying text says 'Two 
stereo streams of PCM record fed from 1 stereo input’; whereas the card that 
the ASI5810 superseded (the ASI5111), that likewise had two physical inputs, 
had each one hard-wired to its respective stream converter.

How many inputs does RDAdmin report? Have you tried with all available inputs?

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Rivendell v3.6.5

[Fred Gleason]

On behalf of the entire Rivendell development team, I'm pleased to
announce the availability of the next production release of the next
major version of Rivendell, 3.6.5. Rivendell is a full-featured radio
automation system targeted for use in professional broadcast
environments. It is available under the GNU General Public License
version 2.

From the 'NEWS' file:
*** snip snip ***
Changes:
   Various bugfixes. 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.
*** snip snip ***

Details and source code are available at 
https://github.com/ElvishArtisan/rivendell/releases 
.


Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|


___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] RDLibrary Generate Reports does nothing on 1 of 2 workstations

[Fred Gleason]

On Mar 15, 2022, at 12:56, Kit Haskins  wrote:

> I have two boxes running 2.19.3 (yes I know it's old) with an odd problem I 
> can't sort out.   When using "REPORTS" from RDLibrary and selecting from any 
> of the following options:
> 
> Cart Report
> Cut Report
> Cart Data Dump (fixed width)
> Cart Data Dump (CSV)
> 
> 
> 
> I would expect to see another window pop up with the report I'm needing.
> However between the two boxes one of them will work as advertised, the other 
> nothing happens when "GENERATE" is clicked ...
> 
> As both boxes are same version and same OS level (6.10 yeah it's really old) 
> I'm still unable to take notice of the difference as to why one of them works 
> the other does not ...
> 
> /var/log/messages does not show anything for debugging this ...
> 
> I've seen this problem before and for the life of me can't recall what the 
> solution was to resolve it.

I suspect that the value of the $VISUAL environmental variable is incorrect 
—i.e. doesn’t point to a valid text editor. Try running rdlibrary from a 
command prompt. You’ll often get useful error message that way.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell v3.x on Debianish distros [WAS: Rivendell v3.6.4]

[Fred Gleason]

On Feb 28, 2022, at 04:01, Alejandro olivan Alvarez 
 wrote:

> However, I'm starting to think that maybe it would be an interesting and 
> relatively quick move, to use the 4.X successful debian-packaging experience, 
> to officially port it to the 3.X code (even if this limits target systems to 
> past-gen qt4-enabled Debian-derivative systems) as a kind of quick way to 
> have a stop-gap/time-buying intermediate-point while 4.X gets ready.

Unfortunately, the packaging challenge is only part of the problem with 
Rivendell v3.x. on current Debian/Ubuntu. Much larger than that are the issues 
with RDBMS (MySQL/MariaDB) compatibility. A big part of doing v4.x was checking 
(and in many cases, remediating) every SQL statement in the codebase to ensure 
compatibility with current MySQL/MariaDB versions. There are literally hundreds 
of such statements in Rivendell.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Reference OS

[Fred Gleason]

On Feb 26, 2022, at 12:15, Steve  wrote:

> What's the timeframe for 4.x to be released?  We're faced with a 
> fundamental choice with deployment onto new hardware, which seems to be:
> 
> v3.6.4. on CentOS7
> v4 on UbuntuStudioLTS
> 
> The downside to v3.x on CentOS 7 is that it will be out of support in 
> 2024.  The downside to v4 is that it's still in beta.  Compiling v3 on 
> UbuntuStudioLTS seems difficult because of the QT4 dependency.

That summarizes the dilemma well. RHEL/CentOS 7 is pretty much the “last stand” 
for distro-supported Qt versions earlier than 5.

The official answer re: Rivendell v4.x is “when it’s ready”. Spring of this 
year seems a reasonable timeframe, but it all depends on what issues continue 
to get sussed out in testing. I have begun putting it into some (quite 
constrained) “on-air” environments, where it has mostly worked pretty well, but 
also uncovered a couple of significant issues (being worked on).

I wish I had more definite advice for you, but that’s the reality at the moment.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell v3.6.4

[Fred Gleason]

On Feb 26, 2022, at 18:48, Florent Peyraud  wrote:

> I've refactored the packaging to be as close as possible to the packaging 
> scheme of v4.0.0beta3, but using genuine debhelper package splitting instead 
> of the very manual file distribution among the different package build 
> directories as it is currently done in v4.0.0beta3. I borrowed some compile 
> tricks from the "rules" Makefile of v4.0.0beta3 in order to improve my own 
> build process so that the manpages embedded in the packages I provide are 
> working well now ! Thanks a lot ;)

Nice. Feel free to feed the relevant automation changes back to v4.x if PRs if 
you’d like. I freely admit to being an beginner when it comes to Debian 
packaging. (Not helped by the fact that I’m completely spoiled by the rpm/yum 
toolchain, where everything is centrally architected and documented, as opposed 
to the seeming “herd of cats” approach in dpkg/apt).

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Reference OS

[Fred Gleason]

On Feb 24, 2022, at 18:10, Steve  wrote:

> Is the reference operating system for Rivendell still CentOS-something 
> or is Debian a solid option?

FWIW, the two distros I use for development of v4.x are RedHat Enterprise Linux 
and UbuntuStudio LTS, and those are the two distros for which I will be 
maintaining downstream integrations. That said however, the goal is to make 
v4.x source compatible with “Linux in general”, so downstream integrations with 
other distros are certainly possible if someone wants to step up and maintain 
it.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] RDAirplay Crash - Double Free Corruption

[Fred Gleason]

On Feb 24, 2022, at 16:23, starrbuck1...@gmail.com wrote:

> And you really should upgrade them all.  Fred shouldn't have to support much 
> older versions.  It's just not realistic.

And mostly I don’t, beyond recommending an upgrade to the latest-and-greatest 
(currently v3.6.4). Bugs reported on *that* version do get lots of attention 
however.

A word to those still running v2.x though — those versions are finally going to 
hit the end of the road when CentOS 7 goes EOL in June 2024, as Qt3 is not 
available on either of the successor systems (RHEL-8 or UbuntuStudio LTS). Best 
start thinking about the transition now.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] RDAirplay Crash - Double Free Corruption

[Fred Gleason]

On Feb 23, 2022, at 22:32, Steve  wrote:

> This is Rivendell 2.19.3 on CentOS 7.

That’s an ancient version. There have been literally hundreds of bug fixes and 
feature enhancements made since in the v3.x tree. Your best bet would be to 
upgrade.

See:

http://wiki.rivendellaudio.org/index.php/Upgrading_from_v2_to_v3_on_CentOS_7 


Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] RDAirplay Crash - Double Free Corruption

[Fred Gleason]

On Feb 23, 2022, at 07:35, Steve  wrote:

> We've seen a few crashes seemingly tied to the end of the log being 
> reached and the next log being loaded.  The only commonality that I've 
> seen is that the logs had been manually edited, although they were 
> manually edited several days prior.

Thanks, this is helpful info! What version of Rivendell was this, and on what 
distro?

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Rivendell-prog mailing list

[Fred Gleason]

Greetings Rivendell folks!

Since the inception of the Rivendell project in 2002, we have maintained two 
mailing lists; Rivendell-devel, intended for general purpose discussion of 
“things Rivendell”, and Rivendell-prog, intended for Rivendell developer 
discussion. The traffic on the Rivendell-prog list has always been very low (a 
dozen or two messages per year), and since the advent of GitHub virtually all 
developer-to-developer discussion takes place by means of that platform. Thus, 
I’m wondering if it would make sense to discontinue the Rivendell-prog mailing 
list entirely. Does anyone see a problem with that happening?

N.B. - This is the Rivendell-*prog* list that we’re talking about here. The 
Rivendell-devel list (where the lions share of Rivendell discussion actually 
takes place) would be unaffected by this change.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
|They shoot horses, don't they?   |
| |
|  -- Anonymous   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Rivendell v3.6.4

[Fred Gleason]

On behalf of the entire Rivendell development team, I'm pleased to
announce the availability of the next production release of the next
major version of Rivendell, 3.6.4. Rivendell is a full-featured radio
automation system targeted for use in professional broadcast
environments. It is available under the GNU General Public License
version 2.

From the 'NEWS' file:
*** snip snip ***
Changes:
   RDLogEdit. Added a 'Log Listing (CSV)' report under the 'Reports'
   button in the 'Edit Log' dialog.

   Added a 'SuppressMusicImportLinks=No|Yes' directive to the [Hacks]
   section of rd.conf(5).

   PyPAD Scripts. Added the ability to filter PAD updates by Group membership
   on a per-script instance basis. See the documentation for the [NowGroups]
   and [NextGroups] sections in the script exemplar files.

   Now & Next/PAD System. Deprecated the use of the 'Transmit Now & Next data'
   checkbox in the 'Group' dialog in rdadmin(1).

   Various bugfixes. 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.
*** snip snip ***

Details and source code are available at 
https://github.com/ElvishArtisan/rivendell/releases 
.


Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Audioscience AES/EBU or S/PDIF output type

[Fred Gleason]

On Feb 21, 2022, at 21:34, Gavin Stephens  wrote:
> I haven't tried connecting the ASI5111 digital I/O to anything yet to see if 
> the output is working by default so I'm not sure if it's even going 
> regardless of what 'Audio Ports' doesn't report. 
> 
> The card only shows as having one output but this is all I got on on my 
> non-Linux machine too, the digital output was just a clone of whatever was on 
> the analogue outputs. 
> 
That exactly correct. If you look at the card mixer diagram, you’ll see that 
the analog and AES3 outputs are hardwired together. There is no 
software-controllable method for splitting them.

It’s the *inputs* that have the ‘oddball’ routing capabilities.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Audioscience AES/EBU or S/PDIF output type

[Fred Gleason]

On Feb 20, 2022, at 16:46, Rob Landry <41001...@interpring.com> wrote:

> I have connected SPDIF outputs to AES/EBU inputs and had them work; I've not 
> tried the other way around. I recall reading somewhere that the differences 
> between the two are essentially that AES/EBU is balanced and SPDIF is 
> unbalanced. The voltage levels are different too, I think.

The data header formats are different too. _Usually_, these differences can be 
ignored; although I have run across some gear (the old 360 Systems ‘Instant 
Replay’ unit comes to mind) where the AES3 input refuses to process any signal 
that doesn’t have the correct AES3 header. I don’t believe this should be a 
problem for ASI cards though.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Audioscience AES/EBU or S/PDIF output type

[Fred Gleason]

On Feb 19, 2022, at 01:56, Gavin Stephens  wrote:

> If I can only select the input digital type on my Audioscience AS5111 in 
> rdadmin, do I take it that my card's digital output type selection is not 
> currently supported by the HPI driver or RD 3.6.2?
> 
> The only output changes I can make are to the analogue ref. level from what I 
> can see. I know the card can do both AES/EBU or S/PDIF output but I can't 
> find any selection for this.

It’s been awhile (and I don’t have one handy to check), but I do recall that 
that card is an oddball in several ways; one of which is that there are 
actually *two* independent capture inputs: the first one via the analog input 
and the second via the digital. You should see this reflected in the ‘Audio 
Resources’ page in rdadmin(1), which should report two inputs. Set the channel 
input assignments to use port 1 on the card and you should get digital. IIRC, 
it’s AES3 only; I don’t believe S/PDIF is supported on that card.

You can find the mixer diagram on page 1 of the data sheet, at:


https://www.audioscience.com/internet/products/obsolete/datasheet_asi5111_5211.pdf

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Here's one I haven't seen before

[Fred Gleason]

On Feb 14, 2022, at 12:14, Rob Landry <41001...@interpring.com> wrote:

> Interesting. I wonder if switching to a different desktop, such as MATE or 
> Cinnamon, would help.

Possible. I believe that both of those use gdm(1) though.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Installing New Rivendell 341

[Fred Gleason]

On Feb 14, 2022, at 00:59, ija...@jamcorbroadcast.com wrote:

> I tried installing in Centos 7 and 9 with the same issues. Do you have any 
> suggestions on what the best way to install Rivendell

https://software.paravelsystems.com/howtos/CentOS/7rd3/ 


Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Here's one I haven't seen before

[Fred Gleason]

On Feb 13, 2022, at 14:35, Rob Landry <41001...@interpring.com> wrote:

> It just happened again. One of the stations called me just now reporting they 
> couldn't get a window to close. The system wasn't responding to regular mouse 
> clicks, only to control/left click, which it interpreted as left-click.
> 
> I opened a terminal window and quickly discovered that, as before, I couldn't 
> type anything, but control/alt/d seemed to fix the problem. According to 
> Google, that's a keyboard shortcut for "show desktop".
> 
> What I can't figure out is what's triggering the problem in the first place, 
> and why I've never encountered it before last week.

I’ve seen stuff like this happen occasionally when using VNC. The cure has 
always been to restart the window manager, by doing (as root):

systemctl isolate multi-user.target
[wait 10 seconds]
systemctl isolate graphical.target

Unfortunately, this will also kill rdairplay(1), thus interrupting any on-air 
playout.

Perhaps a VNC client acting badly? Has there been a recent change in remote 
access patterns to this system —e.g. somebody using a different VNC client?

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] ASI Card output level

[Fred Gleason]

On Feb 12, 2022, at 23:53, Gavin Stephens  wrote:
> If RD is playing a test tone at 0dBFS, and the Ref. Level is 0 in Audio 
> Ports, is the ASI card playing that tone at the maximum rated output level? 
> Or is it still 6dB down from maximum?
> 

+16 dBm.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] ASI Card output level

[Fred Gleason]

On Feb 12, 2022, at 21:16, Gavin Stephens  wrote:
> Thanks for that. Still a little confused though.
> 
> From your suggestion, -20dBFS would be -4dBm?
> 
> The maximum I can change this reference level up is by 6. What would it need 
> to be set at to get +4dBu out of the card from a tone @ -20dBFS? The 1.22V I 
> got was peak to peak, not RMS. So I'm assuming it has to be set at the 
> maximum of 6, or does it really need 8?
> 
You would need 8. However, all ASI cards that I’ve tested max out at +6 dB for 
that mixer setting. If you need more, you’ll have to provide that gain 
externally (or revert to using the standard Rivendell gain structure, where 
‘reference’=-16 dBFS). That gain structure is ‘baked in’ to Rivendell at a 
pretty fundamental level.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] ASI Card output level

[Fred Gleason]

On Feb 12, 2022, at 00:49, Gavin Stephens  wrote:

> Under audio ports in rdadmin, what exactly is the ref level setting, or more 
> specifically what does this do?
> 
> The output on my ASI5111 Rev.F card seems to be a bit low on the RD box. So I 
> decided to plug a multi-meter in to one of the outputs while playing a test 
> file with a 400Hz tone with it's peak at -20dBFS. This card is suppose to 
> output +24dBu max (the Rev.F) so I should be getting a nominal output which I 
> assume would be around 1.228V RMS from that test file.

The 'reference level’ (the ‘0’ level on the meters) in Rivendell’s audio files 
is -16 dBFS. The ‘Ref. Level’ controls in the ‘ASI Audio Ports’ dialog indicate 
the level (in dBm) of a steady-state tone recorded at the reference level on an 
analog ASI card output. 

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Glasscoder HLS encoding

[Fred Gleason]

On Feb 7, 2022, at 08:39, Frank Schultze  wrote:

> I would like to set up an HLS stream directly from a Rivendell machine 
> already running Glasscoder to an Icecast2 server - all working fine. Setting 
> up another instance of Glasscoder for HLS I'm able to get the PUT requests at 
> an nginx web server (manifest and data files) but the server won't save and 
> therefore deliver them.
> 
> According to my readings nginx is able to process these requests directly 
> using WebDAV and write these (maybe even cache them) for availability on the 
> web server as http://sample.com/sample.m3u8 ?
> 
> Could anyone please point me in the right direction without having to write a 
> RESTful API?

You have several options. First though, a bit a clarification: Icecast2 has 
nothing to do with HLS streaming. Those two streaming systems are completely 
orthogonal.

GlassCoder can publish HLS in three different methods: FILE, HTTP[S] and SFTP. 
The FILE method is simple to set up but requires that GlassCoder be running on 
the same system that is serving the streams. HTTP uses basic ‘garden variety’ 
PUT and DELETE transactions; WebDAV is not necessary and would be massive 
overkill. I’ve no experience with nginx, but GlassCoder is known to work well 
with Apache httpd; see the ‘docs/‘ directory in the installation package for a 
sample Apache configuration. Really, any web server that supports standard PUT 
and DELETE should work just fine though.

In many ways however, the third method, SFTP, is the easiest and most flexible. 
SFTP uses the widely deployed Secure Shell protocol, and is basically just 
another name for the scp(1) functionality that ships as part of Secure Shell.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Generating an Air Report

[Fred Gleason]

On Jan 11, 2022, at 11:15, Kit Haskins  wrote:

> There is a red box that shows up behind the countdown wheel when the TA flag 
> is set to 1
> 
> 
> I found it in the Rivendell Documentation under the RML section.
> TA - Toggle On Air Flag …

Correct. That flag can be used to gate all sorts of things —e.g. PyPAD scripts, 
where you can use it to route PAD conditionally depending upon whether a given 
system is actually “on air” or not. Not terribly useful in single-host 
scenarios, but tends to be heavily used in multi-host, multi-station setups.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] GlassCoder v1.0.4

[Fred Gleason]

On behalf of the Rivendell audio community, I’m pleased to announce the release 
of GlassCoder v1.0.4, a minimalist live audio encoder. In addition to streaming 
to IceCast and Shoutcast stream aggregators, GlassCoder is capable of 
generating live HLS streams and publishing them to any standard HTTP server. It 
is available under the GNU Public License version 2.

From the NEWS file:
*** snip snip ***
Changes:
   Fixed a packaging error on RHEL-8.
   Updated the PyPAD plug-in to be compatible with Rivendell v4.x.
*** snip snip ***

Further information, including full source code, is available at 
https://github.com/ElvishArtisan/GlassCoder 
.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Can't seem to win

[Fred Gleason]

On Jan 9, 2022, at 11:42, Mike Carroll  wrote:

> If you're using the Riv2 appliance ISO, I imagine the underlying CentOS 
> system is many years out of date. That might account for some of your 
> installation time, as the system is brought up to current maintenance.

It also uses CentOS 6, which has been out of support for over a year, and hence 
will not receive updates and has known security vulnerabilities.

I *strongly* recommend using the online installers.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] HD Radio

[Fred Gleason]

On Jan 9, 2022, at 09:35, Rob Landry <41001...@interpring.com> wrote:

> WSRO 650 AM in Ashland, MA has been running Rivendell for several years. They 
> recently flipped to all-digital using the MA-3 mode of HD Radio.
> 
> Has anyone developed a way to get metadata from rdairplay to display on an HD 
> Radio? There seems to be precious little documentation about it.

The importer interfaces are all ‘secret sauce’; you need a license from Xperi, 
who bought out the HDRadio IP from Ibiquity awhile back, to get the docs ($$$).

That said, I know of at least one commercial service (https://myquu.net/) that 
supports Rivendell PAD input for HDRadio.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Ransonware attack

[Fred Gleason]

On Dec 15, 2021, at 23:51, Brian  wrote:

> One more thought... Samba is Open Source, and I think you could make a case 
> that mature, established, widely-used open source software is generally less 
> exploitable than widely-used proprietary software of any age. The reason for 
> this being the fact that the source code is public.
> 
> With public source code in a mature codebase, all the low-hanging fruit has 
> been plucked years ago. The first place a would-be exploit creator is going 
> to look for vulnerabilities is the source code. Same with security 
> researchers. The whole world can clearly see the implementation of the 
> software, and so with something as widely deployed as Samba, errors will be 
> caught swiftly by anyone from a random software engineer perusing the 
> codebase out of curiosity to a security researcher being paid to find 
> vulnerabilities in open source software. It follows from the sheer number of 
> eyeballs looking at the code.

One would hope. But, take a look at the currently unfolding horror-show with 
Log2j. That is a FOSS project, *very* widely deployed by Java shops, and had an 
egregious, easily exploitable zero-day flaw (severity level 10 out of 10) 
sitting in the open for years, but discovered only a few weeks ago.

(And before you ask: no, Rivendell does not use Java, and is not vulnerable to 
the Log2j flaw). :)

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Ransonware attack

[Fred Gleason]

On Dec 15, 2021, at 23:43, Brian  wrote:

> I'm not sure this conclusion follows from the premises. Samba on *nix is a 
> totally independent implementation of the SMB/CIFS protocols that shares 
> nothing in common with the MS implementations. 99.9% of the time 
> vulnerabilities like the one described aren't caused by an inherent flaw in 
> the protocol itself, but on one of the implementations of the protocol. If 
> the vulnerability were in the protocol itself, that would generally require 
> disabling the related feature of the protocol or rolling out a new version of 
> the protocol itself, not just patching a bug. The actual coding bugs that 
> could be exploited are nearly always going to be totally different – and in 
> totally different places – from one implementation to the next.

CIFS/SMB has historically had its share of both (flaws in the protocol as well 
as in an implementation). But overall you are correct - a flaw in one 
implementation will rarely if ever carry over to another (assuming that the two 
codebases are completely independent).

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| Every program has at least one bug and can be shortened by at   |
| least one instruction -- from which, by induction, one can deduce   |
| that every program can be reduced to one instruction which doesn't  |
| work.   |
| |
|  -- Anonymous   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Ransonware attack

[Fred Gleason]

On Dec 15, 2021, at 12:02, Alejandro olivan Alvarez 
 wrote:
> If you look at debian security repo packages notes, and you look for samba, 
> you will find that, for the last vulnerability, found this 2021, only the 
> packaged sources for Debian Stable, testing and Sid have being patched with 
> the fix uploaded in samba.org . Older packaged versions, 
> including buster (which was stable until well within 2021) have not (probably 
> they can't due to aging code) been patched and are marked as 'vulnerable’.
> 
The situation it a bit different under RHEL-based distros (including CentOS). 
There, Redhat typically back ports security fixes into the version of the 
affected package being used on the distro, thus preserving ABI compatibility 
(which is, after all, one of the major reasons for having an ‘Enterprise’ 
distro at all). This is why the base version of the kernel on an RHEL system 
usually looks ancient, yet still has all known vulnerabilities patched; Redhat 
back ports the kernel fixes.

> Samba/Windows/SMB/etc has its vulnerabilities, like many other software, but 
> the difference here is that, the attack surface is far greater, since, out of 
> the dark, Windows computers become potential backdoors for our Linux 
> ecosystem.
> 
> Being a Linux-only user, I would add that, IMHO (and risking to be polemic) 
> nothing is more secure regarding security fixes/updates on the SMB protocol 
> than MS Itself (Windows server environment, with AD)... MS will be the first 
> to detect AND DEPLOY any security fix for MS machines via Windows Updates. A 
> Linux machine, on the other hand, can live happily with older/vulnerable 
> samba packages for ages.
> 
Totally agree.

> If I had to think of an ideal mixed Win-Linux environment for ease Dropbox 
> upload/ingestion, my recommendation would be to have a Rivendell machines 
> connecting as clients to a Windows Server, under AD (which is possible at OS 
> level, but I recall maybe it is not for rdimport/export/etc ), and mount the 
> remote share to read/ingest dropboxes, while the rest of the Win machines 
> mounting the same share to do the uploads. This way, all the Win files would 
> stay contained within the windows environment, subject to AD handshake all 
> the time and possibly under antivirus scrutiny... as we say here 'Juntos, 
> pero no revueltos' (toghether, but not mixed)
> 
I’ve seen sites do this. It works quite well. The downside is extra complexity 
with the concomitant reduction of overall reliability (two machines instead of 
one to break down, etc).

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Ransonware attack

[Fred Gleason]

On Dec 15, 2021, at 11:08, Bill Putney  wrote:
> Or to paraphrase Nancy Reagan "Just say NO to Windows.”
> 
Easy to say, but the awkward fact is that (AFAICT) nearly 100% of commercial 
scheduler systems (music and traffic) are Windows-based. The only exception 
that I know of (Jim Hardy’s ‘TrafficLight’ system) received a decidedly tepid 
response when he did a Linux-based release back in 2015. In audio production 
tools the situation is not quite so bleak (Ardour is a true pro-grade DAW, 
while there is the ever popular, and problematic, Audacity), but that’s an area 
where people tend to have their favorite tool and be highly resistant to 
change. And many if not most of those systems are Windows-based. (Heck, I know 
of one major Rivendell site that still uses, and loves, CoolEdit 2003. “Out of 
my cold, dead hands!”)

So, just saying “Interfacing with Windows isn’t supported” isn’t in the cards 
if you expect to be an actually relevant, viable option in Broadcast Automation.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A program is a lot like a nose. Sometimes it runs, and sometimes it |
| blows.  |
| |
|  -- The Illiterati Programus, Canto I   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Ransonware attack

[Fred Gleason]

On Dec 15, 2021, at 04:09, Andy Higginson  wrote:

> Fred, is building some more security into the system something that could be 
> incorporated into the Rivendell 4 build/setup while it is still in Beta?

As far as the installers are concerned, there are two main goals that we try to 
achieve:

1) Provide a “good experience”, in particular, a working, functional setup “out 
of the box” so that new users can see what Rivendell is and is capable of.

2) Install a good foundation, one that is reasonably secure, easy to update and 
to maintain according to industry best practices.

To an extent, these two goals tend to work against each other, especially with 
regard to the ’security’ metric. The first questions any new Rivendell user 
asks after getting the installer to work and playing the Test Tone cart 
typically are:

How do I load audio into this thing?

How do I get schedules (“logs”) into this thing?

How do I get as-played data out of this thing?

Or, in general: how do I transfer data in/out?

Given that our putative new user typically has limited (if any) Linux knowledge 
and indeed, limited or no formal IT experience at all, as well as that, in the 
overwhelming majority of cases, the data that these new users want to use 
resides on one or more Windows systems, our traditional approach for 
facilitating data transfer has been to provision, by default, a set of CIFS 
shares configured to allow ‘guest’ access. That makes them easy to find and 
access by the typical moderately-knowledgeable Windows user. Unfortunately, it 
also makes them easy to find and access by the Black Hats if (when?) they 
manage to get access to the LAN to which the system is connected. Yes, the 
permissions on those shares can be tightened after installation so as to allow 
only users with the actual need for access to do so, but how many new users 
know how to do that? How many know that it’s even *necessary* to do that?

This is the fundamental tension that we have to deal with when setting up 
default installation environments. Sure, we could refrain from installing Samba 
and wind up with a more ‘secure’ setup, but only at the price of the user 
having to configure the requisite access (NFS? Remote mount a CIFS share on a 
Windows box? Install Samba?) All doable, but in no case immediately obvious for 
the average new user. For that user, doing any of those things is going to 
amount to getting thrown into the deep end of a very cold pool.

I guess, at the least, we could call out these sorts of issues in the ‘Final 
Steps’ section of the instructions, along with pointers for various resources.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
|   Real Users never know what they want, but they always know when   |
|   your program doesn't deliver it.  |
| |
|  -- Anonymous   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Ransonware attack

[Fred Gleason]

On Dec 14, 2021, at 14:14, Rob Landry <41001...@interpring.com> wrote:

> USB keys can carry malware, too.
> 
> But more importantly, there's no one here to carry one. They're all working 
> from home.
> 
> It sounds like Samba needs to be disabled.

That can be done, by putting the contents of the ‘utility’ directories 
(‘/home/rd/traffic_export/’, ‘/home/rd/music_export/’, etc) on a completely 
different host (a Windows-based one would work fine) and mounting those shares 
remotely. That would greatly reduce the attack surface on the Rivendell system.

As for ‘/var/snd’, it’s a Really Bad Idea to have that mapped through Samba, 
even read-only. It’s isolated from direct user access for a reason.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| When playing Russian roulette the fact that the first shot got off  |
| safely is little comfort for the next.  |
| |
| -- Robert F. Feynman|
| "Personal Observations on the Reliability of the Shuttle"   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] jackd2 and DBUS

[Fred Gleason]

On Dec 3, 2021, at 05:41, Florent Peyraud  wrote:

> Do you have a target date for the final 4.0.0 release ?

2022Q1 is the current goal, but, in the words of a TV commercial widely aired 
in the US in the 1970s: “We sell no wine before its time.”

Yes, I’m THAT old…  :)

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] jackd2 and DBUS

[Fred Gleason]

On Dec 3, 2021, at 05:41, Florent Peyraud  wrote:

> Well. "unsupported' may not be the correct term. I've read some ML posts 
> talking about this options not being supported, but probably they meant it 
> did not represent the most widely used configuration.

That’s certainly true in the JACK developer community, where promiscuous mode 
is regarded as a rather exotic, rarely used feature. It makes sense when you 
remember that the original (and still overwhelmingly most common) use case for 
JACK is what I call the “recording studio” workflow. A recording engineer comes 
in in the morning, fires up the gear for today’s session, starts up the various 
apps, hooks up all the signal flows, etc. The musicians arrive, set up all of 
their kit, check everything out. The session recording gets done. Then, 
everybody tears everything down and goes home for the night. Tomorrow, repeat. 
Etc. In that context, the same-user-does-everything rule makes perfect sense.

Rivendell’s use case is extremely different. There, we want JACK to be a 
system-wide service, that starts when the computer boots up and then runs 
continuously (sometimes for MONTHS or longer), just doing its job in the 
background, taking care of all users. This is definitely a niche use case from 
JACK’s POV.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| Everything in war is very simple. But the simplest thing is |
| difficult.  |
| |
| -- Carl von Clauswitz   |
| "On War"|
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] jackd2 and DBUS

[Fred Gleason]

On Dec 1, 2021, at 04:27, Florent Peyraud  wrote:

> I would like to mimic this behavior in order to make rivendell service 
> (well... caed) start Jack this way with an external scirpt, but it fails when 
> trying to connect jack. The logfile says "Unable to communicate with JACK 
> server". Obviously, the actual jack server may take too much time to launch 
> and it is not ready when caed tries to connect. DBus provides a way to check 
> the status of jack. Maybe just a pause could be sufficient to allow jack to 
> start before trying to connect to it.

Interesting idea. What would be the advantages of this approach over the 
existing method of starting jackd(1) by having caed(8) fork() a process?


> Would it be possible to take this way of launching jack through DBus into 
> account so that it can be started at boot time with caed instead of waiting 
> for a user session to begin ?

We can already do this in the existing implementation.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] jackd2 and DBUS

[Fred Gleason]

On Dec 2, 2021, at 08:25, Florent Peyraud  wrote:

> unfortunately, either promiscuous mode in jack or system-wide daemon in 
> pulse-audio are configurations not recommended nor supported. And as I'm 
> trying to provide a solution for average users and rivendell administrators, 
> who are not necessarily system administrators, I would like to avoid as much 
> as possible unsupported or not recommended solutions. Moreover, since it 
> deals with shared memory, relaxing permissions on such files may introduce 
> security flaws.

Well, it all depends on your use case. But first, the low-hanging fruit: 
PulseAudio.

The use case for which PulseAudio was designed is ‘general desktops’ —i.e. 
playing the various beeps, boops and other sound effects generated by a GUI in 
the course of its normal operation when running typical ‘office automation’ 
type applications (web browsers, word processors, etc). As such, it has no 
place on a system designed to handle pro audio. It’s one of the first things I 
typically disable on any new Rivendell system.

As for JACK’s promiscuous mode, I’m not quite sure what you mean by calling it 
‘unsupported’. It’s present in the stock tarballs and binary downloads 
available at the canonical JACK GitHub site, so it’s certainly ’supported’ by 
the primary JACK developers. Whether its use is *appropriate* in a given 
situation is a matter of professional judgement. Does it open new avenues by 
which a system could be compromised in some way? Sure. So does giving a user an 
account on the system. So does turning on the power on the computer in the 
first place. I think the more relevant question to ask is: does it provide 
additional capabilities sufficient to justify the additional risk? The standard 
security principle of ‘least privilege’ holds that a user should have no more 
power on a system than the minimum necessary to do their required tasks. Given 
that Rivendell's previous, “non-promiscuous mode” JACK setup required that 
users run all JACK audio applications as ‘root’, I have to imagine that this 
change makes for a vastly improved security posture in general.


> By the way, I could not find a way to start Jackd in promiscuous mode through 
> dbus. If you have any clue, I would be pleased to test it

Unfortunately, the only way I’ve found to enable it is to define a 
$JACK_PROMISCUOUS_SERVER variable in the environment and then export that to 
jackd(1) as well as every audio application that will be using it. There are a 
number of drawbacks to this approach, the primary one in Rivendell’s case being 
that there is no easy way to give the feature a convenient user-facing ON/OFF 
switch (with, say, a checkbox in RDAdmin). Instead, it’s got to be baked-in to 
a number of static configuration files on the system. There are various values 
that can be given to that environmental variable that influence how it works; 
see the ENVIRONMENT section of the jackd(1) man page for specifics. AFAICT, 
there is no way to enable/disable it via dbus.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
|   Liberty is always dangerous, but it is the safest thing we have.  |
| |
|  -- Harry Emerson Fosdick   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] jackd2 and DBUS

[Fred Gleason]

On Dec 2, 2021, at 05:20, Alejandro olivan Alvarez 
 wrote:

> I'm posting new reply on this thread since, to my joy, as of beta4 commit 
> https://github.com/ElvishArtisan/rivendell/commit/3c4e2bd6d7dda1a730d1d8f6fb6754bb76d1530d
>  
> 
>  released tonight, the whole picture regarding Rivendell/Jackd integration in 
> recent systems may very much change for some of us Jackd fans: Rivendell is 
> coming now with out-of-the-box promiscuous mode support...  yay!!! :-D

Wow Alejandro, that was fast! I committed that to Git less than an hour ago.  :)


> So, it is time now to drop old hackish practices and switch to the 
> intended/ortodox packaged ones for the jackd integration with promiscuous 
> mode, which raises me some questions (at this point, I guess just Fred can 
> answer) about overall how the new picture is:
> 
> - Does a rivendell handled jackd instance (defined in RDConfig) automatically 
> run in promiscuous mode for the 'audio' GID? or has to be somehow 'enabled'?
> 
> - While regular users are already set as 'audio' members (very clever move 
> selecting audio as the promiscuous GID!), now the package seems to be 
> handling the environment variable part, pointing to the 'audio' GID, but... 
> is it system wide? or does user-space launched applications have to 
> initialize it?

First off, let’s be clear that the changes we’re talking about here apply to 
Rivendell 4.x ONLY. Previous Rivendell versions (v3.x and earlier) are NOT 
affected.

That said, Rivendell v4.x packages now define a ‘magic’ environmental variable 
($JACK_PROMISCUOUS_SERVER) that causes the JACK subsystem to relax the ‘all 
clients must be run under the same user as the server’ requirement, thus 
eliminating the need to run non-Rivendell audio apps as the ‘root’ user. With 
two caveats (see below), this should ‘just work’, with no other special 
configuration needed.

Caveat 1: The version of the JACK server installed by default by the standard 
Rivendell CentOS 7 installer (jack2-1.9.9.5) does *not* support promiscuous 
mode, so you will need to update that component in order to make use of this 
capability. Fortunately, that’s easy to do. Just get a root shell and run the 
command:

yum update jack2

Caveat 2: When I mentioned ‘Rivendell v4.x packages’ above, I was being very 
specific: Rivendell installations that are done by package managers (yum, dpkg, 
apt, etc) do everything automatically. However, users who are installing 
directly from source (such as those currently testing recent code changes in 
Git) will need to do an extra step: after doing ‘make install’, you’ll need to 
copy a small configuration file from ‘conf/rivendell-env.conf’ in the source 
tree to the ‘/etc/profile.d/‘ directory. This only needs to be done once.


> Thank you very much for such a new feature!

You’re welcome!

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| Never give in. Never stop. Fix bugs. Add features. Iterate. To the  |
| end of time. For real? Yeah. For real.  |
| |
|   -- Daniel Stenberg|
|   Stackoverflow post, 28 April 2019 |
|-|


___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Samba configuration question

[Fred Gleason]

On Nov 30, 2021, at 16:59, Jason McMullan  wrote:

> I'm on Rivendell 3.6.2, is there information on the default samba 
> configuration somewhere in the ops and admin guide or somewhere else? I think 
> I need to make some changes but I don't want to break anything. I believe 
> it's currently running the configuration that comes with a new install of 
> Rivendell.

If you used the standard Paravel installer, then there should be five CIFS 
shares configured by default. They are:

\\COMPUTERNAME\rd_xfer  Local 
path: /home/rd/rd_xfer
\\COMPUTERNAME\music_exportLocal 
path: /home/rd/music_export
\\COMPUTERNAME\music_importLocal 
path: /home/rd/music_import
\\COMPUTERNAME\traffic_export  Local 
path: /home/rd/traffic_export
\\COMPUTERNAME\traffic_import  Local 
path: /home/rd/traffic_import

By default, all of these are configured to be part of the ‘RIVENDELL’ workgroup 
and be accessible to the ‘guest’ user. That can be changed by modifying the 
settings in ‘/etc/samba/smb.conf’ (the standard Samba configuration file).

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Understanding Fade-UP and Fade-Down markers

[Fred Gleason]

On Oct 27, 2021, at 22:52, Chuck  wrote:

> Adding a +1 for this comment.  I am no longer in the commercial end of the 
> business, but rather, with a non-comm; however, I would think the fade up and 
> down ability is more important than ever.  The 2 biggest radio chains 
> operating in town have eliminated the job of production director and the 
> production studios are no longer maintained with their switch to contract 
> engineers, who are only called when something in the main studio dies 
> completely.  Whereas the production director used to comb and massage every 
> bit of audio that was carted, including the segue cue at a cart’s end, audio 
> is now added with no production pre-prep at all.
> 
> In fact, we do not have a production department, either.  We don’t play the 
> count-off or extraneous studio talk prior to the musical start of any song 
> (except for “Daydream Believer”), and we fade out of any applause quickly.  
> All that is done with the fade up and down markers.  I would think with the 
> contraction of jobs in commercial radio the ability to fade within Rivendell 
> would be more important today than in the past, when everything on-air, first 
> passed through a production department.

Some very helpful comments! The original Rivendell design (ca. almost twenty 
years ago, yeeks!) did indeed explicitly posit the preproduction of all 
elements before they were loaded into the automation. Sadly though, your 
experience does seem to have become the mainstream reality in many facilities 
today.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Understanding Fade-UP and Fade-Down markers

[Fred Gleason]

On Oct 25, 2021, at 11:19, Alejandro olivan Alvarez 
 wrote:

> Regarding Fade-Down, I think this is the easy one: I understand that, 
> whenever you put the mark on, RDAirplay, when reaching the mark, will start 
> unconditionally to fade down, FROM that point, onwards... If that's the case, 
> It's unclear to me to which level the fading down will reach (I asume -40dB , 
> or whatever 'mute' level the machine is at) and how long will take the fading 
> lasts (to the end of the song, linearly, for some amount of predefined time, 
> linearly, etc). The way I imagine fade-down use-case, it is meant to be put 
> close to the end of the song (so I can have a trailing bass drum base faded 
> down)... any hints? Am I very wrong?
> 
> Regarding Fade-Up, I'm quite confused... what is supposed to happen in 
> RDAirplay at this mark? if It will start fading up, to full level (0 db I 
> guess) FROM that point on, what is the level before it? does the presence of 
> such mark imply that everything before the mark gets muted? or, on the 
> contrary, the mark indicates the point where/when full level is reached 
> AT?... and, if so, where in time does the fading up starts? could someone 
> clarify?

The ‘base points’ for FadeUp and FadeDown are the ‘Start’ and ‘End’ markers, 
respectively; with the ‘mute level’ being (rather arbitrarily) defined to be 
-46 dBFS (-30 dB from the “reference level” as shown by Rivendell’s meters. The 
fades (both up and down) are logarithmic, meaning that they should be perceived 
as being “uniform” to the typical human listener.

With all of that said, I’ve found that FadeUp and FadeDown are very seldom used 
at most Rivendell sites. There are a couple of niche cases, but they are quite 
rare. Were I redesigning the cart/cut model from scratch, I would very likely 
drop those two functions entirely.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] RHEL 8 alternatives

[Fred Gleason]

On Oct 20, 2021, at 10:05, Andy Higginson  wrote:

> Do we have any consensus yet as to which of the RHEL derivatives is the best 
> to go for in terms of installing Rivendell 4?  There has been mention of 
> Rocky Linux, Oracle Linux and AlmaLinux.  Are any of these a recommended 
> derivative to use or should we just opt for RHEL?

In theory (heh, heh), they should all work exactly the same as far as Rivendell 
is concerned. That said, I have seen some apparent oddities with kernel module 
compatibility with at least one (RockyLinux). For that reason, as of the latest 
beta build (Beta3), I have gone to generating all RPMs and other binaries on 
real, honest-to-god RHEL 8, which is also now my primary testing environment 
for same.

WRT the “clones”, it’s worth bearing in mind that it’s still pretty early days 
for them; I imagine that all of them are still in the process of shaking down 
various compatibility issues. Compatibility will presumably improve.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| At the beginning of the week, we sealed ten BSD programmers into a  |
| computer room with a single distribution of BSD Unix. Upon opening  |
| the room after seven days, we found all ten programmers dead,   |
| clutching each others' throats, and thirteen new flavors of BSD.|
| |
|  -- Anonymous   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell v4.0+ going forward....

[Fred Gleason]

On Oct 14, 2021, at 16:01, Timothy Elwell  wrote:
> 
> I assume like any dist-upgrade requires the changes to the repositories. I 
> did just notice my 3 system (I just updated the other day after a drive and 
> power supply crash many many months back) went from the beta 3 to the current 
> 3.6.2 (might be off on the last dot of that version). Will the 4 beta's do 
> the same, being able to update from the 4 beta to the 4 release when it comes 
> out?

It’s always good practice to start with a new install when moving from a beta 
to a production setup. That’s because the beta setups are testing not only 
Rivendell but the installer system itself. Sometimes significant issu are found 
in those as well. (See https://github.com/ElvishArtisan/rivendell/issues/737 
for a current example).


> Considering for new not-currently-production builds to get ahead on it. And 
> while I can reinstall and start over, I try to not have to do any more of 
> than than necessary.

And, of course the new UbuntuStudio support opens up options for “in-place” 
major distro upgrades. I haven’t even started experimenting with that yet.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell v4.0+ going forward....

[Fred Gleason]

On Oct 13, 2021, at 13:43, Timothy Elwell  wrote:
> Just curious as I start building new machines again...with the coming 
> changes/end to CentOS as we know it, is there an idea on the base platform 
> going forward for the appliance? Obviously, there's still instruction for 
> CentOS and now Ubuntu Studio. Didn't know if the aim was toward studio or if 
> the aim is something else not mentioned. 
> 
The Rivendell Project will continue to support RHEL/CentOS 7 until it hits End 
of Life (currently set for 30 June 2024). In addition to that, we are adding 
support for v4.x to two additional distros: UbuntuStudio (LTS releases only) 
and RHEL 8.

> I've been on v2+ and 3+ (CentOS) for a while and have liked the appliance way 
> of life with upgrades a simple 'yum update' away. Yeah, I can build and 
> compile and have done plenty of that but, for ease of use, the appliance has 
> been pretty much bullet proof for me, so I've become...oh, let's call it 
> complacent (lazy is probably more accurate! Ha!) 
> 
> 2nd question, will the Riv 4 beta's be upward compatible to the full release 
> when released or will it be like the 3 beta the more/less required a full 
> re-install? 
> 
It’ll take slightly more than just a yum(8) invocation to move from v3.x to 
v4.x. At a minimum, you’ll need to change one of software repositories to pull 
from a different location. It’s possible that other steps may required as well; 
detailed instructions will be available when we get to that point.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Rivendell v4.0.0beta3

[Fred Gleason]

On behalf of the entire Rivendell development team, I'm pleased to
announce the availability of the fourth public beta release of the next
major version of Rivendell, v4.0.0beta3. Rivendell is a full-featured radio
automation system targeted for use in professional broadcast
environments. It is available under the GNU General Public License
version 2.

From the 'NEWS' file:
*** snip snip ***
   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.
*** snip snip ***

New installations of Rivendell v4.x can be generated using one of the following 
online installers:

For RedHat/CentOS 7:
https://software.paravelsystems.com/howtos/CentOS/7rd4/ 


For UbuntuStudio 20.04 LTS “Focal Fossa”: 
https://software.paravelsystems.com/howtos/ubuntu/focal/ 


This release also sees the debut of an additional fully supported distribution: 
Red Hat Enterprise Linux 8 (RHEL 8). Installation instructions can be found at:
https://software.paravelsystems.com/howtos/rhel/8rd4/

If you have already installed a previous Rivendell v4.x beta, you can upgrade 
that installation to v4.0.0beta2 by means of the following commands:

For RedHat/CentOS 7:

sudo yum clean expire-cache
sudo yum update rivendell

For UbuntuStudio 20.04 LTS “Focal Fossa”: 

sudo apt update
sudo apt upgrade rivendell

Please feel free to spin up either environment and put the system through its 
paces. Please create an Issue report for any problems found at:

https://github.com/ElvishArtisan/rivendell/issues 


Be sure to mention both the version of Rivendell and distribution used.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
|Opportunity is missed by most people because it is dressed in|
|overalls and looks like work.|
| |
|  -- Thomas Edison   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell Appliance Installer with RAID options

[Fred Gleason]

On Aug 11, 2021, at 23:44, Bruce Lee Mones  wrote:

> I remember before there is an appliance installer with RAID options included. 
> Is this still available? Where can I download the installer?

No longer available I’m afraid. That was based on CentOS 6, so is quite 
unlikely to work with modern hardware anyway (CentOS 6 went EoL almost a year 
ago). You can, of course, configure RAID setups on CentOS 7 when doing the OS 
install.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Automated Library Ingest

[Fred Gleason]

On Aug 11, 2021, at 08:38, Alan Smith  wrote:

> I have not used RD's dropbox feature yet, but I didn't consider RDCatch can 
> pull files locally, and looks like going through the manual didn't know it 
> could do smb either.  I use RDCatch, but have only used it for http and ftp 
> so far.

Direct SMB/CIFS support in RDCatch is highly conditional on the specific 
version of Rivendell in use; the last Rivendell version that explicitly 
supported it was v1.7.0 (released on 22 February 2010) . For modern setups, 
it’s generally much more robust if you set up a CIFS mount point on the host 
system and then use a ‘file:’ style URL to point to that.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Howto set UI Languaje/Translation

[Fred Gleason]

On Aug 5, 2021, at 03:43, Alejandro olivan Alvarez 
 wrote:

> I actually read a little on the wiki about making translations ... I have to 
> calmly refresh my rusted .po skills, re-read the language/translation 
> documentation on rivendell, and evaluate whether I could help... I definitely 
> would like very much to help translating to Spain-Spanish, Catalan (And 
> eventually I know people that could also provide me translation to Euskera)

It’s actually quite a bit easier than that. Qt has some very nice utilities 
that make it easy for translators to work without having to be dev experts. For 
an overview of the process, see:

https://doc.qt.io/qt-5/qtlinguist-index.html

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Howto set UI Languaje/Translation

[Fred Gleason]

On Aug 2, 2021, at 11:30, Alejandro olivan Alvarez 
 wrote:

> This one is probably simple...but I'm failing to see it: how can I switch 
> Rivendell UI to, let's say, Spanish?
> 
> Although I'm from Spain, I always work with En/Us system/Installs, I'm 
> completely used to it ... but how if I would like to have the UI environment 
> in, let's say, Spanish (or any other of the available translations)?
> 
> I don't see an option in RDAdmin at first glance... I'v googled around, and 
> I've found an article on the wiki on howto create translations, which could 
> be very interesting, but... how to apply/activate on of those translations?

For standard production setups, that’s an OS-level setting. The easiest way to 
do it on CentOS 7 to use the ‘system-config-language’ tool. You may need to 
install it; just do (from a root shell):

yum install system-config-language

However, if you’re just hacking Rivendell and don’t want to change the whole 
system over to a different locale, you can do it by setting the ‘LANG’ 
environmental variable to the desired language. For example, to switch to 
Español, you could open a shell (non-root) and do something like:

export LANG=es_ES.UTF-8

Rivendell modules run from that same session will then attempt to use the 
appropriate translation.

While we’re on this subject: the translations currently in Rivendell are 
extremely long in the tooth, with the last updates done way back in the v2.x 
era, so I suspect that coverage for any given language is quite ragged. As we 
converge towards a production v4.x release, we’ll shortly be in a position to 
start soliciting volunteers to update translations. Stay tuned!

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell v4.0.0beta2

[Fred Gleason]

On Aug 2, 2021, at 01:05, Stan Fotinos  wrote:

> Thank you for the update, look forward to testing. I have a simple question, 
> how do you change the user logo in RDAirplay?

At present, that is hard-coded. It will eventually turn into a 
user-configurable option (in RDAdmin->ManageUsers/->RDAirPlay).

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell v4.0.0beta2

[Fred Gleason]

On Aug 1, 2021, at 01:18, Gavin Stephens  wrote:
> What are the main changes to the level meters? 
> 
> Sorry I don't have a spare box here to put 4 on yet but working on it.
> 

Instead of a single meter that displays the sum of all signals, there is a 
meter for each configured output port. Each meter can also be assigned a name, 
which then appears on each button that is sending audio to that channel. The 
idea is to allow a better sense of ‘what' is playing out ‘where’. 

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Rivendell v4.0.0beta2

[Fred Gleason]

On behalf of the entire Rivendell development team, I'm pleased to
announce the availability of the third public beta release of the next
major version of Rivendell, v4.0.0beta2. Rivendell is a full-featured radio
automation system targeted for use in professional broadcast
environments. It is available under the GNU General Public License
version 2.

From the 'NEWS' file:
*** snip snip ***
   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.
*** snip snip ***

New installations of Rivendell v4.x can be generated using one of the following 
two online installers:

For RedHat/CentOS 7:
https://software.paravelsystems.com/howtos/CentOS/7rd4/ 


For UbuntuStudio 20.04 LTS “Focal Fossa”: 
https://software.paravelsystems.com/howtos/ubuntu/focal/ 


If you have already installed a previous Rivendell v4.x beta, you can upgrade 
that installation to v4.0.0beta2 by means of the following commands:

For RedHat/CentOS 7:

sudo yum clean expire-cache
sudo yum update rivendell

For UbuntuStudio 20.04 LTS “Focal Fossa”: 

sudo apt update
sudo apt upgrade rivendell

Please feel free to spin up either environment and put the system through its 
paces. Please create an Issue report for any problems found at:

https://github.com/ElvishArtisan/rivendell/issues 


Be sure to mention both the version of Rivendell and distribution used.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Rivendell v3.6.2

[Fred Gleason]

On behalf of the entire Rivendell development team, I'm pleased to
announce the availability of the next production release of the next
major version of Rivendell, 3.6.2. Rivendell is a full-featured radio
automation system targeted for use in professional broadcast
environments. It is available under the GNU General Public License
version 2.

From the 'NEWS' file:
*** snip snip ***
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.
*** snip snip ***

Details and source code are available at 
https://github.com/ElvishArtisan/rivendell/releases 
.


Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] RDAdmin will not start

[Fred Gleason]

On Jul 17, 2021, at 10:10, Jesse Jones  wrote:

> Something went wrong in restoring a copied database through RDAdmin - the gui 
> "flashed" and now the GUI for RDAdmin refuses to open - so I can't even roll 
> it back to a previous version.
> 
> When I invoked RDAdmin as root in the command line - I get multiple lines of:
> invalid SQL or failed DB connection[Table 'Rivendell.VERSION' doesn't exist 
> QMYSQL3: Unable to execute query]: select DB from VERSION
> 
> I am nonconversant with mySQL mechanics so I need neophyte instructions on 
> how to get this ON AIR machine back on line.  The CentOS is working - only 
> Rivendell is down.

To restore a DB backup “manually” from the command-line, run the following 
commands from a non-root shell on the machine running MySQL:

echo drop\ database\ Rivendell\; | mysql -u -p
echo create\ database\ Rivendell\; | mysql -u -p
cat  | mysql -u -p Rivendell

Then get a root shell and restart the Rivendell service by doing:

service rivendell restart

N.B. — the above procedure will COMPLETELY REMOVE the previously loaded 
database.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] RDAirplay Full Log View UI Details?

[Fred Gleason]

On Jul 16, 2021, at 08:51, Alejandro olivan Alvarez 
 wrote:

> I've been keeping an eye on the changes on the Full Log View widget on 
> RDAirplay for a while while it was playing and I think that there's more 
> information there than the one I explained on the operations guide at pag.44 
> ... Has someone some information/guide about that?
> 
> I mean... I see played events get mid-grayed to the past, but skipped events 
> get white... isn't it?

They remain white, because they are still playable (just do ‘make next’ to 
them), whereas greyed-out elements cannot be played (the log will skip over 
them if you try. I know of at least one ‘morning zoo’ type program that makes 
extensive use of this feature to keep track of which spots have been played 
while rearranging the play-out order of said spots in order to join to various 
external live elements (network news, etc) in a timely fashion.


> The deep-green is the playing one, OK, and the light green the next 7 ones 
> (For Main Log, the ones in the left side buttons)... but why do 'T's in the 
> bold-blue lines are removed, but not removed if the blue event is skipped?

They should probably be removed. Call it a bug.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Send Now-Next MACRO behavior

[Fred Gleason]

On Jul 14, 2021, at 13:21, Alejandro olivan Alvarez 
 wrote:
> It's not entirely clear to me the 'machine stop-down completely' (probably 
> still not enough radio/Rivendell jargon in my mind) maybe I'm wrong, but, 
> translating it to me as 'completelly ending the current playback', that would 
> somehow explain the behavior I experienced.
> 

‘Stopped down’ means that the log machine has a log loaded, but the log is not 
currently playing anything. Typically done when ‘live’ or remotely originated 
programming is being aired.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Test 1

[Fred Gleason]

Please disregard. This is a test.

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Send Now-Next MACRO behavior

[Fred Gleason]

On Jul 13, 2021, at 11:33, Alejandro olivan Alvarez 
 wrote:

> A curious case is when I schedule a macro cart in the log that stops the log 
> machine and switches to an external audio source, the idea is to do a last 
> now update so the resulting Icecast2 stream will display something like 
> 'foo - is now live from bar' ... I can see the 'SN now 1 1X' on the 
> machine, but the pypad never 'catches' the update.

The PAD for the current ‘default Now & Next cart’ that the ‘SN’ macro sets is 
emitted only when the referenced log machine stops-down completely. It will not 
override the PAD sent by currently playing cart(s).

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
|Beware of Programmers who carry screwdrivers.|
| |
|  -- Leonard Brandwein   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Updating scheduler codes via SQL

[Fred Gleason]

On Jul 14, 2021, at 05:14, Alejandro olivan Alvarez 
 wrote:

> I have messed a little with rivendell database, quite successfully, but only 
> for query/read operations ... altering/writing directly the database of such 
> a complex application is for the brave :-)

Just to amplify Alejandro’s point: directly modifying the Rivendell database is 
NOT A SUPPORTED METHOD for making changes in Rivendell! Specifically, the 
database schema CAN and DOES change between different versions of Rivendell; 
meaning that the update method that worked perfectly three months ago could end 
up NUKING YOUR DATABASE next time around.

A much better and safer method for making these sorts of site-specific bulk 
changes is to write a script that uses Rivendell’s WebAPI. See:

http://opsguide.rivendellaudio.org/apis/web_api.pdf

The Web API is a documented, public and above all stable interface; using it 
will allow you to write scripts that won’t break across different versions of 
Rivendell.

N.B. — If you insist on writing changes directly to the DB, be sure that you 
have a known good backup of it first. The sanity and gray hair (not to mention 
job) that you save may be your own.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
|Beware of Programmers who carry screwdrivers.|
| |
|  -- Leonard Brandwein   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] 12 hour time

[Fred Gleason]

On Jul 2, 2021, at 11:54, Mark Murdock  wrote:

> Somebody please show me how to code a writefile pypad script so that it 
> displays 12 hour time instead of 24 hour time. What I have now is:

See:

http://opsguide.rivendellaudio.org/html/appendix.metadata_wildcards.html#sect.metadata_wildcards

and also:

http://opsguide.rivendellaudio.org/html/appendix.metadata_wildcards.html#table.metadata_wildcards.datetimes


> FormatString=%g %d(h:mm) %t - %a\n
>  
> I know it involves the “AP” or “ap” time specification, but I don’t know how 
> to write the format string.

Just add the “AP”/“ap” where you want the meridian indicator to be. For example:

FormatString=%g %d(h:mm AP) %t - %a\n

Should render something like:

MyGroup 10:15 AM MyTitle MyArtist

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Troubleshooting setup of PyPAD

[Fred Gleason]

On Jul 2, 2021, at 07:54, Alejandro olivan Alvarez 
 wrote:

> I'm playing with the PyPAD stuff of Rivendell.
> 
> So far, I've managed to have an script running... so far the problems I've 
> had to evercome (Debian Stable Buster install) were:
> 
> - The documented (on this list) Centos/debianish misplacing of pypad.py which 
> needs to be copied to /usr/lib64/rivendell/pypad
> 
>  cp /usr/lib/python3.7/site-packages/pypad.py /usr/lib64/rivendell/pypad

That doesn’t look right, on a couple of levels. 

First, ‘/usr/lib64’ is a RedHat-ism. Ubuntu at least doesn’t seem to use that 
convention at all, but rather installs binary linkable objects under ‘/usr/lib’ 
regardless of the target arch. I’ve not actually checked on Debian, but I’d be 
somewhat surprised if things are different there as Ubuntu seems to copy Debian 
pretty closely in general file layout.

Second, while the PyPAD scripts themselves (think of them as ‘user programs’) 
do indeed need to go in ${libdir}/rivendell/pypad (which evaluates to 
‘/usr/lib/rivendell/pypad’ on Debian-is setups), the PyPAD *library module* 
should go in the default system location so it will be in Python’s search path. 
On Ubuntu, this location is ‘/usr/lib/python3/dist-packages’.

N.B. Python supports the concept of having multiple parallel installations of 
different versions, each of which get their own orthogonal module store. On my 
UbuntuStudio 20.04 setup, the default installation has installed no less than 
four different versions of Python, resulting separate module paths for each (in 
my case, ‘/usr/lib/python2.7/dist-packages’, ‘/usr/lib/python3/dist-packages’, 
‘/usr/lib/python3.8/dist-packages’ and ‘/usr/lib/python3.9/dist-packages’). 
These locations appear to be a Debian-ism inasmuch as Automake's 
AM_PATH_PYTHON() macro doesn’t recognize them, instead using the expected 
standard Python defaults. At present, there is a nasty hack in ‘configure.in’ 
(lines 290-305) that attempts to detect this situation and install things the 
‘Debian way’ if necessary. I would love some feedback on how this works on 
various Debian-ish setups (or, even better, PRs that improve the heuristic).


> I've created a copy of the included icecast2.py and also the related 
> icecast2.exemplar. So far the script works, green dot and no errors. A ps on 
> console shows the script running:
> 
> root@debian:~# ps aux | grep pypad
> pypad 4095  3.9  0.1 285108 28624 ?Sl   12:18   2:38 
> /usr/sbin/rdpadengined
> pypad 4097  4.2  0.1 211368 28412 ?S12:18   2:50 
> /usr/sbin/rdrssd
> pypad 9777  0.0  0.1  40812 23948 ?S12:25   0:00 
> /usr/bin/python3 /usr/lib64/rivendell/pypad/pypad_icecast2_8000.py localhost 
> 34289 $1
> root 22462  0.0  0.0   6208   824 pts/1S+   13:25   0:00 grep pypad
> 
> The TCP port for metadata appears listening:
> 
> root@debian:~# netstat -tnlp | grep 34289
> tcp0  0 0.0.0.0:34289 0.0.0.0:*   LISTEN  
> 4073/rdpadd
> 
> 
> I've setup username/password/port/mountpoint on the configuration... 
> apparently, OK... now, the problem:
> 
> I've no song update on the Icecast2 server

Ok, first thing to do is verify that your Icecast2 system will accept metadata 
updates from your PyPAD host. Icecast is famously picky in this regard; updates 
*must* originate (or appear to it to be be originating) from the same source IP 
address as the encoder client originating the stream; updates that fail to meet 
this criterion are ignored. A good way to test this is to attempt to send a 
metadata update *from the same system that is running the PyPAD script* 
manually via a curl(1) command of the form:

curl -u source: 
http://:/admin/metadata?mount==updinfo=

where:

 - The hostname or IP address of the system running Icecast

 - The TCP port number of the Icecast instance

 - The mountpoint of the stream

 - The mount point password.

 - The string to set, encoded as specified in Section 2 of RFC3986

For example, to set a string of "The Beatles - Hey Jude” at an Icecast instance 
running at "icecast.example.com:1234" with a
mountpoint of “MyStream” and a password of “hackme", the URL would be:

curl -u source:hackme 
http://encoder.example.com:1234/admin/metadata?mount=MyStream=updinfo=The%20Beatles%20-%20Hey%20Jude

If this doesn’t work, when sent *from the same system that is running the PyPAD 
setup*, then you have an Icecast setup problem, which will need to be resolved 
before proceeding to configuring the PyPAD stuff.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
|   

Re: [RDD] Fresh Beta 4 on Fresh CentOS no ASI detection

[Fred Gleason]

On Jun 22, 2021, at 19:02, Aaron M <99.5engin...@gmail.com> wrote:
> 
> Screenshots showing what is shown.
> On Jun 22, 2021, at 6:00 PM, Aaron M <99.5engin...@gmail.com 
> > wrote:
> How do I get Rivendell to use the PCI version ASI 5111 soundcard for playout?
> 
> 
> Just installed clean Rivendell Beta 4 on a fresh install of CentOS, per 
> instructions.
> 
> 
> Rivendell only sees the onboard ALC892 Analog sound device.
> 
> 
> This isn't my only question, but it needs to be solved before we start adding 
> media files.
> 
> 
> My next question is mass import of 9 categories of music, plus drops and 
> liners.  IDs are fine imported 1 at a time.

You’re going to need to back down to an earlier version of the AudioScience HPI 
driver, because the ASI5111 is past end-of-life and no longer supported in the 
latest driver. See my original reply to this thread for the details.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] RDLogEdit v3.5.0 not showing new Services

[Fred Gleason]

On Jun 29, 2021, at 17:11, Angelena Chapman  wrote:

> I made a new Service in v3.5.0, but in RDLogEdit I can only see the old 
> Services. 
> 
> When I do a Log Report there, I can see the logs I created for the new 
> Service. However, the Service does not appear in the dropdown at the top and 
> those logs are not in the list of logs. 

RDAdmin->ManageUsers->[user], then touch ’Service Permissions’.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Important details missing from the OpsManual PDF

[Fred Gleason]

On Jun 29, 2021, at 16:45, Aaron M <99.5engin...@gmail.com> wrote:

> The manual just shows the following unhelpful information regarding 
> generating reports...
> 
> 
> https://ibb.co/H29K3Z2 
> 
> 
> What should be included is on the RivendellAudio.org  RivendellAudio.org> site
> 
> 
> https://ibb.co/mzBfsL7 

You’re confusing two different types of reports. The passage you cite in the 
Operations Guide refers to the ‘built-in’ reports that are included in 
rdlogedit(1). The design pattern for those types of reports (several other 
modules have them is well) is simply to operate on the current context of the 
module and display its results using the selected report viewer (as specified 
in the ‘Report Editor’ field RDAdmin->ManageHosts->[hostname]. OTOH, the Wiki 
page entry is referring to ‘as played’ reports, which are designed to be highly 
configurable and can configured to automatically generate on a set schedule.


> I would think there should be some mention in the opsmanual pdf about the 
> format of the Admin:Manage Reports:  Export Path requirements.  I didn't 
> expect a path to include a filename template to be required because that 
> isn't mentioned in the opsmanual.pdf file.

Agreed that some overarching discussion about reports in general, including the 
fact that there are two different basic types, would be a Good Thing. A section 
in the ‘Rivendell Administration’ section that discusses configuring (as 
opposed to merely using) such would good too.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] RDImport Notifications

[Fred Gleason]

On Jun 26, 2021, at 20:28, wa7skg  wrote:

> While working on another issue, I took a look at /var/log/boot.log. I had 
> recently imported a bunch of music to the library with rdimport. I find these 
> entries in boot.log:
> 
> Jun 26 17:00:41 rd2 ripcd: sent notification: "NOTIFY CART MODIFY 35741" to 
> 239.192.255.72:20539
> Jun 26 17:00:41 rd2 ripcd: closed connection 4
> Jun 26 17:00:41 rd2 ripcd: cleaned up connection 4
> Jun 26 17:00:41 rd2 ripcd: added new connection 4
> Jun 26 17:00:41 rd2 rdxport.cgi: processing RDXPORT_COMMAND_TRIMAUDIO
> Jun 26 17:00:41 rd2 ripcd: sent notification: "NOTIFY CART MODIFY 35741" to 
> 239.192.255.72:20539
> Jun 26 17:00:41 rd2 ripcd: closed connection 4
> Jun 26 17:00:41 rd2 ripcd: cleaned up connection 4
> Jun 26 17:00:41 rd2 ripcd: sent notification: "NOTIFY CART ADD 35741" to 
> 239.192.255.72:20539
> 
> First, I don't understand why there are a bunch of Rivendell status stuff in 
> the boot.log to begin with.
> 
> Second, where/what is IP address 239.192.255.72 and why is Rivendell sending 
> any notifications to it? Is this a security thing? Is it required? Can I stop 
> it?

As Chris mentioned earlier, those are local (‘administratively scoped’ to be 
precise) multicast messages. Starting with v3.x, Rivendell uses those to notify 
modules that some object (cart, log, whatever) has been added/deleted/changed. 
In the example you quote, cart 35741 was changed. Say, rdairplay(1) had a log 
loaded that included that cart, it would know to update the widgets displaying 
that cart. Likewise, other Rivendell instances can receive these messages and 
keep their views up to date.

Yes, it is required for proper operation. The exact address used for such 
updates can be set in RDAdmin->SystemSettings, although the default value 
should be fine for the overwhelming majority of situations.

As for these entries appearing in ‘boot.log’, I couldn’t say. Doesn’t sound 
right!

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Fresh Beta 4 on Fresh CentOS no ASI detection

[Fred Gleason]

On Jun 22, 2021, at 19:00, Aaron M <99.5engin...@gmail.com> wrote:

> How do I get Rivendell to use the PCI version ASI 5111 soundcard for playout?
> 
> 
> Just installed clean Rivendell Beta 4 on a fresh install of CentOS, per 
> instructions.

Sounds like a driver issue. The ASI5111 was end-of-lifed by AudioScience a 
number of years ago, so is no longer supported in the ‘latest and greatest’ 
driver version.

Chances are good that you can use an earlier version and use the card 
successfully. First, get the driver RPM that you need. It's at:


http://static.paravelsystems.com/audioscience/centos/7/4.13.00-3/hpklinux-4.13.00-3.el7.centos.x86_64.rpm

Then, get a root shell, then remove the current driver by doing:

yum remove hpklinux

This will also want remove Rivendell. Go ahead and let it; we’re restore that 
back in a minute.

Now, install the downloaded driver by doing

yum install /path/to/downloaded/rpm

Then, reinstall rivendell:

yum install rivendell

Reboot, and you’re done.


> This isn't my only question, but it needs to be solved before we start adding 
> media files.
> 
> My next question is mass import of 9 categories of music, plus drops and 
> liners.  IDs are fine imported 1 at a time.

You are aware that this is a beta test version that you’ve installed (and a 
rather early one at that)? It might be a good idea to verify that it actually 
works as you need it to before investing a huge amount of time in loading up a 
production environment.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Sending RML Commands From Windows or Mac

[Fred Gleason]

On Jun 16, 2021, at 11:21, wa7skg  wrote:

> Is it possible to send an RML command from a Windows or Mac computer? 
> Specifically switcher commands?
> 
> I have a Broadcast Tools switcher connected to my Rivendell machine. I'd like 
> to be able to send commands to the switcher from the sanctuary sound booth to 
> switch from Rivendell to the live service. They have both Windows and Mac 
> computers, no Linux, in the sound booth.
> 
> I thought I had read about this somewhere, but can't find it now. Searching 
> these archives is not easy.

Just send the text of the RML to UDP port 5859 of the target Rivendell machine. 
You can use NetCat to do this on macOS, for example:

echo ST\ 1\ 2\ 3\! | nc -u 192.168.0.1 5859

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Switch Taking on ASI6114

[Fred Gleason]

On Jun 14, 2021, at 04:28, Alejandro olivan Alvarez 
 wrote:
> Mmmm... I get the point... I have no experience on those devices, but I 
> understand what you're depicting is kinda hard situation to handle from a 
> sysadmin / programmer point of view... hopefully those things feature some 
> way to check their status on their own.
> 
Most of them have some sort of external mechanism (physical or virtual) for 
ascertaining matrix state. Not all of them include that capability in the 
control API for third-party applications though.

The one big exception though is the ‘Local Audio Adapter’ driver (the very one 
that you’ve been attempting to troubleshoot), as that one exists as a purely 
internal Rivendell construct. Hmm…

> I'm aware that, although easy to say, implementing even a basic cli 
> capability of 'status report' on you internal audio routing/switcher daemon 
> (I guess caed?) would imply rather hard-to-implement features, such as some 
> kind of volatile or persistent storage on crosspoint status, levels, etc, 
> etc... all that on a very 'core' part of rivendell, and not of much help (if 
> any) on those 'autistic' devices.
> 
What say we add some reporting to syslog for the ‘Local Audio Adapter’ driver, 
so one could at least get some feedback on what Rivendell thinks the state of 
the routing matrix is? It wouldn’t be terribly useful operationally, but could 
simply troubleshooting at least.

> It would be very nice but (let's dream! :-), in the future, to have some kind 
> of equivalent to the GPIOMonitor  but for the internal audio 
> routing/crosspoint (caed?) engine 
> 
Very unlikely to happen in Rivendell, unfortunately. However, you might want to 
check out the ‘Drouter’ project, which provides exactly that. Rivendell has a 
switcher driver that will interface to it (’Software Authority Protocol’).

https://github.com/ElvishArtisan/drouter

Currently limited to Livewire devices, but there is some talk of adding support 
for others.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev