Hi, Done a little more testing with a Centos 7 Appliance install. What I can now say is that the problem is only there on the new script installed machines, and not with the Broadcast Appliance machines. I've installed all of the test machines on separate HDDs so I can switch between them. I must admit that this is where my level of knowledge on the backend of the system ends. Any ideas would be very much appreciated.
Oh, before I forget, a happy Easter to everyone here on the mailing list. Andy ---- On Wed, 12 Apr 2017 21:35:06 +0100 Andy Higginson <a...@higgles.co.uk> wrote ---- > Hi, > > Having said all of this, I'm getting issues with the card now. I've been > using it without issue on a CentOS 6 Broadcast Appliance machine. > > I've built a new machine using the new install method and now the card is > not working. When using the default out of the box asound.conf, there is > the usual 1 main output and this is working. When the asound.conf is > configured to use the card with the 3 outputs (which works on the Broadcast > Appliance), it doesn't work. If I play the test audio in the Library, the > play bar does not move and no audio comes out. After 10 seconds, the file > stops playing. At first, nothing is seen on the meters and then they begin > to creep up a little. > > Things I've tried > > New install method with both Centos 7 and then Centos 6 (neither of which > work). > Adding rate to the asound.conf > Changing the soundcard > Building a Centos 6 Broadcast Appliance - This does work, therefore proving > the machine. > > Does anybody have any thoughts? > > Thanks > > Andy > > > > ---- On Tue, 28 Mar 2017 13:12:51 +0100 Andy Higginson <a...@higgles.co.uk> > wrote ---- > > Hi, > > > > Which version of the card is this? I'm using an Audigy 2 card in a > machine and have 3 separate analogue outputs. I've also used a cheaper > Audigy Live SE card and got all of the outputs to work as well. I had to > run the RDAlsaConfig program and define the cards though as by default only > a single output is defined. Once you have configured this, you should be > able to use all of the outputs. > > > > Ooooh, nearly forgot, you may also need to turn up the outputs in > alsamixer. You run this in a terminal. > > > > Andy > > > > > > > > ---- On Thu, 23 Mar 2017 17:37:35 +0000 al davis > <ad...@freeelectron.net> wrote ---- > > > I'm trying to make Rivendell work on a Sound Blaster Audigy sound > card, > > > and support all of the outputs. > > > > > > In a simple sense, it works, but I want to use the rear, side, > > > etc as separate outputs and that doesn't seem to work. I want to use > > > > one output for rdairplay, a separate one for the aux logs, another for > > > > cue, another for the rdcatch decks, etc. > > > > > > I have done this several times with Asus sound cards and motherboards. > > > > They work exactly as I expect them to work. > > > > > > But the Sound Blaster .. even though it has the extra jacks, it just > > > > puts the same audio on all of them. In rdadmin, there is just one > > > "port". > > > > > > Any ideas? > > > > > > al. > > > _______________________________________________ > > > 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 > > > > > _______________________________________________ > 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
