V2.0.2.2 Beta release

[Builty]

V2.0.2.2 beta 1 is available now.
Changes: Refer to https://github.com/Builty/TonexOneController/tree/main?tab=readme-ov-file#release_notes

Please use this chat for bug reports/discussions.

[50pln]

It looks like everything is ok.

[maarthome]

Hi Greg!

Wow FANTASTIC!!! It works great for controling and editing the GP5 AND the Tonex one!!!
Very impressive and for me VERY nice to be able to use the JC3248W535 touch screen to modify parameters and to be able to connect to the m-vave chocolate controller!!!

Also the webpage editting works!!

Thanks again,

Maarten

[Builty]

Thanks guys.

[mikesonos]

Working great for me. Both wired midi and BT midi controllers working. One note, the firmware flashing instructions likely need to be updated for the 5th file (skins.bin file; address: 0x4f2000) Great work!

[Builty]

Awesome. Yes the new skins file looks like its already burnt one user. I'll get that doc updated.

[LariBasillio]

I am using the JC3248W535 board.
The convenience of the beta version is really great.
However, while there are no issues with the official release,
when I install the beta version… it freezes during operation.
At some point, part of the font becomes corrupted, and in most cases it simply stops working.
When I switch back to the official release version, the problem disappears,
so it doesn’t seem to be an issue with the board itself.
I am receiving 5V power via USB through an OTG hub.
With the same setup, when I install the beta version on the 4.3B board, there are no issues at all.

[Builty]

Hi. So version 2.0.1.2 is OK for you, but 2.0.2.2 beta 2 has this issue?
Please confirm. I will run some long term tests on this board.

[LariBasillio]

On the JC3248W535 board, version 2.0.1.2 works normally, but 2.0.2.2 beta2 has the issues described above.
On the 4.3B board, both versions work normally without any problems.

[Builty]

Thanks for confirming. I've been able to reproduce a freeze in the display task. The JC3248W (and Waveshare 3.5B) use a particular display driver chip that has aome strange limitations that make it far more difficult to use than the rest.
I will work on finding the root cause.

[Builty]

I think I have this one fixed now. I just need to leave it running for longer to confirm.

[LariBasillio]

Thanks, Gregs!
If you don’t mind, I’d like to ask one more thing. Would it be possible to change this so that, like turning pages in a book, swiping left brings up the next preset? This feels more natural when swiping left and right.

[Builty]

Regarding the left/right swipe, I was struggling to work out which way was best. I like the book analogy. That is changed now.

With the screen freeze, it was a timing issue that occured much more often during frequent screen updates. I put the tempo flashing indicator back on and with the previous code it would freeze within a few minutes.
With the change made, after 18 hours it will still running fine, so I think its good now.

Please try with this version.
TonexController_V2.0.2.2_beta_3_JC3248W.zip

[LariBasillio]

I’m currently testing beta 3.
The ‘volume’ in the ‘global’ menu does not update its state in real time.
If I switch to another preset and then come back, the value saved on the slider is displayed correctly as a number.
However, if I don’t change presets and instead move a different slider, that’s when the ‘volume’ value gets displayed.

[LariBasillio]

I really like being able to see the exact value as a number to the right of the slider.
However, there are quite a few parameters where it’s not easy to make fine adjustments using the slider. Also, if I accidentally move a slider and want to return it to the default value, I have to tweak it very carefully multiple times.
I was wondering if there might be a more convenient way to handle this. For example, it could be helpful if clicking the text label on the left (the parameter description) would reset the value to its default. Since this is a capture device, the default values seem quite important.
Alternatively, maybe this could apply at least to parameters where the default is frequently used. Of course, this is just my personal opinion.
For instance, if I accidentally adjust the amp gain, it’s not easy to bring it back to a neutral position. The same goes for the tuning reference parameter, since most of the time only one value is used anyway.

[Builty]

I've implemented a new thing where you can click on the value, which launches a dialog box allowing typing of the exact value required.

https://youtu.be/73kp3b9Jxhk

[Builty]

Here's a new beta with this param editor.

TonexController_V2.0.2.2_beta_4_JC3248W.zip