I have the latest OS and haven’t had any issues in five or six months of regular use, until today when the 2nd Save/Load button combo failed to open it’s respective menu. I didn’t have a way to save my progress and eventually powered off the unit to attempt to resolve the bug. It did resolve itself on reboot but I lost about an hour of valued work that I’m not musically talented enough to replicate. Is this a rare occurrence? I know this is meant to be the final OS so I’m worried it will happen again and I’ll loose more time.
I have the latest OS and haven’t had any issues in five or six months of regular use, until today when the 2nd Save/Load button combo failed to open it’s respective menu. I didn’t have a way to save my progress and eventually powered off the unit to attempt to resolve the bug. It did resolve itself on reboot but I lost about an hour of valued work that I’m not musically talented enough to replicate. Is this a rare occurrence? I know this is meant to be the final OS so I’m worried it will happen again and I’ll loose more time.
Thanks
Logan
Replying to boost. I know that’s annoying unless you happen to have this problem. It’s such a great device, and a little more desk-friendly than the flagship, so I wish it could remain with some support from the coding team. I think this is just a very rare bug…or perhaps a falling neutrino flipped just the wrong bit
I don’t know if this is a rare occurance or not. I can say that I haven’t encountered it myself, though.
Did your Pyramid continue to function normally other than this fault? I mean did 2nd + Save/Load just do nothing (no freezing or anything else untoward)? If so it seems like it just wasn’t ‘seeing’ the SD card, as if there wasn’t one there. I guess (if there was no ‘freezing’ or there was nothing to suggest it was trying to access the SD card) you tried ejecting and reinsering the SD or maybe tried another (correctly formatted) SD card in the slot. It seems like for whatever reason, perhaps something physical with the card or slot, or perhaps that neutrino (!) may have ‘fooled’ your Pyramid into ‘thinking’ there was no card present.
The obvious advice is to save more frequently. SD cards are not infallible. I’m sure you know this already but it’s easy to forget when you never seem to have a problem.
If the problem happens again I’d try inserting another SD card (as long as the button combo didn’t result in Pyramid freezing and you were sure Pyramid wasn’t still attempting to access the menu). I think I might consider replacing your SD card anyway, but certainly, if it happened again, because if there was something about the card that made it prone to not being ‘seen’ you wouldn’t want that to happen during saving or loading (I’m not sure how likely that might be, but…). And it’s generally a good idea to have more than one available if (or maybe that should be ‘when’) the one you are using developes a fault. Habits like frequently saving and backing up projects onto a computer, etc, are good ones to get into to help minimise the possible ill effects of a card ‘going bad’.
I’m not suggesting that there is a problem with your SD card, it could be a weird one-off type of issue (a rare bug), or the fault could be some intermittent thing with your Pyramid, but I think the first thing to suspect ought to be the SD card itself (because of the nature of the problem and because SD cards aren’t infallible and they are easy to replace). If the problem happens again, with another card, then maybe it would make it more likely that it was a bug or perhaps, for instance, some issue with the SD card slot on Pyramid (I’d hope these were less likely causes). Of course, though, it wouldn’t necessarily rule out the possibilty that there was an issue with both SD cards.
Hi, I think I encountered the same once, after a particularly long noodling session with lots of copy-pasting tracks (with program change and bank settings), steps and effect parameters. At some point when hitting the 2nd+Save/Load combo the respective window would just flash for a very brief moment and then disappear, making save/load operations impossible. In the same way the issue resolved after the reboot. It was indeed a very rare ocurrence though.
That’s interesting. What @Sundam said suggested they had been working for about 30 minutes when they had the issue. It sounds like it could be related to the amount of available RAM you have ‘left’. Maybe your Pyramid’s RAM was so full that the amount it would need to show the list or perhaps prepare its content for saving on the SD card wasn’t available. It might seem a bit unlikely, but I think some operations (like copying and pasting long passages) are more likely to make parts of the RAM ‘unavailable’ even if the actual amount of memory needed is less (maybe like having an unfragmented disk on a computer). So maybe because of the amount and type of operations (since last saving) had got too close to the limit. If it was something like this, the same advice to save regularly would apply, but also maybe save then reboot occasionally for long/intensive sessions.
If it did happen again, perhaps you could try deleting some part that you could potentially replicate (or one you already have saved), if, say, the work you’d just been doing was unrepeatable or too painful to lose. If you can delete enough data on the current project to enable you to use ‘save as’ and save with another name you may be able to access the deleted parts from the ‘old’ project (with some file management on a computer) to reassemble your project at a later date. That all supposes, of course, that it might be a RAM issue and if that is the problem it might mean that you were running a little too close for comfort to the 13000 MIDI events limit anyway. Although, having said that, I think it might be possible to end up with the RAM being used quite inefficiently after a pretty involved session (depending on the types of operations you’d done) so it might not necessarily mean you were all that close to the 13000 MIDI events per project limit.
