Posts by amclw1

    Ok . Thanks for the clarification. Is there any chance that the official 02 multiparameter function will work as it should(affecting sound with all parameters change)?

    And....silence! They are quick enough to slap you down but pretty tight-lipped about supplying any useful detail whatsoever.

    It's probably been said earlier but it is a real pain that you can't tell which preset was originally initially associated with a current stomp/fx position e.g. 'Default' or 'Formant Blast +'. Once you select it, poof! it's name is gone. Now my memory is not good enough to remember which particular preset I selected many moons ago and it would be great to know so I could go back to where I started from when I f*ck it up.... There is plenty of room on the right side of the display for this. The original preset name should also be the default name when storing as a new preset (with perhaps 'New' at the end?).

    If you are looking for a global Freeze button, consider connecting an external momentary switch to the Remote and assign the function "Freeze" to it . It still appears as "Hold" in the menu, but it's functionally the same. That Freeze switch then does all Freezes in all effects of all Rigs.

    Thanks I will give this a go.

    Just tested. I see what you are getting at, but my point is that I need to assign freeze to the button for each effect (max of four per button?). Then it works as you describe. I don't want to have to do this. I want to assign 'reverb freeze' to a button once only. If there is a magic method I'd be glad to hear it.

    Doesn't do that for me, I have to program the remote button individually for each rig. What I want is to program a button on remote once for freeze and it will activate it for any active effect that has that function. Might be more useful if there was a global freeze for separate types. e.g. delay, reverb.

    Apologies if already requested or available somehow...


    It would be nice to be able assign a switch on the remote as a global freeze. i.e. will affect any active effect that has the freeze function.

    I am going to make a purely speculative statement here.


    The new cab will have the F12-200X Celestion driver. It is the only full range 'guitar' speaker that Celestion has in their lineup, so it makes sense to me.


    If I am correct, it is likely possible that a DIY 2 x 12 or even a 4 x 12 cab with that driver will get the Kone effect to work exactly as expected in the 1 x 12 Kemper cab. ;)

    I wondered about that too. I was about to pull trigger on one of these to put in a Hoffnine 1x12 cab I have.... Think I might wait a little while now.

    By past experience, we will wait a long time for the new updates and rig manager/editor. So it won't be a waste of your time using ToastMe for now (if you have a suitable MIDI interface). Note that Damian is still working on an update that will work with the new beta 5.7. The current ToastMe production release 1.40 works great with 5.5.2. and the previous 5.6 (spring reverb) beta.

    More info on new version from Damian:


    It will create a folder ToastME_Presets under os Documents folder
    It has structure like backup file
    It is for storing and loading presets from disk to overcome Stomps preset section issue.
    Under the settings tab it is a button called Unpack Presets from Backup it will unpack backup file to this folder.
    For now you can only store Stomp , stomps section , effect section and reverb
    When loading presets from file it will open dedicated folder from ToastME_Presets.
    When you want save individual stomp preset it will add (suggest) type name at the beginning with CAPS letters.


    N.B. To obtain a backup file to 'unpack', perform a backup on the Kemper to USB stick then transfer the file (*.kpabackup) to your PC.

    I have successfully disabled updates on my main Win 10 PC. It doesn't even nag me any more. Now if I could only remember how I did it.... One thing I know you CAN'T do is redirect a bunch of the M$ maintenance sites...they are actually hardwired into local DNS!


    See https://www.petri.com/windows-…-specific-name-resolution


    So you do indeed need to resort to blocking at firewall or router.


    Absolutely disgraceful. Saving us from ourselves, and all that.