Hi, it seems a bit weird to me that when you clear all tracks in a song this overrides a saved version.
If this is actually how the Looper works, I would really love to see the option to clear all tracks in working memory, without changing what’s saved.
It seems to me a much better behavior, and safer.
This why you need to use the Sdcard and the internal memory
Play on the internal and save on the SD or vice versa
Would this override the behavior?
Wouldn’t the tracks be erased from whatever medium the song is stored to (SD or internal) ?
Or are you simply suggesting a backup?
If you record a song on the SD card, you can copy it to the internal memory, so if you accidentally delete the song on the SD card, you still have it on the internal memory! A kind of backup indeed. But I’ve made this mistake so many times, I’ve got out of the habit. It’s a bit like on a PC, when you have anything you really want, you put it in a safe place.
I understand that, it’s really a backup.
What I would personally prefer is EVERYTHING I do while editing could be reverted by reloading the saved track.
Thanks!
Hey there,
All you would do is reopen the song again, this does not require a feature there is a workaround
There is a Stopped Slideout menu option called reopen song, the slideout is opened by pressing and holding the bottom left button in the loop studio screen. The stopped slideout must be enabled for it to function, and you must show the reopen function using the slideout settings in the device settings menu.
For this reason we will not be attempting this, and this will be tagged as considered
Thank you for the request!
Thank you Brennan. I would still prefer for the saved version to be locked until saved over.
This would be safer, and more intuitive. People wouldn’t think about it and just see the saved song changed.
Also you might load a new song, get prompted “would you like to save the changes?” and think that if you don’t you would keep the original version, load the new one and loose the workaround option.
But it’s good to know there’s a workaround!
Thanks for considering it, cheers.
Just to piggyback here, Ive always found this function illogical and comically dire. Is the idea to make logically inconsistent features with workarounds or a logically consistent UX? There is no analog to my knowledge in consumer computing. Everyone is used to the heuristic where your changes always and consistently take permanent effect when you SAVE. If you don’t like what you’ve been doing you simply turn off your machine with no worries. This “clear all” tracks feature splits the background logic of save behavior on the machine. Some changes are made permanent when you save like writing over a track, and some catastrophic changes take place immediately like clear all. What is the reason for this?
Its logically inconsistent, has no analog outside of this machine and confusing. I came here looking for answers when a song I had been working on for weeks, and I had been saving fine for weeks, came up totally empty this morning. (zero k). And I realized I must have deleted it on accident. I appreciate all the time spent working on this machine but I am fairly certain theres no justification for this feature that justifies the split in logical behavior and the danger to deleting projects with no means of recovery. Its almost cartoonish how theres basically a nuke button right by the save button and I cant for the life of me figure out its necessity. The logic of “if you don’t like something, just start a new project or just don’t save your current work” has been getting people by just fine to date, and these longstanding principles are more or less ingrained in peoples minds. When you follow that half the time and then serve up insta-nuke the other half it causes problems. I get the workaround but that only works if you don’t shut off the machine first which if youre mistaken in thinking you saved instead of cleared, youd have no reason to do. Changes being made permanent on save keeps this from happening.