0.C issue with spectrum view

[dead-fets]

Hi Martin, thanks for 0.C

I am seeing the app fail to open until I replace the contents of the Settings folder with those from 0.B

And then if I click on a transmission in the Spectrum View panel the name of the transmission gets duplicated on every other transmission I switch to.

http://www.chriswilson.tv/spectrum.jpg

Deleting all the *.json files in Settings and letting 0.C recreate them doesn't seem to fix this.

Is it a bug or is it my end? Thanks.

[dl1rf]

Hi Chris,

I know and I also observed wrong call sign's in the spectrum.
This is under investigation but till know I was not able to fix it completely.
I will try to get a MiniTiouner for more deeper tests with that tuner.

I am seeing the app fail to open until I replace the contents of the Settings folder with those from 0.B

I will retest and fix this. I think I always prepared settings from 0.B Version while testing.

vy 73 de Martin

[dl1rf]

Hi Chris,

I am seeing the app fail to open until I replace the contents of the Settings folder with those from 0.B

I retested the startup of OT with only the frequency_preset.json provided.
OT do not crash.
Have you command line options provided? And if yes, can you please tell them to me?
Or can you provide me the way how it occurs, please?

vy 73 de Martin

[dead-fets]

My Minitiouner uses dual FTDI modules, not sure if it helps or is even relevant. One oddity I see is going back to the previous release from you I see it shows as 0.C in the header.

No particular start up commands, just simply

C:\OpenTuner_DL1RF_0.C\opentuner.exe

A fresh install of 0.C in its own directory crashes as soon as the .exe file is launched by double clicking it. Only when I have input all the *.json files from the previous release into 0.C does it start and run.

Hope this helps a bit Martin, thanks for your work.

[dl1rf]

Can you provide me the log file from the crashing OT please?
Maybe I can see there something. Most exceptions are logged.
And another question: Which Windows version do you use?
From the picture it look like Windows 11, right?

vy 73 de Martin

[dead-fets]

The log files for the last few times I have run, or tried to run 0.C are at http://www.chriswilson.tv/logs.zip

I am using Windows 10 64 bit Professional

On the odd occasion it does open only one FTDI module is usually seen and there are squiggly red lines at the top of the screen. Next time I see that I'll take a screen shot. The previous version of yours continues to work perfectly.

HTH Martin, good luck.

[dl1rf]

Ok, same problem here with PicoTuner USB in Minitiouner mode.
I will fix it this weekend and create a new 0.C.1 release with issue fixed.

73 de Martin

[dl1rf]

Problem found and seem to be fixed.
Reason for the problem: Due to my fault wrong Minitiouner code made it to the main branch and was not retested by me.
Sorry for that.

@chris: Can you please try the new version 0.C.1 with your MiniTiouner as I only can test with PicoTuner USB.

Here the link to the test package: OpenTuner_DL1RF_0.C.1.zip

73 de Martin

[dead-fets]

O.C.! up and running with the issue seemingly fixed, many thanks Martin.

My only comment is that it would not launch at all after pressing the "Connect" button until I had put my settings into the Settings folder of 0.C.1 from the Settings folder of the first release version. I put ALL the *.json files in at once, so I am unable to say if only one was causing it not to connect. I can test further if you wish?

Thanks again and enjoy the rest oft he weekend.

[dead-fets]

I spoke too soon, just now O.C.1 failed to open, on the second attempt it opened without a problem. 2 logs, the earliest where it failed to open, the later one where it opened OK. HTH.

http://www.chriswilson.tv/logs2.zip

[dl1rf]

Hi Chris,

I think I found the problem.
The several asynchronous tasks causes the problem.
I have to restructure the program flow.

73 de Martin