DAX Reserved channels

  • 1
  • Question
  • Updated 5 years ago
  • Answered
Is it possible to do something to the DAX Reserved channels so they do not show up as an audio device with external programs?  If they are disabled in the control panel will they still do what they are designed to do?


Photo of Greg

Greg

  • 656 Posts
  • 63 Reply Likes

Posted 5 years ago

  • 1
Photo of Steve - N5AC

Steve - N5AC, VP Engineering / CTO

  • 1053 Posts
  • 1076 Reply Likes
Official Response
You cannot disable them.  Unfortunately, we do not know of a way to keep Windows from showing them either.

Ultimately, we could eliminate them entirely, but it is a significant investment to do so (it involves moving all of our DAX UDP code into a kernel mode driver).  The payoff is a cleaner looking system, but other than that, there's no benefit.  We discussed doing this at the outset, but it would have pushed out things like waterfall, etc. that are next on the list.  It was unanimous in our company to take the faster approach and focus on delivering more important radio features rather than take on another kernel mode driver project ;-)  Having said this, I think those of you that have used it will agree that it far surpasses running a sound card, cables, serial for PTT, etc. in terms of simplicity, flexibility and performance.

If I have my way, you guys are going to get tired of hearing me say this: sound cards are a compromise method for connecting to a digital radio.  The best way is for the digital mode program to directly consume UDP streaming data.  It avoids a classic two-clocks problem, eliminates latency, get's rid of meddling Windows resampling, etc.  I do everything I can to encourage folks that write digital mode programs to connect directly to us if possible.  I understand this is a "single radio" solution, but we have adopted the VITA-49 standard to make this a winning prospect for the digital mode program author -- hopefully over time other vendors will also support this standard for delivery of radio IF data.
Photo of Greg

Greg

  • 656 Posts
  • 63 Reply Likes
I agree and thanks Steve.  The reserved channels just get in the way and make it difficult, if not impossible with some software, to match up the correct RX and TX pair.

I love DX Labs...great software and he will be supporting the 6xxx radios more as time goes on.  But he has a limit as to the number of devices that can be shown and too many of them end up being IQ or Reserved channels.
Photo of Al / NN4ZZ

Al / NN4ZZ

  • 1849 Posts
  • 670 Reply Likes
Steve,
In the short term, maybe a name change would help avoid picking a reserved channel by accident or disabling it by accident.  See snapshot with a suggestion for the wording. 

We can do this ourselves from the "properties" dialog (right click on the device), but it might be nice for consistency to have it set up that way from the start for everyone. 

It's a minor change but might help avoid some confusion and trouble tickets.....

Regards, Al / NN4ZZ  
al (at) nn4zz (dot) com







Photo of Steve - N5AC

Steve - N5AC, VP Engineering / CTO

  • 1053 Posts
  • 1076 Reply Likes
If you change the name, DAX will not work.  It finds the sound cards by their name.  We spent 20 minutes talking about how to name these and get them to show up in most of the programs (many of which truncate length, etc) and I wish I could get THOSE 20 minutes back (never mind spending another 20).  We really hoped that the word RESERVED along with the explanation in the manual would be enough to help folks understand that this is the side you keep away from (don't connect to it).  It really seems like a pretty simple rule to me.  There were lots of suggestions like "DAX DONT TOUCH" and the like, but we felt that RESERVED was reasonably professional and explanatory at the same time.

Now we also have detail here to help people find the right side, too.
Photo of Ken - NM9P

Ken - NM9P, Elmer

  • 4203 Posts
  • 1338 Reply Likes
At the risk of opening old wounds... perhaps INTERNAL would express the same sentiment?  But then again, I think EDUCATION for the users is the best approach! "A little learnin' prevents a whole lotta hurtin'..."   Keep on teaching us!  Thanks....

This conversation is no longer open for comments or replies.