Get well soon, Richie!ramdor wrote:Some more progress. I have been busy + rather ill recently so not much spare time.
https://youtu.be/rB5HRvNXWEI
The code in the video is not committed to git yet, correct?
Get well soon, Richie!ramdor wrote:Some more progress. I have been busy + rather ill recently so not much spare time.
https://youtu.be/rB5HRvNXWEI
no, not yet, perhaps in a few daysw-u-2-o wrote:Get well soon, Richie!ramdor wrote:Some more progress. I have been busy + rather ill recently so not much spare time.
https://youtu.be/rB5HRvNXWEI
The code in the video is not committed to git yet, correct?
we have ditched the various skins based on output power, and now the scale is rendered in code. You can specify power limit for the cross/ananmm. Tomorrow the hbar scaling will be reworked in a similar way.DH1KLM wrote:Amazing Job Richie and Ernst. I am very thrilled. The wait was really worth it.
I compiled the latest Multimeterbranch and also MeterSkinInstaller with all images. I found out that the Meters are ANAN model depended. But how can I switch to the ananMM-200 skin without having a ANAN8000? Is this possible?
It will be all configurable by user.K4IBC wrote:Watched your video short demonstrating meter display. I would like to suggest to change the numbers about the bar graph numbers on the right side to something other than red. This way they will contrast with the numbers directly below them Yellow or Orange like the left side unless they are above the limit then turning Red is good.
https://youtube.com/shorts/z_BORrwSCdE?feature=share
no idea, probably best start a new thread somewhere asking about it, as not related to the metersvu2mb wrote: I have changed the radio to 100D and TX Meter is working. So there is something wrong with the hardware.
Any help will be appreciated regarding this issue - what might be the issue?
Hi Scott,w-u-2-o wrote:I built the latest that was posted yesterday. At least I think I did, I'm not fully up to speed on pulling down Git updates, etc.
Paul,w9ac wrote:Hi Scott,w-u-2-o wrote:I built the latest that was posted yesterday. At least I think I did, I'm not fully up to speed on pulling down Git updates, etc.
How difficult was the bar graph meter update? While we await a full installer version, do you have any tips to share or care to offer step-by-step instructions for the rest of us? Many thanks.
Paul, W9AC
I'm in the same category. Not sure I have the motivation at the moment to try so it's probably best to wait.w-u-2-o wrote:If you've done any programming and have a rudimentary grasp of these sort of tools but not these exact tools (I'd put myself in this category) I'd say it was around a 4 or 5 on the difficulty scale, mostly because you know enough to know what you want and get impatient learning the tools to get there.
Hey Scott,w-u-2-o wrote: Wish list (in no particular order):
- User adjustable low/high threshold (for instance to set a lower SWR threshold, but might as well make it generic to any meter).
- Add low/mid/high threshold (for instance, mic level green below -5, yellow -5 to 0, red > 0, and user adjustable as per the previous wish)
- Allow horizontal/vertical stretch (override aspect ratio).
- Option to fade entire container to transparent on RX or TX (use case--place TX meter container over the spectral display but it only appears during TX, alternate use case--separate RX and TX containers inhabit the same screen real estate but only one is visible at a time, etc.).
- Not meter related, but dark theme for the Thetis title bar would be super-nice.
Things that might be bugs or might just be work-in-progress:
- Allow clicking the PBSNR meter to get S units or decibels (like the Signal and Signal Average meters).
- Peak hold/history doesn't seem to work (yet) on TX related meters.
Point of confusion:
- Not sure exactly how all the windoid controls work. I did figure out that tacked means "always on top"
Hi Richie,ramdor wrote: Also, the peak hold stuff in your video on tx is getting disrupted by vox unkeying/keying between words. There is an ignore time when tx<>rx/bandchange happens before peak/history is gathered, and at the moment this is around 2 seconds. The reason being is that WDSP needs to settle and would otherwise show odd history where the whole meter bar may get filled with min/max. This delay/ignore time could probably be made configurable for the end user.
...
73 for now, need to get back to the code