Re: [RDD] Big Book of Rivendell Cookbook?
On Mar 13, 2020, at 15:14, David Klann wrote: > Is the Wiki a suitable place to do this? Maybe something git-based (or github- > based) in order to continue with the current source code workflow? Perhaps, though I suspect that that could be intimidating for many casual contributors. I admit that I am not conversant with the gamut of what is available by way of online corroborative documentation (as opposed to coding) tools. Perhaps some others here can fill us in! 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] Big Book of Rivendell Cookbook?
Hi All, On Fri, 2020-03-13 at 15:02 -0400, Fred Gleason wrote: > On Mar 6, 2020, at 22:16, Steve wrote: > > > The first challenge is making the cookbook canonical, as in, The One > > True Source for such things and then making Google or > > Search_Engine_Of_Choice *find* and rank the cookbook. ... > > I’m wondering if a similar sort of workflow could be achieved with the > Cookbook —i.e. a ‘beta’ version that any registered user could freely edit, > changes to which could then be promoted to the ‘canonical’ site upon > approval of one of a (necessarily small) group of ‘core' documenters. FWIW, > I would be glad to serve as part of such a group. > I too would be willing and honored to be part of such a group. Is the Wiki a suitable place to do this? Maybe something git-based (or github- based) in order to continue with the current source code workflow? Thanks! ~David Klann ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
On Mar 6, 2020, at 22:16, Steve wrote: > The first challenge is making the cookbook canonical, as in, The One > True Source for such things and then making Google or > Search_Engine_Of_Choice *find* and rank the cookbook. The other side of > that is that people will get half of the wrong information from > somewhere else before arriving at the cookbook. This IMO is one of the fundamental obstacles facing the FOSS Community in general today. I call it the ‘It worked for me!’ syndrome. Yet, that very willingness —nay, eagerness— of knowledgable volunteers to help solve problems for perfect strangers is one of the key *strengths* of that Community as well. You can see it in action virtually every day here. It’s a dilemma that I doubt can ever be fully “fixed” (though having a well maintained cookbook that comes in on the top three results on the popular search engines would be a giant step towards that goal). The way that this is currently managed on the code side in Rivendell is that, while anybody can do anything they want with the code that is consonant with the GPLv2 license, changes that go into the ‘master’ branch at https://github.com/ElvishArtisan/rivendell (thence they eventually proceed to a subsequent ‘official’ release) must first be approved by the ‘Rivendell Architect’ —i.e. yours truly. I like to think that this is not because of dictatorial ambitions or other sinister motives on my part, but simply as a final sanity check to ensure not only correct technical operation but also consistency with the overarching design and ’style’ of Rivendell as a whole. I’m happy to say that it is relatively rarely that a pull request [request for a code change] has ever had to be dismissed out of hand. I’m wondering if a similar sort of workflow could be achieved with the Cookbook —i.e. a ‘beta’ version that any registered user could freely edit, changes to which could then be promoted to the ‘canonical’ site upon approval of one of a (necessarily small) group of ‘core' documenters. FWIW, I would be glad to serve as part of such a group. > Having more cooks leads to the third challenge: There is more than one > way to make lasagna. The way that I have Rivendell set up will have a > lot in common with everyone but will also have some nuances that I've > added based on local need or personal experience. If we all add our > "local need" and "personal experience" into the recipe, pretty soon > we're no longer making something consumable. A person new to Rivendell > won't know what to follow and we have a mess. This has been a central part of the UNIX culture since its very inception at Bell Labs in 1970. The way to manage it in a ‘cookbook' context is to maintain publicly a set of Best Practices (not unlike the style guides maintained by major national newspapers) and then use those as the basis for the approval decisions of the core documenters group. As always, one is free to manage Rivendell any way they want, but if one uses the Cookbook, one will get a necessarily opinionated (and consistent, and hopefully well thought out) ‘slant’ on how one goes about that. Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | Conceptual integrity in turn dictates that the design must proceed | | from one mind, or from a very small number of agreeing resonant | | minds. | | | | -- Frederick Brooks Jr.| | "The Mythical Man-Month" | |-| ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
On Mar 6, 2020, at 22:03, Robert Jeffares wrote: > It must be heartbreaking for people to write code for an operating system > that that have made a commitment to, and probably purchased or licenced > source code so their software will run, to find that the latest version, now > the sole version, has been re written such that their original code no longer > functions well, if at all. This has been the basic M$ game since at least the late 80s. Change a bunch of stuff, deprecate a bunch of other stuff, then release it with great fanfare as something “better”. Sometimes, some things *are* actually improvements, but mostly it’s an exercise in Change For The Sake Of Change, so they can sell the whole stack all over again (not just the code, but manuals, books, training, professional certifications, etc, etc). Being a huge multinational conglomerate means having *large* fixed costs which must be covered come hell or high water. Linux is not wholly immune to this phenomenon either (just look at GNOME 3), but the FOSS community has many Linux distros to choose from, as well as tools, techniques and an overall *culture* that are conducive to minimizing its effects (not to mention an overall pool of coders, writers and support people at least an order of magnitude larger than anything M$ can bring to bear). Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | The day-to-day travails of the Windows (tm) programmer are so | | amusing to most of us who are fortunate enough never to have been | | one -- like watching Charlie Chaplin trying to cook a shoe.| |-| ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
Robert's email inspired me to finally jump in on this thread, for better or worse... Much of what Robert wrote coincides with my experience, but I thought I'd add some perspective to the challenges I see around writing and maintaining a cookbook of that style. The project sounds interesting - I love the proposed chapter/recipe names. I've written several technical books, covering both Linux/Open Source and Microsoft technologies. There are a few challenges in writing a cookbook of the style being proposed. The first challenge is making the cookbook canonical, as in, The One True Source for such things and then making Google or Search_Engine_Of_Choice *find* and rank the cookbook. The other side of that is that people will get half of the wrong information from somewhere else before arriving at the cookbook. The next challenge is keeping the cookbook up to date. While there have been changes to Linux, many of those changes are not "break"-style changes from a Rivendell perspective. MySQL (now MariaDB) has been stable from the perspective of how Rivendell uses it. NFS has stayed roughly the same, and so forth. Granted, it could be argued that in a wiki-style cookbook we can have volunteers add and update. However, it will need to be maintained which takes commitment (and time). Having more cooks leads to the third challenge: There is more than one way to make lasagna. The way that I have Rivendell set up will have a lot in common with everyone but will also have some nuances that I've added based on local need or personal experience. If we all add our "local need" and "personal experience" into the recipe, pretty soon we're no longer making something consumable. A person new to Rivendell won't know what to follow and we have a mess. I created a cookbook-style manual specific to the station where I serve as an advisor. It didn't get read as much as I would have liked and is probably collecting dust in a production room somewhere. There is no doubt that having Linux experience has helped in getting more out of the system or, more appropriately, automating even more behind the scenes. However, I purposefully did not include that in the cookbook beyond how to recreate it. If there is energy towards making a cookbook-style reference, I would be happy to contribute where possible as a way of giving back too. Steve Suehring On Sat, Mar 07, 2020 at 03:10:28PM +1300, Robert Jeffares wrote: > > On 27/02/20 11:48 am, Frank Christel wrote: > > Drew, you asked ???I am not aware of a book like you are looking for. > > Can you give a little more details as to what sort of things you would > > want it to cover It???s always my hope when embarking on new > > explorations (such as a journey to Rivendell) that someone has written a > > travel guide. Something that doesn???t so much explain the nuts and > > bolts of how things work, but instead tells inspiring stories about the > > journey and what to see and do. Testimonies about overcoming obstacles. > > How whipping up raw ingredients yielded a yummy concoction. Chapter > > titles for a ???Big Book of Rivendell Cookbook??? might include: ??? Oh > > no, not again!: Cheerleading the adoption of (yet) another automation > > system ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
Hi Frank, I see the challenge. We have a similar situation here. A Windows 10 based system that has worked fine XP on has problems in W10. The vendor says it shouldn't but those updates and audio just don't go together. The 3am outages don't affect me as I am not the first responder. I get called at 6am when he knows I will be checking overnight mail. You need to be able to originate any programme from any studio: I am assuming a suitable switcher in MCR NPR will be some local and some link with local inserts. Thats one Rivendell service The Classical will be fully automated with possibly some live. Thats a second Service Looks like 5 in all. I would build one server with all services and one library so any studio can be used for live or voice tracking. Then a hot standby copy. The playout for the classical songbook and the jazz will be in MCR The BBC relay is direct or do you insert local ID's in the 1 min TOH window? Get an agreement to deal with the low hanging fruit and put the Jazz and the Songbook on First using a MCR located server and have one studio with a Client where VT's can be recorded. After it runs non stop for a while the argument for migrating the others will not be so hard. Actually I would put the classical on first. It must be heartbreaking for people to write code for an operating system that that have made a commitment to, and probably purchased or licenced source code so their software will run, to find that the latest version, now the sole version, has been re written such that their original code no longer functions well, if at all. Faced with a re write that they have not planned or budgeted for, possibly because there was no indication there would be a change, they have to go back to their clients and ask for more. Of course clients who have paid a monthly support fee for 10 years expect these changes to be dealt with. What should have been retained against such eventuality has ineviteably been used for something else. The result is grumpy end users, mountains of junk, and re tooling. R On 27/02/20 4:12 pm, Frank Christel wrote: Rob, We’re two FM / five HD stations licensed to The University of Tulsa. One station is NPR news/talk and the other is all-classical. Our HDs include an American songbook music channel, a jazz channel, and a 24/7 BBC World Service channel. https://www.publicradiotulsa.org Basically, we would need Rivendell to replace our network of ten BSI Simian workstations located in three studios, a master control, and one office, all tied together by a ZFS server. Programming originates from our studios, four NPR satellite receivers, Content Depot, and PRX SubAuto. The motivating factor behind considering a switch to Rivendell is the utter madness induced by Windows 10 updates over which we have little control. Our Simians ran fine on XP; were stable running 7; but are now falling apart on 10. Factory fixes include obscure registry tweaks on individual machines following Windows updates. In the meantime, too much dead air and 3 am calls. Even in the midst of all this insanity, zombie-eyed staff are embracing the devil they know rather than the one they don’t. It’s going to be a hard sell to switch automation systems for a third time; it took ten years for them to adjust to this one. Frank On 2/26/2020, at 10:26 AM, Rob Landry <41001...@interpring.com> wrote: What do you need Rivendell to do? I have it running on two satellite-driven commercial news/talk stations in New Hampshire, and on a CPB-funded, but locally programmed, music station in Boston, among others. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev -- Communication Consultants 2020 Limited 64 Warner Park Avenue Laingholm Auckland 0604 New Zealand ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
On 27/02/20 11:48 am, Frank Christel wrote: Drew, you asked “I am not aware of a book like you are looking for. Can you give a little more details as to what sort of things you would want it to cover?” It’s always my hope when embarking on new explorations (such as a journey to Rivendell) that someone has written a travel guide. Something that doesn’t so much explain the nuts and bolts of how things work, but instead tells inspiring stories about the journey and what to see and do. Testimonies about overcoming obstacles. How whipping up raw ingredients yielded a yummy concoction. Chapter titles for a “Big Book of Rivendell Cookbook” might include: — Oh no, not again!: Cheerleading the adoption of (yet) another automation system It's true there many computer based radio automation systems now, but if you take 2001 as a benchmark there were about 10 in general use and about the same now. The number available has increased from maybe 20 to well over 100. Windows based systems have had to deal with changes in the way Windows handles audio and other system calls. Windows 10 updates being the latest. Linux and Unix based systems have also had changes to deal with. Managed better by open source applications because the pool of programming personnel is larger. Rivendell has been on the list, in the top 5, all the time. Some systems have been adopted because vendors also supply Music and Schedule Billing software. For many access to support is vital. Automation is used to replace expensive people, and anything that can be operated by a fresh out of school intern has to be more attractive. On Air Staff tend not to be bundled with technical aptitude, so replacing records and cart machines with a computer is a challenge. The one thing old school jocks recognize immediately, is the Rivendell screen layout. The 'live' workflow is easy to adopt. The back office stuff is about the same for all systems. Rivendell stacks up on features, and is constantly being augmented as new needs and wants are incorporated. Rivendell is a 'made for broadcast' system. A number of systems used for automation were created for 'in store' systems or club DJ applications and need additional work to be able to include news bulletins or other timed events. Rivendell will run on almost any computer hardware platform. It works fine on 'stock' machines. As with any system, more RAM, faster Processors, Bigger Hard Drives and faster network connections will make it go better. The music plays the same. Users have a choice of on board cards, which may be adequate. External Cards, which also may be adequate, and ASI Cards which enable some features as well as delivering balanced audio at line level. More bang = more bucks. No matter what live assist/automation system you put in you will need at least one competent person on staff, or on call, to manage it. Rivendell has a paid support service if you are light on local talent. Some of the other systems offer support. Interpretations vary. — Who’s on first?: Where files live, sync, and play Rivendell is based on a single stand alone computer server which can also be the playout source for up to 3 independent services. Any number of Client computers can also deliver up to 3 independent services from the same global audio library. There is no Theoretical limit to services. Client computers may be Production or Voice Tracking nodes. There is no limitation other than hardware. Various 'commercial' systems have licence keys which may be a USB dongle or software registered to a specific computer. Running independent services may not be possible. The nightmare comes when the hardware fails and you need to cut to a back up. Rivendell back up is a mirrored server or whatever suits your situation. Rivendell uses wav files to store, retrieve & play audio. There are advantages over 'compressed' file formats, most relate to quality or the loss of it. There are also issues with 'tags' which can jam up the works. No operating system is immune to broken audio files that just lock things up. Large audio storage systems are not expensive. The history of mp3 mp2 and other 'lossy' formats is well documented elsewhere. If you are going to be a serious broadcaster you need to be serious about audio quality. — Doing the SaMBa: Integration with NPR satellite receivers Rivendell plays with any audio source. The satellite receiver delivers audio and may provide cue tones or pulses to stop start cut away for local ID 'live' or record for later transmission. Just how you implement it is up to you. Satellite, FTP, email. dropbox, you can manage all sources. — All roads lead to Rivendell: VNC access from inside and outside the studios Rivendell has remote desktop and command line access which you can configure to suit your needs. Team Viewer if you like. — Break down this wall!: Mass file importation strategies Rivendell can import large numbers of
Re: [RDD] Big Book of Rivendell Cookbook?
Ya... I tried to register and got: Error sending mail: Failed to connect to caspian.paravelsystems.com:25 [SMTP: Failed to connect socket: Permission denied (code: -1, response: )] Tim On 3/6/20 6:30 AM, Kyle Robbertze wrote: > Hi, > > On 2020/03/06 16:28, David Klann wrote: >> Hi Tim, >> >> That's a gorgeous setup you have there (in the screenshot). I love the eye- >> candy! :) >> >> On Thu, 2020-03-05 at 20:24 -0800, Tim Požár wrote: >>> I am starting a doc that looks like this may overlap the efforts here >>> for the cookbook. I am running KPEA-LP on a Raspberry Pi with a 1TB >>> drive handing off of it using Rivendell and StereoTool for the audio >>> processing on the same box[1]. Should I just start to add it here? >>> >> >> It would be awesome if you contributed to the new-ish cookbook on the >> Rivendell wiki. I believe Fred manages the wiki, and must approve requests >> for >> accounts. I encourage you to request an account and post your document there. > > Unfortunately it seems that wiki account creation is currently broken > due a broken connection to the SMTP server... > > Cheers > Kyle > ___ > 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] Big Book of Rivendell Cookbook?
Hi, On 2020/03/06 16:28, David Klann wrote: > Hi Tim, > > That's a gorgeous setup you have there (in the screenshot). I love the eye- > candy! :) > > On Thu, 2020-03-05 at 20:24 -0800, Tim Požár wrote: >> I am starting a doc that looks like this may overlap the efforts here >> for the cookbook. I am running KPEA-LP on a Raspberry Pi with a 1TB >> drive handing off of it using Rivendell and StereoTool for the audio >> processing on the same box[1]. Should I just start to add it here? >> > > It would be awesome if you contributed to the new-ish cookbook on the > Rivendell wiki. I believe Fred manages the wiki, and must approve requests for > accounts. I encourage you to request an account and post your document there. Unfortunately it seems that wiki account creation is currently broken due a broken connection to the SMTP server... Cheers Kyle ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
Hi Tim, That's a gorgeous setup you have there (in the screenshot). I love the eye- candy! :) On Thu, 2020-03-05 at 20:24 -0800, Tim Požár wrote: > I am starting a doc that looks like this may overlap the efforts here > for the cookbook. I am running KPEA-LP on a Raspberry Pi with a 1TB > drive handing off of it using Rivendell and StereoTool for the audio > processing on the same box[1]. Should I just start to add it here? > It would be awesome if you contributed to the new-ish cookbook on the Rivendell wiki. I believe Fred manages the wiki, and must approve requests for accounts. I encourage you to request an account and post your document there. Thanks! ~David Klann ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
I am starting a doc that looks like this may overlap the efforts here for the cookbook. I am running KPEA-LP on a Raspberry Pi with a 1TB drive handing off of it using Rivendell and StereoTool for the audio processing on the same box[1]. Should I just start to add it here? Tim [1] https://lns.com/rivendell_and_stereotool.png ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
The resistance to switching automation systems right now at Public Radio Tulsa has less to do with the pain of learning a new schema and coping with a new interface, but instead a somewhat unusual personnel issue. Within its staff of nine, there will be three retirements within six months. The station’s operation director will retire in May. No one is wanting to rock the boat right now, either for their own sake or those who come on board. That’s why we’ve begun research now into automation system alternatives. If the stations decide Rivendell is the way to go, then searching for a new operations director with Linux and Rivendell experience would be beneficial for future adoption. __ On Wed, Feb 26, 2020 at 10:13 PM Frank Christel wrote: Even in the midst of all this insanity, zombie-eyed staff are embracing the devil they know rather than the one they don’t. __ On 2/27/2020, at 6:30 AM, drew Roberts wrote: What is the break down of job categories and how many people are in each? What is the main area of concern? The jocks in the air studio in front of rdairplay? The people in the production studio? The people scheduling the music and traffic? The more technical people in the background keeping the system humming? ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
Hey drew, On Thu, 2020-02-27 at 13:07 -0500, you wrote: > > I suggest the addition of: > > — Party at the Beach: Live remote via IP with (openvpn and ((openob) or > (icecast and liquidsoap)). > > Fixed a spelling error from an earlier post and added in openvpn which may > be on the way out soon enough... > > I will try and run down my access to the wiki and start in on the vnc > remote control chapter soon. > Good point(s)! I've added the remote section to the table of contents... Thanks! ~David ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
On Thu, 27 Feb 2020, drew Roberts wrote: Have you tried running on windows in a VM hosted on linux? The only machine I have configured like that runs Windows Server 2003 in a virtual machine under Debian; it's used for an old Visual Traffic system that is otherwise unsupportable, and previous management insisted on RAID-1, which Debian supports. Now I come to think of it, there is one other: the streaming encoder at another station runs Omnia A/XE under Windows running in a virtual machine under Debian. That one had to be set up remotely, at a time when I couldn't physically get to the site, and the VM was the only way I could think to do it. It's been running like that for several years now. But generally, I don't like to run Windows under Linux; I don;t see how it can ever be as fast as Windows running directly on the hardware. Rob -- Сквозь грозы сияло нам солнце свободы И Linus великий нам путь озарил; Нас вырастил Stallman на верность народу, На труд и на подвиги нас вдохновил. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
David, I suggest the addition of: — Party at the Beach: Live remote via IP with (openvpn and ((openob) or (icecast and liquidsoap)). Fixed a spelling error from an earlier post and added in openvpn which may be on the way out soon enough... I will try and run down my access to the wiki and start in on the vnc remote control chapter soon. all the best, drew On Thu, Feb 27, 2020 at 11:57 AM David Klann wrote: > Greetings Frank, and others! > > On Wed, 2020-02-26 at 21:12 -0600, you wrote: > > Rob, > > > > ... [background info snipped] > > > > The motivating factor behind considering a switch to Rivendell is the > utter > > madness induced by Windows 10 updates over which we have little control. > Our > > Simians ran fine on XP; were stable running 7; but are now falling apart > on > > 10. Factory fixes include obscure registry tweaks on individual machines > > following Windows updates. In the meantime, too much dead air and 3 am > > calls. > > > > I LOVE your idea of the Big Book of Rivendell Cookbook. I've taken the > liberty > to start such a section on the Rivendell Wiki: > http://wiki.rivendellaudio.org/index.php/Cookbook > > It's just a start, and I intend on continuing the work on it (I've been > contemplating writing such a book for a couple of years...). I look > forward to > seeing contributions from others in the community! > > > Even in the midst of all this insanity, zombie-eyed staff are embracing > the > > devil they know rather than the one they don’t. It’s going to be a hard > sell > > to switch automation systems for a third time; it took ten years for > them to > > adjust to this one. > > > > Frank > > > > As I wrote in the nascent "first chapter" of the Cookbook, adopting a new > automation system is like rebuilding after a flood or a fire. As you no > doubt > know, you definitely want to get everyone on board before taking on such a > monumental task. > > I'm excited and tickled to be part of this active and passionate community > of > Rivendell users and developers! > > Best, > > ~David Klann > > > ___ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > -- Enjoy the *Paradise Island Cam* playing *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/ ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
Rob, On Thu, Feb 27, 2020 at 12:11 PM Rob Landry <41001...@interpring.com> wrote: > > On Wed, 26 Feb 2020, Tim Camp wrote: > > > BTW for the cold dead hands person, audition 3.0 runs quite well under > wine > > 4.2 and above on Linux. > > I have not had much success doing that; the software installs and runs, > but it's slow and I get lots of audio dropouts. > Have you tried running on windows in a VM hosted on linux? all the best, drew > > > Rob > > -- > Сквозь грозы сияло нам солнце свободы > И Linus великий нам путь озарил; > Нас вырастил Stallman на верность народу, > На труд и на подвиги нас вдохновил. -- Enjoy the *Paradise Island Cam* playing *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/ ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
On Wed, 26 Feb 2020, Frank Christel wrote: Basically, we would need Rivendell to replace our network of ten BSI Simian workstations located in three studios, a master control, and one office, all tied together by a ZFS server. Programming originates from our studios, four NPR satellite receivers, Content Depot, and PRX SubAuto. That should be eminently doable. The satellite receivers are Linux boxes and can do NFS. At WUMB, we no longer use satellite receivers because the university took our dish away, but it shouldn't be hard to get them to work with Rivendell. With WUMB's old WireReady system, I had to write a Perl script to grab the files off the receivers, extract the metadata, decode the files to linear .wav files, and rename them to the five-digit numbers specified in the metadata. Rivendell can do all of that out of the box. We still have a script executed by a cron job that grabs files from Content Depot and drops them into Rivendell drop boxes. The motivating factor behind considering a switch to Rivendell is the utter madness induced by Windows 10 updates over which we have little control. Our Simians ran fine on XP; were stable running 7; but are now falling apart on 10. Factory fixes include obscure registry tweaks on individual machines following Windows updates. In the meantime, too much dead air and 3 am calls. I take it that continuing to run the Simians son Windows 7 is not an option. Even in the midst of all this insanity, zombie-eyed staff are embracing the devil they know rather than the one they don’t. It’s going to be a hard sell to switch automation systems for a third time; it took ten years for them to adjust to this one. Give them a laptop with a stand-alone Rivendell system on it for them to play with. Rivendell was so much more intuitive than what they were used to that our people's inertia quickly melted away. Rob -- Сквозь грозы сияло нам солнце свободы И Linus великий нам путь озарил; Нас вырастил Stallman на верность народу, На труд и на подвиги нас вдохновил. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
On Wed, 26 Feb 2020, Tim Camp wrote: BTW for the cold dead hands person, audition 3.0 runs quite well under wine 4.2 and above on Linux. I have not had much success doing that; the software installs and runs, but it's slow and I get lots of audio dropouts. Rob -- Сквозь грозы сияло нам солнце свободы И Linus великий нам путь озарил; Нас вырастил Stallman на верность народу, На труд и на подвиги нас вдохновил.___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
Greetings Frank, and others! On Wed, 2020-02-26 at 21:12 -0600, you wrote: > Rob, > > ... [background info snipped] > > The motivating factor behind considering a switch to Rivendell is the utter > madness induced by Windows 10 updates over which we have little control. Our > Simians ran fine on XP; were stable running 7; but are now falling apart on > 10. Factory fixes include obscure registry tweaks on individual machines > following Windows updates. In the meantime, too much dead air and 3 am > calls. > I LOVE your idea of the Big Book of Rivendell Cookbook. I've taken the liberty to start such a section on the Rivendell Wiki: http://wiki.rivendellaudio.org/index.php/Cookbook It's just a start, and I intend on continuing the work on it (I've been contemplating writing such a book for a couple of years...). I look forward to seeing contributions from others in the community! > Even in the midst of all this insanity, zombie-eyed staff are embracing the > devil they know rather than the one they don’t. It’s going to be a hard sell > to switch automation systems for a third time; it took ten years for them to > adjust to this one. > > Frank > As I wrote in the nascent "first chapter" of the Cookbook, adopting a new automation system is like rebuilding after a flood or a fire. As you no doubt know, you definitely want to get everyone on board before taking on such a monumental task. I'm excited and tickled to be part of this active and passionate community of Rivendell users and developers! Best, ~David Klann ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
Frank, On Wed, Feb 26, 2020 at 10:13 PM Frank Christel wrote: > Rob, > > snip > > The motivating factor behind considering a switch to Rivendell is the > utter madness induced by Windows 10 updates over which we have little > control. Our Simians ran fine on XP; were stable running 7; but are now > falling apart on 10. Factory fixes include obscure registry tweaks on > individual machines following Windows updates. In the meantime, too much > dead air and 3 am calls. > > Even in the midst of all this insanity, zombie-eyed staff are embracing > the devil they know rather than the one they don’t. What is the break down of job categories and how many people are in each? What is the main area of concern? The jocks in the air studio in front of rdairplay? The people in the production studio? The people scheduling the music and traffic? The more technical people in the background keeping the system humming? I was involved in a 5 station switch from AudioVAULT to WideOrbit. Somewhere before the switch I started mucking about with beta Rivendell on a used machine with no soundcard to run a streaming only station of my own that played only gratis available music that was under what I considered to be the Creative Commons libre licenses (BY, and BY-SA)... We were considering WideOrbit for the new station I am with now but while we were in the process of securing an FM license, we brought up a streaming only station as a demo for The Bahamas Junkanoo Carnival and when that took longer than expected to work out, we decided to do a Bahamian Music only streaming station until we got that license. The rest, as they say, is history: https://bahamianornuttin.com/ We now also build what we call Private Radio Stations for clients. (Basically as full as needed, Rivendell based radio stations sans the transmitter.) > It’s going to be a hard sell to switch automation systems for a third > time; it took ten years for them to adjust to this one. > I said all that above to suggest this: One option would be to buy as many used laptops or mini machines capable of running Rivendell as needed to give enough key people their own private standalone Rivendell learning environments. Set it up to where they can be managed and updated remotely for troubleshooting and help / hand holding. I would be willing to help some with this project if that angle sounds interesting to you. > Frank > > all the best, drew -- Enjoy the *Paradise Island Cam* playing *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/ ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
Rob, We’re two FM / five HD stations licensed to The University of Tulsa. One station is NPR news/talk and the other is all-classical. Our HDs include an American songbook music channel, a jazz channel, and a 24/7 BBC World Service channel. https://www.publicradiotulsa.org Basically, we would need Rivendell to replace our network of ten BSI Simian workstations located in three studios, a master control, and one office, all tied together by a ZFS server. Programming originates from our studios, four NPR satellite receivers, Content Depot, and PRX SubAuto. The motivating factor behind considering a switch to Rivendell is the utter madness induced by Windows 10 updates over which we have little control. Our Simians ran fine on XP; were stable running 7; but are now falling apart on 10. Factory fixes include obscure registry tweaks on individual machines following Windows updates. In the meantime, too much dead air and 3 am calls. Even in the midst of all this insanity, zombie-eyed staff are embracing the devil they know rather than the one they don’t. It’s going to be a hard sell to switch automation systems for a third time; it took ten years for them to adjust to this one. Frank On 2/26/2020, at 10:26 AM, Rob Landry <41001...@interpring.com> wrote: What do you need Rivendell to do? I have it running on two satellite-driven commercial news/talk stations in New Hampshire, and on a CPB-funded, but locally programmed, music station in Boston, among others. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
BTW for the cold dead hands person, audition 3.0 runs quite well under wine 4.2 and above on Linux. Tim Camp WZEW-FM On Wed, Feb 26, 2020, 5:20 PM drew Roberts wrote: > Frank, > > On Wed, Feb 26, 2020 at 5:48 PM Frank Christel > wrote: > >> Drew, you asked “I am not aware of a book like you are looking for. Can >> you give a little more details as to what sort of things you would want it >> to cover?” >> >> It’s always my hope when embarking on new explorations (such as a journey >> to Rivendell) that someone has written a travel guide. > > > I think we may be somewhat similar in this. I tend to prefer HOW-TOs to > man pages. Even though I know I should invest the time and it will likely > pay off big in the long run, I have never quite managed to grok man pages. > I much prefer several variations or working examples from which I can mix > and match and extrapolate. > > Do you have a favourite example of this genre of book on another subject? > > >> Something that doesn’t so much explain the nuts and bolts of how things >> work, but instead tells inspiring stories about the journey and what to see >> and do. Testimonies about overcoming obstacles. How whipping up raw >> ingredients yielded a yummy concoction. >> > > Would you like to try developing this book on the wiki? > > >> >> Chapter titles for a “Big Book of Rivendell Cookbook” might include: >> >> — Oh no, not again!: Cheerleading the adoption of (yet) another >> automation system >> — Who’s on first?: Where files live, sync, and play >> — Doing the SaMBa: Integration with NPR satellite receivers >> — All roads lead to Rivendell: VNC access from inside and outside the >> studios >> > > I could work some on the above chapter. I have been doing it long enough. > Perhaps too long, I may be doing it in an outdated manner. > > > >> — Break down this wall!: Mass file importation strategies >> — Rosie the Robot: Clever uses of macro carts in the real world >> — Flowing down the river: Understanding Rivendell’s system of carts, >> events, clocks, grid, and logs >> — We just have time for one more: Automating music hours to meet time >> posts >> — Glasnost, comrade: Network coexistence with Windows machines >> — Doing what comes naturally: The easy way to integrate Natural Log and >> Natural Music >> — In five, four, three: Breaking format for local emergencies and >> congressional debates >> — Play it again, Sam: Playing MP2 files without using ASI cards >> — The path less travelled: Linux isn’t as scary as it looks >> — You’ll pry my dead, cold hand: Switching staff from Adobe Audition to a >> Linux-based audio editor >> — Front porch whittlin’:What to do with free time saved by not >> babysitting cranky automation systems >> >> > — Party at the Beach: Live remote via IP with openop or icecast and > liquidsoap. > > >> Purely by coincidence, those chapters mirror questions and objections >> staff have raised in considering our adoption of Rivendell. >> >> Frank >> > > all the best, > > drew > -- > Enjoy the *Paradise Island Cam* playing > *Bahamian Or Nuttin* - https://www.paradiseislandcam.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
Re: [RDD] Big Book of Rivendell Cookbook?
Frank, On Wed, Feb 26, 2020 at 5:48 PM Frank Christel wrote: > Drew, you asked “I am not aware of a book like you are looking for. Can > you give a little more details as to what sort of things you would want it > to cover?” > > It’s always my hope when embarking on new explorations (such as a journey > to Rivendell) that someone has written a travel guide. I think we may be somewhat similar in this. I tend to prefer HOW-TOs to man pages. Even though I know I should invest the time and it will likely pay off big in the long run, I have never quite managed to grok man pages. I much prefer several variations or working examples from which I can mix and match and extrapolate. Do you have a favourite example of this genre of book on another subject? > Something that doesn’t so much explain the nuts and bolts of how things > work, but instead tells inspiring stories about the journey and what to see > and do. Testimonies about overcoming obstacles. How whipping up raw > ingredients yielded a yummy concoction. > Would you like to try developing this book on the wiki? > > Chapter titles for a “Big Book of Rivendell Cookbook” might include: > > — Oh no, not again!: Cheerleading the adoption of (yet) another automation > system > — Who’s on first?: Where files live, sync, and play > — Doing the SaMBa: Integration with NPR satellite receivers > — All roads lead to Rivendell: VNC access from inside and outside the > studios > I could work some on the above chapter. I have been doing it long enough. Perhaps too long, I may be doing it in an outdated manner. > — Break down this wall!: Mass file importation strategies > — Rosie the Robot: Clever uses of macro carts in the real world > — Flowing down the river: Understanding Rivendell’s system of carts, > events, clocks, grid, and logs > — We just have time for one more: Automating music hours to meet time posts > — Glasnost, comrade: Network coexistence with Windows machines > — Doing what comes naturally: The easy way to integrate Natural Log and > Natural Music > — In five, four, three: Breaking format for local emergencies and > congressional debates > — Play it again, Sam: Playing MP2 files without using ASI cards > — The path less travelled: Linux isn’t as scary as it looks > — You’ll pry my dead, cold hand: Switching staff from Adobe Audition to a > Linux-based audio editor > — Front porch whittlin’:What to do with free time saved by not babysitting > cranky automation systems > > — Party at the Beach: Live remote via IP with openop or icecast and liquidsoap. > Purely by coincidence, those chapters mirror questions and objections > staff have raised in considering our adoption of Rivendell. > > Frank > all the best, drew -- Enjoy the *Paradise Island Cam* playing *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/ ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
Drew, you asked “I am not aware of a book like you are looking for. Can you give a little more details as to what sort of things you would want it to cover?” It’s always my hope when embarking on new explorations (such as a journey to Rivendell) that someone has written a travel guide. Something that doesn’t so much explain the nuts and bolts of how things work, but instead tells inspiring stories about the journey and what to see and do. Testimonies about overcoming obstacles. How whipping up raw ingredients yielded a yummy concoction. Chapter titles for a “Big Book of Rivendell Cookbook” might include: — Oh no, not again!: Cheerleading the adoption of (yet) another automation system — Who’s on first?: Where files live, sync, and play — Doing the SaMBa: Integration with NPR satellite receivers — All roads lead to Rivendell: VNC access from inside and outside the studios — Break down this wall!: Mass file importation strategies — Rosie the Robot: Clever uses of macro carts in the real world — Flowing down the river: Understanding Rivendell’s system of carts, events, clocks, grid, and logs — We just have time for one more: Automating music hours to meet time posts — Glasnost, comrade: Network coexistence with Windows machines — Doing what comes naturally: The easy way to integrate Natural Log and Natural Music — In five, four, three: Breaking format for local emergencies and congressional debates — Play it again, Sam: Playing MP2 files without using ASI cards — The path less travelled: Linux isn’t as scary as it looks — You’ll pry my dead, cold hand: Switching staff from Adobe Audition to a Linux-based audio editor — Front porch whittlin’:What to do with free time saved by not babysitting cranky automation systems Purely by coincidence, those chapters mirror questions and objections staff have raised in considering our adoption of Rivendell. Frank ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
Folks, Kudos to Mike, Tim, Drew, John, and Rob for pointing me toward Rivendell learning resources, offering advice, and describing their real-world setups. I’ve also received great encouragement over on the PubTech list, especially from Bill Putney at WBTZ and Darrell McCalla at WBHM who are rabid (in a good way) Rivendell adopters. I can’t remember when I’ve encountered such a friendly and eager-to-share group like this. This is certainly a welcome resource for the RD noobs like me. Thank you! Frank ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
On Mon, 24 Feb 2020, Frank Christel wrote: We're walking through the manual and searching the rivendell-dev archives for answers. So far, we’ve not hit a brick wall in researching what Rivendell might do for our NPR stations. What do you need Rivendell to do? I have it running on two satellite-driven commercial news/talk stations in New Hampshire, and on a CPB-funded, but locally programmed, music station in Boston, among others. Rivendell Macro Language, and its ability to execute shell commands, makes Rivendell very versatile. I assume you've looked at the Rivendell Operations Guide. Rob -- Сквозь грозы сияло нам солнце свободы И Linus великий нам путь озарил; Нас вырастил Stallman на верность народу, На труд и на подвиги нас вдохновил. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
Mike, your post reminded me of something I forgot. There is the #rivendell IRC channel on freenode.net On Mon, Feb 24, 2020 at 7:30 PM Mike Carroll wrote: > There's a wiki with some information here: > http://wiki.rivendellaudio.org/index.php/Main_Page > And this blog entry about scheduling music with Rivendell (2009, still > useful): > https://thebrettblog.wordpress.com/2009/12/31/rivendell-how-to-schedule-music/ > And a Rivendell users group on Facebook here (private, requires > membership): https://www.facebook.com/groups/1739406449620107/ > I am not sure I knew about the facebook group. Thanks. I just joined. all the best, drew > > > On Mon, Feb 24, 2020 at 3:40 PM Frank Christel > wrote: > >> We’re researching a switch to Rivendell. We’ve used Simian for the last >> decade and before that AudioVault. Lately, though, almost every Windows 10 >> update is breaking Simian. And BSI says Simian is at end-of-life. >> >> I’ve been discovering what Rivendell can do on a Raspberry Pi - it runs >> surprisingly well. We’re configuring a Dell as a Rivendell test bed for one >> of our HD channels. >> >> We're walking through the manual and searching the rivendell-dev archives >> for answers. So far, we’ve not hit a brick wall in researching what >> Rivendell might do for our NPR stations. >> >> Is there a “Big Book of Rivendell Cookbook” to give us a 20,000-ft setup >> and operational view? >> ___ >> 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 > -- Enjoy the *Paradise Island Cam* playing *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/ ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
Hi Frank... On Mon, Feb 24, 2020 at 6:40 PM Frank Christel wrote: > We’re researching a switch to Rivendell. We’ve used Simian for the last > decade and before that AudioVault. Lately, though, almost every Windows 10 > update is breaking Simian. And BSI says Simian is at end-of-life. > Our current team was audiovault for many years, wideorbit for a while and then rivendell for several years for a different group. In addition, I have been using Rivendell since 0.9x iirc perhaps earlier? > > I’ve been discovering what Rivendell can do on a Raspberry Pi - it runs > surprisingly well. We have done this for a small experiment. We have also done small "stations" with liquidsoap. > We’re configuring a Dell as a Rivendell test bed for one of our HD > channels. > > We're walking through the manual and searching the rivendell-dev archives > for answers. So far, we’ve not hit a brick wall in researching what > Rivendell might do for our NPR stations. > > Is there a “Big Book of Rivendell Cookbook” to give us a 20,000-ft setup > and operational view? > You indicate you know of the manual and the mailing list. There is also the wiki. And github. I am not aware of a book like you are looking for. Can you give a little more details as to what sort of things you would want it to cover? Perhaps it could be developed on the wiki? all the best, drew > ___ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > -- Enjoy the *Paradise Island Cam* playing *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/ ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Big Book of Rivendell Cookbook?
There's a wiki with some information here: http://wiki.rivendellaudio.org/index.php/Main_Page And this blog entry about scheduling music with Rivendell (2009, still useful): https://thebrettblog.wordpress.com/2009/12/31/rivendell-how-to-schedule-music/ And a Rivendell users group on Facebook here (private, requires membership): https://www.facebook.com/groups/1739406449620107/ On Mon, Feb 24, 2020 at 3:40 PM Frank Christel wrote: > We’re researching a switch to Rivendell. We’ve used Simian for the last > decade and before that AudioVault. Lately, though, almost every Windows 10 > update is breaking Simian. And BSI says Simian is at end-of-life. > > I’ve been discovering what Rivendell can do on a Raspberry Pi - it runs > surprisingly well. We’re configuring a Dell as a Rivendell test bed for one > of our HD channels. > > We're walking through the manual and searching the rivendell-dev archives > for answers. So far, we’ve not hit a brick wall in researching what > Rivendell might do for our NPR stations. > > Is there a “Big Book of Rivendell Cookbook” to give us a 20,000-ft setup > and operational view? > ___ > 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
