Good luck. I've gone as far as I can go for now. I'll be watching to see if anyone comes up with a suggestion/solutionI haven't got that far yet, so I can't advise you. I'm still playing with the other settings.
Good luck. I've gone as far as I can go for now. I'll be watching to see if anyone comes up with a suggestion/solutionI haven't got that far yet, so I can't advise you. I'm still playing with the other settings.
I had the same thing for my frequencies file. Turns out that there were in fact three errors. The way I tracked it down was by loading the frequencies into Word and activating line counting.
1. In the event log Input menu I chose "Line 1 (Virtual Audio Cable)
2. In the same menu I also chose "Monitor Source Audio Always" as I pass analog audio through DSD+ via SDR# as well.
Well I'll be damned. So now that I see that, my first line is grayed out and won't allow me to make a change. I changed Monitor Source to always as suggested with no joy.
Mike,Dan,
In the Event Log window, in the menu system choose Control --> Passive Digital Monitor. That will then allow you to adjust what VB cable input you want to use. When Passive Digital Monitor is enabled, you do not use FMP24/FMPA but instead use your own audio source (like SDRSharp or something else). The latest version _defaults_ to having Passive Digital Monitor turned off, because it presumes that you would be using FMP24/FPA with TCP linking.
Remember what I told ya before. I'm around all week this week if you wanna call and pick my brain.
Mike
SameStill waiting on my damn update
Mike,
That did it. Once again thank you. If I don't talk to you before Have a Merry Christmas
They really lagging behind sending email
what would be a less cheesy platform?Could be, or you might be using a cheesy email provider. When I say cheesy, I mean any Microsoft email platform, Any Yahoo email platform (including SBC), any AOL stuff, any crumcast, etc. They are all garbage. But you could be right and it may not be your email.
what would be a less cheesy platform?
None of the menu input/output settings worked for me. I resorted to command line -i1m -o2m settings or I had no input. If I just use -i1m, I see decoding and it records with -Pmp3 but no output unless -o2m and -i1m settings used in junction with other settings. I just got it working and will have to dsdtune again to see if the decode is any better.
The menu options weren't grayed out, they just didn't do anything. I selected on input VB-Cable output and for output the Speakers and it didn't do any decode. There was a house fire and things were very active on the primary VHF band along with toning out the EMS on P25 with traffic from police which I didn't receive until I went back to using command line options. DSD tune keeps the digital down. If I don't some talkgroups esp the local ems and police have stutters and glitches and when I dsdtune them, It picks a good setting. Anything from surrounding areas sound better. Most of the time the Police or EMS are so far out there they go "digital" I get weak digital and the dispatcher cant even hear it and has to call out a repeat. Even with all that the update is much better with improvements. It's very hard to do any tinkering around when the site here has almost non-existent traffic. Most of the time I see the same DNR officer making tons of data calls from his SUV. I believe he's running all kinds of names and plates through the LEIN. Most of the time they call on the phone or email.If you have to dsdtune anything, you are working with a poor signal to begin with.
When you say the menu input/output settings didn't work for you, were they greyed out? Or could you select them and they just didn't seem like they worked? You need to provide details.
Could be, or you might be using a cheesy email provider. When I say cheesy, I mean any Microsoft email platform, Any Yahoo email platform (including SBC), any AOL stuff, any crumcast, etc. They are all garbage. But you could be right and it may not be your email.