Hx stomp 3.80 keeps doing transferring data...

[gencinoza]

Hi,

Im very happy how are appearing this alternative options for HX edit specially for people like me Linux main platform.

Using HX edit in a virtual machine limits or makes more complicated to keep a workflow

Since several versions of tonepush when I start to try, Ive never succeed to pass the stage, Hx stomp 3.80 keeps doing transferring data..., display in the unit meanwhile the application opens, gather the patch display correctly in it but then it becomes not responsive and disconnects. The stomp remains transferring, and only reset to start the again at the initial point.

Let me know if you have any suggestion what could be happening and if I can get useful information for you.

[crmne]

Thanks for reporting this. I am investigating it.

I have just tested the current TonePush 0.5.5 against an HX Stomp on firmware 3.80. I ran the same sequence the GUI runs at startup in one session: connect, read and display the preset, fetch the preset list, read all five footswitches, run several notification/keepalive polls, and disconnect cleanly. I also ran six open/close cycles. All completed here, so this is not a deterministic incompatibility with Stomp 3.80; the exact request or USB condition that fails on your machine matters.

After a fresh 9V power cycle, with HX Edit and the VM completely shut down, could you please provide:

1. The exact message in the TonePush status bar or Activity panel when it disconnects. A screenshot is fine if the window stops responding.
2. The output of:

tonepush --version
tonepush info
tonepush presets
lsusb -t
uname -a

Please run tonepush info and tonepush presets as separate invocations, and stop at the first command that leaves the pedal on Transferring Data. The distinction is useful: info exercises the loaded-preset path, while presets exercises the larger control-channel transfer that the GUI starts immediately after showing the patch.

Also tell me how TonePush was installed (AUR tonepush, tonepush-git, release archive, or source), whether the pedal is on a hub/dock or a direct USB port, and whether USB passthrough is configured for the HX Edit VM even when the VM is stopped. No preset writes or saves are needed for any of these checks.

[crmne]

An update: TonePush 0.5.6 is now available, and it changes the exact transport paths most likely to produce this symptom. In particular, it now decodes multiple Line 6 frames coalesced into one USB transfer, stops queued polling after a session loss, and tolerates firmware-dependent absent settings during the automatic backup.

While auditing startup for the next release I also found that the GUI wrapped the transport’s own narrow opening-handshake retry in a second blanket retry. That is now removed from the release candidate, so one failed open can no longer fan out into up to four fresh sessions.

Could you please try 0.5.6 after a fresh 9V power cycle, with HX Edit and the VM fully shut down? If it still sticks on Transferring Data, the command outputs requested above will tell us whether it fails in the preset-name transfer or the later backup. I’m leaving this open until we have that hardware result rather than guessing that it is fixed.