Re: [RDD] CentOS 8 short-lived, only rolling versions after that
Thanks for the comments, Fred. I was hoping you were going to chime in. The commentary on Hacker News and elsewhere is far gloomier than yours. I hope you are correct. Ryan On Wed, Dec 9, 2020 at 11:22 AM Fred Gleason wrote: > On Dec 8, 2020, at 19:46, Mike Carroll wrote: > > Not a popular decision, going by the comments on the post. > > > I’m not actually sure that it’s The End of the World for Rivendell on > CentOS just yet. > > A lot will depend on what exactly changes between CentOS 8 and CentOS 8 > Stream. At first look, it appears that CentOS is merely moving their > release cycle to be just *ahead* of RHEL releases, instead of just *after*. > If that’s truly all it is, and, all importantly, provided the CentOS 8 ABI > is being held stable, then I see no reason *per se* that we couldn’t > support Rivendell just fine on CentOS 8 Stream. I do know that there has > been a lot of frustration within the CentOS Project about churn > (particularly in the package management realm) from Upstream; this move to > CentOS 8 Stream I suspect is an attempt to get a better handle on that > problem by what might be called a ‘pre-emptive release’ strategy that > allows them to better synchronize the state of their own port from Upstream. > > A lot will also depend on where EPEL lands with all of this. EPEL is part > of Fedora (not CentOS), and has historically always based their builds on > RHEL. Provided that the ABI is stable, it shouldn’t much matter, but the > devil is in the details. I’ve sensed a bit of the same ‘churn angst’ WRT > Upstream with many of the EPEL maintainers as well. > > We’ll see. Given that we don’t currently have a shipping CentOS 8 > integration, it’s definitely too early to panic. Indeed, holding off on > that integration is starting to look like a rather fortuitous move. > > 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 > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] 2.18.2 Evergreen
I think there might be another element to this bug besides just aesthetics. If a cut has a data range enabled and you then also make it evergreen, it will not be a valid cut. The evergreen does not appear to overrule the date range. Can anyone else confirm this? On Mon, Jan 8, 2018 at 9:30 AM, Fred Gleason <fr...@paravelsystems.com> wrote: > On Jan 6, 2018, at 17:34, Ryan Williams <rya...@gmail.com> wrote: > > In RDLibrary on 2.18.2, cuts that are selected to be "evergreen" are no > longer showing a green highlight. Instead they are white until selected and > then light grey. > > > Fixed in Git ‘stable’. > > 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 > > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] 2.18.2 Evergreen
In RDLibrary on 2.18.2, cuts that are selected to be "evergreen" are no longer showing a green highlight. Instead they are white until selected and then light grey. Anyone else seeing this? Ryan ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell v2.15.3
That's good to know as a partial work around for the time being. On Tue, Mar 28, 2017 at 10:05 AM, Fred Gleason <fr...@paravelsystems.com> wrote: > On Mar 28, 2017, at 10:57, Ryan Williams <rya...@gmail.com> wrote: > > I'm having an regression with the most recent release. If I open RDLogEdit > and try to add to a log's description it does not save. We use the field > field to add "READY" to the end of the description when the log is cleared > for air, so this one is going to sting a lot. > > > Partially confirmed here. If you use the ‘Save’ button, the updated > Description is indeed lost. However, clicking ‘OK’ (without clicking > ‘Save’ first) appears to work normally. > > 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 > > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell v2.15.3
I'm having an regression with the most recent release. If I open RDLogEdit and try to add to a log's description it does not save. We use the field field to add "READY" to the end of the description when the log is cleared for air, so this one is going to sting a lot. Ryan On Sat, Mar 25, 2017 at 8:36 AM, Fred Gleasonwrote: > On Mar 24, 2017, at 18:14, Hoggins! wrote: > > Looks like the tar.gz file is not present on the repository. > > > Fixed. > > 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 > > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Startup Error Message / ASI Card Not Working
I'm wishing, right now, that I had skipped updating too. It sounds kind of dicey to recompile the ASI driver and then replace the current one. I don't want to make a bad situation worse. Any other ideas? On Wed, Aug 31, 2016 at 1:40 PM, Rob Landry <41001...@interpring.com> wrote: > > This sort of problem is why I generally don't do software updates on > Rivendell workstations. > > The last time I had problems with the machine seeing an ASI card, I > recompiled the asihpi driver, reinstalled it, and the problem went away. > > > Rob > > -- > Я там, где ребята толковые, > Я там, где плакаты "Вперёд", > Где песни рабочие новые > Страна трудовая поёт. > > > On Wed, 31 Aug 2016, Ryan Williams wrote: > > Recently I did a software update on an appliance installation (the update >> included a kernel update as well as the most recent version of Rivendell). >> After reboot one of the two ASI cards is not showing up in audio >> resources. >> Unfortunately, this is the card that we do all of the satellite recording >> on. >> I tried booting into the last couple of kernels and the card does not show >> on any of them. >> >> Here is the strange message at boot time: >> >> "Welcome to CentOS >> Starting udev: hpi6205. c:777 DSP code load failed >> hpioctl.c:520 adapter_probe failed" >> >> Any idea what is going on here and how to fix it? Did not have any trouble >> with this card prior to update and reboot. >> >> The other ASI card is working normally. >> >> Ryan >> >> ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] Startup Error Message / ASI Card Not Working
Recently I did a software update on an appliance installation (the update included a kernel update as well as the most recent version of Rivendell). After reboot one of the two ASI cards is not showing up in audio resources. Unfortunately, this is the card that we do all of the satellite recording on. I tried booting into the last couple of kernels and the card does not show on any of them. Here is the strange message at boot time: "Welcome to CentOS Starting udev: hpi6205. c:777 DSP code load failed hpioctl.c:520 adapter_probe failed" Any idea what is going on here and how to fix it? Did not have any trouble with this card prior to update and reboot. The other ASI card is working normally. Ryan ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] Serial Port PCI Card
Does anyone have a recommendation for a PCI serial card that works out of the box with the appliance? I've bought a couple and have been unable to get them to work. A specific make and model would be greatly appreciated! Ryan ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] RDCartSlots Feature Request
I am very pleased with the addition of RDCartSlots to the Rivendell project. Here at the station we still have an old license of WaveCart to use during live events, this is done so the main log can continue running in the background without being disturbed and can be rejoined in-progress whenever necessary. What is missing from RDCartSlots is a way to auto-step from one cartslot to another. Say I have a break and want to run 3 :30s and a 5 second liner. Running that from RDCartSlots would require the board op to have four perfect clicks to avoid dead-air or overlap. What I would like is a way to cue up additional cartslots to air after the first slot is over. Does this sound useful to anyone else? Ryan ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Need Help With Serial Problems
I think I have this issue mostly figured out and will write another email to the list soon explaining the problem when time allows. Spoiler: it was mostly operator error. Thanks everyone for the initial help and ideas. Ryan On Thu, Jan 30, 2014 at 4:50 PM, Ryan Williams rya...@gmail.com wrote: Thank you everyone very much for the helpful ideas. Right after I wrote the first SOS email, I came down sick and have been under the weather since. I was able to try a couple of the suggestions. Here is the output for the dmesg command: [rd@rdserv ~]$ dmesg | grep tty console [tty0] enabled ttyS0: detected caps 0700 should be 0100 :02:00.0: ttyS0 at I/O 0xe060 (irq = 16) is a 16C950/954 ttyS1: detected caps 0700 should be 0100 :02:00.0: ttyS1 at I/O 0xe068 (irq = 16) is a 16C950/954 ttyS2: detected caps 0700 should be 0100 :02:00.0: ttyS2 at I/O 0xe070 (irq = 16) is a 16C950/954 ttyS3: detected caps 0700 should be 0100 :02:00.0: ttyS3 at I/O 0xe078 (irq = 16) is a 16C950/954 usb 3-4: pl2303 converter now attached to ttyUSB0 [rd@rdserv ~]$ Typing characters into minicom connected to ttyS0, ttyS1 and ttyUSB0 (I didn't try S2 or S3) made the activity light on the switcher flash. I couldn't remember the command for changing the input to a particular output, but it does seem to be receiving some bits. After I noticed the light flashing with minicom, I was curious if it would show activity when a switch event was fired off from RDCatch. It did flash, but the channel did not change. (Fred, you said to set minicom to full duplex. I couldn't find that setting. Does it have a different name?) I was able to make a loopback serial plug and can hopefully work with it more tomorrow if I am feeling up to it. Thanks again everyone and if anything stands out to you or if you have any more ideas, please let me know. Ryan On Wed, Jan 29, 2014 at 11:30 AM, Cowboy c...@cwf1.com wrote: On Wednesday 29 January 2014 11:46:54 am drew Roberts wrote: Try leaving Rivendell out of the mix. Can you talk to the device from a program like minicom? You can even leave minicom out of the mix. Do the dmesg thing and find the device. Find the device file. Let's say it ends up being /dev/ttyS1 for discussion purposes. Check the permissions, group memberships, etc. on the device. If they are wrong, then the tests can fail even if you do things right ! In a terminal window, do echo The Quick Brown Fox Jumped Over The Lazy Dogs Back /dev/ttyS1 If there is a serial port there, you'll get nothing. If there is no serial port there, you'll get an error message. You should find some useful information in /proc/devices /proc/interrupts /proc/ioports /proc/tty/drivers /proc/tty/driver/serial Once you know that the hardware is there, and that the terminal window can cat stuff to it, it's a matter of configuring things correctly, but at least you will know it really is there, and can be accessed. -- Cowboy http://cowboy.cwf1.com Please take note: ___ 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] Need Help With Serial Problems
Thank you everyone very much for the helpful ideas. Right after I wrote the first SOS email, I came down sick and have been under the weather since. I was able to try a couple of the suggestions. Here is the output for the dmesg command: [rd@rdserv ~]$ dmesg | grep tty console [tty0] enabled ttyS0: detected caps 0700 should be 0100 :02:00.0: ttyS0 at I/O 0xe060 (irq = 16) is a 16C950/954 ttyS1: detected caps 0700 should be 0100 :02:00.0: ttyS1 at I/O 0xe068 (irq = 16) is a 16C950/954 ttyS2: detected caps 0700 should be 0100 :02:00.0: ttyS2 at I/O 0xe070 (irq = 16) is a 16C950/954 ttyS3: detected caps 0700 should be 0100 :02:00.0: ttyS3 at I/O 0xe078 (irq = 16) is a 16C950/954 usb 3-4: pl2303 converter now attached to ttyUSB0 [rd@rdserv ~]$ Typing characters into minicom connected to ttyS0, ttyS1 and ttyUSB0 (I didn't try S2 or S3) made the activity light on the switcher flash. I couldn't remember the command for changing the input to a particular output, but it does seem to be receiving some bits. After I noticed the light flashing with minicom, I was curious if it would show activity when a switch event was fired off from RDCatch. It did flash, but the channel did not change. (Fred, you said to set minicom to full duplex. I couldn't find that setting. Does it have a different name?) I was able to make a loopback serial plug and can hopefully work with it more tomorrow if I am feeling up to it. Thanks again everyone and if anything stands out to you or if you have any more ideas, please let me know. Ryan On Wed, Jan 29, 2014 at 11:30 AM, Cowboy c...@cwf1.com wrote: On Wednesday 29 January 2014 11:46:54 am drew Roberts wrote: Try leaving Rivendell out of the mix. Can you talk to the device from a program like minicom? You can even leave minicom out of the mix. Do the dmesg thing and find the device. Find the device file. Let's say it ends up being /dev/ttyS1 for discussion purposes. Check the permissions, group memberships, etc. on the device. If they are wrong, then the tests can fail even if you do things right ! In a terminal window, do echo The Quick Brown Fox Jumped Over The Lazy Dogs Back /dev/ttyS1 If there is a serial port there, you'll get nothing. If there is no serial port there, you'll get an error message. You should find some useful information in /proc/devices /proc/interrupts /proc/ioports /proc/tty/drivers /proc/tty/driver/serial Once you know that the hardware is there, and that the terminal window can cat stuff to it, it's a matter of configuring things correctly, but at least you will know it really is there, and can be accessed. -- Cowboy http://cowboy.cwf1.com Please take note: ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] Need Help With Serial Problems
I have a new Rivendell system that I am trying desperately trying to bring online. I've been fighting with the serial ports to work for the last couple of weeks and I am posting here because think I need additional help. The goal here is to control a BroadcastTools 8.2 switcher and a Unity 4000 satellite receiver. I am using the latest appliance, so CentOS 6.4 with Rivendell 2.5.5 (also tried with 2.7.1) running on an Intel DH87MC motherboard. The motherboard has no on-board serial ports, so I bought a Rosewill RC-301 PCI serial card. The card supposedly supports Linux, but their instructions seem incomplete and I could never get the switcher to budge even trying /dev/ttyS0 through /dev/ttyS3 with proper settings for the 8.2. I also purchased two different USB to Serial adapters, at least one of which uses the Prolific chipset. Both adapters show up automatically when plugged in as /dev/ttyUSB0 and /dev/ttyUSB1 respectively, but neither can get the switcher to change channels. Finally, I pulled a SIIG CyberPro S4 PCI serial card out of our current Rivendell box. This card is old and is used to control the switcher and receiver throughout the day. That box runs version 1 of the appliance and is on CentOS 5 and Rivendell 2.0.2-1. When I set up that system, I do not remember doing anything special to make the card work. That same card does nothing in the new box, even though an exhaustive process of trying all /dev/ttySx addresses. I'm running out of ideas and and already running behind schedule. Does anyone have any additional insights? Am I missing something beyond the RDAdmin Manage Hosts Serial Ports that enables the ports to operate? Do I need to enable something in the bios? If there is another PCI serial card that for sure works out of the box with the appliance I will order it today. Please help! Ryan ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] USB to Serial Adapter
Does anyone have a recommendation for a USB to Serial adapter? This is to control a BT 8x2 switcher using the Appliance v2. Ryan ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] mySQL Problem on Fresh Appliance Install
Thanks, Fred. I'm going to keep working with it and I'll update this with any further results. Ryan On Mon, Dec 23, 2013 at 11:10 AM, Fred Gleason fr...@paravelsystems.comwrote: On Dec 20, 2013, at 12:05 41, Ryan Williams rya...@gmail.com wrote: Are there credentials I can enter to reconnect to the database? The default admin credentials are ‘root’ with no password. The default user credentials are ‘rduser’ with a password of ‘letmein’. 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 ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] System Hardware
I am wanting to put together a little Rivendell system for a side project. I need to do this quickly and inexpensively. I was looking at some cheap Dell towers or I might put something together myself. I am planning on using the RD Appliance. Is there any common hardware I should avoid that has known issues with the Appliance? Any processors, chipsets or cards that I need to stay away from? Ryan ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
Re: [RDD] More reasons to use Rivendell
Maybe I missed something, why is Bill Gates' wealth a good reason to use Rivendell? Ryan On Mon, Mar 4, 2013 at 4:05 PM, Geoff Barkman countryra...@gmail.comwrote: I just read online and in the news Bill Gates is the second richest in the world $67 Billion dollars (I presume that is US dollars). Yet another reason not to use M$ based products for radio Automation. :) http://www.forbes.com/billionaires/list/ Many thanks Geoff Barkman ___ 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