AtomicBlaze
Inspired
Could you post a recording with its preset?
A reinstall of 19.06 fixed it.
Could you post a recording with its preset?
As far as I recall 19.05 has a bug that affects the Amp block in a negative way...At the risk of being asking a redundant question...how does it sound compared to 19.05?
19.05 has sounded spectacular at the last 2 jams I attended.
I mainly use the Dumble, Wrecker, Fender amp models.
Burgs Dumbles, the Kid Charlemagne preset, and the odd SRV preset are the ones I have tweaked to suit my setup.
Apart from bug fixes is there a reason to move to .06?
I ONLY USE PRESETS, NO SCENES, AND HAVE NO USE FOR SET LISTS.
Your thoughts please.
can confirm this in axe edit as of 1.10.11 but don't currently have it home to test it on 1.11.01If i open any custom Preset, the Amp Block shows a 59 Bassman with all controlls at noon, untill i click on Channel "A" once,
then my Amp from the Preset is there.
when I change a preset, unit's screen blinks
...not in a bad way. It sounds good, I like it!a little brighter
I was having some issues with the C/C# note resonating more than the other notes when palm muting. This is mainly because of my room. Although it is lightly treated (and it works very well) there was always this more than necessary resonance. With the last updates, this area is more under control. With the latest update, the low end seems to be a little more compressed, in a good way. Low end definitely isn't compressed mush. Actually it is a bit more angry, maybe because it is compressed LOL. The difference is too obvious compared to the beta. Low end is more focused and I feel the power when palm muting. JP2C is now a great amp!For me it sounds slightly LESS bright (in a very good way) compared to Beta. Great update, highly recommend everyone to try it out!
Awesome update!
What I have noticed is that now when I change a preset, unit's screen blinks for a half of a second instead of seamless switching.
It was not like that with 19.06 beta as I remember.
I did import the songs first but didn't bother trying to import the set lists because it just didn't seem to be working right.You may have tried this but you need to import the Songs first, then the Setlists.
So I'm lying in bed last night thinking about this when the light bulb goes on... Refresh after FW! Doh, I'll shut up now.Cab manager bug bummer. Tried rearranging some IR's, deleting old ones and adding some new ones. Now everything is all messed up. Looked ok at first, everything saved. But when I close cab manager and view cabs thru cab block, the new ones aren't there. Only my older ones. The deleted ones stayed deleted there. Reloading my backup file now, man is it s l o w.
Apparently the backup file loaded successfully, the cabs sound correctly but the names read as "empty". Has to be an Axe Edit glitch as the cab names read properly via front panel. Axe Edit version 1.11.01
Anybody have the previous version I can use?
View attachment 100028View attachment 100029
I haven't read the whole thread but I might have found a BUG:
Parametric EQ bypass state does not get reflected across scenes. I made sure to toggle scene ignore on/off too so that it does not have an effect.
To replicate, in Axe-Edit (latest version) I have Parametric EQ 1 set to enabled in scene 1. In scene 2 I have it set disabled.
When I switch to scene 2, the block gets bypassed. When I switch back to scene 1 the effect is still bypassed.
I am also seeing the channel reset back to ch A. I can't get this to happen when using the Axe-Edit UI but when I use a MIDI controller to send scene select MIDI CC (mapped to CC 34) this occurs. I made sure to check that there were no MIDI mappings for channel or bypass that could cause this.
Huh, seems I had somehow Scene revert on despite not remembering ever setting it. Maybe I've set it by accident. Thanks, that seems to have solved it.Can't test it atm, but as I understand it: when switching through MIDI, bypass state is determined by Scene Revert, not by Scene Ignore.
That's why switching in the editor versus MIDI-switching can have different results, because the editor always ignores the Scene Revert setting (by design).