So now it's back talking to the app and all presets are available, but obviously all my saves are erased and the app keeps losing touch with the module, in that I can select something (ie CV1 to pitch) but I scroll down and the assignment is lost.
TLDR: something is wrong with one of my tbds. Really really frustratingly so as I'm wasting the majority of my music time troubleshooting.
So last not of troubleshooting - basically started over, saved three presets, module crashed, one of the three presets doesn't recall any of my changes.
That's two different methods of programming (computer and app), reflashed, lots of time and same results - presets lost/corrupted. I think I probably need to give up now and accept there is a hardware issue at play here.
Post by maydonpoliris on Mar 18, 2023 22:07:39 GMT
not good! only thing I've notice with mine is sometimes the preset isn't there on startup and I need to select it again, but that's really no problem obviously. Haven't noticed corrupting etc or anything on this scale. My presets have been non complicated thus far though.
As far as I can tell I seem to only have these issues on one of the two I have, so assume it's an issue in that. I'm out of ideas I can try really - I might load some very simple presets just so it does something sometimes and then see what Robert suggests.
It's a shame currently as when it works it's great - I just can't at all rely on it.
To be clear, my exact issue is that upon boot up it doesn't find any saved presets, you press a button and it reboots.
I can find the presets when it connects to my interface, however try and load from the module and there's no text and it crashes. It also doesn't save the edits on multiple patches, meaning when it reloads I get just a tone.
So I reflashed the new one and have been programming only with the official app (ie avoiding the android one)... so far it's behaving, though I need to figure how to get samples back into it.
What's interesting is my other one was also losing settings on certain presets. These were also which lost in the app (saved favourites disappeared). This has been stable throughout until now.
I've now reflashed that one too, installed a load of exports into the slots and have put a couple of additt subotnik based patches in, since that seems to be one of the main causes of lockups/bugs. So far stable... I hope.
What will be interesting is to see if, with no further computer messing, it stays that way.
I have a couple of theories as to what is bugging it out - I don't think it likes being disconnected from the host computer, and also that it doesn't like being connected to more than one hist device. Guessing, but once presets get corrupted it needs a reflash as further problems always arise. Lose one patch setting and you can guarantee another one will soon turn up.
We'll see if using one host device and limited editting keep it stable. I really hope it does since I'm at risk of taking a hammer to the lit if not. (I half joke).
Wrote a big long post and lost it - basically my replacement module has lost presets again on the braids patch I was using, and also on all three braids patches stored in the machine.
I've now had this on three units, also with plaits, subotnik and rains presets - They are pretty much the only presets I've used since I was trying to use each TBD as a waveform generator, so I'm pretty confident, as in I'm sure, that the module itself does not run reliably on the current code.
Once one preset is broken/lost all versions of presets running with the same plugin are also lost. And once a preset is broken the saved patch on the computer is also lost.
I'm 100% convinced this is a module/code issue - there's an issue with however presents are stored that when reloading saves are lost on all versions of whichever preset is on there (however many times it's stored too).
So I figure I'm 18 months in with the TBD, with classic six months wait for an unusable replacement, and no closer to having a working pair of modules. I'm now going to put this system away and consider whether it's something that I'm better off cutting my losses with - I'm afraid my confidence in the digital modules I've wanted to go with is at an all time low, and I'm really not sure I want to spend four months or whatever find out whether the sample player actually works.
It's all very disappointing on a number of levels.
Posting my notes here in case others have the same issues:
The TBD will lose presets - if the plugin is still in the slot but the saves are gone the way to get it going again is to import a saved patch.
Export any patches you wish to save, since the preset saving module/app end isn't reliable. It's worth renaming the file each time.
To import = import, recall, snap, done.
If settings in a preset are lost, any other presets with the same plugin will also be lost - import to all saved with that plugin. It's worth naming the save after the plugin used to help here.
Saved presets will also be lost on the computer, presumably because they are stored in the memory of the module.
If the preset is lost and plugin is showing as void or nothing can be seen in the menu you will need to reflash firmware, since eventually it will get to a point where it reboots/locks.
When you reflash samples and wavetables are lost. I haven't worked out getting the originals back in yet.
Other things I need to test further:
It doesn't seem to like switching between using the android app and the computer, though I need to test this further since it might just be related to the (void/blank) issue above, in that it was already broken/corrupt beyond the point of saving without a reflash.
Using the android app might increase the chances of a preset displaying as void. Again, it might be because the unit had already bugged itself out.
Sometimes in the android app settings disappear when you scroll down to edit others - I'm not sure if this is an app issue or its indicating that all is not happy module side, though I suspect it's a good indication a reflash is needed. (I haven't used the android app after my last reflash as I've been testing with the official app only, on windows fwiw, though I might have a go later.)
So Robert wondered if it might be power related, so I made a small 16x1 test config. Same results unfortunately:
Lost preset on new/replacement unit after long load on first change. All three Rains and three braids didn't load with saved edits.
Went through preset loads on the old one - 2x subotnik patches corrupted.
Both units lost settings pretty much immediately with reduced load on PSU.
I used the android app to edit, which wasn't holding settings, ie scrolled down and settings appeared lost, though sometimes held. I do wonder if the android app itself causes power issues, since I wonder if it's trying to charge the attached device.
Anyhow, I resaved patches using app after a bit of messing... Old tbd lost subot patch immediately and new tbd lost saved settings immediately.
I then wonder if the PSU itself was the issue so tested it with a multimeter - it's outputting a steady 5.02v with no fluctuations.
I think that rules out power, unless it's supply noise causing the issues? I'm going to go ahead and reflash both units before testing with the desktop linear PSU - that's rock solid so if there are any issues after that I'll remain convinced it's bugs.
Ok so broke down immediately after the (extended) power off - both got stuck in a reboot cycle on first preset load and the new one lost the braids preset. Obviously that's on the linear PSU wired in as above.
I believe that rules out power.
Also worth noting that this is less than twenty minutes use time after a full reflash.
Edit: sorry, error above in that I'm pretty sure it's a subotnik patch I broke.