@xko The only reason it should fail to save is if the filesystem is too full. Can you determine how much available space you have is?
1 Like
I donāt think this is the case. /data is only 14% full
Also I think it should somehow report the save success/failure in UI. Rght now the only way to find out, is when you try to load it, thatās too late - you donāt have it anymore, might even forget what you played exactly.
Iād like to, but I need to explore what UI elements have been added to the host to support this concept. In the meantime, Iām going to add some logging code. Once we have that, you can provide me with the log messages so that I can debug what is happening.
1 Like
there is no way for plugins to send web gui notifications yet, but using the LV2 log the messages sent there will appear on the browser console.
1 Like
@xko Reading through my code, I had forgotten that I had created a maximum quota for save files. Looking at the number that was picked, I believe that it is too small for the Dwarf. Iām going to increase the number and we can see if this makes your save problem go away.
3 Likes
@xko I have pushed an update which increases the quota for LP3 save files. I also added logging to the LV2 log on the MOD if save fails to succeed.
5 Likes
But what is the qouta now? IMO itās very improtant number. Iād have nothing against it written right on top the save button 
Also why quota at all? I want to record a lot, would be happy to have all of the space available.
I think itās not of much use for the regular user. I propose to just indicate if file is there or not, e.g. by painting slot number green. It will be then clear - if didnāt turn green, something went wrong. Even better - put the last sucessful save timestamp next to the number.
But, no. This didnāt help in my case 
No file appeared, and also nothing in the Chrome console
You have no TRACK files. That is strange. Save works by copying the latest TRACK file. Does the TRACK file ever appear?
One step at a time. Iām trying to resolve your save issue first. Then Iāll explore what LV2 will allow. Iām going to send you a private message because providing upgrades through the store is slowing the process down.
@xko Send me an email: bob at looperlative dot com
Iāll provide you a test binary to help me find why your save is failing. Once we get that sorted out, all the rest can be looked at later.
4 Likes
In the meanwhile I fixed it by removing LP3 form PB and placing it again. But still worth debugging IMO. Email sent.
Agree. This thread is quite flooded already. Maybe better use some sort of issue tracker?
Iāve historically never kept actual issues unresolved long enough to need a tracker, but will set one up should it become necessary.
3 Likes
I think this is related: when loading a saved track (in track 1), it looks the LP3 MIDI clock output is not updatedā¦
My use case is Dwarf sync to MIDI and LP3 Clock output connected to the virtual MIDI loopback. In this way my tremolo and delay are sync automatically to the loop lengthā¦ (very convenient for a lazy dude ā¦)
I just checked. This is a bug, Iāll get it fixed this week.
4 Likes
Thank you for all the updates, this is one of my favorite plugins on my Dwarf so far.
Is there any chance users could select the behavior for the stop function - i.e. stop immediately vs stop at end of loop?
The way I want to use it, parts can be minutes long - pressing stop then having to wait that long for the audio to stop is not ideal for me.
If this is already possible somehow, I apologize.
If you stop using the Play/Stop button, then it will stop immediately. The problem with the Loop multifunction button is that because it is a double tap that triggers the stop, then it is difficult to stop immediately because you need two taps to make it happen.
1 Like