Date   

Re: Post Articles to the files section

kb3cs
 

the Berne Convention, for instance, set a default copyright for ALL materials in all Nations which are signatories.
the consequence is the default applies to materials not specifically copyLEFTED at the time of publication.


On Wed, Oct 23, 2019 at 10:21 AM, prog wrote:
On Wed, Oct 23, 2019 at 07:19 PM, Everett N4CY wrote:
which were never copyrighted
No copyright doesn't grant you the right to redistribute. Just saying.


Re: SDR# and Multipsk #airspydiscovery

Steve Sykes
 

Yes, add CalicoCat. You put the extension into the SDR# directory and add a line to the plugin file. Use the Kenwood 2000 control in FLdigi or MultiPSK

73 Steve KD2OM 


On Sun, Oct 27, 2019 at 19:08 MiJo H. <mijoherzog@...> wrote:
I can work using a virtual audio cable! But is it possible to control the hf+ discovery directly?
Many thanks!


Re: Help please? Device was sleeping. Wake up! Could not acquire the device #spyserver

prog
 

On Mon, Oct 28, 2019 at 10:28 AM, Randall Wayth wrote:
I have a similar problem running linux spyserver, and googling finds other people who have similar problems like this, but no resolution.
This just means you hijacked someone's thread thinking you have the same problem. Same for the others. Statistically, 100% of people failed to read the solution in the archives.

Let's fix this.
1) Create a thread with your specific conditions, then may be, I say, May Be, someone will be tempted to see what's going on.
2) Follow these guidelines for describing your problem (first pinned topic) : https://groups.io/g/airspy/topic/9747306
3) Be kind (very important in the Internet)


Re: Help please? Device was sleeping. Wake up! Could not acquire the device #spyserver

Randall Wayth
 

Did this thread ever get resolved? I have a similar problem running linux spyserver, and googling finds other people who have similar problems like this, but no resolution. A definitive response on what is the root cause of this error would be very helpful.

I have an airspyHF+ and an RTL dongle that cause the same behaviour. E.g.:


/usr/local/spyserver
$ ./spyserver spyserver.config.airspyhf 

SPY Server v2.0.1700

Copyright (C) 2016-2018 Youssef Touil - https://airspy.com

Reading the configuration file: spyserver.config.airspyhf

Listening for connections on 127.0.0.1:5555

Accepted client 127.0.0.1:54014 running gr-osmosdr

Device was sleeping. Wake up!

Could not acquire the device

Running with a different config file for the RTL dongle gives the same result.


Re: SDR# and Multipsk #airspydiscovery

EB4APL
 

I do it routinely. Instead of an external program I use the Windows Stereo Mixer to route the SDR# audio output to Multipsk audio input. Nothing special.

A thing that I need to review sometimes is that in the Stereo Mixer Properties/Levels, the audio is not muted, because for some reason many programs that I use with the Stereo Mixer as the audio input mutes it.

73 de Ignacio EB4APL

El 27/10/2019 a las 16:21, Steve Sykes escribió:
Not to Multipsk but to FLdigi. They would be the same, you need to install a Virtual Audio Cable.  Then direct the output of SDR# to the VAC input and the VAC output to Multpsk.
73
Steve KD2OM
--
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
https://www.avast.com/antivirus


Re: SDR# and Multipsk #airspydiscovery

mijoherzog@...
 

I can work using a virtual audio cable! But is it possible to control the hf+ discovery directly?
Many thanks!


Re: SDR# and Multipsk #airspydiscovery

Steve Sykes
 

Not to Multipsk but to FLdigi. They would be the same, you need to install a Virtual Audio Cable.  Then direct the output of SDR# to the VAC input and the VAC output to Multpsk.
 
73
Steve KD2OM


SDR# and Multipsk #airspydiscovery

mijoherzog@...
 

Hello!
Has anyone connected SDR# with Multipsk?
I am thankful for every help.
73 Michael


Re: Accessibility Plugin...Ideas...Comments...

Simon Brown
 

Also there’s text to speech – I can give you a C++ class for this if you’ve not used it.

 

Simon Brown, G4ELI

https://www.sdr-radio.com

 

From: airspy@groups.io <airspy@groups.io> On Behalf Of Edward MacDonald
Sent: 27 October 2019 09:50
To: airspy@groups.io
Subject: Re: [airspy] Accessibility Plugin...Ideas...Comments...

 

Absolute I will look into it. If it is something I dont need to license I will do my best to add it in. Thanks for this suggestion.

 

I do add tool tips to everything. I am unaware if screen readers utilize them or not, however I will go and research your idea now.


Re: Accessibility Plugin...Ideas...Comments...

Edward MacDonald
 

Absolute I will look into it. If it is something I dont need to license I will do my best to add it in. Thanks for this suggestion.

I do add tool tips to everything. I am unaware if screen readers utilize them or not, however I will go and research your idea now.

On Sun, Oct 27, 2019, 1:41 AM Eric Oyen, <eric.oyen@...> wrote:
Is that plugin compatible with screen readers like narrator, NVDA or jaws in windows? Anything that makes the use of SDRE easier for us blind radio enthusiasts to use makes life better for everyone else too (usually, there is an API used in Microsoft Windows called the MSAA). Could be something to look at.

DE n7zzt Eric
Blind Ham radio Operator and Blind bicyclist/athlete.


On Oct 22, 2019, at 10:18 PM, Edward MacDonald <edwardmacdonald74@...> wrote:

So, I have almost finished creating a new plugin which consolidate three separate plugins I have made into one plugin I call "Accessibility Control" because these three plugins all deal with accessibility of SDR#.

One plugin is also much easier to maintain than three separate ones. The plugin have been re-coded from scratch to make sure my code is as tightly coupled between different classes as possible and to reduce the file size.

I have created it so the On Screen Display, toolbar buttons, and keyboard shortcuts can all be enabled / disabled separately or work in unison with each other seamlessly.

In addition, The on screen display has adjustments for the text size, text brightness, and the dwell time (amount of time the on screen text is displayed before fading out).

The toolbar can be docked in the main SDR# toolbar window or floated in the undocked mode, this way if you have more than one instance of SDR# running you can drag the toolbars from each to wherever you want them ( or even to another monitor if you are using multi-monitor setups).

The toolbar button sets I have created so far are:

 - Detector Buttons
 - Band Switch Buttons
 - Memory Bank Buttons (10 memory slots where you can instantly store and recall presets)
 - Filter Bandwidth Setting Control
 - Squelch Setting Controls
 - FFT Setting Controls
 - AGC Setting Controls
 - Digital / Analog Mode Controls
 - Analog SNR Meter (< I may remove this before the plugin is released)

All of the shortcuts and toolbar button actions are shown with the on screen display control. Pressing shortcut keys or pressing the toolbar buttons has the same exact end result.

<controlpanel.jpg>

While I do not currently have a license for the Telerik theme controls, I have made the plugin so the controls look as good as possible with the new SDR# themes.
While not the same as Telerik's controls (they are just the regular windows common controls) at least they look like they can co-exist in the same space and my plugin windows respond to theme changes.

My question for those of you interested is this:

What other features / functions would you like added to each of the above mentioned items?

I would like to make this plugin as useful as possible for everyone.

There a few items that were in the old toolbar which will not be appearing in the newer version (the reason why was mentioned in other thread posts) 

So, if there is some cool feature or setting I can add, I would like to incorporate it before I remove the original separate plugins from my website and replace it with this one. 

ALSO - This particular plugin will only be compatible with the NEWER THEMED VERSIONS of SDR# (inclusive of the .NET 4.6 and .NET 4.8 framework versions).

Sorry, but I WILL NOT be supporting my plugins from the older versions of SDR#. 

Thanks 




Re: Accessibility Plugin...Ideas...Comments...

Eric Oyen
 

Is that plugin compatible with screen readers like narrator, NVDA or jaws in windows? Anything that makes the use of SDRE easier for us blind radio enthusiasts to use makes life better for everyone else too (usually, there is an API used in Microsoft Windows called the MSAA). Could be something to look at.

DE n7zzt Eric
Blind Ham radio Operator and Blind bicyclist/athlete.


On Oct 22, 2019, at 10:18 PM, Edward MacDonald <edwardmacdonald74@...> wrote:

So, I have almost finished creating a new plugin which consolidate three separate plugins I have made into one plugin I call "Accessibility Control" because these three plugins all deal with accessibility of SDR#.

One plugin is also much easier to maintain than three separate ones. The plugin have been re-coded from scratch to make sure my code is as tightly coupled between different classes as possible and to reduce the file size.

I have created it so the On Screen Display, toolbar buttons, and keyboard shortcuts can all be enabled / disabled separately or work in unison with each other seamlessly.

In addition, The on screen display has adjustments for the text size, text brightness, and the dwell time (amount of time the on screen text is displayed before fading out).

The toolbar can be docked in the main SDR# toolbar window or floated in the undocked mode, this way if you have more than one instance of SDR# running you can drag the toolbars from each to wherever you want them ( or even to another monitor if you are using multi-monitor setups).

The toolbar button sets I have created so far are:

 - Detector Buttons
 - Band Switch Buttons
 - Memory Bank Buttons (10 memory slots where you can instantly store and recall presets)
 - Filter Bandwidth Setting Control
 - Squelch Setting Controls
 - FFT Setting Controls
 - AGC Setting Controls
 - Digital / Analog Mode Controls
 - Analog SNR Meter (< I may remove this before the plugin is released)

All of the shortcuts and toolbar button actions are shown with the on screen display control. Pressing shortcut keys or pressing the toolbar buttons has the same exact end result.

<controlpanel.jpg>

While I do not currently have a license for the Telerik theme controls, I have made the plugin so the controls look as good as possible with the new SDR# themes.
While not the same as Telerik's controls (they are just the regular windows common controls) at least they look like they can co-exist in the same space and my plugin windows respond to theme changes.

My question for those of you interested is this:

What other features / functions would you like added to each of the above mentioned items?

I would like to make this plugin as useful as possible for everyone.

There a few items that were in the old toolbar which will not be appearing in the newer version (the reason why was mentioned in other thread posts) 

So, if there is some cool feature or setting I can add, I would like to incorporate it before I remove the original separate plugins from my website and replace it with this one. 

ALSO - This particular plugin will only be compatible with the NEWER THEMED VERSIONS of SDR# (inclusive of the .NET 4.6 and .NET 4.8 framework versions).

Sorry, but I WILL NOT be supporting my plugins from the older versions of SDR#. 

Thanks 




Re: PSU Noise with #spyserver #airspyhfplus

andrea ottaviani
 

ciao Garcia.
Thanks. I connected the orange server directly to the battery and the spikes are still there!
If I connect the HF+ receiver directly to the PC everything disappears.
My Orange Pi plus is fucked, its voltage regulator is gone.

best 73 de IK0MMI
andrea


Identifying ADSB interference with Airspy

jbart1@...
 

Hi,

I think I have managed to set up ADS B s Spy ( which is receiving signals) and SDR sharp Airspy.  Well thats as far as I have got.  What I am trying to do is to check on local interference to my airspy ADS B receivers locally.  When I think I have dialled up 1090 mhz on the SDR, select Airspy in the SDR sharp, press the start, I get a no  device selectedc.  the airspy is connected to my PC and airspy is indicating signal being received.  Not seeing anything on the SDR sharp screens...... help 


Re: PSU Noise with #spyserver #airspyhfplus

h. garcia
 

I had something similar (noise spikes) when connecting the antenna directly to HF+.

It became much better when inserted a 1:1 balun with galvanic isolation (that is: distinct coil windings).

For my tests, I used NooElecs 1:9 balun, not ideal, but worked nevertheless.

Some ideas:

I haven't tested yet, my guess those very cheap CCTV baluns may be used for experiments.

Old network cards (those that used to have both BNC and RJ45 outputs around 1990-97) often have a boxy component near the RJ45 jack that looks like a relay. These are actually combined 1:1 isolation baluns  (one each pair) enclosed in a single package. A friend reported they worked very well in LF to HF range.

On Tue, Oct 22, 2019, 16:23 andrea ottaviani via Groups.Io <mmh=libero.it@groups.io> wrote:
Hello.
If I connect HF Plus directly it receives good, if I connect from the server (Orange) I see all this noise and spurs.
I tried disconnecting everything.
Some time ago there have been strong lightning, about a month and this has happened since. What do you suggest?
can you try my server sdr: //ik0mmi.ddns.net?
Thanks
best 73 of IK0MMI
Andrew


Re: NOAA APT 136 Mhz

thw
 

Hello Glenn,

I used to record NOAA sats (9 to 18) using a WinRadio set.  However I recall that NOAA APT transmissions occupy 40KHz bandwidth and that finer image resolution needs all of that.  Selecting NFM limits your bandwidth to 32KHz.  You can use WFM and slide the band edges into the 40KHz span.  There is no point in using more than 40KHz as there will be no improvement in quality and may add to the noise. 

It may help to recall that NOAA APT images are broadcast as an amplitude modulated sub-carrier on 2280Hz, which frequency modulates the transmitted carrier.   This was hot new technology in the 1960s when this scheme was designed.

I hope this helps you.

Regards,  Tom.


On 25/10/2019 21:35, w3wte wrote:
I seem to be stuck at #1702 for good reception. I am using a AIRSPY Mini and have been receiving NOAA Sats. for many years, with out any problems. Starting with the latest versions ( that have selectable skins) I am getting blurred decodes using WXTOIMG. My configuration is to go into # config and change 32000 to 42000 and use NFM with a Sample rate of 3 MSPS and a Dec. of 64. The noise alone when testing WXTOIMG also looks blurry. Their seems to be a change in the Audio causing this to happen as far as I can tell. I have tested this over many days, with no luck on the picture quality, using the new versions. The new versions work just fine using my SDR IQ, SPyvertrer, and general usage. Any clues to the issue would be appreciated, as I like to be using the latest # versions.
Thank You,
Glenn W3WTE


Re: NOAA APT 136 Mhz

prog
 

On Fri, Oct 25, 2019 at 10:36 PM, w3wte wrote:
I seem to be stuck at #1702 for good reception. I am using a AIRSPY Mini and have been receiving NOAA Sats. for many years, with out any problems. Starting with the latest versions ( that have selectable skins) I am getting blurred decodes using WXTOIMG. My configuration is to go into # config and change 32000 to 42000 and use NFM with a Sample rate of 3 MSPS and a Dec. of 64. The noise alone when testing WXTOIMG also looks blurry. Their seems to be a change in the Audio causing this to happen as far as I can tell. I have tested this over many days, with no luck on the picture quality, using the new versions. The new versions work just fine using my SDR IQ, SPyvertrer, and general usage. Any clues to the issue would be appreciated, as I like to be using the latest # versions.
Thank You,
Glenn W3WTE
This is unrelated to the GUI. If you don't remember which settings you changed, you can copy SDRSharp.exe.config from the old version to the new one.


NOAA APT 136 Mhz

w3wte
 

I seem to be stuck at #1702 for good reception. I am using a AIRSPY Mini and have been receiving NOAA Sats. for many years, with out any problems. Starting with the latest versions ( that have selectable skins) I am getting blurred decodes using WXTOIMG. My configuration is to go into # config and change 32000 to 42000 and use NFM with a Sample rate of 3 MSPS and a Dec. of 64. The noise alone when testing WXTOIMG also looks blurry. Their seems to be a change in the Audio causing this to happen as far as I can tell. I have tested this over many days, with no luck on the picture quality, using the new versions. The new versions work just fine using my SDR IQ, SPyvertrer, and general usage. Any clues to the issue would be appreciated, as I like to be using the latest # versions.
Thank You,
Glenn W3WTE


Re: Plugin Ideas: RNNoise Plugin #software #plugins

Simon Brown
 

Hi,

 

I use rrnoise, most recently for SSB Squelch with very good results. As far as I can see rrnoise is finished, there’s little that can be done to improve the concept. Even if the API does change (which I doubt) the calls are simple with only a few parameters.

 

Simon Brown, G4ELI

https://www.sdr-radio.com

 

From: airspy@groups.io <airspy@groups.io> On Behalf Of Peter KM6WXN
Sent: 24 October 2019 21:30
To: airspy@groups.io
Subject: Re: [airspy] Plugin Ideas: RNNoise Plugin #software #plugins

 

Thanks for that git link.  So no updates from the original dev since 2017 (a few months after original commit), then a group of updates from one other dev on a single day in May of this year...

Not sure if that means the API has basically been completed, or is still a WIP?


Re: Accessibility Plugin...Ideas...Comments...

Edward MacDonald
 

Thanks Prog. Much appreciated. It works perfectly.



On Thu, Oct 24, 2019, 6:49 AM prog, <info@...> wrote:
On Thu, Oct 24, 2019 at 02:19 PM, Edward MacDonald wrote:
Thanks for the info.
Check the latest update.


Re: Plugin Ideas: RNNoise Plugin #software #plugins

jdow
 

In perfectly accented Lower Slobovian....
{O,o}

On 20191024 08:28:52, prog wrote:
It will be funny to see the algo synthesizing a human voice out of pure noise.

7381 - 7400 of 39937