The block Mix and individual Voice Levels are different things.Yes, the Mix for Voice 1 was 100% and for Voice 2, 0%
Set the block mix to 100%.
The block Mix and individual Voice Levels are different things.Yes, the Mix for Voice 1 was 100% and for Voice 2, 0%
NoDo you have to reset the Pitch block after applying the firmware? I'm always a little confused about how to make sure I'm getting the 'lastest and greatest' after firmware updates.
FWIW; I have a dual shift block I had saved in my library. It sounded funky when I loaded up a scene with it engage. I reset the block and dialed the same settings back in and it was fine. There was an odd sort of delay happening? Or I was just temporarily nuts.Do you have to reset the Pitch block after applying the firmware? I'm always a little confused about how to make sure I'm getting the 'lastest and greatest' after firmware updates.
Went back to 1.18, too many weird things with 1.19, specially with the pitch block.
What other weird things are occurring?Went back to 1.18, too many weird things with 1.19, specially with the pitch block.
What other weird things are occurring?
this feels more like a "worked too fast in Axe-Edit" thing, where communication had been lost.I had an issue using the beta yesterday, where I was working on a preset via Axe Edit and noticed that my output 3 LEDs were maxed out. I believe it was after I had copied an Austin Buddy preset for a Marshall type sound, and I was customizing it for a RHCP song (Dani California). From memory it happened at the point that I was deleting all the blocks I didn't need from the Austin Buddy preset (which I think contained an Output 3 block). When I noticed output 3 maxed I think I changed scenes a couple of times and ended up with I think Output 2, 3 and 4 LEDs all maxed, with some big pops happening each time I changed scenes. I saved the preset via Axe Edit, then power cycled the Axe-Fx, and all came back to normal with that same preset. I continued customizing and didn't experience the behavior again.
Apologies - I know that doesn't give you a lot to go on - I'll keep an eye on it and will try and give more detail if it happens again.
this feels more like a "worked too fast in Axe-Edit" thing, where communication had been lost.
good to share, thanks, but might not be a "bug" per se.
Went back to 1.18, too many weird things with 1.19, specially with the pitch block.
Sounds about right. To do polyphonic pitch shifting well you need around 50 ms of history. So nominally the delay will be half that, 25 ms.I'm getting what sounds like a 20-30 ms delay when I drop a half-step.
Interesting because one of the products I used in my comparison was an Eventide Eclipse. The Axe-Fx stability and tracking was superior. Perhaps the H8000 has better algorithms than the Eclipse. From what I've been told, though, the algorithms are identical. The Eclipse has a more colored tone though. This is due to an aggressive lowpass filter on the input to the pitch shifter. The Axe-Fx uses less aggressive filtering. For upward pitch shifts this aggressive filtering produces a bell-like quality that might be considered desirable by some, I suppose, but I find it too colored sounding.Definitely an improvement on the pitch block. I hope it continues still not there in my opinion but getting there..I pretty much compare it to my eventide H8000.
I had an issue using the beta yesterday, where I was working on a preset via Axe Edit and noticed that my output 3 LEDs were maxed out. I believe it was after I had copied an @austinbuddy preset for a Marshall type sound, and I was customizing it for a RHCP song (Dani California). From memory it happened at the point that I was deleting all the blocks I didn't need from the Austin Buddy preset (which I think contained an Output 3 block). When I noticed output 3 maxed I think I saved the current preset, then changed presets a couple of times to try and clear the issue, and ended up with I believe Output 2, 3 and 4 LEDs all maxed, with some big pops happening on Output 1 each time I changed presets. I power cycled the Axe-Fx, and all came back to normal. I continued customizing that initial preset and didn't experience the behavior again.
I've followed this exact same procedure a number of times for different presets/songs on older firmware, and this is the first time I've seen this behavior, which makes me think it might somehow be related to the beta, so I figured I should write it up.
Apologies - I know that doesn't give you a lot to go on - I'll keep an eye on it and will try and give more detail if it happens again.