Loading ...
Sorry, an error occurred while loading the content.

(Sigh) getting Softrock and Quisk to work with Audigy Fx (SB1570) under Linux - ANOTHER issue.

Expand Messages
  • n4fbz
    I ve been fighting with this computer - trying to get my softrock RxTx6.3 up and running. The computer is an almost new Dell Optiplex 7010 (i7 processor), and
    Message 1 of 19 , Aug 9, 2014
    • 0 Attachment
      I've been fighting with this computer - trying to get my softrock RxTx6.3 up and running.  The computer is an almost new Dell Optiplex 7010 (i7 processor), and I've got both the on-board audio and a SB1570 (SB Audigy Fx) audio card in it.


      I purchased the Audigy card separately and installed it for ham use (so the computer serves multiple purposes).  I run only Linux (for strong reasons) and got the Audigy card to work for a while yesterday - impressively so (192k bandwidth, very wide dynamic range, great sensitivity on the part of the board).  Now I'm not getting audio from the Audigy although Quisk recognizes the card (as well as the onboard audio).  The programs aplay -l and arecord -l both list the card and show both inputs and outputs, but I'm having a fit with ALSA regarding mixers - there is inadequate documentation of the software.


      I think that there is a software switch blocking the audio from going to Quisk.  No audio gets through whatsoever from either line in or microphone in to Quisk.  I'm not too happy with the ALSA software and configuration (I think that a value was changed when I shut down the computer last night - but I don't know what).


      Has anyone had experience getting one of these cards to reliably work with linux?  I don't want to have to purchase another audio card - the one I have was the only one I could afford, that was locally available (and that also was PCIe) and we are on an extremely tight budget.  The bandwidth and dynamic range are pretty good - better than the onboard audo and especially the USB sound board I have (rather limited audio bandwidth and reduced dynamic range).



    • Mike
      Did you try pavucontrol(terminal) ? or alsamixer(terminal) ... ... -- Mike KC7NOA
      Message 2 of 19 , Aug 9, 2014
      • 0 Attachment
        Did you try pavucontrol(terminal)  ? or alsamixer(terminal) ...


        On 08/09/2014 11:35 AM, n4fbz@... [softrock40] wrote:
         

        I've been fighting with this computer - trying to get my softrock RxTx6.3 up and running.  The computer is an almost new Dell Optiplex 7010 (i7 processor), and I've got both the on-board audio and a SB1570 (SB Audigy Fx) audio card in it.


        I purchased the Audigy card separately and installed it for ham use (so the computer serves multiple purposes).  I run only Linux (for strong reasons) and got the Audigy card to work for a while yesterday - impressively so (192k bandwidth, very wide dynamic range, great sensitivity on the part of the board).  Now I'm not getting audio from the Audigy although Quisk recognizes the card (as well as the onboard audio).  The programs aplay -l and arecord -l both list the card and show both inputs and outputs, but I'm having a fit with ALSA regarding mixers - there is inadequate documentation of the software.


        I think that there is a software switch blocking the audio from going to Quisk.  No audio gets through whatsoever from either line in or microphone in to Quisk.  I'm not too happy with the ALSA software and configuration (I think that a value was changed when I shut down the computer last night - but I don't know what).


        Has anyone had experience getting one of these cards to reliably work with linux?  I don't want to have to purchase another audio card - the one I have was the only one I could afford, that was locally available (and that also was PCIe) and we are on an extremely tight budget.  The bandwidth and dynamic range are pretty good - better than the onboard audo and especially the USB sound board I have (rather limited audio bandwidth and reduced dynamic range).




        -- 
        Mike KC7NOA
      • n4fbz
        Yep, both of them. Obviously the Audigy is recognized by Ubuntu (and by Quisk), so it s not the usual sort of problem.
        Message 3 of 19 , Aug 9, 2014
        • 0 Attachment
          Yep, both of them.  Obviously the Audigy is recognized by Ubuntu (and by Quisk), so it's not the usual sort of problem.
        • Sid Boyce
          Click the Config button and see if what the Status tab says. I have seen device status busy but that was a long time ago when for some reason after firefox
          Message 4 of 19 , Aug 9, 2014
          • 0 Attachment
            Click the Config button and see if what the Status tab says.

            I have seen device status busy but that was a long time ago when for some reason after firefox played a video file it wasn't releasing the audio but that was fixed so shouldn't be an issue in 13.x or 14.04.
            73 ... Sid.
             

            On 10/08/14 00:06, n4fbz@... [softrock40] wrote:
             

            Yep, both of them.  Obviously the Audigy is recognized by Ubuntu (and by Quisk), so it's not the usual sort of problem.



            -- 
            Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
            Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
            Senior Staff Specialist, Cricket Coach
            Microsoft Windows Free Zone - Linux used for all Computing Tasks
            
          • n4fbz
            Interesting. I d turned Firefox off after I started having problems, and wondered if there was some sort of interaction like that (capturing and not releasing
            Message 5 of 19 , Aug 9, 2014
            • 0 Attachment
              Interesting.  I'd turned Firefox off after I started having problems, and wondered if there was some sort of interaction like that (capturing and not releasing the stream).  My Firefox version is rather recent - 31.

              Actually, that rather fits the pattern - and this is where it's getting weird:  I was playing with different settings and trying to dig into the config files for the audio - without finding anything that could create the problem.  After a while, I tried changing things so that the received signal(s) came in through the built-in audio and went out to the speakers via the same, and the microphone (and "audio" to the radio) where hooked to the Audigy.  That didn't work, but when I put back the cables and settings the way I had it (receive "audio" in to the Audigy, Transmit "audio" out through the Audigy, Microphone audio through the built-in board, speaker out from the same - the crazy setup was working again.  I played around with it for a while and the receive "audio" just quit a second time.  This time I changed the settings (receive audio in and out to motherboard audio, transmit "audio" in and out to the Audigy), started Quisk (which didn't like those settings too much), and then shut Quisk down and changed the settings back- and restarted Quisk.  That fixed the problem.

              Throughout all of this, the built-in audio is showing up as the default sound card - which I want because I do watch occasional videos on this machine and sometimes listen to music.

              I'm also having problems with bad noise/audio getting into the transmit stream (I'm trying to figure out where that might be coming from).  At least I now have more symptoms for the receive portion and know that it will work - and by changing the input/output settings it seems to fix the problem.

              (Laugh!)  The things we go through trying to get "non-standard" and non-typical stuff working!!!  (Gotta admit that SDR isn't what most people like to play with - or run on their computers!)
            • Mike
              The names for the devices might be getting re-assigned after a reboot .... I think some one posted a script to make them the same each time after a reboot ...
              Message 6 of 19 , Aug 9, 2014
              • 0 Attachment
                The names for the devices might be getting re-assigned after a reboot ....
                I think some one posted a script to make them the same each time after a reboot ... Sid might remember better ....
                (and i think ill need the same script soon too)


                On 08/09/2014 07:58 PM, n4fbz@... [softrock40] wrote:
                 

                Interesting.  I'd turned Firefox off after I started having problems, and wondered if there was some sort of interaction like that (capturing and not releasing the stream).  My Firefox version is rather recent - 31.

                Actually, that rather fits the pattern - and this is where it's getting weird:  I was playing with different settings and trying to dig into the config files for the audio - without finding anything that could create the problem.  After a while, I tried changing things so that the received signal(s) came in through the built-in audio and went out to the speakers via the same, and the microphone (and "audio" to the radio) where hooked to the Audigy.  That didn't work, but when I put back the cables and settings the way I had it (receive "audio" in to the Audigy, Transmit "audio" out through the Audigy, Microphone audio through the built-in board, speaker out from the same - the crazy setup was working again.  I played around with it for a while and the receive "audio" just quit a second time.  This time I changed the settings (receive audio in and out to motherboard audio, transmit "audio" in and out to the Audigy), started Quisk (which didn't like those settings too much), and then shut Quisk down and changed the settings back- and restarted Quisk.  That fixed the problem.

                Throughout all of this, the built-in audio is showing up as the default sound card - which I want because I do watch occasional videos on this machine and sometimes listen to music.

                I'm also having problems with bad noise/audio getting into the transmit stream (I'm trying to figure out where that might be coming from).  At least I now have more symptoms for the receive portion and know that it will work - and by changing the input/output settings it seems to fix the problem.

                (Laugh!)  The things we go through trying to get "non-standard" and non-typical stuff working!!!  (Gotta admit that SDR isn't what most people like to play with - or run on their computers!)


                -- 
                Mike KC7NOA
              • Sid Boyce
                Sound card issues can be a real pain when it comes to getting QSD/QSE SDR rigs to work properly. The problems can massively swamp any other concerns and more
                Message 7 of 19 , Aug 10, 2014
                • 0 Attachment
                  Sound card issues can be a real pain when it comes to getting QSD/QSE SDR rigs to work properly. The problems can massively swamp any other concerns and more often than not represent the totality of SDR problems. Sometimes you get lucky and everything works properly.

                  Though I have enjoyed QSD/QSE SDR's over a number of years there have often been sound card peculiarities that have occasionally baffled me to the point where I eventually sought refuge in DDC/DUC SDR's where I-Q phase and amplitude balancing and other sound card artifacts do not occur.
                  73 ... Sid.
                   
                  On 10/08/14 03:58, n4fbz@... [softrock40] wrote:
                   

                  Interesting.  I'd turned Firefox off after I started having problems, and wondered if there was some sort of interaction like that (capturing and not releasing the stream).  My Firefox version is rather recent - 31.

                  Actually, that rather fits the pattern - and this is where it's getting weird:  I was playing with different settings and trying to dig into the config files for the audio - without finding anything that could create the problem.  After a while, I tried changing things so that the received signal(s) came in through the built-in audio and went out to the speakers via the same, and the microphone (and "audio" to the radio) where hooked to the Audigy.  That didn't work, but when I put back the cables and settings the way I had it (receive "audio" in to the Audigy, Transmit "audio" out through the Audigy, Microphone audio through the built-in board, speaker out from the same - the crazy setup was working again.  I played around with it for a while and the receive "audio" just quit a second time.  This time I changed the settings (receive audio in and out to motherboard audio, transmit "audio" in and out to the Audigy), started Quisk (which didn't like those settings too much), and then shut Quisk down and changed the settings back- and restarted Quisk.  That fixed the problem.

                  Throughout all of this, the built-in audio is showing up as the default sound card - which I want because I do watch occasional videos on this machine and sometimes listen to music.

                  I'm also having problems with bad noise/audio getting into the transmit stream (I'm trying to figure out where that might be coming from).  At least I now have more symptoms for the receive portion and know that it will work - and by changing the input/output settings it seems to fix the problem.

                  (Laugh!)  The things we go through trying to get "non-standard" and non-typical stuff working!!!  (Gotta admit that SDR isn't what most people like to play with - or run on their computers!)



                  -- 
                  Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
                  Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
                  Senior Staff Specialist, Cricket Coach
                  Microsoft Windows Free Zone - Linux used for all Computing Tasks
                  
                • Sid Boyce
                  cat /proc/asound/cards will tell you if the cards are detected correctly but I have never seen them change. It s possible to define the default sound card in
                  Message 8 of 19 , Aug 10, 2014
                  • 0 Attachment
                    "cat /proc/asound/cards" will tell you if the cards are detected correctly but I have never seen them change.
                    It's possible to define the default sound card in /etc/asoundrc or in ~/.asoundrc if there is a requirement to specify a different card as default.
                    "zcat /usr/share/doc/libasound2/examples/asoundrc.txt.gz|less" gives examples but is quite cryptic.
                    Lots of troubleshooting stuff https://wiki.archlinux.org/index.php/PulseAudio but too heavy for most problems encountered.

                    On all my boxes I use http://napan.ca/ghpsdr3/index.php/Pulseaudio_Setup which works with all my SDR and other programs and hardware - quisk, qsdr, rasdr, QtRadio and cuSDR64.

                    On ODROID-U3 ARM
                    -----------------------------
                    # cat /proc/asound/cards
                     0 [Audio          ]: Built-in_Audio - Built-in Audio
                                          Built-in Audio
                     1 [Aureon51MkII   ]: USB-Audio - Aureon5.1MkII
                                          TerraTec Aureon5.1MkII at usb-s5p-ehci-3.2.2.6, full speed

                    On x86_64 where card 2 was removed over a year ago.
                    --------------------------------------------------------------------------------------------------
                    tindog:/usr/src/XXX # cat /proc/asound/cards
                     0 [SB             ]: HDA-Intel - HDA ATI SB
                                          HDA ATI SB at 0xfdff4000 irq 16
                     1 [NVidia         ]: HDA-Intel - HDA NVidia
                                          HDA NVidia at 0xfcffc000 irq 19
                     3 [Aureon51MkII   ]: USB-Audio - Aureon5.1MkII
                                          TerraTec Aureon5.1MkII at usb-0000:00:16.2-4.4.1, full speed
                    73 ... Sid.

                    On 10/08/14 04:13, Mike Patriot121@... [softrock40] wrote:
                     

                    The names for the devices might be getting re-assigned after a reboot ....
                    I think some one posted a script to make them the same each time after a reboot ... Sid might remember better ....
                    (and i think ill need the same script soon too)


                    On 08/09/2014 07:58 PM, n4fbz@... [softrock40] wrote:
                     

                    Interesting.  I'd turned Firefox off after I started having problems, and wondered if there was some sort of interaction like that (capturing and not releasing the stream).  My Firefox version is rather recent - 31.

                    Actually, that rather fits the pattern - and this is where it's getting weird:  I was playing with different settings and trying to dig into the config files for the audio - without finding anything that could create the problem.  After a while, I tried changing things so that the received signal(s) came in through the built-in audio and went out to the speakers via the same, and the microphone (and "audio" to the radio) where hooked to the Audigy.  That didn't work, but when I put back the cables and settings the way I had it (receive "audio" in to the Audigy, Transmit "audio" out through the Audigy, Microphone audio through the built-in board, speaker out from the same - the crazy setup was working again.  I played around with it for a while and the receive "audio" just quit a second time.  This time I changed the settings (receive audio in and out to motherboard audio, transmit "audio" in and out to the Audigy), started Quisk (which didn't like those settings too much), and then shut Quisk down and changed the settings back- and restarted Quisk.  That fixed the problem.

                    Throughout all of this, the built-in audio is showing up as the default sound card - which I want because I do watch occasional videos on this machine and sometimes listen to music.

                    I'm also having problems with bad noise/audio getting into the transmit stream (I'm trying to figure out where that might be coming from).  At least I now have more symptoms for the receive portion and know that it will work - and by changing the input/output settings it seems to fix the problem.

                    (Laugh!)  The things we go through trying to get "non-standard" and non-typical stuff working!!!  (Gotta admit that SDR isn't what most people like to play with - or run on their computers!)


                    -- 
                    Mike KC7NOA


                    -- 
                    Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
                    Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
                    Senior Staff Specialist, Cricket Coach
                    Microsoft Windows Free Zone - Linux used for all Computing Tasks
                    
                  • n4fbz
                    Interesting. I don t have the files ~/.asoundrc or /etc/asoundrc. There is software (installed) for setting the default, but the proper modules to use it are
                    Message 9 of 19 , Aug 10, 2014
                    • 0 Attachment
                      Interesting.  I don't have the files ~/.asoundrc or /etc/asoundrc.  There is software (installed) for setting the default, but the proper modules to use it are missing from Ubuntu and have been for some time (there is a workaround, but it's a PITA) - I just haven't gotten around to removing it because it's useless.

                      I think the problem is a software switch somewhere... or configuration error.  This morning I can't get the softrock to work at all with the proper configuration - the little trick that worked last night isn't working now.  My Audigy Fx is showing up in all of the programs I have to check the audio, but nothing is coming from it.

                      The Pulseaudio setup (mixer) is the default mixer for this computer.  I use the built-in audio as default device because I don't think it has near the specs of the Creative board (which will go 192,000 sample rate and has dynamic range that is pretty good) - which I've reserved as the interface board for the softrock.  The cards are being properly recognized, btw (I checked /proc/asound/cards).

                      I don't know if this has much to do with the problem or not, but every time I start Quisk, it seems to be checking for ports on the cards that don't exist, plus I have a bluetooth adapter (which I keep switched off until I need it) and it seems to be trying to scan ports on that device as well.  Here are the errors as generated every time I start Quisk:

                      ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
                      ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
                      ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
                      ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Unknown error 251(251)
                      ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Unknown error 251(251)
                      ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Unknown error 251(251)
                      ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Unknown error 251(251)
                      ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
                      ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
                      ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
                      ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
                      ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
                      ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
                      ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
                      Cannot connect to server socket err = No such file or directory
                      Cannot connect to server socket
                      jack server is not running or cannot be started

                      My motherboard audio (PCM) doesn't have "pcm.rear", center, or side.  I don't ever want the software trying to connect to the bluetooth adapter (I keep it turned off for very good reasons).  I have "Jack" installed on this computer, but not running.  I've poked around the conf files for Quisk, and I'm not sure why the software is checking all of those ports.

                      Besides the errors above, I had Quisk crash a couple of times with "segmentation fault", but I'd neglected to reduce the sample rate from 192000 to 96000 (going back to the motherboard audio).

                      It's a fun problem - NOT.
                    • Sid Boyce
                      Those messages are normal, just operating system noise when quisk is started rather than errors. There is a bluetooth package if removed gets rid of the
                      Message 10 of 19 , Aug 10, 2014
                      • 0 Attachment
                        Those messages are normal, just operating system noise when quisk is started rather than errors. There is a bluetooth package if removed gets rid of the bluetooth messages but none of these have any impact on quisk, just ignore them.
                        python quisk.py -c quisk_conf.py_HiQSDR_1&
                        [2] 27010
                        [1]   Done                    python quisk.py -c quisk_conf.py_HiQSDR_1
                        tindog:/opt/quisk-3.6.18 # ALSA lib pcm.c:2259:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
                        ALSA lib pcm.c:2259:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
                        ALSA lib pcm.c:2259:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
                        ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching channel map
                        Cannot connect to server socket err = No such file or directory
                        Cannot connect to server request channel
                        jack server is not running or cannot be started

                        On Config --> Status I have rolling numbers for Sample interrupts, Device - Play radio sound.
                        Whistling or tapping the Mic shows Microphone level dB changing.
                        73 ... Sid.


                        On 10/08/14 18:51, n4fbz@... [softrock40] wrote:
                         

                        Interesting.  I don't have the files ~/.asoundrc or /etc/asoundrc.  There is software (installed) for setting the default, but the proper modules to use it are missing from Ubuntu and have been for some time (there is a workaround, but it's a PITA) - I just haven't gotten around to removing it because it's useless.

                        I think the problem is a software switch somewhere... or configuration error.  This morning I can't get the softrock to work at all with the proper configuration - the little trick that worked last night isn't working now.  My Audigy Fx is showing up in all of the programs I have to check the audio, but nothing is coming from it.

                        The Pulseaudio setup (mixer) is the default mixer for this computer.  I use the built-in audio as default device because I don't think it has near the specs of the Creative board (which will go 192,000 sample rate and has dynamic range that is pretty good) - which I've reserved as the interface board for the softrock.  The cards are being properly recognized, btw (I checked /proc/asound/cards).

                        I don't know if this has much to do with the problem or not, but every time I start Quisk, it seems to be checking for ports on the cards that don't exist, plus I have a bluetooth adapter (which I keep switched off until I need it) and it seems to be trying to scan ports on that device as well.  Here are the errors as generated every time I start Quisk:

                        ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
                        ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
                        ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
                        ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Unknown error 251(251)
                        ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Unknown error 251(251)
                        ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Unknown error 251(251)
                        ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Unknown error 251(251)
                        ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
                        ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
                        ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
                        ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
                        ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
                        ALSA lib pcm_hw.c:1401:(_snd_pcm_hw_open) Invalid value for card
                        ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
                        Cannot connect to server socket err = No such file or directory
                        Cannot connect to server socket
                        jack server is not running or cannot be started

                        My motherboard audio (PCM) doesn't have "pcm.rear", center, or side.  I don't ever want the software trying to connect to the bluetooth adapter (I keep it turned off for very good reasons).  I have "Jack" installed on this computer, but not running.  I've poked around the conf files for Quisk, and I'm not sure why the software is checking all of those ports.

                        Besides the errors above, I had Quisk crash a couple of times with "segmentation fault", but I'd neglected to reduce the sample rate from 192000 to 96000 (going back to the motherboard audio).

                        It's a fun problem - NOT.



                        -- 
                        Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
                        Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
                        Senior Staff Specialist, Cricket Coach
                        Microsoft Windows Free Zone - Linux used for all Computing Tasks
                        
                      • n4fbz
                        I have the rolling numbers, but no audio and no noise showing on the spectrum (blank) and the scope shows a flat trace - no detectable signal at all.
                        Message 11 of 19 , Aug 10, 2014
                        • 0 Attachment
                          I have the rolling numbers, but no audio and no noise showing on the spectrum (blank) and the scope shows a flat trace - no detectable signal at all.  Sometimes the audio seems to lock up and the numbers only change every now and then (that's usually a sign that I got something messed up - when I really got it wrong, Quisk would lock up).

                          I've gone to using the built-in motherboard audio for the receive "audio" and the speakers, with that set as the default card.  The mike is attached to the Audigy... and the "audio" out to the softrock transmitter.  That seems to be the most reliable setup.  I found a few other oddball things... both I and Q have to be set (or defined) otherwise all I'd get was distorted noise (with some audio) to the transmitter, even though according to the information Quisk only uses one channel.  There are also other problems in that section - either the audio from the mike feeds back into (and mixes with) the "audio" from the softrock, or no audio at all.  I am sure that's some sort of setup problem, and probably connected with ALSA or maybe pulseaudio.

                          The microphone for the Audigy works reliably.  The audio out... that's been a bit squirrelly.  The way I had it set up before... the line in was acting up and the output was stable.

                          Thanks for the help and the tips.  We'll get this monster going.  It's about 80% there now.
                        • Sid Boyce
                          One card for I-Q processing - connected to the Softrock and the other card connected to Mic/Speakers. Softrock: Line In -- Line In and Line Out -- Line Out
                          Message 12 of 19 , Aug 10, 2014
                          • 0 Attachment
                            One card for I-Q processing - connected to the Softrock and the other card connected to Mic/Speakers.

                            Softrock: Line In --> Line In and Line Out --> Line Out on the same card.
                            Think of this card as part of the Softrock rather than a sound card.
                            ~/.quisk_conf.py
                            name_of_sound_capt ="hw:0"  if the on-board sound card is used for I-Q.
                            name_of_mic_play = "hw:0"  The Mic audio from the Audigy (hw:1) is sent to the I-Q card, i.e to the Softrock.

                            Mic --> Mic In and Speakers --> Line Out on the same card.
                            name_of_sound_play = "hw:1"   If the Audigy is used for Mic/Spkrs
                            microphone_name = "hw:1" if the Audigy is used for Mic/Spkrs
                            73 ... Sid.

                            On 11/08/14 00:41, n4fbz@... [softrock40] wrote:
                             

                            I have the rolling numbers, but no audio and no noise showing on the spectrum (blank) and the scope shows a flat trace - no detectable signal at all.  Sometimes the audio seems to lock up and the numbers only change every now and then (that's usually a sign that I got something messed up - when I really got it wrong, Quisk would lock up).

                            I've gone to using the built-in motherboard audio for the receive "audio" and the speakers, with that set as the default card.  The mike is attached to the Audigy... and the "audio" out to the softrock transmitter.  That seems to be the most reliable setup.  I found a few other oddball things... both I and Q have to be set (or defined) otherwise all I'd get was distorted noise (with some audio) to the transmitter, even though according to the information Quisk only uses one channel.  There are also other problems in that section - either the audio from the mike feeds back into (and mixes with) the "audio" from the softrock, or no audio at all.  I am sure that's some sort of setup problem, and probably connected with ALSA or maybe pulseaudio.

                            The microphone for the Audigy works reliably.  The audio out... that's been a bit squirrelly.  The way I had it set up before... the line in was acting up and the output was stable.

                            Thanks for the help and the tips.  We'll get this monster going.  It's about 80% there now.



                            -- 
                            Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
                            Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
                            Senior Staff Specialist, Cricket Coach
                            Microsoft Windows Free Zone - Linux used for all Computing Tasks
                            
                          • n4fbz
                            That s the way I had it- but very intermittent audio (and unreliable connections). I d rather have it set up that way, but the computer is fighting against
                            Message 13 of 19 , Aug 10, 2014
                            • 0 Attachment
                              That's the way I had it- but very intermittent audio (and unreliable connections).  I'd rather have it set up that way, but the computer is fighting against it.

                              Same card - same clock frequency, same architecture, all connected to the same thing (softrock or speakers/mike)... nowhere near the potential for issues.  The two audio boards respond differently (I'm pretty sure the Audigy has a much wider bandwidth and I know a greater dynamic response - I can tell), but that I can adjust out and (I think) live with the differences.

                              The sad fact is that I have to live within my means... which means making what I have work - and often dealing with headaches because the less expensive manufacturers don't like to share information or work with you - so you're pretty much on your own trying to get a non-standard setup to work right.
                            • Sid Boyce
                              Your setup should work. What spec is you laptop? Thinking may be not enough power, python being a CPU hog when I was running it on an ODROID-X without the
                              Message 14 of 19 , Aug 10, 2014
                              • 0 Attachment
                                Your setup should work.
                                What spec is you laptop? Thinking may be not enough power, python being a CPU hog when I was running it on an ODROID-X without the mali400 GPU driver and I could only get blotches of sound, shaky waterfall and spectrum.

                                Running quisk on a Zotac MaG mini PC with an Atom N330 1.6 GHz and 2 GB memory there is no problem.
                                73 ... Sid.

                                On 11/08/14 01:35, n4fbz@... [softrock40] wrote:
                                 

                                That's the way I had it- but very intermittent audio (and unreliable connections).  I'd rather have it set up that way, but the computer is fighting against it.

                                Same card - same clock frequency, same architecture, all connected to the same thing (softrock or speakers/mike)... nowhere near the potential for issues.  The two audio boards respond differently (I'm pretty sure the Audigy has a much wider bandwidth and I know a greater dynamic response - I can tell), but that I can adjust out and (I think) live with the differences.

                                The sad fact is that I have to live within my means... which means making what I have work - and often dealing with headaches because the less expensive manufacturers don't like to share information or work with you - so you're pretty much on your own trying to get a non-standard setup to work right.



                                -- 
                                Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
                                Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
                                Senior Staff Specialist, Cricket Coach
                                Microsoft Windows Free Zone - Linux used for all Computing Tasks
                                
                              • n4fbz
                                (Laugh) not a laptop - Dell Optiplex 7010 desktop, quad processors, 3.4Ghz, 16Gb memory, intel HD audio, Radeon HD7570 video (driving dual monitors), very
                                Message 15 of 19 , Aug 10, 2014
                                • 0 Attachment
                                  (Laugh) not a laptop - Dell Optiplex 7010 desktop, quad processors, 3.4Ghz, 16Gb memory, intel HD audio, Radeon HD7570 video (driving dual monitors), very fast.  The Audigy Fx is in a PCIe slot, and was supposed to be fairly potent for the price.  At the time, my old audigy board (PCI) wouldn't work with the new computer - caused all sorts of headaches (I did get it working with the old system).

                                  The sort of stuff I do often demands much more than an "average" system, and this monster delivers.  Think huge GIS files and spatial analysis (and digitizing), plus other various forms of processor-cooking analyses.

                                  The computer is my school/work system, but also for ham and personal use.  I added the Audigy card so I could use it with my softrock.

                                  I've spent hours digging through thread after thread, trying to figure out this problem.  A huge part of it is Creative's hostility towards Linux and unwillingness to work with anyone not throwing money at Microsoft.  Part of it is the obtuse information you sometimes get when trying to figure out problems (and people giving you a list of links and "start reading" - I already spend most of my year reading journals and technical books, and getting that really pisses me off).  Part of it is a lack of decent documentation.  In reality, Quisk is probably one of the better-documented programs available these days.  Between you and me, I miss the old DOS days and the adequate documentation you could get back then (or the reams of info available back in the teletype-and-mainframe days). 

                                  I'm going to keep at it, but do need to start "cleaning up" and try to finish some projects- school starts in two weeks.

                                  Thanks for "listening", and trying to help.  Maybe we'll hit on something that does the trick.
                                • Sid Boyce
                                  You could run quisk and tons of other apps on that box so I am puzzled as to what the problem could be. Take some snapshots of the quisk window, especially the
                                  Message 16 of 19 , Aug 11, 2014
                                  • 0 Attachment
                                    You could run quisk and tons of other apps on that box so I am puzzled as to what the problem could be.
                                    Take some snapshots of the quisk window, especially the Status and email me direct.

                                    With quisk up "fuser -v /dev/snd/*" to see what it reports.

                                    Don't worry about hostility, I have even met it at work when I used only Linux on the company's laptop when I and a few other blew Win95 off ours.
                                    When the corporation woke up to Linux I was asked with a team of 2 helpers to provide a "tools" CD to be installed on RedHat so we could ditch the Windows audits and license charges.
                                    My manager handed 6 CD's to our Corporate Director to hand to the tech guys in Sunnyvale, Calif. On the next conference call with the guys they said they hadn't received them so we conferenced in the Director and the the only answer my manager and I got was that he thought he distributed them.

                                    We had a team of 30 guys developing Linux in early 2003 when IBM had 200, laid them all off around August 2003 and in October 2003 were thinking of heading off to the bars in Austin to see if they could entice some IBM'ers to do Linux for us in Sunnyvale.

                                    I was in this game way before DOS and worked for a daily crust with at least 13 other OS's on PDP-11's, Mainframes, SPARC, Burroughs TC's, etc., not counting DOS/Windows - Univac OS/3, OS/4,  OS/9, Amdahl UTS, IBM OS/2, AIX, MVS, VM, z/OS, z/VM, Sun Solaris  and Linux on SPARC and Mainframes. I even ran FreeBSD on PC's.
                                    Each demanding a different mindset and getting to grips speedily with whatever was required to get the job done.
                                    73 ... Sid.

                                    On 11/08/14 03:34, n4fbz@... [softrock40] wrote:
                                     

                                    (Laugh) not a laptop - Dell Optiplex 7010 desktop, quad processors, 3.4Ghz, 16Gb memory, intel HD audio, Radeon HD7570 video (driving dual monitors), very fast.  The Audigy Fx is in a PCIe slot, and was supposed to be fairly potent for the price.  At the time, my old audigy board (PCI) wouldn't work with the new computer - caused all sorts of headaches (I did get it working with the old system).

                                    The sort of stuff I do often demands much more than an "average" system, and this monster delivers.  Think huge GIS files and spatial analysis (and digitizing), plus other various forms of processor-cooking analyses.

                                    The computer is my school/work system, but also for ham and personal use.  I added the Audigy card so I could use it with my softrock.

                                    I've spent hours digging through thread after thread, trying to figure out this problem.  A huge part of it is Creative's hostility towards Linux and unwillingness to work with anyone not throwing money at Microsoft.  Part of it is the obtuse information you sometimes get when trying to figure out problems (and people giving you a list of links and "start reading" - I already spend most of my year reading journals and technical books, and getting that really pisses me off).  Part of it is a lack of decent documentation.  In reality, Quisk is probably one of the better-documented programs available these days.  Between you and me, I miss the old DOS days and the adequate documentation you could get back then (or the reams of info available back in the teletype-and-mainframe days). 

                                    I'm going to keep at it, but do need to start "cleaning up" and try to finish some projects- school starts in two weeks.

                                    Thanks for "listening", and trying to help.  Maybe we'll hit on something that does the trick.



                                    -- 
                                    Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
                                    Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
                                    Senior Staff Specialist, Cricket Coach
                                    Microsoft Windows Free Zone - Linux used for all Computing Tasks
                                    
                                  • n4fbz
                                    I think I ve cornered the problem (after a 12 hour day of reading, and checking various things). The video card in this computer (came with it) has built-in
                                    Message 17 of 19 , Aug 12, 2014
                                    • 0 Attachment
                                      I think I've cornered the problem (after a 12 hour day of reading, and checking various things).  The video card in this computer (came with it) has built-in HDMI audio - the audio device from hell.  It "insists" on being card 0 and nothing (so far) will change that... a forcible "deletion" (only way to describe in a few words) results in there being no "card 0" with ALSA, but the other two cards show - but it's still screwing with the audio.  The HDMI audio also has a reputation for screwing with the inputs and outputs of other audio cards.  Oh, and another funny thing - all of my sound boards in the system (built-in, Audigy, and the HDMI) use the same codec - snd-HDA-Intel.  It's been fun trying to figure out how to put the cards in order through ALSA (that's where I picked up that the HDMI was a problem).  Each version of Linux seems to have it's own structure and way of arranging things.  (Sigh) well, that's what can happen with open-source OSes.I always wondered why there were few complaints found regarding my audio board - now it makes sense, because that isn't the problem.Once i get this licked, the softrock will work fine.  When I hit a (temporary) right change which enables the audio (until the next boot) the radio transmits and receives great (although with a maximum of 5mW - about what was expected).I'll let you know how things go today.  This is a good lesson on troubleshooting - sometimes the real problem is something completely different than it seems, and being really observant is key.  The real problem can mimic other issues.
                                    • Sid Boyce
                                      With multiple sound cards, quisk only needs to be configured to use 2. In my setup I am using card 0 for Speakers, and card 3 for Microphone - HiQSDR only
                                      Message 18 of 19 , Aug 12, 2014
                                      • 0 Attachment
                                        With multiple sound cards, quisk only needs to be configured to use 2.

                                        In my setup I am using card 0 for Speakers, and card 3 for Microphone - HiQSDR only needs one card but I have a problem with the Mic on card 0.
                                        tindog:~ # cat /proc/asound/cards
                                         0 [SB             ]: HDA-Intel - HDA ATI SB
                                                              HDA ATI SB at 0xfdff4000 irq 16
                                         1 [NVidia         ]: HDA-Intel - HDA NVidia
                                                              HDA NVidia at 0xfcffc000 irq 19
                                         3 [Aureon51MkII   ]: USB-Audio - Aureon5.1MkII
                                                              TerraTec Aureon5.1MkII at usb-0000:00:16.2-4.4.1, full speed
                                        tindog:~ # fuser -v /dev/snd/*
                                                             USER        PID ACCESS COMMAND
                                        /dev/snd/controlC0:  lancelot  18871 F.... pulseaudio
                                        /dev/snd/controlC3:  lancelot  18871 F.... pulseaudio
                                        /dev/snd/pcmC0D0p:   root       7513 F...m python
                                        /dev/snd/pcmC3D0c:   root       7513 F...m python

                                        "m python" indicating that quisk is running and it can write to both cards 0 and 3.

                                        For Softrock I used 2 cards out of the 4 installed on another box where the camera shows up as a 5th., 1 on-board, 1 PCI and 2 USB.

                                        HDMI sound only has output. On ODROID I use HDMI for Speakers and card 1 for Mic.

                                        I have seen no difference between the distros - openSUSE x86_64, Ubuntu x86_64, Ubuntu ARM and Fedora x86_64 in a VirtualBox VM, they all configure and work the same.
                                        73 ... Sid.
                                         
                                        On 12/08/14 15:45, n4fbz@... [softrock40] wrote:
                                         

                                        I think I've cornered the problem (after a 12 hour day of reading, and checking various things).  The video card in this computer (came with it) has built-in HDMI audio - the audio device from hell.  It "insists" on being card 0 and nothing (so far) will change that... a forcible "deletion" (only way to describe in a few words) results in there being no "card 0" with ALSA, but the other two cards show - but it's still screwing with the audio.  The HDMI audio also has a reputation for screwing with the inputs and outputs of other audio cards.  Oh, and another funny thing - all of my sound boards in the system (built-in, Audigy, and the HDMI) use the same codec - snd-HDA-Intel.  It's been fun trying to figure out how to put the cards in order through ALSA (that's where I picked up that the HDMI was a problem).  Each version of Linux seems to have it's own structure and way of arranging things.  (Sigh) well, that's what can happen with open-source OSes.I always wondered why there were few complaints found regarding my audio board - now it makes sense, because that isn't the problem.Once i get this licked, the softrock will work fine.  When I hit a (temporary) right change which enables the audio (until the next boot) the radio transmits and receives great (although with a maximum of 5mW - about what was expected).I'll let you know how things go today.  This is a good lesson on troubleshooting - sometimes the real problem is something completely different than it seems, and being really observant is key.  The real problem can mimic other issues.



                                        -- 
                                        Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
                                        Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
                                        Senior Staff Specialist, Cricket Coach
                                        Microsoft Windows Free Zone - Linux used for all Computing Tasks
                                        
                                      • n4fbz
                                        It s up and running, finally.The problem was the video card and its built-in HDMI audio. I dealt with that, and suddenly the built-in audio became reliable
                                        Message 19 of 19 , Aug 22, 2014
                                        • 0 Attachment
                                          It's up and running, finally.The problem was the video card and its built-in HDMI audio.  I dealt with that, and suddenly the built-in audio became reliable and configurable -and the configuration was easily changed.

                                        Your message has been successfully submitted and would be delivered to recipients shortly.