rhummellh
Experienced
Camilo, for now just have unplug FC-6/12 to do changes via new axe edit version and plug back in for use. Or use front axe panel obviously
Camilo, for now just have unplug FC-6/12 to do changes via new axe edit version and plug back in for use. Or use front axe panel obviously
good tip! thanks!
Issue for most was coding for the FC which is in work. Imagine would be a future FC update. Have you had a chance to play with the new updates? They are bad ass! Leon already did a video on it. Stack/hold, Ultra reverb, etc.
In other contexts, RC = the best cola....
"Refresh after new FW" from the Settings menu.
That solved it! Funny, I've never had to do that manually before. The automatic "reading block definitions" thing has always been enough after updates.
Yes, and the attenuation parameter in gate is missing too but that's expected
Not to nit, but it'd save a lot of people asking this if Axe-Edit remembered the firmware version it had loaded, and refreshed automatically if the attached device was on a different version, maybe only a higher one.
That's what it does
So why do so many people ask questions whose answer is to "Refresh after new FW" from the Settings menu, like you just replied?
Because they used a beta firmware then went to release firmware which has the same version number maybe
Because people run beta firmware. If you're running firmware 3.3 Beta 1 and you then load 3.3 Beta 2, you're still on 3.3, so the editor won't know to that the firmware has changed.
The version communicated only has the major and minor number and a flag indicating beta or not
So only noobs want their software to figure out basic arithmetic, and update itself to match the environment it's actually in? Ok, sign me up
That's not basic arithmetic : beta iterations are not numbered in the version information sent to AxeEditSo only noobs want their software to figure out basic arithmetic, and update itself to match the environment it's actually in? Ok, sign me up
Don't mean to make a big deal out of this, it's not. Fixing it for real doesn't seem like it would be either.
So the most real fix relies on both sides, firmware and software.
Could be, but tbh this is a very minor problem.