@lauchlin -- are you running Protocol 1 firmware?

There's nothing wrong with those results if you are using two-tone. As previously mentioned the dotted line is an artifact of the two-tone waveform. What power level was being used when you grabbed those screenshots? However, you may want to revisit your SetPk value. Make note of the current value, ...

Laurence: can we publish the schematic for the balanced mic preamp?

It might be helpful if someone who is having distorted audio problems could put an oscilloscope to work and see what was going on. Perhaps on some of these boards the NE5534 is going into oscillation.

That's a beautiful connector!

Okay this seems to happen only with my electret mic. It seems that the audio is lower if I use the MOX button. But If I use my dynamic mic there is no difference in xmit audio level whether I use physical ptt or mox. Maybe something with bias voltage switching in. Assuming you mean "PTT switch...

You are using the second ADC for RX2, with a separate antenna?

So if I understand you correctly from your original item 2 most mic/headphone setups get their bias supplied on the ring.....which would mean that the bias being supplied to the mic would in fact be the 3.2 volts on the logic input that puts the rig into TX.....which will of course dis-appear when ...

I cannot duplicate your results.

Is the DEXP and everything else 100% identical across the board except for the state of VOX?

What happens when you use MOX with VOX enabled?

Bottom line .....either there's a hardware mistake somewhere, or theres a software fault thats been there for ever. There's nothing wrong with the hardware or the software. There is something wrong with your mic wiring, either inside the mic or inside the cable or both, that is causing the problem....

Laurence: he wrote above that it is an RE320, which is a dynamic mic. Thus lack of phantom power is not an issue.

It is conceivable that the cable could be bad. @MW0XDT do you have a way to test the cable with another piece of audio gear?

n2gq wrote:I currently use the Behringer bigfoot. It only has an asio4all driver which I just discovered on their website.

ASIO4ALL is an ASIO wrapper around WDM.

Both openHPSDR mRX PS and Thetis can happily be installed at the same time on the same PC. No special methods are necessary, just use the normal installer for each. There's no need to run one or the other to enjoy different settings. Both Thetis and openHPSDR (aka "PowerSDR") provide a com...

Do I need to install HPSDRBootloader, or just HPSDRProgrammer, in order to set the ANAN static IP and NIC priority? To clarify: you don't use either of those utilities to set the Network Metric (what you called "NIC priority"). You do use them to set the ANAN IP. In a multi-NIC environmen...

Running FW 2.2.2 with Thetis 2.10.3.6 dev_2 on an ANAN-8000DLE. No problems to report at this time, but it's only been running for a few hours.

IMHO this is not an unreasonable request. People with noisy shacks that have fans running, etc. often have trouble with background noise. Conceptually it would not be hard to use NR2 on the transmit audio. Of course you probably are aware that the console code in Thetis is quite complex (complex bei...

Everything you need to know about Bootloader and the various versions of Programmer is in this topic: https://community.apache-labs.com/viewtopic.php?f=18&t=2333 I prefer to use Bootloader because it always works no matter what firmware you have loaded. NIC priority is a Windows setting and has ...

See this topic: viewtopic.php?f=22&t=4127

Remember that Wi-Fi counts as a NIC, i.e. you can use Wi-Fi for your normal network connection and the Ethernet port for the radio.

Thetis benefits from a lot of cores/threads. Get at least an 8 core (16 thread) CPU. 12 cores would be even better. At equivalent speed/price points the AMD CPUs generally offer more cores. If I was building new I'd be getting a Ryzen 9 with 12 or 16 cores. Memory requirements are driven by Windows ...

It's the same list no matter what input is selected: mic, line, VAC, cmASIO.

-65 dB is too much. The -55 dB of the VK unit is perfect at the legal limit.

The other thread should answer your question.

Would the 1/8" TRS 'Line In' be a better choice, due to the high gain mic pre on the XLR input? Hard to say. You'll have to try it. As I already wrote, a lot of people have had trouble using the G2 balanced input even with just a microphone by itself. 1) What is the simplest way to 'bridge' my...

Why would you suggest analog through CAT? Not doubting your knowledge, just wondering. IMHO, MIDI is a lot of extra processing in order to form the required MIDI messages. Click a button or turn a knob one increment and puke out the appropriate CAT message seems simpler to me, especially if I was c...

For line in see here: https://www.w1aex.com/anan/anan.html#audio_chain The G2 has a balanced input on the rear. I don't have a G2 but I believe that connector is a 1/4" TRS jack. People have had all manner of difficulty trying to use that input but theoretically it is the obvious way to go. One...

AFAIK the Purge Buffers option only affects the spectral display and not any audio.

This problem occurs even without external source of latency like Voicemeeter. The problem is that the Thetis TX audio pipeline is not flushed prior to the start of the transmission. This problem can be mitigated by setting General > Options > Options-1 > RF Delay to an appropriate value. I've never ...

There will be no conflicts. Internal Thetis logic is "last command wins".

You might consider processing the analog controls into CAT rather than MIDI.

Note also that Thetis can accept CAT over IP as well as serial.

K5WC wrote:It would be nice if we had a pinned post in the G2 section about software and firmware updates was posted.

Like this one: viewtopic.php?f=48&t=4772 ?

A quick post to the bottom of that one by one of you G2 folks might be all that is necessary.

That will work fine.

See also this large thread on GPSDO use: viewtopic.php?f=17&t=2499

Power cycling the ANAN hardware to fix a problem indicates that the firmware went to a bad place and needed to be rebooted.