Re: [RDD] Two studios

2013-04-26 Thread Jay Eames
Firstly, damn autocorrect on the iPhone! The name's Jay! :)

Secondly, thanks Stan. I know we can use timed starts etc to move the log
on - my question would be more this. If both studios are running on the
same log, and someone makes a change to the log in Studio 1 - that change,
as I understand it, would not show up in Studio 2 playout. Also, if the
timed starts fire then you would end up with both studios playing at the
same time.

I am just wondering if anyone has any practical experience of this kind of
setup. We are about to move into our new premises and will be setting up
two studios - and ideally either or both of which would be able to go to
air or be used for production at any one time. I know that in the paid
software I have used in the past, you can mark one machine as on air, and
the other(s) would just follow the log without playing out.


On 26 April 2013 08:04, Stan Fotinos sfoti...@rtrfm.com.au wrote:

 Hi Kay

 If I understand correctly what you are trying to achieve is time
 synchronisation of your log. Using timed starts in your log and Make
 Next might do the trick for you.

 Thanks

 Stan

 On 26/04/13 1:41 PM, Jay Eames wrote:
  Thanks or the reply. I think my initial question wasn't quite clear
 enough. My bad!
 
  We gave several machines networked on Rivendell, all sharing the same
 database and var/snd - the question is more on how to run the same log in
 two studios so we can switch between them during the day
 
  Kay
 
  Sent from my iPhone
 
  On 26 Apr 2013, at 06:38, al davis ad...@freeelectron.net wrote:
 
  On Friday 26 April 2013, Jay Eames wrote:
  Has anyone used Rivendell in a setup where there is more than
  one live studio available? As in, where either studio can be
  used for the live output, and each studio has it's own
  playout machine, and they both share the same log?
  We use it in 4 studios at 3 sites.
 
  The two at the same site share files and sql on a local net.
  There is also an office computer that shares and is used for
  uploads.
 
  The other sites get scheduled backups of the main.  Sound files
  are transferred as ogg, so they act as hot standby computers
  that work even if the main is down.
 
  ___
  Rivendell-dev mailing list
  Rivendell-dev@lists.rivendellaudio.org
  http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
  ___
  Rivendell-dev mailing list
  Rivendell-dev@lists.rivendellaudio.org
  http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
 

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




-- 
There are 2 kinds of people in the world; Those who can extrapolate from
incomplete data
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev


Re: [RDD] Alternative MySQL port?

2013-04-26 Thread MICHAEL SMITH
I can't remember if this works (but I have seen it somewhere on the net)... 

Try in rd.conf:
Hostname=192.168.55.1
Port=5026





 From: Andy Brown a...@thebmwz3.co.uk
To: rivendell-dev@lists.rivendellaudio.org 
Sent: Thursday, 25 April 2013, 20:42
Subject: [RDD] Alternative MySQL port?
 

Hi all,

subject pretty much says it all. I need to connect to MySSQL running on
an alternative port. I tried in /etc/rd.conf by using the colon, but
this didn't connect. Is there a way of doing this?

[mySQL]
Hostname=192.168.55.1:5026
Loginname=rduser
Password=letmein
Database=Rivendell
Driver=QMYSQL3

Regards,

-- 
Andy
e: andy @ thebmwz3.co.uk
e: andy @ broadcast-tech.co.uk
w: http://www.thebmwz3.co.uk
w: http://www.broadcast-tech.co.uk
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev


Re: [RDD] Two studios

2013-04-26 Thread Tim Camp
Greetings,
Timed events don't have to be starts, they can be 'make next'.
Is there no human intervention in this scenario?
Cheers
 On 26 Apr 2013 02:13, Jay Eames alcham...@googlemail.com wrote:

 Firstly, damn autocorrect on the iPhone! The name's Jay! :)

 Secondly, thanks Stan. I know we can use timed starts etc to move the log
 on - my question would be more this. If both studios are running on the
 same log, and someone makes a change to the log in Studio 1 - that change,
 as I understand it, would not show up in Studio 2 playout. Also, if the
 timed starts fire then you would end up with both studios playing at the
 same time.

 I am just wondering if anyone has any practical experience of this kind of
 setup. We are about to move into our new premises and will be setting up
 two studios - and ideally either or both of which would be able to go to
 air or be used for production at any one time. I know that in the paid
 software I have used in the past, you can mark one machine as on air, and
 the other(s) would just follow the log without playing out.


 On 26 April 2013 08:04, Stan Fotinos sfoti...@rtrfm.com.au wrote:

 Hi Kay

 If I understand correctly what you are trying to achieve is time
 synchronisation of your log. Using timed starts in your log and Make
 Next might do the trick for you.

 Thanks

 Stan

 On 26/04/13 1:41 PM, Jay Eames wrote:
  Thanks or the reply. I think my initial question wasn't quite clear
 enough. My bad!
 
  We gave several machines networked on Rivendell, all sharing the same
 database and var/snd - the question is more on how to run the same log in
 two studios so we can switch between them during the day
 
  Kay
 
  Sent from my iPhone
 
  On 26 Apr 2013, at 06:38, al davis ad...@freeelectron.net wrote:
 
  On Friday 26 April 2013, Jay Eames wrote:
  Has anyone used Rivendell in a setup where there is more than
  one live studio available? As in, where either studio can be
  used for the live output, and each studio has it's own
  playout machine, and they both share the same log?
  We use it in 4 studios at 3 sites.
 
  The two at the same site share files and sql on a local net.
  There is also an office computer that shares and is used for
  uploads.
 
  The other sites get scheduled backups of the main.  Sound files
  are transferred as ogg, so they act as hot standby computers
  that work even if the main is down.
 
  ___
  Rivendell-dev mailing list
  Rivendell-dev@lists.rivendellaudio.org
  http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
  ___
  Rivendell-dev mailing list
  Rivendell-dev@lists.rivendellaudio.org
  http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
 

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




 --
 There are 2 kinds of people in the world; Those who can extrapolate from
 incomplete data

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


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


Re: [RDD] Alternative MySQL port?

2013-04-26 Thread Andy Brown
Aha,
good thinking. I'll try that this evening. Thanks for the suggestion.

Andy

On 26/04/13 08:41, MICHAEL SMITH wrote:
 I can't remember if this works (but I have seen it somewhere on the net)... 
 
 Try in rd.conf:
 Hostname=192.168.55.1
 Port=5026
 
 
 
 
 
  From: Andy Brown a...@thebmwz3.co.uk
 To: rivendell-dev@lists.rivendellaudio.org 
 Sent: Thursday, 25 April 2013, 20:42
 Subject: [RDD] Alternative MySQL port?
  
 
 Hi all,
 
 subject pretty much says it all. I need to connect to MySSQL running on
 an alternative port. I tried in /etc/rd.conf by using the colon, but
 this didn't connect. Is there a way of doing this?
 
 [mySQL]
 Hostname=192.168.55.1:5026
 Loginname=rduser
 Password=letmein
 Database=Rivendell
 Driver=QMYSQL3
 
 Regards,
 
 
 
 ___
 Rivendell-dev mailing list
 Rivendell-dev@lists.rivendellaudio.org
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
 


-- 
Andy
e: andy @ thebmwz3.co.uk
w: http://www.thebmwz3.co.uk
g: https://github.com/andyb2000/
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev


Re: [RDD] Two studios

2013-04-26 Thread John Anderson
what about duplicating monitors and keyboards on the same machine?, or kvm 
control to the same machine from duplicate studios?

 take the audio playback sources and duplicate it to multiple studios, have 
different audio inputs to record from different locations...As long as both 
don't try and edit the exact same cart at the same time, it seems it should work



 From: Tim Camp t...@wnsp.com
To: User discussion about the Rivendell Radio Automation System 
rivendell-dev@lists.rivendellaudio.org 
Sent: Friday, April 26, 2013 8:58 AM
Subject: Re: [RDD] Two studios
 


Greetings,
Timed events don't have to be starts, they can be 'make next'.
Is there no human intervention in this scenario?
Cheers

On 26 Apr 2013 02:13, Jay Eames alcham...@googlemail.com wrote:

Firstly, damn autocorrect on the iPhone! The name's Jay! :)


Secondly, thanks Stan. I know we can use timed starts etc to move the log on - 
my question would be more this. If both studios are running on the same log, 
and someone makes a change to the log in Studio 1 - that change, as I 
understand it, would not show up in Studio 2 playout. Also, if the timed 
starts fire then you would end up with both studios playing at the same time.


I am just wondering if anyone has any practical experience of this kind of 
setup. We are about to move into our new premises and will be setting up two 
studios - and ideally either or both of which would be able to go to air or be 
used for production at any one time. I know that in the paid software I have 
used in the past, you can mark one machine as on air, and the other(s) would 
just follow the log without playing out.



On 26 April 2013 08:04, Stan Fotinos sfoti...@rtrfm.com.au wrote:

Hi Kay

If I understand correctly what you are trying to achieve is time
synchronisation of your log. Using timed starts in your log and Make
Next might do the trick for you.

Thanks

Stan


On 26/04/13 1:41 PM, Jay Eames wrote:
 Thanks or the reply. I think my initial question wasn't quite clear enough. 
 My bad!

 We gave several machines networked on Rivendell, all sharing the same 
 database and var/snd - the question is more on how to run the same log in 
 two studios so we can switch between them during the day

 Kay

 Sent from my iPhone

 On 26 Apr 2013, at 06:38, al davis ad...@freeelectron.net wrote:

 On Friday 26 April 2013, Jay Eames wrote:
 Has anyone used Rivendell in a setup where there is more than
 one live studio available? As in, where either studio can be
 used for the live output, and each studio has it's own
 playout machine, and they both share the same log?
 We use it in 4 studios at 3 sites.

 The two at the same site share files and sql on a local net.
 There is also an office computer that shares and is used for
 uploads.

 The other sites get scheduled backups of the main.  Sound files
 are transferred as ogg, so they act as hot standby computers
 that work even if the main is down.

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


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




-- 

There are 2 kinds of people in the world; Those who can extrapolate from 
incomplete data
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev


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


Re: [RDD] Two studios

2013-04-26 Thread Alan Peterson
If I'm reading you right, you want to be able to make on-the-fly changes to an 
active log now running in RDAirplay, and have that change immediately reflected 
on all machines running that particular log, correct? 

As I understand the flow on my own small-scale system, such changes need to be 
made and saved in LogEdit; after which all machines sense the alteration in the 
log and are prompted to refresh.

But you know... for your own purpose, it does sound like a good idea -- the 
ability to make a change on a master RDAirplay window and have it fan out to 
all subservient computers tracking the same log. I'd make it an optional (turn 
on/off) feature though, otherwise it's one more way for live jocks to 
commandeer the log and create havoc.

AP


- Original Message -
From: Tim Camp t...@wnsp.com
To: User discussion about the Rivendell Radio Automation System 
rivendell-dev@lists.rivendellaudio.org
Sent: Friday, April 26, 2013 8:58:50 AM
Subject: Re: [RDD] Two studios




Greetings, 
Timed events don't have to be starts, they can be 'make next'. 
Is there no human intervention in this scenario? 
Cheers 

On 26 Apr 2013 02:13, Jay Eames  alcham...@googlemail.com  wrote: 



Firstly, damn autocorrect on the iPhone! The name's Jay! :) 


Secondly, thanks Stan. I know we can use timed starts etc to move the log on - 
my question would be more this. If both studios are running on the same log, 
and someone makes a change to the log in Studio 1 - that change, as I 
understand it, would not show up in Studio 2 playout. Also, if the timed starts 
fire then you would end up with both studios playing at the same time. 


I am just wondering if anyone has any practical experience of this kind of 
setup. We are about to move into our new premises and will be setting up two 
studios - and ideally either or both of which would be able to go to air or be 
used for production at any one time. I know that in the paid software I have 
used in the past, you can mark one machine as on air, and the other(s) would 
just follow the log without playing out. 



On 26 April 2013 08:04, Stan Fotinos  sfoti...@rtrfm.com.au  wrote: 


Hi Kay 

If I understand correctly what you are trying to achieve is time 
synchronisation of your log. Using timed starts in your log and Make 
Next might do the trick for you. 

Thanks 

Stan 



On 26/04/13 1:41 PM, Jay Eames wrote: 
 Thanks or the reply. I think my initial question wasn't quite clear enough. 
 My bad! 
 
 We gave several machines networked on Rivendell, all sharing the same 
 database and var/snd - the question is more on how to run the same log in two 
 studios so we can switch between them during the day 
 
 Kay 
 
 Sent from my iPhone 
 
 On 26 Apr 2013, at 06:38, al davis  ad...@freeelectron.net  wrote: 
 
 On Friday 26 April 2013, Jay Eames wrote: 
 Has anyone used Rivendell in a setup where there is more than 
 one live studio available? As in, where either studio can be 
 used for the live output, and each studio has it's own 
 playout machine, and they both share the same log? 
 We use it in 4 studios at 3 sites. 
 
 The two at the same site share files and sql on a local net. 
 There is also an office computer that shares and is used for 
 uploads. 
 
 The other sites get scheduled backups of the main. Sound files 
 are transferred as ogg, so they act as hot standby computers 
 that work even if the main is down. 
 
 ___ 
 Rivendell-dev mailing list 
 Rivendell-dev@lists.rivendellaudio.org 
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev 
 ___ 
 Rivendell-dev mailing list 
 Rivendell-dev@lists.rivendellaudio.org 
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev 
 

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




-- 

There are 2 kinds of people in the world; Those who can extrapolate from 
incomplete data 
___ 
Rivendell-dev mailing list 
Rivendell-dev@lists.rivendellaudio.org 
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev 


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


Re: [RDD] Two studios

2013-04-26 Thread Jay Eames
Thanks Alan,

Yes you have understood correctly. Perhaps a use-case example might
clarify. In our community station we have quite a few specialist shows.
The presenter comes in an hour or so before their show to sort out the
playout order etc from a machine in the office. This is then readily
available to them when they start their show and has not disturbed the
on-air presenter.

We have played with rdlogedit, but the problem there is that any ad-hoc
changes the on-air presenter has made get overwritten the moment the log is
saved (assuming auto log refresh is on), which has potential to royally
mess with our output.

Jay


On 26 April 2013 14:19, Alan Peterson apeter...@radioamerica.org wrote:

 If I'm reading you right, you want to be able to make on-the-fly changes
 to an active log now running in RDAirplay, and have that change immediately
 reflected on all machines running that particular log, correct?

 As I understand the flow on my own small-scale system, such changes need
 to be made and saved in LogEdit; after which all machines sense the
 alteration in the log and are prompted to refresh.

 But you know... for your own purpose, it does sound like a good idea --
 the ability to make a change on a master RDAirplay window and have it fan
 out to all subservient computers tracking the same log. I'd make it an
 optional (turn on/off) feature though, otherwise it's one more way for live
 jocks to commandeer the log and create havoc.

 AP


 - Original Message -
 From: Tim Camp t...@wnsp.com
 To: User discussion about the Rivendell Radio Automation System 
 rivendell-dev@lists.rivendellaudio.org
 Sent: Friday, April 26, 2013 8:58:50 AM
 Subject: Re: [RDD] Two studios




 Greetings,
 Timed events don't have to be starts, they can be 'make next'.
 Is there no human intervention in this scenario?
 Cheers

 On 26 Apr 2013 02:13, Jay Eames  alcham...@googlemail.com  wrote:



 Firstly, damn autocorrect on the iPhone! The name's Jay! :)


 Secondly, thanks Stan. I know we can use timed starts etc to move the log
 on - my question would be more this. If both studios are running on the
 same log, and someone makes a change to the log in Studio 1 - that change,
 as I understand it, would not show up in Studio 2 playout. Also, if the
 timed starts fire then you would end up with both studios playing at the
 same time.


 I am just wondering if anyone has any practical experience of this kind of
 setup. We are about to move into our new premises and will be setting up
 two studios - and ideally either or both of which would be able to go to
 air or be used for production at any one time. I know that in the paid
 software I have used in the past, you can mark one machine as on air, and
 the other(s) would just follow the log without playing out.



 On 26 April 2013 08:04, Stan Fotinos  sfoti...@rtrfm.com.au  wrote:


 Hi Kay

 If I understand correctly what you are trying to achieve is time
 synchronisation of your log. Using timed starts in your log and Make
 Next might do the trick for you.

 Thanks

 Stan



 On 26/04/13 1:41 PM, Jay Eames wrote:
  Thanks or the reply. I think my initial question wasn't quite clear
 enough. My bad!
 
  We gave several machines networked on Rivendell, all sharing the same
 database and var/snd - the question is more on how to run the same log in
 two studios so we can switch between them during the day
 
  Kay
 
  Sent from my iPhone
 
  On 26 Apr 2013, at 06:38, al davis  ad...@freeelectron.net  wrote:
 
  On Friday 26 April 2013, Jay Eames wrote:
  Has anyone used Rivendell in a setup where there is more than
  one live studio available? As in, where either studio can be
  used for the live output, and each studio has it's own
  playout machine, and they both share the same log?
  We use it in 4 studios at 3 sites.
 
  The two at the same site share files and sql on a local net.
  There is also an office computer that shares and is used for
  uploads.
 
  The other sites get scheduled backups of the main. Sound files
  are transferred as ogg, so they act as hot standby computers
  that work even if the main is down.
 
  ___
  Rivendell-dev mailing list
  Rivendell-dev@lists.rivendellaudio.org
  http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
  ___
  Rivendell-dev mailing list
  Rivendell-dev@lists.rivendellaudio.org
  http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
 

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




 --

 There are 2 kinds of people in the world; Those who can extrapolate from
 incomplete data
 ___
 Rivendell-dev mailing list
 Rivendell-dev@lists.rivendellaudio.org
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev


 

Re: [RDD] Confused! Talk In/Out Segue In/Out

2013-04-26 Thread Gavin Stephens
Talk start will set its self to immediately if you just set the talk end.

I can see the reasoning with the talk markers at the end of the track. This 
would be confusing though if talent was watching the pie counter thinking 
it's counting down to segue, or talk, or how would you know which? If 
there's room for confusion, someone would find it.

I can't figure out what you were meaning by multiple segue markers for 
though.

Cheers,
Gavin.

- Original Message - 
From: Andy Brown a...@thebmwz3.co.uk
To: rivendell-dev@lists.rivendellaudio.org
Sent: Saturday, April 27, 2013 12:58 AM
Subject: [RDD] Confused! Talk In/Out Segue In/Out


 Hi folks,

 Still battling my way through ready to launch a community station
 shortly and one issue cropping up from the guys programming in music is
 the confusion over the different markers.

 The main confusion is over the TalkStart/TalkStop and SegueStart/SegueEnd.

 As in many songs we need multiple entries for both.

 E.g. at the start of a song we set a TalkStart immediately and a
 TalkStop just before the vocals of the song comes in.
 Then we would ideally need to place another TalkStart and TalkStop
 towards the end of the song where the last vocals are sung and its just
 musical until the end of the song.

 Similar for SegueStart/SegueEnd we have cases where having one at start
 one at end would also be useful, is this a fair summary or am I missing
 something here?

 Regards,

 -- 
 Andy
 e: andy @ thebmwz3.co.uk
 w: http://www.thebmwz3.co.uk
 g: https://github.com/andyb2000/
 ___
 Rivendell-dev mailing list
 Rivendell-dev@lists.rivendellaudio.org
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev 


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


Re: [RDD] Confused! Talk In/Out Segue In/Out

2013-04-26 Thread Alan Peterson
It's not the coolest solution out there, but the simplest method is to put a 
text notation in the Artist or Title line of the cart:

POINTER SISTERS 
I'M SO EXCITED (end talk 3:51)

The jocks are going to be watching the clock anyway.

-ap



- Original Message -
From: Andy Brown a...@thebmwz3.co.uk
To: rivendell-dev@lists.rivendellaudio.org
Sent: Friday, April 26, 2013 8:58:47 AM
Subject: [RDD] Confused! Talk In/Out Segue In/Out

Hi folks,

Still battling my way through ready to launch a community station
shortly and one issue cropping up from the guys programming in music is
the confusion over the different markers.

The main confusion is over the TalkStart/TalkStop and SegueStart/SegueEnd.

As in many songs we need multiple entries for both.

E.g. at the start of a song we set a TalkStart immediately and a
TalkStop just before the vocals of the song comes in.
Then we would ideally need to place another TalkStart and TalkStop
towards the end of the song where the last vocals are sung and its just
musical until the end of the song.

Similar for SegueStart/SegueEnd we have cases where having one at start
one at end would also be useful, is this a fair summary or am I missing
something here?

Regards,

-- 
Andy
e: andy @ thebmwz3.co.uk
w: http://www.thebmwz3.co.uk
g: https://github.com/andyb2000/
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev


Re: [RDD] Confused! Talk In/Out Segue In/Out

2013-04-26 Thread Gavin Stephens
I haven't used the outcue field, but I'd imagine that the cut outcue field 
shows on the entry in the players too like the description does.

- Original Message - 
From: Alan Peterson apeter...@radioamerica.org
To: User discussion about the Rivendell Radio Automation System 
rivendell-dev@lists.rivendellaudio.org
Sent: Saturday, April 27, 2013 1:32 AM
Subject: Re: [RDD] Confused! Talk In/Out Segue In/Out


 It's not the coolest solution out there, but the simplest method is to put 
 a text notation in the Artist or Title line of the cart:

 POINTER SISTERS
 I'M SO EXCITED (end talk 3:51)

 The jocks are going to be watching the clock anyway.

 -ap



 - Original Message -
 From: Andy Brown a...@thebmwz3.co.uk
 To: rivendell-dev@lists.rivendellaudio.org
 Sent: Friday, April 26, 2013 8:58:47 AM
 Subject: [RDD] Confused! Talk In/Out Segue In/Out

 Hi folks,

 Still battling my way through ready to launch a community station
 shortly and one issue cropping up from the guys programming in music is
 the confusion over the different markers.

 The main confusion is over the TalkStart/TalkStop and SegueStart/SegueEnd.

 As in many songs we need multiple entries for both.

 E.g. at the start of a song we set a TalkStart immediately and a
 TalkStop just before the vocals of the song comes in.
 Then we would ideally need to place another TalkStart and TalkStop
 towards the end of the song where the last vocals are sung and its just
 musical until the end of the song.

 Similar for SegueStart/SegueEnd we have cases where having one at start
 one at end would also be useful, is this a fair summary or am I missing
 something here?

 Regards,

 -- 
 Andy
 e: andy @ thebmwz3.co.uk
 w: http://www.thebmwz3.co.uk
 g: https://github.com/andyb2000/
 ___
 Rivendell-dev mailing list
 Rivendell-dev@lists.rivendellaudio.org
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
 ___
 Rivendell-dev mailing list
 Rivendell-dev@lists.rivendellaudio.org
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev 


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


Re: [RDD] Two studios

2013-04-26 Thread Alan Peterson
So how about separate logs for separate shows, so changes made to one's show 
doesn't botch the others? 

The classic radio station broadcast day log concept has been with us since we 
started spraying RF into the atmosphere last century, but it may not be your 
best solution here. Create a different log for each presenter. The entire day's 
output can be merged and rendered at midnight if you truly need to have a 
24-hour record of playout.

-a.



- Original Message -
From: Jay Eames alcham...@googlemail.com
To: User discussion about the Rivendell Radio Automation System 
rivendell-dev@lists.rivendellaudio.org
Sent: Friday, April 26, 2013 9:25:21 AM
Subject: Re: [RDD] Two studios



Thanks Alan, 


Yes you have understood correctly. Perhaps a use-case example might clarify. In 
our community station we have quite a few specialist shows. The presenter 
comes in an hour or so before their show to sort out the playout order etc from 
a machine in the office. This is then readily available to them when they start 
their show and has not disturbed the on-air presenter. 


We have played with rdlogedit, but the problem there is that any ad-hoc changes 
the on-air presenter has made get overwritten the moment the log is saved 
(assuming auto log refresh is on), which has potential to royally mess with our 
output. 


Jay 



On 26 April 2013 14:19, Alan Peterson  apeter...@radioamerica.org  wrote: 


If I'm reading you right, you want to be able to make on-the-fly changes to an 
active log now running in RDAirplay, and have that change immediately reflected 
on all machines running that particular log, correct? 

As I understand the flow on my own small-scale system, such changes need to be 
made and saved in LogEdit; after which all machines sense the alteration in the 
log and are prompted to refresh. 

But you know... for your own purpose, it does sound like a good idea -- the 
ability to make a change on a master RDAirplay window and have it fan out to 
all subservient computers tracking the same log. I'd make it an optional (turn 
on/off) feature though, otherwise it's one more way for live jocks to 
commandeer the log and create havoc. 

AP 



- Original Message - 
From: Tim Camp  t...@wnsp.com  
To: User discussion about the Rivendell Radio Automation System  
rivendell-dev@lists.rivendellaudio.org  

Sent: Friday, April 26, 2013 8:58:50 AM 
Subject: Re: [RDD] Two studios 






Greetings, 
Timed events don't have to be starts, they can be 'make next'. 
Is there no human intervention in this scenario? 
Cheers 

On 26 Apr 2013 02:13, Jay Eames  alcham...@googlemail.com  wrote: 



Firstly, damn autocorrect on the iPhone! The name's Jay! :) 


Secondly, thanks Stan. I know we can use timed starts etc to move the log on - 
my question would be more this. If both studios are running on the same log, 
and someone makes a change to the log in Studio 1 - that change, as I 
understand it, would not show up in Studio 2 playout. Also, if the timed starts 
fire then you would end up with both studios playing at the same time. 


I am just wondering if anyone has any practical experience of this kind of 
setup. We are about to move into our new premises and will be setting up two 
studios - and ideally either or both of which would be able to go to air or be 
used for production at any one time. I know that in the paid software I have 
used in the past, you can mark one machine as on air, and the other(s) would 
just follow the log without playing out. 



On 26 April 2013 08:04, Stan Fotinos  sfoti...@rtrfm.com.au  wrote: 


Hi Kay 

If I understand correctly what you are trying to achieve is time 
synchronisation of your log. Using timed starts in your log and Make 
Next might do the trick for you. 

Thanks 

Stan 



On 26/04/13 1:41 PM, Jay Eames wrote: 
 Thanks or the reply. I think my initial question wasn't quite clear enough. 
 My bad! 
 
 We gave several machines networked on Rivendell, all sharing the same 
 database and var/snd - the question is more on how to run the same log in two 
 studios so we can switch between them during the day 
 
 Kay 
 
 Sent from my iPhone 
 
 On 26 Apr 2013, at 06:38, al davis  ad...@freeelectron.net  wrote: 
 
 On Friday 26 April 2013, Jay Eames wrote: 
 Has anyone used Rivendell in a setup where there is more than 
 one live studio available? As in, where either studio can be 
 used for the live output, and each studio has it's own 
 playout machine, and they both share the same log? 
 We use it in 4 studios at 3 sites. 
 
 The two at the same site share files and sql on a local net. 
 There is also an office computer that shares and is used for 
 uploads. 
 
 The other sites get scheduled backups of the main. Sound files 
 are transferred as ogg, so they act as hot standby computers 
 that work even if the main is down. 
 
 ___ 
 Rivendell-dev mailing list 
 Rivendell-dev@lists.rivendellaudio.org 
 

Re: [RDD] Confused! Talk In/Out Segue In/Out

2013-04-26 Thread Hoggins!
Hello guys,

Actually, I was thinking of something that would help a lot any DJ using
Rivendell for live : displaying the waveform of the current playing track.
I used to work on a proprietary system, running on Windows,called
WinRadio (not the Ham software). Very expensive (the license was approx
20.000 euros), and really not very clever. On a lot of points,
Rivendellis a real challenger.

Anyway, this software had one really cool feature, consisting in the
displayof the waveform of the current playing track, the position of the
reading head on the track, and all the markers, represented as regions
on the track. I think it would be really nice.

Here is a screenshot of the (very ugly, don't mind the other features)
user interface of the software, found /via/Google Images :
http://www.305broadcast.com/wp-content/uploads/2011/09/WinMedia_OnAir_Lite-1024x824.jpg

What do you think ? Wouldn't it help your DJs who cannot set several
talk regions on their cuts ?

Hoggins!


Le 26/04/2013 15:27, Gavin Stephens a écrit :
 Talk start will set its self to immediately if you just set the talk end.

 I can see the reasoning with the talk markers at the end of the track. This 
 would be confusing though if talent was watching the pie counter thinking 
 it's counting down to segue, or talk, or how would you know which? If 
 there's room for confusion, someone would find it.

 I can't figure out what you were meaning by multiple segue markers for 
 though.

 Cheers,
 Gavin.

 - Original Message - 
 From: Andy Brown a...@thebmwz3.co.uk
 To: rivendell-dev@lists.rivendellaudio.org
 Sent: Saturday, April 27, 2013 12:58 AM
 Subject: [RDD] Confused! Talk In/Out Segue In/Out


 Hi folks,

 Still battling my way through ready to launch a community station
 shortly and one issue cropping up from the guys programming in music is
 the confusion over the different markers.

 The main confusion is over the TalkStart/TalkStop and SegueStart/SegueEnd.

 As in many songs we need multiple entries for both.

 E.g. at the start of a song we set a TalkStart immediately and a
 TalkStop just before the vocals of the song comes in.
 Then we would ideally need to place another TalkStart and TalkStop
 towards the end of the song where the last vocals are sung and its just
 musical until the end of the song.

 Similar for SegueStart/SegueEnd we have cases where having one at start
 one at end would also be useful, is this a fair summary or am I missing
 something here?

 Regards,

 -- 
 Andy
 e: andy @ thebmwz3.co.uk
 w: http://www.thebmwz3.co.uk
 g: https://github.com/andyb2000/
 ___
 Rivendell-dev mailing list
 Rivendell-dev@lists.rivendellaudio.org
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev 

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

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


Re: [RDD] Confused! Talk In/Out Segue In/Out

2013-04-26 Thread Andy Brown
Thanks Gavin,
Maybe I'm not being very clear here. If you're familiar with other
similar playout systems it may make more sense (Myriad, Soundbox, etc).

In a standard song, you have a musical intro (start) and a musical extro
(end), these are sections that could be segue'd over by a sweeper. This
can take place at the start and the end of a track potentially, so you
could sandwich music in as follows:

Music
sweeper
Music
sweeper
Music

So each of the music tracks in the list would have a segue intro and
segue extro allowing the sweeper to play over the top of the end of one
track and the start of the next.

We use this a lot on another station I do work for using another playout
system and it gives a very good audio sound.

I do however understand your point about the talk markers and the pie
counter being confusing with all these in.

Regards,
Andy


On 26/04/13 14:27, Gavin Stephens wrote:
 Talk start will set its self to immediately if you just set the talk end.
 
 I can see the reasoning with the talk markers at the end of the track. This 
 would be confusing though if talent was watching the pie counter thinking 
 it's counting down to segue, or talk, or how would you know which? If 
 there's room for confusion, someone would find it.
 
 I can't figure out what you were meaning by multiple segue markers for 
 though.
 
 Cheers,
 Gavin.
 
 - Original Message - 
 From: Andy Brown a...@thebmwz3.co.uk
 To: rivendell-dev@lists.rivendellaudio.org
 Sent: Saturday, April 27, 2013 12:58 AM
 Subject: [RDD] Confused! Talk In/Out Segue In/Out
 
 
 Hi folks,

 Still battling my way through ready to launch a community station
 shortly and one issue cropping up from the guys programming in music is
 the confusion over the different markers.

 The main confusion is over the TalkStart/TalkStop and SegueStart/SegueEnd.

 As in many songs we need multiple entries for both.

 E.g. at the start of a song we set a TalkStart immediately and a
 TalkStop just before the vocals of the song comes in.
 Then we would ideally need to place another TalkStart and TalkStop
 towards the end of the song where the last vocals are sung and its just
 musical until the end of the song.

 Similar for SegueStart/SegueEnd we have cases where having one at start
 one at end would also be useful, is this a fair summary or am I missing
 something here?

 Regards,

 -- 
 Andy
 e: andy @ thebmwz3.co.uk
 w: http://www.thebmwz3.co.uk
 g: https://github.com/andyb2000/
 ___
 Rivendell-dev mailing list
 Rivendell-dev@lists.rivendellaudio.org
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev 
 
 
 ___
 Rivendell-dev mailing list
 Rivendell-dev@lists.rivendellaudio.org
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
 


-- 
Andy
e: andy @ thebmwz3.co.uk
w: http://www.thebmwz3.co.uk
g: https://github.com/andyb2000/
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev


Re: [RDD] Confused! Talk In/Out Segue In/Out

2013-04-26 Thread Hoggins!
Of course, I second that. But that wouldbe a feature one could
deactivate at will, like e.g. show extra buttons in the RDAirplay
configuration screen.

Le 26/04/2013 15:53, Andy Brown a écrit :
 I'm also not sure if the waveform would help a lot of presenters (Our
 presenters are all volunteers for a community station, so they need very
 simple+clear guides). I think a lot of them would not understand the
 waveform, but a timer that says:
 Intro counter: 0:10 seconds
 9 seconds
 8 seconds,
 etc. Then at the end of the song
 Extro counter: 0:10 seconds
 9 seconds,
 etc. would be easy to follow.

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


Re: [RDD] Confused! Talk In/Out Segue In/Out

2013-04-26 Thread Alan Peterson
I have to agree; waveform display of an on-air cut is overkill. I can't imagine 
an on-air scenario where this was necessary, unless the jock was doing a mashup 
mix show and wanted to be able to loop and isolate portions of a song for 
creative scratch-mixing.

In which case, MIXXX (www.mixxx.org) is probably a solution you'd be interested 
in, running on a non-RD machine.

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


Re: [RDD] Two studios

2013-04-26 Thread Bill Putney
We have at KPTZ. We have a a main air studio and a production studio. 
They both have Rivendell client playout machines. When we do maintenance 
in  the air studio we frequently load the same log in the production 
studio's Rivendell machine and start that one playing in as close to 
sync as we can get it. Then the cutover between the two studios is 
seamless on the air.


In our case we only have one transmitter to feed but there's no reason 
the second Rivendell machine couldn't just as easily be feeding a 
separate Internet stream, an AM transmitter or other audio sink.


Bill

On 4/25/13 10:21 PM, Jay Eames wrote:

Hi guys,

Has anyone used Rivendell in a setup where there is more than one live 
studio available? As in, where either studio can be used for the live 
output, and each studio has it's own playout machine, and they both 
share the same log?


Jay

--
There are 2 kinds of people in the world; Those who can 
extrapolate from incomplete data



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


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


Re: [RDD] Two studios

2013-04-26 Thread Wayne Merricks

Hi,

I understand the premise of going live between studios but I don't 
understand why everyones going the complicated route.  We do the same 
here but we use good old fashioned Audio on a fader.


In each studio we have a selectable fader.  When we switch from Studio 1 
to Studio 2, we set Studio 2's fader to pick up Audio from Studio 1.


Then we hit the broadcast rack switcher to go live in Studio 2 (via a 
GPIO signal).


At this point Rivendell inside Studio 2 is doing nothing but waiting for 
a show to start (manually moved to the correct starting point). When the 
presenter is ready in Studio 2 we fade down Studio 1 (usually at the end 
of pips or a song or whatever so there is no hard cut).   Fade up the 
Studio 2 Rivendell + Mics and away you go.


Repeat the process in reverse next time we move studios.

Regards,

Wayne

On 26/04/13 16:18, Bill Putney wrote:
We have at KPTZ. We have a a main air studio and a production studio. 
They both have Rivendell client playout machines. When we do 
maintenance in  the air studio we frequently load the same log in the 
production studio's Rivendell machine and start that one playing in as 
close to sync as we can get it. Then the cutover between the two 
studios is seamless on the air.


In our case we only have one transmitter to feed but there's no reason 
the second Rivendell machine couldn't just as easily be feeding a 
separate Internet stream, an AM transmitter or other audio sink.


Bill

On 4/25/13 10:21 PM, Jay Eames wrote:

Hi guys,

Has anyone used Rivendell in a setup where there is more than one 
live studio available? As in, where either studio can be used for the 
live output, and each studio has it's own playout machine, and they 
both share the same log?


Jay

--
There are 2 kinds of people in the world; Those who can 
extrapolate from incomplete data



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




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


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


Re: [RDD] Two studios

2013-04-26 Thread Matthew Chambers
Even though in the facility I am in currently we are using a different
automation system but we do a very similar setup in that we have to have
the ability to playout the same log from any studio. Our playout box is
located in our equipment rack and is fed into our wheatstone audio network
and can be pulled up on any console (can do the same with analog system
with a DA) and we use a remote KVM to select which automation playback
machine the talent looks at in each studio. So if they switch studios they
can pull up the MAIN A playout box in the MAIN B studio or vice versa.



On Fri, Apr 26, 2013 at 12:13 AM, Jay Eames alcham...@googlemail.comwrote:

 Firstly, damn autocorrect on the iPhone! The name's Jay! :)

 Secondly, thanks Stan. I know we can use timed starts etc to move the log
 on - my question would be more this. If both studios are running on the
 same log, and someone makes a change to the log in Studio 1 - that change,
 as I understand it, would not show up in Studio 2 playout. Also, if the
 timed starts fire then you would end up with both studios playing at the
 same time.

 I am just wondering if anyone has any practical experience of this kind of
 setup. We are about to move into our new premises and will be setting up
 two studios - and ideally either or both of which would be able to go to
 air or be used for production at any one time. I know that in the paid
 software I have used in the past, you can mark one machine as on air, and
 the other(s) would just follow the log without playing out.


 On 26 April 2013 08:04, Stan Fotinos sfoti...@rtrfm.com.au wrote:

 Hi Kay

 If I understand correctly what you are trying to achieve is time
 synchronisation of your log. Using timed starts in your log and Make
 Next might do the trick for you.

 Thanks

 Stan

 On 26/04/13 1:41 PM, Jay Eames wrote:
  Thanks or the reply. I think my initial question wasn't quite clear
 enough. My bad!
 
  We gave several machines networked on Rivendell, all sharing the same
 database and var/snd - the question is more on how to run the same log in
 two studios so we can switch between them during the day
 
  Kay
 
  Sent from my iPhone
 
  On 26 Apr 2013, at 06:38, al davis ad...@freeelectron.net wrote:
 
  On Friday 26 April 2013, Jay Eames wrote:
  Has anyone used Rivendell in a setup where there is more than
  one live studio available? As in, where either studio can be
  used for the live output, and each studio has it's own
  playout machine, and they both share the same log?
  We use it in 4 studios at 3 sites.
 
  The two at the same site share files and sql on a local net.
  There is also an office computer that shares and is used for
  uploads.
 
  The other sites get scheduled backups of the main.  Sound files
  are transferred as ogg, so they act as hot standby computers
  that work even if the main is down.
 
  ___
  Rivendell-dev mailing list
  Rivendell-dev@lists.rivendellaudio.org
  http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
  ___
  Rivendell-dev mailing list
  Rivendell-dev@lists.rivendellaudio.org
  http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
 

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




 --
 There are 2 kinds of people in the world; Those who can extrapolate from
 incomplete data

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


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


Re: [RDD] Two studios

2013-04-26 Thread Jay Ashworth
- Original Message -
 From: Matthew Chambers n...@grandcanyonham.info

 Even though in the facility I am in currently we are using a different
 automation system but we do a very similar setup in that we have to have
 the ability to playout the same log from any studio. Our playout box is
 located in our equipment rack and is fed into our wheatstone audio network
 and can be pulled up on any console (can do the same with analog system
 with a DA) and we use a remote KVM to select which automation playback
 machine the talent looks at in each studio. So if they switch studios
 they can pull up the MAIN A playout box in the MAIN B studio or vice versa.

This seems like a good time to point out that Fred's original architecture
plan was that all the UIs lived on a Big Server Box in the engineering
room, and you VNCd into them to run your airshift...

Cheers,
-- jra
-- 
Jay R. Ashworth  Baylink   j...@baylink.com
Designer The Things I Think   RFC 2100
Ashworth  Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA   #natog  +1 727 647 1274
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev


Re: [RDD] Two studios

2013-04-26 Thread Matthew Chambers
Yup and I forgot to mention the really neat part is that during voice
tracked hours we just change some cross points in Wheatstone so that the
playout of the automation feeds directly to the uplink to the satellite and
out to the stations without running through any studio or console.


Matthew A. Chambers, CBT
Broadcast Engineer
Family Life Radio


On Fri, Apr 26, 2013 at 11:10 AM, Jay Ashworth j...@baylink.com wrote:

 - Original Message -
  From: Matthew Chambers n...@grandcanyonham.info

  Even though in the facility I am in currently we are using a different
  automation system but we do a very similar setup in that we have to have
  the ability to playout the same log from any studio. Our playout box is
  located in our equipment rack and is fed into our wheatstone audio
 network
  and can be pulled up on any console (can do the same with analog system
  with a DA) and we use a remote KVM to select which automation playback
  machine the talent looks at in each studio. So if they switch studios
  they can pull up the MAIN A playout box in the MAIN B studio or vice
 versa.

 This seems like a good time to point out that Fred's original architecture
 plan was that all the UIs lived on a Big Server Box in the engineering
 room, and you VNCd into them to run your airshift...

 Cheers,
 -- jra
 --
 Jay R. Ashworth  Baylink
 j...@baylink.com
 Designer The Things I Think   RFC
 2100
 Ashworth  Associates http://baylink.pitas.com 2000 Land
 Rover DII
 St Petersburg FL USA   #natog  +1 727 647
 1274
 ___
 Rivendell-dev mailing list
 Rivendell-dev@lists.rivendellaudio.org
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev

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


Re: [RDD] Two studios

2013-04-26 Thread Jay Eames
Thanks for the ideas guys. As always I have the issue of being in community
radio, meaning on the whole:

a) No money for kit, and
b) Presenters being occasional amateurs on the whole rather than seasoned
jocks (although we are blessed with a few of those as well)

So things have to be as simple (and as relatively foolproof) as they can be.


On 26 April 2013 19:13, Matthew Chambers n...@grandcanyonham.info wrote:

 Yup and I forgot to mention the really neat part is that during voice
 tracked hours we just change some cross points in Wheatstone so that the
 playout of the automation feeds directly to the uplink to the satellite and
 out to the stations without running through any studio or console.


 Matthew A. Chambers, CBT
 Broadcast Engineer
 Family Life Radio


 On Fri, Apr 26, 2013 at 11:10 AM, Jay Ashworth j...@baylink.com wrote:

 - Original Message -
  From: Matthew Chambers n...@grandcanyonham.info

  Even though in the facility I am in currently we are using a different
  automation system but we do a very similar setup in that we have to have
  the ability to playout the same log from any studio. Our playout box is
  located in our equipment rack and is fed into our wheatstone audio
 network
  and can be pulled up on any console (can do the same with analog system
  with a DA) and we use a remote KVM to select which automation playback
  machine the talent looks at in each studio. So if they switch studios
  they can pull up the MAIN A playout box in the MAIN B studio or vice
 versa.

 This seems like a good time to point out that Fred's original architecture
 plan was that all the UIs lived on a Big Server Box in the engineering
 room, and you VNCd into them to run your airshift...

 Cheers,
 -- jra
 --
 Jay R. Ashworth  Baylink
 j...@baylink.com
 Designer The Things I Think   RFC
 2100
 Ashworth  Associates http://baylink.pitas.com 2000 Land
 Rover DII
 St Petersburg FL USA   #natog  +1 727
 647 1274
 ___
 Rivendell-dev mailing list
 Rivendell-dev@lists.rivendellaudio.org
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev



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




-- 
There are 2 kinds of people in the world; Those who can extrapolate from
incomplete data
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev


Re: [RDD] Trying to Mount USB Drive in CentOS 5

2013-04-26 Thread Steve Atkins
Thanks Robert and Alessio! 


I appreciate your response. I have now copied the /var/snd library from the old 
ubuntu 10.04 box (32 bit) to the new CentOS appliance (5.9 Final) 2.5 Rivendell 
/var/snd directory. 


Now, I anxiously enter RDLibrary, only to find the test tone (cart# 99) 
supplied with the new appliance setup and nothing else. Hmmm. Oh, maybe the 
database needs to be restored from the 2.2 version on the old machine. I was 
sure I'd read to do that. So in a daring (foolish) poke of the button, I 
restore the previous db. And now, the results of that trial. 


What? The RDLibrary is empty, RDAirPlay buttons are grey'd out and so is 
LogEdit. I'm betting there's a simple command or two to straighten out 
permissions. (yes, I did back up the new 2.5 as soon as I got it situated on 
the new box rdbackup-20130402-202.sql 11.3 gzip file -rw-r-r-- root root). 


Well, that's interesting since the previous db backup was  -rwxr--r-- rd 
users so I'd have to unzip the backup to take the 2.5 db a step back to the 
clean new setup. Correct? Or, hopefully I can fix this as it sits now. 


Thanks for your patience with a production guy/wannabe Rivendell operator. 


Steve Atkins 
Portland, Or 

- Original Message -
From: Jeffares, Robert jeffares.rob...@gmail.com 
To: Rivendell, Mail List rivendell-dev@lists.rivendellaudio.org 
Sent: Thursday, April 18, 2013 9:28:08 PM 
Subject: Re: [RDD] Trying to Mount USB Drive in CentOS 5 

you should have been able to copy the contents of /var/snd/ on the old 
system onto the WD which will be mounted at /media/nameofdrive/ 

The network copy works better and I tend to use rsync because you can 
recover from any interruption and there seems to be a better throughput 
than cp 

which may be just me. 


Hope that's some help 

regards 

Robert Jeffares 
Big Valley Radio 


On Fri, 2013-04-19 at 02:48 +, Steve Atkins wrote: 
 I'm trading up to the Paravel appliance (2.5) and attempting to copy 
 carts from the ubuntu 10.04 machine (riv 2.2) via a WD usb drive. 
 While now learning the CentOS etiquette, I'm looking for the accepted 
 method of finding the drive and using it on this nice shiney new box. 
 
 
 I imagine this has been covered earlier, but I can't find it in the 
 archives. I have found lots of creative methods on-line but I'll 
 defer to your advice to be safe. 
 
 
 Many thanks! 
 
 
 -Steve 
 ___ 
 Rivendell-dev mailing list 
 Rivendell-dev@lists.rivendellaudio.org 
 http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev 


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


Re: [RDD] Confused! Talk In/Out Segue In/Out

2013-04-26 Thread Gavin Stephens
You can't tell voice ramps much by waveform's either. A lot of times I'm 
setting talk end markers I do it by guess at first, according to the 
waveform, then when I hit play I realise the vocals start much earlier 
etc...


- Original Message - 
From: Alan Peterson apeter...@radioamerica.org
To: User discussion about the Rivendell Radio Automation System 
rivendell-dev@lists.rivendellaudio.org
Sent: Saturday, April 27, 2013 3:05 AM
Subject: Re: [RDD] Confused! Talk In/Out Segue In/Out


I have to agree; waveform display of an on-air cut is overkill. I can't 
imagine an on-air scenario where this was necessary, unless the jock was 
doing a mashup mix show and wanted to be able to loop and isolate portions 
of a song for creative scratch-mixing.

 In which case, MIXXX (www.mixxx.org) is probably a solution you'd be 
 interested in, running on a non-RD machine.

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


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