I believe this could be accomplished with the addition of a simple software selector switch which would allow the user to select whether the PTT would stream audio from the selected mic or from a local mic.
I further believe the selector switch should have the default set to stream audio from whatever mic is selected.
Such a scenario would have the following benefits:
1) The program would operate as expected (and as intuition says it should) for new users.
2) A seasoned user could change the switch setting if and as he wished.
3) Users who have their mic connected to their PC and want to use a PTT hand/foot switch would not face the challenge of devising a way to connect the PTT to their computer, they could simply use the built-in PTT port on their Flex 6000.
4) New users would no longer potentially waste time and effort trying to get the program to operate as they expect it to (and as common sense and intuition says it should). I speak as one who has expended considerable energy on such a pursuit.
Thank you very much for your consideration,
In this case, they choose their regular Mic input (either front panel MIC, back panel BAL/Line, or AUX) and then activate the DAX button. When the DVK activates, the computer keys the rig via CAT or API Commands, or via a COM PTT port and the TX Audio comes via the DAX TX Audio port from the computer. But if the Mic PTT, Footswitch PTT port, or VOX are activated, then the hardwired Mic takes over.
This has been the standard operating procedure for a couple of years.
However, A feature could be implemented that allows the choice of:
1) The way it is now - favored by most hams who use DVK features on their logging programs for contesting or DXing.
2) a mode where the Footswitch always activates audio from whatever Mic is selected - including "PC"
3) a mode where the Footswitch always audio from whatever Mic is selected UNLESS the DAX button is selected, in which case, it operates like #1 above.
4) the rig operates as in #1 above, unless "PC" is the selected Mic, in which case an external PTT uses audio from the PC.
I think the main issue in all of this is deciding what to do with PTT and audio routing when PC is the selected Mic....
We may find that the current mode of operation may be a requirement needed for future feature implementations, such as multi-client, etc.?
Personally, I have never found a good reason to use external computer audio processing with my Flex-6500, other than briefly playing with "Stereo Tool." In the long run, I found that I could get better audio much more easily by simply using the internal TX EQ, PROC, and DEXP.
But that is another matter of personal preference.
Along those lines, I have though that it would be really neat to have an option for an "Audio LOOP" where the rig would be able to take the audio from one of the MIC inputs, send it via an audio port like "DAX TX LOOP" to the computer and then return the computer processed audio for TX using the "PC" Mic input. This option would also be able to use the external PTT.
Ken - NM9P
I have wanted this feature since I bought my 6500/6700 over 4 years
Just have a check box in the MENU for Transmit so for people who want the PTT/DAX have a choice how the PPT works.
"One thing we know from the Flex world is: Creating features is extremely expensive, coding."
since many of us have spent Thousands of dollars on radios and now
$199 for each significant SSDR version I don't think it wrong to ask!
After all it is "Software Defined Radio" and we are the customers!
And please don't tell me about FRS stacks or any other external software I can use to do this. If I wanted to piggy back a ton of apps on to SSDR just to get it to do simple things I could go with an old Flex 5000.
You have now posted this...
Let's see how many likes you get as the number of LIKES votes give Flex an idea as to the real world desirability of this feature so that they can give it a development priority
Having been a alpha tester for this and many other products.. NOTHING is SIMPLE when it comes to changing software - you have to be very careful that even when enabling a feature it does not break something else.
The amount of traffic on a posting is definitely a factor. Likes are part of the traffic measure - in making a decision to implement a feature.
Didn't say they should not try because software development is not easy.
I said, that Flex needs to understand how desirable a feature may be to the widest possible audience to make it worth the investment in software development time and money.
I suspect the fact that only two of you are currently hot for this feature will put it far down on the development desirability list as there are many other features with many more likes and many more people expressing the desirability for the feature.
When I search "PTT DAX" there are hundreds of post's going back years on this very subject.
Give it a Try. Type "PTT DAX" in the search bar and look how many people have posted the same question.
When I search I see :
Conversations = 1 - 15 of 3284
Looks like more than just Mark and I.
Even if only 25% of these result are for the "PTT/DAX qustion thats still a LOT of people!
I think your idea may be good, just mentioning from past statements from Gerald one of the things they consider when looking into such a project.
Mark, the reason I asked Ken to say something about the audio part is because Ken has spent many hours researching this subject, audio and Flex Radios... I respect his information and he has done more work in this regard then I. One area I have spent time on is learning the relationship between the PROC and the EQ and how they react to each other.
"Wow I sense so much anger from my comments."
I think it's because you feel the need to comment on almost every topic on this forum all day and night long.
Also you regularly act as if your a moderator or employee and just cant resist to just comment for the sake of commenting.
I don’t know and I’m probably wrong but You have just got to be a plant hired by FRS pretending to be a customer to handle public relations on the forum and move the topics in favor of FRS even when no one asked you.
Ken’s tutorials are very helpful and I like many are thankful
for Ken’s great Videos.
But Bill, Ken's videos have nothing to do with this topic.
Here is just a sample of some of the posts on this topic.
You get it now. This has been talked about for years.
I will stop now otherwise I will be guilty of doing the very thing you do.
I can vouch for the fact the Bill is only a good customer of Flex and neither an employee or a shill
But I also agree with Bill that your posts are often tinged with one might say earnestness. which is why you end up goading Bill to reply.
I do agree that your links make your point that there is clearly a significant demand to be able to optionally enable DAX so that it works with PTT. (In the trade these are called Nerd Buttons or Nerd Switches)
I also agree that there could be several use cases for PTT via DAX albeit there are also work arounds that I use that seems to satisfy my needs but clearly direct PTT would be easier.
Ken did point out that there are at least 4 or as you say 3 different ways to implement this feature. Plus there needs to be an obvious placement for the Nerd Button. Obviously Engineering at Flex will have to look at determining the best way to actually do it.
Bottom Line: I think you made your point very effectively.
Mark said: so when I engage the SSDR Monitor function I can hear exactly how my transmitted audio will sound. You can't do that if you're using the internal EQ, as that feature is downstream from the Monitor function.
Kens tutorials do speak to Marks comment. SSDR allows us to hear just what we sound like in a couple different ways, Record and playback and Full Duplex method.