-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permit frequency shorthand of "M" (e.g. 90.9M instead of 90900000) #50
Comments
nrsc5 doesn't support that, but I think it would be a useful feature. I'll put it in the next time I'm working on the project. |
Thank you. Some additional testing... If I ask RTL_FM to tune 90.1M, it consistently tunes 90371000 Hz, not 90100000 Hz. 90100000 Hz works fine for nrsc5 but 90371000 Hz results in
Similarly with 90.9Mhz HD1 or 909000000 specified: |
I suspect that's just because rtl_fm is using offset tuning to keep the signal of interest away from the noise spike around 0 Hz. nrsc5 doesn't have that problem because the noise spike is in the analog FM signal, which is filtered out anyway. |
Ah, makes sense. I was confused because I was looking for the exact frequency to plug in. And what worked in analog wasn't working in digital. All the more reason to just simplify the UX and just use 90.9M or similar... |
This is fixed in #54. Instead of a prefix, it will accept a decimal number for the frequency, and if it is less than 10,000, it will be multiplied by 1M. |
In rtl_fm, you can specify a frequency of 90.9M instead of writing out all the zeros like 90900000.
In nrsc5, if you specify a frequency of 90.9M, it will do auto gain control but not play anything.
I have tried a number of stations with the same result. Unless I am missing something...
The text was updated successfully, but these errors were encountered: