Thetis v2.8.11 - UPDATES and current issues

[Joe]

Richie,
I did have a win 11 update today, had to be the audio buffer sampling Issue, good ole updates, ha! Never know what comes up? Thanks so much for all of your hard work with the Thetis code!

73’s
Joe
WD5Y

[vk6cpu]

Seeing unexpected interactions between VAC1 & VAC2 when adjusting RX /TX gain on VAC1.

After selecting RX2 and IF VAC2 RX TX gain are displayed on "front" panel adjusting either the RX or TX gain on the VAC1 tab changes the VAC2 RX /TX gain in lock step.

However, On selecting the VAC2 tab - I can adjust the RX gain without affecting VAC1, however, no change is mirrored on the front panel. Audio levels do change on JTDX so the RX gain change is happening,

Not sure if I have missed some button that links the two VACs or its unexpected interaction?

Its non critical and easily worked around - once you realise its happening.

Thanks

[ramdor]

thanks Nigel, inadvertently broken in a recent release. Fixed along with the apostrophe issue.

Updated to rc5b.
viewtopic.php?f=9&t=3817&p=18763#p18763

R.

[ramdor]

The drop-down button UI is quite innovative and acts to address ever shrinking UI real-estate. However, the mixing of TX audio related controls with spectral display related controls is quite jarring and very counterintuitive. It flies in the face of UI design principles.

Blobs, Info, Spot and Peak correctly belong on spectral display related (located) buttons. CFC, CFCeq, and Lev do not. Tdrive is yet another outlier.

While it is also counter to UI design principles to obfuscate controls behind right clicks or, worse, modifier keys, please consider that it would be better to re-arrange these buttons as follows:

1. Blob, Info, Spot, Peak on a button or buttons located on the status line of the spectral display.

2. CFC, CFCeq (more properly "PostEQ"), Lev could more properly and logically become part of the existing DEXP button.

3. Tdrive could become part of the existing TUN button.

Even better, would be to simply show these buttons outright. The smallest allowable size of a Thetis window is 1018x609 pixels. This makes the smallest screen resolution allowable to be XGA, or 1024x768. Perhaps it is time to require a minimum screen resolution of WXGA, or 1280x720. This would provide ample space for a row of 4 buttons alongside MIC-to-DEXP, as well as 4 separate buttons on the spectral display status line.

I'm sure there must be some person that feels compelled to run on a 10 year old laptop with an XGA display, but even micro-laptops come with WXGA displays these days. It might be time for those folks to upgrade!

Hi Scott,

Yep, there are options that shouldn't be in there if you think of those buttons as just being related to the display. I know that, I knew that before anyone when I was coding it during ~10hrs that it took to re-engineer all the existing text box nightmare implementation of the info bar. However if you think of them as two general quick access buttons then they work as intended and it doesn't matter what is in there. Perhaps if you don't like what is in there, then just forget about them. Set them to what you want or just ignore them. I would imagine that over 75% of ops couldn't care less about RBW and the other hundred of options that are available, they just ignore them.

That said, we could of course add everything to the front end and add to the button splatter fest. If you want 'to fly in the face of UI design principles' then just look at the display already which can not be shrunk enough to fit an andromeda screen without using the collapse view. Groups of those control are adjusted by a delta every window resize which is why it is the slowest resizing window known to man.

21k9 is fast approaching completion with a few items left to tidy, I do not see me changing any of that info bar or distributing more buttons around the front end before then, because it does nothing for me, or gain me anything from the radio/experience right now.

Richie.

[PD3LK]

Just a big word of THANK to Richie for the latests updates and Ernst for updating his wonderful Yaesu skins that also corrected the white ZTB button. Regards,

[I2NOY]

Hi,

pls place these png's into the skin directory (Thetis must be closed):



73 Ernst

Hi Ernst, now it is perfect!
Many thanks and 73.

[w2ner]

Richie

I have said this in the past, THANK YOU!! But, really, there are no words to put into a sentence that would show my appreciation for all the hard work, time and dedication you put into making this UI the best it can be. My hat is off to you! If I lived anyplace near you, I would not just buy you a beer, we would shut the bar down.

Thanks again Richie,

[w-u-2-o]

That said, we could of course add everything to the front end and add to the button splatter fest. If you want 'to fly in the face of UI design principles' then just look at the display already which can not be shrunk enough to fit an andromeda screen without using the collapse view. Groups of those control are adjusted by a delta every window resize which is why it is the slowest resizing window known to man.

It is unfortunate that the Andromeda design is utilizing a ridiculously low spec display.

I do hope you noted that I did offer an alternative to the "splatter fest" in my suggestions, whereby other buttons could become right clickable rather than the current selection, and knowing how much you dislike the current UI from that perspective, and being aware that screen resolution might be an issue (although I had not thought about Andromeda being the source of it).

Something for the wish list, then.

Thanks,

Scott

[N4QNT]

Hi Richie, just noticed after updating to RC5 when the AGC Gain is auto-enabled it's not making the auto adjustment like the previous versions did.. The G line would rise and fall accordingly..

Thank you,
Art N4QNT

[ramdor]

Hi Richie, just noticed after updating to RC5 when the AGC Gain is auto-enabled it's not making the auto adjustment like the previous versions did.. The G line would rise and fall accordingly..

Thank you,
Art N4QNT

There are no changes in rc5 related to that, however there were changes a couple of release ago that included fft width and a bunch of other stuff with the auto agc, and It has been discussed in the thread. You will probably need to change your offsets accordingly, assuming you have it turned on.

R.

[ramdor]

For those that are able, please could you check the ErrorLog.txt file for the following [0x8899000C] and let me know how many occurrences there are in the log. I do not need the log, just the number of occurrences if you have some.

Depending on the frequency, I may have to put effort into recovering from it.

Thanks, Richie.

[NJ2US]

That error occurred twice in my error log, two times on the same day, March 25.
THANKS for all you do for the Thetis community Richie.

73,
Jeff NJ2US

For those that are able, please could you check the ErrorLog.txt file for the following [0x8899000C] and let me know how many occurrences there are in the log. I do not need the log, just the number of occurrences if you have some.

Depending on the frequency, I may have to put effort into recovering from it.

Thanks, Richie.

[DO2ZA Erwin]

Hi Ritchie,

in my Errorlog this comes up only in July 2021, did not know wich Version that was. Nothing in the 2.8.11K9 up to RC4.

Thanks agian for yor hard work!

73 Erwin

[DL8LAQ]

No 0x8899000C in the log.

[W2QAQ]

Good afternoon Richie,

Does RC5 run on win7 ? A friend logged in to my computer last night and uploaded via teamviewer, backed up last version 2.8.11 and installed it. Upon opening got an error message. Shut program and rechecked everything then started again with same result. Restored to previous version.

Thanks in advance,
Harry W2QAQ

[dl5tt]

For those that are able, please could you check the ErrorLog.txt file for the following [0x8899000C] and let me know how many occurrences there are in the log. I do not need the log, just the number of occurrences if you have some.

Depending on the frequency, I may have to put effort into recovering from it.

Thanks, Richie.

Hi Richie,

1st of all: Thanks for your time and great work!
2nd: I don't have this error in my log.

73 de Joe

PS: The ADC-overload-message (for example from PS-feature) is YELLOW in LIME GREEN status bar, but I think this issue is allready reported.

[ramdor]

PS: The ADC-overload-message (for example from PS-feature) is YELLOW in LIME GREEN status bar, but I think this issue is allready reported.

warning messages have their own colours, yellow, then red, depending. They override what you select.

R.

[oe3ide]

For those that are able, please could you check the ErrorLog.txt file for the following [0x8899000C] and let me know how many occurrences there are in the log. I do not need the log, just the number of occurrences if you have some.

Depending on the frequency, I may have to put effort into recovering from it.

Thanks, Richie.

Nothing here, since May 2021.

73 Ernst

[W9BHI]

Richie,
RC5 running fine here, NO problems whatsoever.
Thanks again for all you do for us here on the forum.
Looking foreword to any new updates!
Don W9BHI

[W9EZ]

3 instances of 0x8899000C in my log. March and July of 2021 and Feb 14 2022
Todd

[BPerk]

I have zero 0x8899000C errors in my log currently running RC5.

Thanks,
Bob

[rbduck]

I have 12 occurrences of 0x8899000C between October of 2020 through November of 2021. Nothing else since then.

Edit:
Richie: Great work on all updates. I've had no issues and if there has been any glitches it was my fault. . I run it in the latest
version of Windows 11 from the Dev channel. So, with all the Windows changes I would hesitate to report any problems here. I know you have not done a lot on the audio chain, but, for me. the audio has been working as flawlessly as ever.


Anan 7000DLE MK II, Thetis v2.8.11 21k9rc5b

[W4GM]

RC5 running here with zero issues!
Thanks for all the hard work and things you do on the forum for us!

I have 2 instances of 0x8899000C in my error log. July 17, 2020 and August 1 of 2020.

73,
Mike

[W1PL]

Thank you!

Works very good.

73!
Mike W1PL

[W1AEX]

Hi Richie,

Version 21K9(rc5b) is running fine here and I am enjoying the implementation of the new features very much. No sign of error 0x8899000C anywhere in the log.

Thanks for all your work!

73, Rob W1AEX

[K1LSB]

Stupid question here, where would I find the file ErrorLog.txt? I can't find a file of that name anywhere.

Thanks,
Mark

[ramdor]

Stupid question here, where would I find the file ErrorLog.txt? I can't find a file of that name anywhere.

Thanks,
Mark

Either

C:\Users\<you>\AppData\Roaming\OpenHPSDR\Thetis-x64
or
C:\Users\<you>\AppData\Roaming\OpenHPSDR\Thetis

depending if you run 64bit or 32bit versions

Richie.

[G3ZQH]

[highlight=]For those that are able, please could you check the ErrorLog.txt file for the following [0x8899000C] and let me know how many occurrences there are in the log. I do not need the log, just the number of occurrences if you have some.[/highlight]

21k9/rc5 running well here. No instances of 0x8899000C error since 10/2020.

73 Dave G3ZQH

[mike b]

scott lol, yes certainly before he was a boy. Just a bit of info, during the speed up process of 21k9d the vac/txprofile load changed slightly.

Prior to 21k9d if a new TX profile was selected that had the same VAC enable state as the one already in use, then the enabled state would be applied anyway. Consequently when each buffer change/etc/etc was loaded and applied, and due to vac being potentially enabled, it could take quite a long time to make the change, causing all sorts of nice debug log as audio devices and buffers changed whilst in use.

Since 21k9d vac is explicitly turned off prior to reading in all the TX profile vac settings, and then turned back on if that new profile requires it.

So there is a subtle difference before and after 21k9d, however it could be improved by checking if anything is different in the about to be selected TX profile vac settings. I will probably add that in at some point, so that an unnecessary turn off can be skipped.

Are you going to change the vac back so it don't turn off and back on or is this the new normal? is it possible to make it select-able ?
also i can no longer exit thetis by clicking the x in the top right corner it just hangs on please wait thetis is closing down ,the only way to exit it is to use the task manager and force it closed, thanks mike

[W7GES]

Hi Richie,

Thanks for all the changes... RC5b running fine here.

I see 0x8899000C in my error log on Sep 21, 2021

Love that your screenshot name referenced the wafer-thin mint...

I miss that kind of comedy, not sure Monty Python would be understood today.

73,

George / W7GES

The drop-down button UI is quite innovative and acts to address ever shrinking UI real-estate. However, the mixing of TX audio related controls with spectral display related controls is quite jarring and very counterintuitive. It flies in the face of UI design principles.

Blobs, Info, Spot and Peak correctly belong on spectral display related (located) buttons. CFC, CFCeq, and Lev do not. Tdrive is yet another outlier.

While it is also counter to UI design principles to obfuscate controls behind right clicks or, worse, modifier keys, please consider that it would be better to re-arrange these buttons as follows:

1. Blob, Info, Spot, Peak on a button or buttons located on the status line of the spectral display.

2. CFC, CFCeq (more properly "PostEQ"), Lev could more properly and logically become part of the existing DEXP button.

3. Tdrive could become part of the existing TUN button.

Even better, would be to simply show these buttons outright. The smallest allowable size of a Thetis window is 1018x609 pixels. This makes the smallest screen resolution allowable to be XGA, or 1024x768. Perhaps it is time to require a minimum screen resolution of WXGA, or 1280x720. This would provide ample space for a row of 4 buttons alongside MIC-to-DEXP, as well as 4 separate buttons on the spectral display status line.

I'm sure there must be some person that feels compelled to run on a 10 year old laptop with an XGA display, but even micro-laptops come with WXGA displays these days. It might be time for those folks to upgrade!

Hi Scott,

Yep, there are options that shouldn't be in there if you think of those buttons as just being related to the display. I know that, I knew that before anyone when I was coding it during ~10hrs that it took to re-engineer all the existing text box nightmare implementation of the info bar. However if you think of them as two general quick access buttons then they work as intended and it doesn't matter what is in there. Perhaps if you don't like what is in there, then just forget about them. Set them to what you want or just ignore them. I would imagine that over 75% of ops couldn't care less about RBW and the other hundred of options that are available, they just ignore them.

That said, we could of course add everything to the front end and add to the button splatter fest. If you want 'to fly in the face of UI design principles' then just look at the display already which can not be shrunk enough to fit an andromeda screen without using the collapse view. Groups of those control are adjusted by a delta every window resize which is why it is the slowest resizing window known to man.

21k9 is fast approaching completion with a few items left to tidy, I do not see me changing any of that info bar or distributing more buttons around the front end before then, because it does nothing for me, or gain me anything from the radio/experience right now.

Richie.