¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. N2adr-Sdr
  2. Messages
Expanded Topics Messages Polls
Date
Quisk Version 4.2.29 January 2024

 

This version updates the FreeDV library files and program logic. I added a "Monitor" item to the FreeDV menu. It routes the sound to the speakers instead of to the demodulator. Turn on both the monitor and FDX to listen to your transmitted FreeDV signals. Please test.
?
Modes 700x and 1600 are finished. The other modes will be added shortly. If you use any of them post here and I will move them to the top of the list.

Jim
N2ADR
Re: Quisk Version 4.2.28 December 2023

 

Hello Jim

If it is easier for you to fix FreeDV, that is perfectly fine.?
I am just happy to be able to use Quisk and am very thankful for your help.

73 de OZ1UM Bjarne
Re: Quisk Version 4.2.28 December 2023

 

Hello?Bjarne,

I have all the files from Quisk 4.1.40, but that version is from June, 2019, and is for Python 2.7. I am not sure whether it will run on Python3. Also, PyPi will not let me put it back on the server. It claims the name is in use even though 4.1.40 was removed. Perhaps I can make a Python3 version of 4.1.40 and name it something else.

But a better solution may be to make FreeDV work properly in the new Quisk. Then you can install the latest version. I have not had other complaints about FreeDV but I will look at it. There have been few changes except for updated FreeDV libraries.?

I will work on this and let you know.

Jim
N2ADR
Re: Quisk Version 4.2.28 December 2023

 

Hello Jim

I installed it using pip and 32 bit Python 2.7.x and wxPython 4.0.1 and for windows 7.

Now I have updated to windows 10 and am using 64 bit Python 3.11.5 and the newest wxPython.

73 de OZ1UM Bjarne
Re: Quisk Version 4.2.28 December 2023

 

Please describe how you install Quisk version 4.1.40. Do you use pip? This version is for Python 2.7, not 3.11. And it is for 32-bit Python.

Jim
N2ADR
Re: Quisk Version 4.2.28 December 2023

 

Hello Jim
?
I am not a specialist at PCs, I am just a simple user.
But as we see it in our FDV group the newest versions are listening on both sidebands no matter what we choose, but transmit is taking place on the chosen sideband. We have just experienced that if we change sideband on the receiver side then we still receive the signal and if there is heavy traffic in the opposite sideband, then the signal gets ruined and it is impossible to hear anything.
?
It is absolutely ok if we can have access to version 4.1.40, but of course we would like to be able to use the newest versions so we can keep us updated.
We use windows 10 and it is old PCs from our kids we use. I for instance is 82 years old and we are all in that age range.
It is possible that it's our own mistake, as we are all from the analogue age.
We mainly use mode 1600 and mode C700.?
We don't know anything about codec2, so maybe the fault is there? We just use Quisk along with Python 3.11.5.
?
In SSB and CW everything seems to be ok.
?
It is ok if we can just be able to download and use version 4.1.40 if we can't figure out codec2, which is unknown to us and the fault for us might be there.
?
73 de OZ1UM Bjarne
Re: Some gtk error messages

 

Hi Graeme,

I get gtk error messages too, but haven't found the cause. If they were absent before, it is probably due to a different version of wxPython in the git install.

Jim
N2ADR
Re: Quisk Version 4.2.28 December 2023

 

Hello Bjarne,

I looked at the FreeDV code from 4.1.40 and the only changes were the introduction of modes with sample rates other than 8000 sps, and a change in the included codec2 library. As far as receiving USB and LSB, Quisk does not do any filtering. All filtering is done in FreeDV.

Do you need 4.1.40 for reasons other than FreeDV? Or should we just fix FreeDV?

Are you on Windows or Linux?

What FreeDV mode are you using?

What makes you think that both USB and LSB are being mixed?

Where did you get your FreeDV codec2 library?

Jim
N2ADR
Re: Virtual Environment

 

No problems here, HiQSDR with ODROID-C4 Ubuntu 23.10 and 7" touch screen.
73 ... Sid.

On 26/12/2023 21:15, jimahlstrom wrote:
I have been trying to use the recommended Python installation methods for many years. But using virtual environments just to install an app is just too much. I am changing the Linux Quisk installation to use git. To install Quisk just clone the repository: git clone . Then run "make". You will still need all the required packages as usual. You can run Quisk with "python3 quisk.py".

I will write more complete instructions soon, but feel free to try it now.

Jim
N2ADR
--
Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot
Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks
Re: Quisk Version 4.2.28 December 2023

 

Hello Jim
?
I have observed that FDV-mode has problems in quisk versions newer than approx. 4.1.40.
In listening mode it can receive both LSB and USB, which leads to poor or impossible receiving when there is other activity in the opposite sideband.
So far it hasn't been a problem as we have just used version 4.1.40 when we have built something new.
We are very excited for Quisk and have used it for all our SDR timeline. It has been used for Lima-SDR, HiQSDR, Red Pitaya and Hermes lite 2.
Now a new problem has arisen as I can't find version 4.1.40 when trying to download it.
So what should I do now; of course I would like to be able to use the new versions. So if you, Jim, maybe can look into the problem or have a solution, or maybe if I can download 4.1.40 somehow.
We are very happy to be able to use Quisk and appreciate your service and help concerning the program.
?
Happy new year to all in this group.
?
OZ1UM Bjarne
Re: Virtual Environment

 

I am doing my best as Fedora downstream maintainer :)

73! Jaroslav, OK2JRQ

Randall Sanborn napsal(a):

One of the things that sent me down this path was that break system packages screwed up LibreOffice for me. Dependency hell is real. I ended up going back to Fedora which has one of you wonderful folks keeping the Quisk package maintained. So I'm just using that for now.
Regards,
Randall
AE8RS
On Wed, Dec 27, 2023 at 2:57?AM Graeme Jury <gvjury@... <mailto:gvjury@...>> wrote:
Hello Jim,
Git works well and for me is preferable. There is a few things to get
right with Python yet and I am using PySide6 which has even more but it
is still a fabulous language.
Everything went smoothly and I see that you have dropped the
requirement
for make quisk3 so I guess that Python2 is no longer supported which
again is a good decision as we should move along I guess.
Again thanks a million for the most user friendly radio and of course
for me the remote operation.
73 de Graeme ZL2TE (Call-sign change from ZL2APV)

smime.p7s
smime.p7s

Some gtk error messages

 

Using the new git setup, I started Quisk from a terminal rather than my normal startup script and of course got all the debug messages which I missed off the script. I have reproduced them below and wonder if they are significant as it does not seem to affect the operation of Quisk at all but it might be of interest

gvj@DLap:/opt/quisk$ python3 quisk.py
(quisk.py:3067): Gtk-CRITICAL **: 08:57:00.124: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar
Pulseaudio threaded mainloop started
Connected to DLap
open client radio sound from remote_radio: opened socket 120.89.81.18 port 4587
open client graph data from remote_radio: opened socket 120.89.81.18 port 4586
read_remote_radio_sound_socket() sending 'rr'
read_remote_radio_sound_socket() sending 'rr'
read_remote_radio_sound_socket() sending 'rr'
read_remote_radio_sound_socket() sending 'rr'
read_remote_radio_sound_socket() sending 'rr'
Context Terminated
Closing Remote Control connection
radio sound from remote_radio: closed socket
graph data from remote_radio: closed socket
total packets sent = 0, recd = 0
(quisk.py:3067): Gtk-CRITICAL **: 09:31:06.777: gtk_notebook_get_tab_label: assertion 'list != NULL' failed
(quisk.py:3067): Gtk-CRITICAL **: 09:31:06.779: gtk_notebook_get_tab_label: assertion 'list != NULL' failed
(quisk.py:3067): Gtk-CRITICAL **: 09:31:06.780: gtk_notebook_get_tab_label: assertion 'list != NULL' failed
(quisk.py:3067): Gtk-CRITICAL **: 09:31:06.791: gtk_notebook_get_tab_label: assertion 'list != NULL' failed
gvj@DLap:/opt/quisk$

73, Graeme ZL2TE
Re: Virtual Environment

 

Github version working fine on my Ubuntu 22.04 machine.
Re: Virtual Environment

 

One of the things that sent me down this path was that break system packages screwed up LibreOffice for me. Dependency hell is real. I ended up going back to Fedora which has one of you wonderful folks keeping the Quisk package maintained. So I'm just using that for now.

Regards,

Randall
AE8RS


On Wed, Dec 27, 2023 at 2:57?AM Graeme Jury <gvjury@...> wrote:
Hello Jim,

Git works well and for me is preferable. There is a few things to get
right with Python yet and I am using PySide6 which has even more but it
is still a fabulous language.

Everything went smoothly and I see that you have dropped the requirement
for make quisk3 so I guess that Python2 is no longer supported which
again is a good decision as we should move along I guess.

Again thanks a million for the most user friendly radio and of course
for me the remote operation.

73 de Graeme ZL2TE (Call-sign change from ZL2APV)
Re: Virtual Environment

 

Hello Jim,

Git works well and for me is preferable. There is a few things to get right with Python yet and I am using PySide6 which has even more but it is still a fabulous language.

Everything went smoothly and I see that you have dropped the requirement for make quisk3 so I guess that Python2 is no longer supported which again is a good decision as we should move along I guess.

Again thanks a million for the most user friendly radio and of course for me the remote operation.

73 de Graeme ZL2TE (Call-sign change from ZL2APV)
Re: Tips on interfacing I/Q data into quisk?

 

¿ªÔÆÌåÓý

Cool!? Thanks Jim.? I will try and decimate it down to something more manageable on my end,? It is a relief to know Quisk can handle some small mismatch.

73,
Rob
KL7NA

From: [email protected] <[email protected]> on behalf of jimahlstrom via groups.io <jahlstr@...>
Sent: Tuesday, December 26, 2023 1:06 PM
To: [email protected] <[email protected]>
Subject: Re: [n2adr-sdr] Tips on interfacing I/Q data into quisk?
?
CAUTION: This email originated from outside the Walla Walla University email system.

>>Do you have a feel for the best way to deal with the fact that my sample rate is going to be 48.0460 kHz, not 48 kHz?

Quisk can correct small rate differences itself. Otherwise the SDR-IQ rate correction can be used. We will have to deal with this once we have the hardware available.

Jim
N2ADR

Re: Virtual Environment

 

I have been trying to use the recommended Python installation methods for many years. But using virtual environments just to install an app is just too much. I am changing the Linux Quisk installation to use git. To install Quisk just clone the repository: git clone?. Then run "make". You will still need all the required packages as usual. You can run Quisk with "python3 quisk.py".?

I will write more complete instructions soon, but feel free to try it now.

Jim
N2ADR?
Re: Tips on interfacing I/Q data into quisk?

 

>>Do you have a feel for the best way to deal with the fact that my sample rate is going to be 48.0460 kHz, not 48 kHz?

Quisk can correct small rate differences itself. Otherwise the SDR-IQ rate correction can be used. We will have to deal with this once we have the hardware available.

Jim
N2ADR
Re: Tips on interfacing I/Q data into quisk?

 

¿ªÔÆÌåÓý

Thanks Jim,

I'll look at the sdr_iq hardware file some more.? I've been looking at making a SoapySDR driver too.? I might try that too.? ? Right now I am trying to get a good way to verify there won't be times when the UART communications won't cause glitches in the audio.? I don't need low latency really, because I'm not trying to do CW QSK with these receivers or anything like that, so bigger buffers should solve my problem.? Right now my testing method is to send the signal to the host using eight eight bit binary numbers, and then have the host send it to alsa.? I'm getting under-runs or samething now, but I'm not implementing a buffer either yet, just shooting it straight to the sound card.

Do you have a feel for the best way to deal with the fact that my sample rate is going to be 48.0460 kHz, not 48 kHz?

TNX & 73,

Rob

KL7NA

From: [email protected] <[email protected]> on behalf of jimahlstrom via groups.io <jahlstr@...>
Sent: Wednesday, December 20, 2023 1:01 PM
To: [email protected] <[email protected]>
Subject: Re: [n2adr-sdr] Tips on interfacing I/Q data into quisk?
?
CAUTION: This email originated from outside the Walla Walla University email system.

Quisk has an interface that can accept I/Q samples from a custom hardware file written in Python. It is fairly easy to use, and the most work will probably be in accepting the samples from the hardware. Please see the file quisk_hardware_model.py starting at line 100.

This interface is used for the RF Space SDR-IQ radio. This radio returns samples from a USB serial port interface. The file is quisk_hardware_sdriq.py and should be a good starting point.

But PC soundcards have always been a nightmare, and you may have problems. Some cards have a fixed time delay between the I and Q channels. If the delay is one sample, it can be corrected, but some cards have a fraction of a sample delay. And then there is the rate problem as already discussed.

Jim
N2ADR

Re: Tips on interfacing I/Q data into quisk?

 

Quisk has an interface that can accept I/Q samples from a custom hardware file written in Python. It is fairly easy to use, and the most work will probably be in accepting the samples from the hardware. Please see the file quisk_hardware_model.py starting at line 100.

This interface is used for the RF Space SDR-IQ radio. This radio returns samples from a USB serial port interface. The file is quisk_hardware_sdriq.py and should be a good starting point.

But PC soundcards have always been a nightmare, and you may have problems. Some cards have a fixed time delay between the I and Q channels. If the delay is one sample, it can be corrected, but some cards have a fraction of a sample delay. And then there is the rate problem as already discussed.

Jim
N2ADR
461 - 480 of 3465