Axe-Fx III Firmware Version 11.02 Public Beta #2

Tommy Tempest said:
Backup Daily - lose minimal to nothing
Click to expand...
Depends a lot on the business in question.

I work for a company in the top 15 of the Fortune 500 list. Backing up only daily for our critical systems would be a major loss. ;)

In Disaster Recovery there are two acronyms: RPO and RTO.

Recovery Point Objective (RPO) describes the expected data loss in time.

Recovery Time Objective (RTO) describes the expected time to recover your system(s).

The current RPO for systems I support is 20 minutes...
 
Last edited:
unix-guy said:
Depends a lot on the business in question.

I work for a company in the top 15 of the Fortune 500 list. Backing up only daily for our critical systems would be a major loss. ;)

In Disaster Recovery there are two acronyms: RPO and RTO.

Recovery Point Objective (RPO) describes the expected data loss in time.

Recovery Time Objective (RTO) describes the expected to recover your system(s).

The current RPO for systems I support is 20 minutes...
Click to expand...
I was keeping it simple, as to not confuse the AXE FX users not wanting to backup. It would be overkill to suggest offsite, CDM, etc..:)
Bottom line BACKUP or risk losing.
 
phil92 said:
Dammit, I lost a few presets trying to go back to 11.01 for comparison; every preset I edited in 11.02 beta 1 (the second one) was empty in11.01. Went back to 11.02 beta and still empty.

Vowing to backup before every update from now on.
Click to expand...

refresh axe edit so it re-scans all of your presets
 
haven't used the flanger in years cuz it never gelled with me.. huge improvement. I only mix about 10% and it sounds incredible.
you can do some really cool things with your sound stage..
 
Just updated today and find that my scene controllers are not at the "values," instead they all read 0% and my CS all are "ON" even when they aren't in the preset. Hmmm....Scene Controllers are an IMPORTANT part of how I use my presets...Edit isn't reading them correctly.

Firmware 11.02 Beta 2
Axe Edit 1.04
 
GtarLover said:
Just updated today and find that my scene controllers are not at the "values," instead they all read 0% and my CS all are "ON" even when they aren't in the preset. Hmmm....Scene Controllers are an IMPORTANT part of how I use my presets...Edit isn't reading them correctly.

Firmware 11.02 Beta 2
Axe Edit 1.04
Click to expand...
Do they look correct from the front panel?

Did you try a Refresh After Update in Axe-Edit?
 
Bulletv1 said:
Anyone else having issues with getting presets to save which then causes the Axe FX to freeze?
Click to expand...

I was having this happen with firmware 11.01 and the last Axe Edit. Every time I tweaked any preset and hit save it locked up. It took 3 to 5 minutes to save a preset, and sometimes it didn't work at all. It just locked up totally. I am not sure if it's a firmware issue or an Axe Edit issue. I haven't tried it with the new beta firmware and Axe Edit 1.04 yet to see if it's still happening or not. Which firmware and Axe Edit version are you on?
 
GtarLover said:
Just updated today and find that my scene controllers are not at the "values," instead they all read 0% and my CS all are "ON" even when they aren't in the preset. Hmmm....Scene Controllers are an IMPORTANT part of how I use my presets...Edit isn't reading them correctly.

Firmware 11.02 Beta 2
Axe Edit 1.04
Click to expand...

Yes, this has already been reported. It happens not only with the scene controllers but also with the EQ values and other parameters.

The problem is at both Axe-Edit and at the Axe-FX front panel

If that is important to you, you should revert to the latest official firmware release.
 
Piing said:
Yes, this has already been reported. It happens not only with the scene controllers but also with the EQ values and other parameters.

The problem is at both Axe-Edit and at the Axe-FX front panel

If that is important to you, you should revert to the latest official firmware release.
Click to expand...


Will do, thanks
 
So weirdness going on the first IR spot, it loads the IR transient close, but then the same IR in the other 3 spots is a mile away, which is normal lol, then I added a celestion IR and it put IR 1 back to where the rest of the other OwnHammer IRs are, a mile away from the start, and FYI, I have viewed the OH IRs in a Daw, and yes, they have an excess amount of nothing (7/8192 to be exact ) at the beginning of the IR. If nothing else, it should be a wake-up call to ownhammer to properly cut their IR start point , wonder if cubase has a macro to do it? Lol or FAS add a cut to move IR forward instead of just back.
 

Attachments

  • IMG_20191227_093356.jpg
    IMG_20191227_093356.jpg
    3.1 MB · Views: 39
  • IMG_20191227_093425.jpg
    IMG_20191227_093425.jpg
    2.2 MB · Views: 39
  • 15774612291968745467699904251520.jpg
    15774612291968745467699904251520.jpg
    3.7 MB · Views: 35
  • 15774614200257267456888737959874.jpg
    15774614200257267456888737959874.jpg
    5.7 MB · Views: 33
  • 15774616427898345542960845738779.jpg
    15774616427898345542960845738779.jpg
    4.9 MB · Views: 29
never mind, figured out how to cut off all the extra dead space at the beginning of the IR, thank you Cab-Lab lol, axe 3 IR import didn't do it, so CabLab Min phase WavIR to Sysex IR convert solves the issue.
 
You must log in or register to reply here.
Back
Top Bottom