You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two channel definitions created: 1 is 771.95625 (P25), 2 is 454.1875 (Con+). Channel 1 is set to prefer Tuner 1, Channel 2 is set to prefer Tuner 2.
I then decide that I want to flip-flop the preferred tuners, so I stop both channels. I modify the channel definitions to have Channel 1 prefer Tuner 2, and Channel 2 to prefer Tuner 1. When starting up both channels again, it throws an error that it can't start one of the channels, and a message like the following is logged:
20201013 000902.210 [sdrtrunk pool-1-thread-5] INFO i.g.d.source.tuner.TunerModel - Unable to source channel [454187500] from preferred tuner [RTL2832 SDR/R820T 00001000] - searching for another tuner [438MB/740MB 59%]
It appears that even though both tuners were shut down, something still has them locked to a particular frequency range, preventing them from re-tuning to a different range. SDRTrunk must be restarted in order for the new preferred tuner assignments to take effect.
The text was updated successfully, but these errors were encountered:
Two channel definitions created: 1 is 771.95625 (P25), 2 is 454.1875 (Con+). Channel 1 is set to prefer Tuner 1, Channel 2 is set to prefer Tuner 2.
I then decide that I want to flip-flop the preferred tuners, so I stop both channels. I modify the channel definitions to have Channel 1 prefer Tuner 2, and Channel 2 to prefer Tuner 1. When starting up both channels again, it throws an error that it can't start one of the channels, and a message like the following is logged:
20201013 000902.210 [sdrtrunk pool-1-thread-5] INFO i.g.d.source.tuner.TunerModel - Unable to source channel [454187500] from preferred tuner [RTL2832 SDR/R820T 00001000] - searching for another tuner [438MB/740MB 59%]
It appears that even though both tuners were shut down, something still has them locked to a particular frequency range, preventing them from re-tuning to a different range. SDRTrunk must be restarted in order for the new preferred tuner assignments to take effect.
The text was updated successfully, but these errors were encountered: