Author Topic: KCCR DOWN for 8 hours  (Read 6851 times)

Offline sgtstakem

  • Newbie
  • *
  • Posts: 28
KCCR DOWN for 8 hours
« on: January 10, 2011, 06:59:53 PM »
Can't get a break, my trusty SB Live sound card took a crap on me last night after a power outage



Offline sgtstakem

  • Newbie
  • *
  • Posts: 28
Re: KCCR DOWN for 8 hours
« Reply #1 on: January 16, 2011, 10:53:11 PM »
KCCR is back up, had a delayed outage as child birth happened during repair. BTW - the issue I had was due to a oss - opensound trial software licence expiring not a hardware failure which urked me to say the least. CentOS 5.5 (final) oss driver has a 6 month trail licence that needs to be reinstalled every 6 months(or pay 50 bucks). Never heard of drivers packaged with a GNU OS having this type of requirement...grr

Offline tyketto

  • Hero Member
  • *****
  • Posts: 1138
Re: KCCR DOWN for 8 hours
« Reply #2 on: January 17, 2011, 11:26:48 AM »
KCCR is back up, had a delayed outage as child birth happened during repair. BTW - the issue I had was due to a oss - opensound trial software licence expiring not a hardware failure which urked me to say the least. CentOS 5.5 (final) oss driver has a 6 month trail licence that needs to be reinstalled every 6 months(or pay 50 bucks). Never heard of drivers packaged with a GNU OS having this type of requirement...grr

that's why the linux kernel now favours ALSA over OSS. You may want to see if ALSA supports your card, and go that route. www.alsa-project.org, IIRC.

BL.

Offline sgtstakem

  • Newbie
  • *
  • Posts: 28
Re: KCCR DOWN for 8 hours
« Reply #3 on: February 01, 2011, 01:46:02 AM »
My apologies, I noticed today that there was an issue with my scanner, needed to be replaced. It apparently wasn't sending audio anymore and it has been a few days since I noticed it. Fixed now.. replaced everything I have on this feed so it better work ;-)

Offline dave

  • Site Founder
  • Administrator
  • Hero Member
  • *****
  • Posts: 4598
    • LiveATC.net
Re: KCCR DOWN for 8 hours
« Reply #4 on: February 03, 2011, 10:54:57 AM »
If you use the ALSA drivers just set the input device to 'default' - that should work.  If not let me know.