Re: [RDD] [RDP] Rivendell-prog mailing list

[Bemis, Andru]

As someone who signed up first for Rivendell-prog before realizing that
rivendell-dev was what I really wanted, I also concur. In fact, I never
quite knew what this list was for.

Andru Bemis

Producer & Host | The Chenango Sessions
Director | Cranberry Coffeehouse
Music Director | WBDY-LP 99.5 FM
Piano Technician | Binghamton Piano Rescue

557 Chenango St, Binghamton, NY 13901, USA
(269) 767-8235
he/him

On Tue, Feb 22, 2022, 12:23 PM David Klann  wrote:

> Hi Fred,
>
> I was confused by the two mailing lists when I first got involved with
> Rivendell, so I'm in favor of dropping the "-prog" list. And I concur
> with you that it seems the development action is on GitHub these days.
>
> +1 on the suggestion from me!
>
>~David Klann
>
>
> On 2/22/22 11:16, Fred Gleason wrote:
> > 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
>

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

Re: [RDD] RDCatch Wildcard Question(s)

[Robert Jeffares]

You may be able to set the week variable up before the download like

wn=$(date +%V); echo $wn <-- use V or W as appropriate

in front of the catch command

worst case a simple bash script will hook the audio in and you can deal 
with it locally using RDCATCH or DROPBOX



R

On 23/02/22 06:22, Alan Smith wrote:

What is the difference between %V and %W?

Also, is there a difference between a broadcast week and an ISO week?  
I've researched the subject, but its blowing up my brain.


The root of the issue is I am trying to set up an automated download 
via RDCatch, but the provider uses broadcast weeks in their filename.  
If I put the URL in without wildcards it works fine.  I plug in the 
wildcards and I'm getting invalid URL.


Thanks,


-Alan

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

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

Re: [RDD] RDCatch Wildcard Question(s)

[Mike Carroll]

I'd never heard of those, so I poked around some as well. Not sure it helps
any with your issue though.

Wikipedia has this for "broadcast calendar":
"The broadcast calendar is a standardized calendar used primarily for the
planning and purchase of radio and television programs and advertising.[1]
Every week in the broadcast calendar starts on a Monday and ends on a
Sunday, and every month has either four or five such weeks. Broadcast
calendar months thus have either 28 or 35 days."

and this:
"The key link between the broadcast and Gregorian calendars is that the
first week of every broadcast month always contains the Gregorian calendar
first of the month."
https://en.wikipedia.org/wiki/Broadcast_calendar

The Wiki article for "iso week year" is somewhat confusing, but I think
this is the main idea:
"Weeks start with Monday and end on Sunday. Each week's year is the
Gregorian year in which the Thursday falls. The first week of the year,
hence, always contains 4 January. ISO week year numbering therefore usually
deviates by 1 from the Gregorian for some days close to 1 January."
https://en.wikipedia.org/wiki/ISO_week_date

Regards, Mike

On Tue, Feb 22, 2022 at 9:22 AM Alan Smith  wrote:

> What is the difference between %V and %W?
>
> Also, is there a difference between a broadcast week and an ISO week?
> I've researched the subject, but its blowing up my brain.
>
> The root of the issue is I am trying to set up an automated download via
> RDCatch, but the provider uses broadcast weeks in their filename.  If I
> put the URL in without wildcards it works fine.  I plug in the wildcards
> and I'm getting invalid URL.
>
> Thanks,
>
>
> -Alan
>
> ___
> Rivendell-dev mailing list
> Rivendell-dev@lists.rivendellaudio.org
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] RDCatch Wildcard Question(s)

[Alan Smith]

What is the difference between %V and %W?

Also, is there a difference between a broadcast week and an ISO week?  
I've researched the subject, but its blowing up my brain.


The root of the issue is I am trying to set up an automated download via 
RDCatch, but the provider uses broadcast weeks in their filename.  If I 
put the URL in without wildcards it works fine.  I plug in the wildcards 
and I'm getting invalid URL.


Thanks,


-Alan

___
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

Re: [RDD] Auto restart after power failure.

[Bryan Burchfield]

Thank you both

Bryan Burchfield
Oldies 98.3 WMTY
WDEH AM-800
(423) 337-5025
mytrueoldies.com
wdehradio.com

On Tue, Feb 22, 2022, 10:46 AM Jake Tremper  wrote:

> In addition to ensuring BIOS is set to boot after power loss, and the
> Rivendell user account automatically logs in, we typically want rdairplay
> to start making sounds as soon as possible after the power comes back,
> perhaps even leading with a legal ID if in the US.
>
> First, make sure the correct log format is set to automatically load via
> rdadmin -> Hosts -> $(hostname) -> RDAirPlay -> Start/Stop Settings.
>
> How you proceed from here will depend on your log structure. For a
> hypothetical station that runs overnight music programming, it's pretty
> straightforward. You tell Rivendell to start playing in auto-mode (rmlsend
> PM\ "2"! ; rmlsend PN\ "1"!) as soon as it starts, and then at some point
> in your clocks should have a "make next" transition on an Event. This could
> be your top-of-the-hour legal ID, for example.
>
> So, in this scenario, the power comes back, the Rivendell computer boots,
> the rd user account automatically logs in, and then the script below fires
> on login. It will immediately start that day's log at midnight, and then
> align itself to the correct hour at the next "make next" style event. If
> you make a legal ID the very first thing in your log at midnight, you can
> even make The Commission happy with this setup.
>
> Here is the script I use to auto-start rdairplay. It checks for a lock
> file (".rdairplaylock") which could potentially be left-over from a dirty
> shutdown. If it finds an orphaned lock file, it will remove the that lock
> file and start rdairplay. I name this file "Rivendell_Airplay_Autostart.sh"
> so there's no chance of grep getting confused:
>
> #!/bin/bash
>
> if test -f "~/.rdairplaylock"; then
> ps faux | grep rdairplay | grep -v grep
> if [ ${?} -ne 0 ]; then
>   rm -f ~/.rdairplaylock
>  else
>   DISPLAY=:0 xhost +local:
>   rmlsend --to-host=$(hostname) MB\ ":0"\ "1"\
> "Multiple_instances_not_allowed"!
>   exit 0
> fi
> fi
> DISPLAY=:0 rdairplay &
> sleep 5
> rmlsend LB\ "Info for the label area can go here"!
> rmlsend PM\ "2"!
> rmlsend PN\ "1"!
>
> On Tue, Feb 22, 2022 at 5:18 AM Alejandro olivan Alvarez <
> alejandro.olivan.alva...@gmail.com> wrote:
>
>> Regarding your first question (fully automated auto-start of Rivendell)
>>
>> It is doable for sure, however, the actual details on how to achieve
>> that, very much depends and/or conditions on what pieces make up your
>> 'Linux' system (I assume that your hardware, has in BIOS the appropriate
>> setting to power-on after a power failure)
>>
>> As a general idea, you need to setup your session manager (which may
>> depend on what Desktop-Environment have you installed.. GDM, XDM, KDM,
>> Slim, etc...) to auto-login your user upon system boot.
>>
>> Once you achieve that, you have to setup that, upon login, your user
>> session automatically launches whatever software you need (and again,
>> depending on the environment, there are different ways to do that).
>>
>> As I think we can assume that you want RDAirplay going to air, apart of
>> having Rivendell daemons up and running, you need, by one side, to either
>> setup RDAirplay to automatically load on the LogMachines the last logs that
>> was loaded (a feature you can setup in RDConfig) or to script the loading
>> of the log you want using a MACRO. And then, make it to play This links
>> to your second question.
>>
>>
>> Commands to air in proper time:
>>
>> There are commands to do quite a lot of actions related to the thing you
>> want: you can launch a command that makes RDAirplay to play a cart, to play
>> the next cart in the log, or to 'push' one of the buttons of the Main log,
>> just to mention some...Rivendell Macro Language makes the whole thing
>> incredibly flexible!
>>
>> However, consider that, if properly taylored, a log, on its own, can go
>> to air 'by itself' if it has scheduled a cart to be aired on hard time (I
>> recommend you to look at the Start time types, transition types and,
>> overall, the behaviour of the logs on RDAirplay ) with a stop transition.
>>
>> Moreover, there's a wonderful module (RDCatch... I miss it very much in
>> Debian beta4) that is all about executing tasks (including for sure
>> executing a command) on the wallclock, so you don't need to have a
>> wallclock log dedicated to schedule hard time tasks. So, in RDCatch, if you
>> create a Macro cart that loads a certain log on a RDAirPlay log machine,
>> and starts its playout, and you schedule that cart on RDCatch... then, no
>> matter what, when the time comes, the cart will be executed)
>>
>>
>> Hope I gave you some clues on where to focus on.
>>
>> Best regards.
>>
>>
>> On 2/22/22 4:40 AM, Bryan Burchfield wrote:
>>
>> I am trying to figure out how to set my Linux operating system to
>> automically restart after a power failure and for RD Airplay to
>> automatically open 

[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] Auto restart after power failure.

[Jake Tremper]

In addition to ensuring BIOS is set to boot after power loss, and the
Rivendell user account automatically logs in, we typically want rdairplay
to start making sounds as soon as possible after the power comes back,
perhaps even leading with a legal ID if in the US.

First, make sure the correct log format is set to automatically load via
rdadmin -> Hosts -> $(hostname) -> RDAirPlay -> Start/Stop Settings.

How you proceed from here will depend on your log structure. For a
hypothetical station that runs overnight music programming, it's pretty
straightforward. You tell Rivendell to start playing in auto-mode (rmlsend
PM\ "2"! ; rmlsend PN\ "1"!) as soon as it starts, and then at some point
in your clocks should have a "make next" transition on an Event. This could
be your top-of-the-hour legal ID, for example.

So, in this scenario, the power comes back, the Rivendell computer boots,
the rd user account automatically logs in, and then the script below fires
on login. It will immediately start that day's log at midnight, and then
align itself to the correct hour at the next "make next" style event. If
you make a legal ID the very first thing in your log at midnight, you can
even make The Commission happy with this setup.

Here is the script I use to auto-start rdairplay. It checks for a lock file
(".rdairplaylock") which could potentially be left-over from a dirty
shutdown. If it finds an orphaned lock file, it will remove the that lock
file and start rdairplay. I name this file "Rivendell_Airplay_Autostart.sh"
so there's no chance of grep getting confused:

#!/bin/bash

if test -f "~/.rdairplaylock"; then
ps faux | grep rdairplay | grep -v grep
if [ ${?} -ne 0 ]; then
  rm -f ~/.rdairplaylock
 else
  DISPLAY=:0 xhost +local:
  rmlsend --to-host=$(hostname) MB\ ":0"\ "1"\
"Multiple_instances_not_allowed"!
  exit 0
fi
fi
DISPLAY=:0 rdairplay &
sleep 5
rmlsend LB\ "Info for the label area can go here"!
rmlsend PM\ "2"!
rmlsend PN\ "1"!

On Tue, Feb 22, 2022 at 5:18 AM Alejandro olivan Alvarez <
alejandro.olivan.alva...@gmail.com> wrote:

> Regarding your first question (fully automated auto-start of Rivendell)
>
> It is doable for sure, however, the actual details on how to achieve that,
> very much depends and/or conditions on what pieces make up your 'Linux'
> system (I assume that your hardware, has in BIOS the appropriate setting to
> power-on after a power failure)
>
> As a general idea, you need to setup your session manager (which may
> depend on what Desktop-Environment have you installed.. GDM, XDM, KDM,
> Slim, etc...) to auto-login your user upon system boot.
>
> Once you achieve that, you have to setup that, upon login, your user
> session automatically launches whatever software you need (and again,
> depending on the environment, there are different ways to do that).
>
> As I think we can assume that you want RDAirplay going to air, apart of
> having Rivendell daemons up and running, you need, by one side, to either
> setup RDAirplay to automatically load on the LogMachines the last logs that
> was loaded (a feature you can setup in RDConfig) or to script the loading
> of the log you want using a MACRO. And then, make it to play This links
> to your second question.
>
>
> Commands to air in proper time:
>
> There are commands to do quite a lot of actions related to the thing you
> want: you can launch a command that makes RDAirplay to play a cart, to play
> the next cart in the log, or to 'push' one of the buttons of the Main log,
> just to mention some...Rivendell Macro Language makes the whole thing
> incredibly flexible!
>
> However, consider that, if properly taylored, a log, on its own, can go to
> air 'by itself' if it has scheduled a cart to be aired on hard time (I
> recommend you to look at the Start time types, transition types and,
> overall, the behaviour of the logs on RDAirplay ) with a stop transition.
>
> Moreover, there's a wonderful module (RDCatch... I miss it very much in
> Debian beta4) that is all about executing tasks (including for sure
> executing a command) on the wallclock, so you don't need to have a
> wallclock log dedicated to schedule hard time tasks. So, in RDCatch, if you
> create a Macro cart that loads a certain log on a RDAirPlay log machine,
> and starts its playout, and you schedule that cart on RDCatch... then, no
> matter what, when the time comes, the cart will be executed)
>
>
> Hope I gave you some clues on where to focus on.
>
> Best regards.
>
>
> On 2/22/22 4:40 AM, Bryan Burchfield wrote:
>
> I am trying to figure out how to set my Linux operating system to
> automically restart after a power failure and for RD Airplay to
> automatically open up as well. Can anyone help with this? Also, is there a
> command for RD Airplay to begin airing at the proper time on the log after
> the power failure? Thank you for any help.
>
> Bryan Burchfield
> Oldies 98.3 WMTY
> WDEH AM-800
> (423) 337-5025
> mytrueoldies.com
> wdehradio.com
>
> 

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] Auto restart after power failure.

[Alejandro olivan Alvarez]

Regarding your first question (fully automated auto-start of Rivendell)

It is doable for sure, however, the actual details on how to achieve 
that, very much depends and/or conditions on what pieces make up your 
'Linux' system (I assume that your hardware, has in BIOS the appropriate 
setting to power-on after a power failure)


As a general idea, you need to setup your session manager (which may 
depend on what Desktop-Environment have you installed.. GDM, XDM, KDM, 
Slim, etc...) to auto-login your user upon system boot.


Once you achieve that, you have to setup that, upon login, your user 
session automatically launches whatever software you need (and again, 
depending on the environment, there are different ways to do that).


As I think we can assume that you want RDAirplay going to air, apart of 
having Rivendell daemons up and running, you need, by one side, to 
either setup RDAirplay to automatically load on the LogMachines the last 
logs that was loaded (a feature you can setup in RDConfig) or to script 
the loading of the log you want using a MACRO. And then, make it to 
play This links to your second question.



Commands to air in proper time:

There are commands to do quite a lot of actions related to the thing you 
want: you can launch a command that makes RDAirplay to play a cart, to 
play the next cart in the log, or to 'push' one of the buttons of the 
Main log, just to mention some...Rivendell Macro Language makes the 
whole thing incredibly flexible!


However, consider that, if properly taylored, a log, on its own, can go 
to air 'by itself' if it has scheduled a cart to be aired on hard time 
(I recommend you to look at the Start time types, transition types and, 
overall, the behaviour of the logs on RDAirplay ) with a stop transition.


Moreover, there's a wonderful module (RDCatch... I miss it very much in 
Debian beta4) that is all about executing tasks (including for sure 
executing a command) on the wallclock, so you don't need to have a 
wallclock log dedicated to schedule hard time tasks. So, in RDCatch, if 
you create a Macro cart that loads a certain log on a RDAirPlay log 
machine, and starts its playout, and you schedule that cart on 
RDCatch... then, no matter what, when the time comes, the cart will be 
executed)



Hope I gave you some clues on where to focus on.

Best regards.


On 2/22/22 4:40 AM, Bryan Burchfield wrote:
I am trying to figure out how to set my Linux operating system to 
automically restart after a power failure and for RD Airplay to 
automatically open up as well. Can anyone help with this? Also, is 
there a command for RD Airplay to begin airing at the proper time on 
the log after the power failure? Thank you for any help.


Bryan Burchfield
Oldies 98.3 WMTY
WDEH AM-800
(423) 337-5025
mytrueoldies.com 
wdehradio.com 

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