V2.0.0.2 Beta release

[Builty]

V2.0.0.2 beta 1 is released now.

Changes:
https://github.com/Builty/TonexOneController/tree/main?tab=readme-ov-file#release_notes

Please use this discussion to report any bugs.

[50pln]

Hey. I just got some rest after Forest Fest 2025 (https://fb.me/e/7FHJtuDgt). I was about to write (I even wrote it, but deleted it) that something was wrong, and I was an idiot who didn't notice the bypass switch. It works perfectly, just as I wanted it to, and that's why I was bothering you about it. Thanks a lot!!! You're the best!

[Builty]

Awesome, glad you got it sorted.

[50pln]

I don't know if anyone has already raised this topic, but is it possible, for example, to set the tap tempo by tapping the value (4.3B) on the display, just like it is done via the website? :)

[Builty]

It should be possible. I'll check that out

[50pln]

I don't know if anyone else has experienced this, but in 4.3B, when I connect via Wi-Fi, the screen goes black and I hear a faint beeping sound. The device freezes. Maybe it's just me. I'm following :)

[Builty]

I think 500 mA is probably not enough. I use 9v 1 amp on my 4.3B.

WiFi doesn't work for you? If you can connect to the access point but "tonex.local" doesn't work, try typing in "192.168.4.1" into the web browser address and see if that works. I suspect the mDNS part is not quite perfect, and using the IP adress directly bypasses it.

[Sundeeprk93]

Also, i also change the wifi settings on the Web Config to Access Point with 50% power usage from Access Point Timed. As i realised in Access Point Timed mode, the wifi drops out after a minute or two, which is not very suitable for me, using a zero board and doing all the tweaks on the Web Config.

[50pln]

I think 500 mA is probably not enough. I use 9v 1 amp on my 4.3B.

WiFi doesn't work for you? If you can connect to the access point but "tonex.local" doesn't work, try typing in "192.168.4.1" into the web browser address and see if that works. I suspect the mDNS part is not quite perfect, and using the IP adress directly bypasses it.

I have two MDNS settings: 4.3B - tonex.local, Zero - tonex0.local, and both work fine. I'm guessing the problem in my case is the power supply (Harley Benton PowerPlant ISO-1 Pro) being too low. Despite this, the problem hasn't recurred.

[50pln]

I am reporting that everything is still working fine for me.

[50pln]

I'm reporting that everything is still OK :)

[andy-k-dot]

Hi Greg,
not sure if this is a bug, as such, I am still on 1.10.2 final, and will be updating to v2 soon.
Just did a new build with a Waveshare 1.69 v2 board, using 4 switches, and powered by USB powerbank.
All seems to be working correctly, however, in the web UI, I notice that in global settings / input gain, when I adjust setting via the numerical input and save, the setting reverts when changing a patch.
It does not seem to revert if the setting is changed with the slider.
I will investigate further, and will be updating to V2 on a few devices soon.
I have recently updated the Tonex 1 to latest firmware on my Satriani model, and this is the one I am having the issue with.
Otherwise, I seem to be having no issues with 5V powerbank running this setup.
Also, is there any more information available on using this rig with the big pedal, I am assuming the power supply will be different? ie, big pedal will not be drawing power from the midi board, just haven't seen anybody using it yet.
Cheers
andy k

[Builty]

Hi Andy. Espressif did so some USB fixes recently, so I've upgraded to ESP IDF 5.5.1 to incorporate them.
I've build V2.0.0.2 beta 2. Its a long shot, but could you please check if anything has changed with this one?
Thanks.

[andy-k-dot]

It is good news initially,
Upgraded my latest 1.69 build to V2.02.2 beta, have it connected to my Satch T1, on latest firmware, and connected up to my least reliable ( weakest ) powerbank, when powered up it syncs and connects immediately.
Am leaving it powered up to see if any lock ups occur, am not currently passing sound, so that will be done later, but it seems something has worked at the moment.
Will keep you posted.
cheers.

[andy-k-dot]

Short lived,
more weird behaviour, after about 15 mins, with everything still powered up I decided to plug in a power amp and a guitar, and with sound being produced I connected wifi, after changing a few settings-ie 4 switches, screen rotate, wifi settings and rebooting a couple of times, I realised that the controller was showing the list of presets from my OG T1, which I had previously tested.
I hadn't immediately spotted this-as I was using a Satch preset on my OG pedal.
At this point I realised that the controller was not communicating with the Satch anymore.
Initially, I put this down to my power supply-now I am producing sound, so I tried to make the connections with a mains adaptor powering it all up.
Now the Satch is again refusing to connect.
I have now got my OG T1 running, producing sound, and connected to wifi, just to see if connection persists with V2.02.2 beta, not seeing any other issues yet.
Will try Satch again in a couple of hours, maybe as stand alone pedal first, to see if anything unusual happens, before trying controller.
Keep you posted.

[andy-k-dot]

More weirdness,
after around 20 mins of using OG T1, decided to try and connect Satch, powered down ( powerbank ) and made connections, amp, guitar, powered up 1.69 and then connected Satch, which syncs and works with switches on controller, HOWEVER, patches on wifi all have names from previous OG T1.
Weirdness continues, I am sure I have patches A and B on Satch as re-arranged patches from original factory settings, and I am sure I put Patch C as Crowd Chant--- so would be patch 3 in Tonex editor.
I also have this patch on OG T1 as patch 20, but now I am playing through it, it is listed as Patch 16 ( which I think is factory setting )
At this moment, I can switch through patches with 1.69 footswitches, and the patch names change on the controller, but on the wifi page they remain named as on OG T1.
When ( if ) it locks up again, I will re check the patches in Tonex editor, but I am sure I swapped them earlier today.

OK, just refreshed wifi web page, and presets are correctly named- now refreshed seems to be working correctly, about 30 mins uptime.

[andy-k-dot]

Further update,
everything seemed to be working fine for about another half an hour-ie appx 1 hour uptime.
Switching via footswitches and app seemed ok, refreshing seemed ok, attempted power cycle after appx 1 hour, now refuses to sync, either pre or post connection.
Checked OG T1, which connects and syncs immediately ( ie, power supply is fine )
Checked Satch on PC with Tonex editor-which initially did not connect, but did on second attempt.
Patches were in factory positions, so re-ordered them as desired, but could not see a way to save settings apart from re-ordering them in list, so I physically changed the order, will try again tomorrow.

[Builty]

Hi Andy. The web showing old presets until refresh will be a bug on my side. Its a lot of data to transfer so I do it on first load of web page.

"Checked Satch on PC with Tonex editor-which initially did not connect, but did on second attempt." this is interesting. I wonder if the root cause here is that the Satch USB port has an intermittent issue?
If you connect to PC, and then gently wiggle the USB socket around at the Tonex end, does it experience any dropouts?

[andy-k-dot]

Hi again,
I'll do some more testing today, and I had a similar thought re the issue may be localised to my Satch hardware.
In the instance you mention, it was resolved by changing ports at the PC end of the connection, not the T1, but I now think it may be something heat related in the USB circuit of the pedal, as it held a connection for around an hour, before I powered down, then up again.
The first time it occurred ( couple of weeks ago ) was probably after using the pedal for a similar amount of time, but more recently, ie since V2.02.2, it has allowed connection initially, but then stopped connection, after a very short time.
I am going to try repeating the connection process today, with a view to allowing time for it to cool down before repeating , to see if there is a pattern here. I have also already tried the wiggle test, with no drop out, but will experiment.
I have re-ordered the patch list in Tonex editor, to ensure patches are being read in the same order as I expect them, as that was confusing me a bit.
I am also a bit wary of my power supply (USB powerbank ) as I think it could be something related to a stable voltage, ie if the V or A fall due to the drain on the battery, the connection becomes unstable?
Generally, with my OG T1, I am having no issues with the controller hardware, software or wifi.
Can I make another suggestion, which I did mention in the past - in that, when the T1 appears on the wifi app, it does so on some sort of neutral 'home page', that does not allow settings to be changed.
The reason is, that it would be good to see which patch / fx / settings are enabled, but at the same time it is not possible to change a setting?
At the moment, I think it loads on the 'amp' tab, and it is very easy to touch a setting and alter it, with no way of reverting it, it will either save to current preset, or save over another slot, which could be a problem.
I know it is something that I mentioned in the earlier days, and you have limited resources, but a neutral page, as a 'home page' would eliminate this issue, I tend to always set my web app page to the midi page, which has the fewest options available, as this means that an accidental touch can be avoided- maybe the BT and wifi tabs could be merged to free up a tab to be set to 'home', showing only current patch settings?
I realise, my Satch T1 might have some hardware fault, and these faults may not be software related, but otherwise it seems to working fine with Tonex software, so maybe I will just have to live with the issue, as long as it works as a unit.
cheers.

[andy-k-dot]

Small follow up,
powered up 1.69, connected wifi, connected Satch T1, syncs and works fine.
I left it running in this state for 30 mins, no sound passing, T1 felt slightly warm.
Powered off, then refuses to connect-either wired up or disconnected.
Waited an hour, T1 felt cool.
Repeated power up sequence, and T1 syncs and works as expected.
powered down and up a few times, and it continues to sync-so maybe problem is heat related.
However, in the last few days, prior to the V2.02.2 update, the Satch would simply not connect, so heat was not the issue then.
I now have Satch T1 fully connected, and can switch on battery to boot up, and it is connecting and syncing, so the problem seems to have gone away-until I power down after around half an hour, so in a way it is fixed.
I will try this again later, while actually playing guitar through it - to see if this exaggerates the heat that is being generated ( I suspect it will, thus reducing time before it locks up )
I'll keep you posted.

[Builty]

Regarding the web page suggestion, I had it planned to create a home screen that looks like the 4.3 UI, but adding images to the web page makes the page get huge.
I've had a go at doing something different. Added a home tab at the top, and added an animating "oscilloscope" display using javascript (so the client does the animaton and the controller has no extra work.)

What do you think about this?

osc.mp4

[Builty]

Hi Andy. I set my One (also latest firmware) to A/B mode. As soon I set a new preset, it jumps to Stomp mode (I am commanding stomp mode in code.)
As the mode changed, it was behaving normally.

When you select a preset, does yours change to Stomp mode? (mode led is green for A/B and Amber for Stomp.)

[andy-k-dot]

Hi again,
I have tested both Satch ( latest FW ) and OG T1 on older FW, Manually put T1 into A/B mode, then connect up and power up.
It behaves as Is have described- I'm calling it 'flip flop mode', as it could be useful in some instances, I can use 4 switches to step up and around a bank for example, but the T1 switch seems to recall the preset from a previous bank.
I tried manually changing T1 to stomp mode and reconnect, and then it behaves as normal, and T1 switch operates as a bypass, which could be awkward if accidentally switched as it greatly mutes the signal.
I can then repeat the process, by disconnecting everything and manually going back into A/B mode, and then they both behave in 'flip flop' mode.
The weird thing is, I always understood that the controller needed the T1 to be in 'stomp' for the software to work, and an earlier version forced the switch on boot.
It must be hard to keep up, if IK are continually changing things with FW updates.
'Flip flop' mode could be useful, if there was a way to keep track of which patches are in memory, at the moment a bank change with the 4 switch method means either A or B on the T1 gets swapped, and when that switch is used, it makes the patches seem to go out of sequence.
I'll try and do a vid.

[andy-k-dot]

Video evidence--[](https://www.youtube.com/shorts/IbPnIk482gE

[Builty]

Hi Andy. Thanks for the info and vid, it does help. So your older T1 also has this same issue where it will not change to Stomp mode?
I can understand that in A/B mode things will be weird, as normally its forced to stomp and I haven't tried any testing of A/B mode.

What I suspect is going on here is that setting on the Tonex is causing the Stomp mode setting to be in a different location in memory.
The communications protocol inserts the value 0x80 as an escape byte to some values.

Would it be possible for you to repeat the Wireshark log of it syncing with the PC one more time? This should give me the exact values that the pedal is reporting in its status packet, and hopefully let me see if I'm right about the extra escape character.

And yes, it sure is hard to keep up with IK changes.

[Builty]

Also, if you check the web config, is the value shown for input trim correct? 0.1 in the last log.

[madejm]

Hi! Since the CI is working now (thanks to @nicola-lunghi), could we have release binaries attached as assets in releases, instead of keeping them commited in the repository directly?

[Builty]

I had similar thoughts. I'd love to be able to create the release zip files. I'm just not familiar with the CI system at the moment to do anything else with it.

[vurguuz]

Hi! Unfortunately on the latest V2.0.0.2 beta 2 I lost the ability to change presets both via midi and via the web interface.

• ToneX One FW ver. 1.3.15
• Waveshare Zero board that was working fine with previous non-beta releases

My "Presets" screen in the web config looks like this, showing the first preset multiple times:

Changing the presets via the dropdown at the top doesn't actually change the presets. Clicking on the presets does nothing. Clicking on "undefined" at the bottom does nothing.

The settings for the footswitches in the config (different settings don't change the behavior):

• Internal footswitches: preset switch layout: disabled
• Internal footswitches: FX1 .. FX4: disabled
• External footswitches: preset switch layout: disabled
• External footswitches: FX1 .. FX8: disabled

Any ideas on what could be wrong here?

[Builty]

Hi. I haven't seen this kind of thing before, however the method of storing the configuration had to change in V2.0.0.2 (due to the big Tonex having 150 presets) and that screen shot shows the configuration is messed up, and that can effect the preset switching.

Can you please try using the programming tool, but do an Erase. And then when finished, program again as normal.
This will reset the config to default, which I suspect will get it back to normal again.

[vurguuz]

The Erase fixed things. Thanks, your work on this is amazing.