#104

I got SD card driver to crash? the unit responds properly to commands, but when playing, the orange light over loop just blinks. Just left the synth on for an hour or so while I made dinner, patch cables going into in and out but nothing happening.

#105

Sorry – this won’t be especially helpful due to lack of reproducible steps, but I wanted to mention that I’ve gotten stuck in the short, infinite loop bug a couple of times on the newest beta, where just a sliver of a recording gets captured.

That said, the beta feels much more stable overall, and the reduced clicking on loop points has made this an even more beautiful thing for delay experiments.

2 Likes
#106

@yoyosandshoes
Sorry it’s been a few days. If you remember, can I ask if you did a ‘clear-tape’ since installing the beta? Specifically I’m surprised to hear it locked up after trying to change tapes. I thought that bug had been fixed.

Oh just realized. Are you saying you tried to change tapes after the ‘short loop’ began? If that’s the case it totally makes sense as the SD driver has crashed & so the tape-change code will never return.

Speaking of, I’m going to add a timeout for the Change-Tape command such that it will detect a frozen SD card & reset the driver. That way if you experience the stuck-in-loop behaviour, you can just reload your tape to get back to a working state. A workaround, but good to have just in case.

@jwhiles
I’m going to look at the load-tape details to see if there is more ways to verify the data is valid.
In your “oh no” moment, you could do a ‘clear-tape’ to get back to a workable state (record+down while turning on). It appears to me that the cue data stored in that tape is invalid & causing the module to try and load non-existing data (and waiting forever for it to return). again, timeouts should be implemented, but obviously finding the source of the problem is more important!

@stripes

Do you mean a click when you engage playback, or a click at the loop point? Noted the point about the blip in a reversed loop, should be a quick fix…

@alanza @stripes
Special thanks for group testing the NAV/LIVE crash bug cv thing. I would never have made the leap that it was related to looping. Hoping to get this one today.

8 Likes
#107

I haven’t had any problems since clearing the cue points on that tape. If you’ve been able to fix the issue with creating invalid cue points - It feels like it be might be worth forcibly removing them when people bump to this firmware. Or at least strongly advising it in the patch notes? :slight_smile:

1 Like
#108

Is there any chance of getting a clean current tape TT op in the near future (it would be really ncie to have that prior to the TT v2.3 release).

W/ Type Firmware Ideas
#109

@GoneCaving
I don’t think so, the reason being 1) it creates a loud click as currently we have to turn off the codec to do this without crashing, or a bunch more code, and 2) it doesn’t seem like a performative command. I’m sorry to insist, but I’d far prefer to fix the underlying problems rather than provide bandaids. Sorry it’s taking so long to get to the bottom of it all!

@jwhiles
It does recommend to clear all tapes up top on this thread. The problem is once there’s a single invalid cue, you can’t trust the rest of them (because it’s a linked list and they are created relative to their neighbours). Thus the only real solution is to delete them all. That’s what the firmware is meant to do now, but clearly it didn’t work in your case… It’s on the list!

2 Likes
W/ Type Firmware Ideas
W/ Type Firmware Ideas
#110

I still think it could be useful in a performance context (build up tapes and layers, fade down, clear tape, go again). I wasn’t so much suggesting it as an alternative to fixing the tape issue.

Can you also update the docs to include the commends for clearing tape. (note to self: find the instructions and bookmark it this time!!)

#111

@GoneCaving
I’m thinking this is better solved with a different solution (eg. switching to a different tape. jumping to a next (known empty) cue. clearing the tape with overwrite). Certainly there’s many options for these types of things, but I’d like to give it the time to make sure the metaphor is as consistent as possible.

@jwhiles
Funnily enough, I just (for the first time) am experiencing the ‘won’t turn on’ bug, even after factory_reset-ing. Yay! I can actually debug it!

3 Likes
#112

Fair enough. It’s hard to roll this stuff back if it turns out to be the wrong decision.

1 Like
#113

I think I may have been slightly confusing - the tape where I had problems was one for which I hadn’t cleared the cue points. I’ve been able to clear them now and everything seems good!

#114

repeating click at the loop point, it seems

1 Like
#115

After flashing the current firmware, my unit consistently boots at the beginning of the tape rather than the last cue point at power-down. I tried switching tapes and deleting all cues on all tapes I’ve used, but the issue remains. The active mode on power-down makes no difference (I haven’t cycled power in cue mode).

I have not cleared any tapes, but I did start on an unused one after installation.

#116

yes this is what happened.
Glad to hear there will be a workaround!! Thanks for the hard work and lovely machines

edited for bad quote formatting

#117

Oh, I’ve always had this happen to! I thought it was intentional xD

#118

With the first beta, It seemed to happen less frequently. I jumped from that one to the current and I’ve only had it reboot to the last cue once.

Edit: make that thrice. After posting, I gave it two boots and both started where I left off.

#119

Anyone know the brand of the sd card? I know it’s 4gb but was thinking of trying Sandisk and Kingston cards. Is there any limit or disadvantages to using a bigger card? 8, 16, 32 gb? Wondering if changing the card will iron out some issues as cards are pretty cheap nowadays.

#120

@mlogger
Main requirement is it should be a class10 card. Don’t use a U1 or U3 (eg Sandisk Ultra) as they prioritize continuous read/write and are dreadful at switching between read & write accesses. Typically these are only available in <8GB sizes.

W/ reads & writes in small 8kB chunks (necessary in a system with only 512kB of ram) and throughput is typically not an issue. I still believe the issues people are experiencing flow from driver implementation, and impossible accesses caused by bogus cue data.

We bought dozens of different cards and the particular ‘generic’ brand 4GB, class10 card we found to be the best for this purpose.

That said any sdcard will work (it will trash the filesystem), though you might run into different issues like gaps in audio etc.

@Gexex
Notably the metadata that saves which cue you’re at is only saved when entering NAV mode currently, so if you turn off while in LIVE, none of the changes since last being in NAV will be saved (including audio, cuepoints & metadata). This is currently being reworked to be done more regularly (whenever the sdcard access buffer empties).

Of course there could be a different issue if this description doesn’t align with your experience.

3 Likes
#121

Thanks, that often describes my issue, though I’ve experienced it when powering down with CV into That in NAV mode (tape moving). I haven’t tested powering down this way with the newest firmware yet.

#122

@Galapagoose - Not sure if this will be entirely helpful, but the infinite short loop bug has been happening pretty consistently for me on the latest beta, even after starting with a cleared tape. Seems to happen every 3rd of 4th time I boot up the modular and start using w/ – happens pretty much immediately, actually. So far, I’ve observed the following (in LIVE mode specifically):

  1. With PLAY is engaged (forward-playback), I toggle down to insert a start point, and then the module goes into the short loop bug when I toggle up to close the loop. AFAIK, these loop points are being inserted into a blank part of the tape (no previous recordings or cues).
  2. Again, with PLAY engaged (forward-playback), the bug can occur when a previously recorded loop reaches its closing loop point.

I should also note that, as far as I can tell, I didn’t have anything plugged into either THIS or THAT in these instances. Let me know if you have any follow-up questions!

2 Likes
#123

i can confirm this bug; it triggers the same way for me as soon as i toggle up to set the finish & loop marker.

this same bug is triggered when using the two-button record+loop method to set an immediate marker when starting play; as soon as i toggle up, the bug hits.

both methods were duplicated after a fresh power-up, using a completely blank tape even after following the “factory reset/wipe all” procedures, and nothing plugged into this/that.

1 Like