Bug? Per-Preset Compatibility

[brianv4]

Not really sure where to go with this. If it's an issue with Edit or a compatibility problem between the III and the 9 but when I transfer a preset from the AxeFx III to the FM9 (and vice-versa) the per-preset switches don't maintain their correct assignments.

 

[chris]

Can you give an example so we have a starting place to look?

 

[brianv4]

I'm setup so when I select a preset it links right to the scenes layout. Sometimes I use scenes (especially when checking out factory presets) but most of the time I'll use all per-preset switches overriding in the scenes layout.

I never use a block that isn't in both the III and the 9 so compatibility isn't an issue. But whenever I export a preset from either machine to the other, these assignment don't follow correctly.

Take the preset I'm attaching as an example, It's from the III. Checkout the switch assignments then load it in the 9 and you'll see what happens. And I realize there are 12 per-preset switches but 1-9 should line up. Sometimes it has the wrong block or channel or smart bypass isn't selected correctly. Thx!

Oh, and switch the cab block back to channel A. I'm using custom IR's on Channel C.

 

[unix-guy]

I haven't loaded your preset but wanted to mention that switches are presented differently on an FC-12 versus an FM9.

FC-12 switches are like this:

7  8  9  10 11 12
1  2  3  4  5  6

FM9 are like this:

10 11 12 7  8  9
1  2  3  4  5  6

Are you checking switches by number or position on the layout?

 

[brianv4]

I haven't loaded your preset but wanted to mention that switches are presented differently on an FC-12 versus an FM9.

FC-12 switches are like this:

7  8  9  10 11 12
1  2  3  4  5  6

FM9 are like this:

10 11 12 7  8  9
1  2  3  4  5  6

Are you checking switches by number or position on the layout?

Yes I do realize, thx!

 

[brianv4]

Here's a visual example of whats happening. I took the preset in the OP and loaded it in the FM9. This is what happens:

EX 1:

EX 1 when loaded in the FM9:


EX 2:

EX 2 when loaded in the FM9:


Lastly EX 3:


And when loaded in the FM9:

 

[brianv4]

I just want to make sure this can be confirmed, thanks!
@chris or @Michael Pickens or @Admin M@

 

[mr_fender]

I've wondered about this myself but haven't had a chance to test it. Are FC Per Preset functions stored as part of the FC data or in the actual preset?

 

[unix-guy]

I've wondered about this myself but haven't had a chance to test it. Are FC Per Preset functions stored as part of the FC data or in the actual preset?

I would think per-preset has to be stored with the preset.

 

[brianv4]

I would think per-preset has to be stored with the preset.

Agree.

This issue with per-preset assignments has been happening thru several FW versions, and not just with the blocks I've shown in the examples. Just glad I finally have some downtime to report it. I'll be away thru Tuesday but will do my best to follow the thread.

 

[Rex]

I've wondered about this myself but haven't had a chance to test it. Are FC Per Preset functions stored as part of the FC data or in the actual preset?

All per-preset data — FC or otherwise — is stored in the preset. Otherwise, it would be lost when you load a saved preset.

 

[mr_fender]

That's kind of what I figured and would keep it from getting messed up if you moved a preset as well.

 

[Michael Pickens]

@brianv4 Fixed for next release.

 

[brianv4]

@brianv4 Fixed for next release.

Wow that was fast, thanks Michael!

 

[Dave Merrill]

Do I understand right that the fix is in FM9-Edit, and won't affect the Axe III or Axe-Edit?

 

[Michael Pickens]

Do I understand right that the fix is in FM9-Edit, and won't affect the Axe III or Axe-Edit?

That is correct. The fix will be in FM9-Edit.

 

[brianv4]

That is correct. The fix will be in FM9-Edit.

Thanks for the clarification!