Replies created

 

Viewing 2 replies - 1 through 2 (of 2 total)
  • CarlRadford
    Participant

    I’m saving by going through File > Save. To save my progress. I initially thought that it was due to having the grid editor open. But that doesn’t seem to make any difference.

    What’s happening is I can create a project. Add some blocks, and save. I can then open the project again, make some changes and everything is working fine. but every once in a while I’ll open a project, and all the changes I have made to the blocks would have disappeared. And that’s ALL blocks not just what I had edited in my previous session.

    For example; I can select a block, delete the kicks and add my own kicks. I will then save and exit. the following day, I can open the project and the block I edited the day before will be fine. I will then select a new or different block, and move the snare to be inline with what I want. I can then save and exit like before. And I would repeat this to gradually to create a drum track. If I open it again somewhere down the line it could be fine, or every once in a while when I open it, the kicks in the first block would vanish, and the snare that I moved in the second will also vanish. So any changes to the blocks that I have made will vanish, but the parts of each block that I haven’t touched will remain. And this will be in all instances where I have copied those blocks around.

    I think something is wrong with the saving process. I’m just speculating so I cold be wrong. But I think when it saves, it firstly records what blocks are active in the project, then it records all the parts of the block that have been removed or location changed. After this, it records all the new parts that have been added to the block. And it’s this last step that seems to be the issue. If that hasn’t saved correctly or corrupted, It won’t be applied to the block in all its instances when you next open it. That’s the only explanation I can think of that would account for what’s happening. But this more of a rational guess into what’s going on, and it could be something else entirely.

    CarlRadford
    Participant

    I’m having the same issue. I spend hours creating blocks with complex drum sequences. Press save. Then when I reopen it, parts of the blocks default or entire drums are missing. I’ve even had one song revert to nothing but a 4/4 snare in every block and no other drums.

    And its not user error. After it third time it happened, I tested it by creating a random block. Saved it, closed the program down. Reopened it, and the block had reset. I then did the exact thing again. And it saved correctly.

    Theirs definitely something intermittent with the saving.


    Reply To: SD3 will not save session. version: 3.2.3
    Operating system: macOS Catalina (10.15)
Viewing 2 replies - 1 through 2 (of 2 total)

No products in the cart.

×