so, after seeing all the posts i haven’t upgraded to the final release. I used beta 1 through 4 as I was working through an issue with squarp. I don’t have the flicker issue, I didn’t notice the long notes and I hadn’t noticed any corruption - i regularly went between the beta versions and 3.23 without any issues. Granted, I do have backups in revision control just in case. So, I don’t know if there’s a difference between beta4 and the final rev to be totally honest, but after seeing all the posts i still have beta 4 installed. :-/
Corrupting a project is like my worst fear when it comes to new revs - that’s part of why I moved to a git based backup system so even if i didn’t catch corruption before making a backup, i’d still have a recovery plan.
And the other thing i don’t know is if any of people’s issues are hw dependant. I have a mk1 and i haven’t see any of this stuff yet - but i don’t import midi i only ever author it on the pyramid directly – but its so hard to imagine how imported midi would be different unless it’s got weird messages from the daw or something.
For me anyways beta 4 is better because it fixes several spurious program change bugs that were affecting me because i rely on sync on load. Uh, man maybe I spoke too soon and no one should upgrade at this point unless they’re chasing down a specific bug.
after I got the email notification about the new version I immediately downloaded and flashed it. Then it seemed to disappear from the webpage for a couple of minutes and then reappeared again after a couple of minutes. However the file that reappeared again has 41 bytes different from the one that was there originally. The new reappeared file has the screen glitching problem, but the original file doesn’t. Here’s the original 4.00 bin file if you want to try it:
[MOD NOTE: please do not post versions for firmware]
[edit] sadly the incorrect note length loading bug is present even in the original file
Having issues here as well. Just opened a file working on last night after updating and all notes sustain indefinitely while playing, every track. Back to 3.23 for now
Right. This incident has “wrong version uploaded” written all over it, and this seems to confirm that. There was a similar incident a few months ago with the Rample. Thanks for sharing the info!
When you fixup something in a haste, chances are you end up only making it worse. And never release just before weekend/vacation, no matter how great the temptation. Been there, on both accounts
Ive just removed a link to a 3rd party copy of a version of the firmware that was later updated
please do not post copies of firmware on alternative sites… it will just lead to more confusion.
screen flickering issue
as others have pointed out, beta-1 did not include this display issue. so its obviously a bug that crept in just before release.
Squarp have been notified… however its the weekend, so they may or may not be working on it now.
Im sure they will let is know whats happening after the weekend.
if there will be a quick fix, I guess will depend on what has caused the issue and how easily it is to reverse that change.
If you have not updated, I’d suggest not…
if you have then Id suggest rolling back to the official release, or if you were on the beta, the last beta you have.
if you notice any other bugs, please report via the contact form
sorry about that. That was the first original 4.00 final release that didn’t have the display bug. The difference from the current version is only in 41 bytes
ah ha - and now i go to play my pyramid and find some of the bugs.
So like i said, i didn’t upgrade to 4.0 release yet. I did find on the beta that some, but not all of my tracks the note length has increased to 127. I already sent it to squarp, but just to validate you all
okay - so if you upgraded to 4.0 - I just tested this - but if you see the note length thing and you DONT SAVE it looks like it’ll be okay if you down grade to 3.23. I just repro’d the issue in 4.00 beta 4 (cause i still had it), i restored my back up, I tried in 4.00 again and i saw the note length issue. Then I downgraded to 3.23 (but didn’t press save) and my note lengths were back to normal
If i were anyone, unless you thoroughly check every single track for this note length thing, I wouldn’t press save if I were you. Anyways - it’s unfortunate that we missed this in beta testing - I realized why I missed it myself, it was simply because the tracks I tried this bug didn’t affect - some of my tracks were totally fine, but half of my tracks exhibit the note issue. Oops. Anyways - i’m not one of the devs or anything, just a passionate person - but I guess next time i’m on a beta I’ll probe more thoroughly on my songs.
So yea - don’t save the tracks if you’re on 4.0 so they don’t possibly get corrupted, and downgrade and you should be okay for now.
I understand this is probably a bit obvious and maybe too late for some of us… I think it’s good to repeat it however because as long as I’ve used computers and such… people seem to forget this kind of thing and then are irritated when something happens…
Before updating a piece of hardware it’s definitely worth it to back up your project files and then proceed with an update…
My process is essentially move everything over to the computer so I am absolutely sure there is nothing on the card that will get corrupted either by a new OS or… well anything else that could happen.
I know… I know… people do not want to hear it after the fact… and yes… it sucks to lose work… I’ve been in this position far too many times to think… “oh, it will be fine this time.”.
TLDR; Always back up your project files, definitions and settings before updating to new firmware. Better safe than sorry.
