Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

In SS SSB...Audio Problems with N1mm

Member ✭✭
Not getting audio monitor in headset.  Only speaker.

Long delays after using Fkeys (N1MM)

Welcome!

It looks like you're new here. Sign in or register to get started.

Comments

  • Member ✭✭
    edited November 2019
    Same problem as Mitch and Grant.  Headset is fixed but the delays can only be cured by turning radio off and then on again.
  • Member ✭✭
    edited May 2020
    Richard,

    Setup here is a 6700/Maestro.  Used N1MMLogger+ audio the entire contest with no issues.  Don't forget the computer in the setup.  I am using a Win7 machine, AMD X4 955 3.2 GHz, 8.00 Gig RAM 64 bit OS.  Delays such as you describe make me think external computer issues.

    My headphones are plugged into the Flex (Not an issue with the 6600M as you don't have the Maestro/6600 choice far as I know)..  Tx DAX on, Microphone DAX on, Monitor on and set to comfortable volume.  N1MM setup per instructions.

    Does that help?

    John
  • Member ✭✭
    edited November 2019
    There is a software bug with using monitor with DAX and VOX.  I reported this issue to Flex support.  This is a software bug that will be addressed in the future. This issue has been logged as defect number: G7691
  • Member ✭✭
    edited November 2019
    Did not work for me either. Some random combination of VOX operating PTT or something else, maybe at the same time as DAX stream was active would sometimes kick-in the monitor audio for the next over before you lost it again. This did work properly in previous releases. It's a PITA no knowing for certain how your voice keyer sounds in a contest.
  • Member ✭✭
    edited November 2019
    Flex claims this defect was introduced after the 2.4.9 code release.  I have not rolled back and will wait for the fix.  

Leave a Comment