That would take memory and CPU cycles which in turn would affect overall CPU and memory usage. This would result in lower quality effects or less options (e.g. routing). There is no free lunch.Also, a wild idea - maybe it is possible to develop this: when you PRESS AND HOLD the switch, AX8 prepares something in background (your current preset and sound still stay intact) to make the preset change more seamless? Once you RELEASE the switch, system finalizes the preset change and switches to it with shorter lag.
i'm working on your preset right now on my new live stream platform. the switching is actually faster using 2 presets vs switching XY in the same preset. i duplicated your preset and made each different sound Scene 1 respectively, and the switching was much faster, still a small gap as expected.
when i got the preset under about 75% CPU, the XY Amp switching was much faster, and around 70 or below was even faster. but that speed basically matched the 2 separate presets at their high CPU usage.
Do you know how to copy a scene? For example I want scene 2 to reset so its the same as scene 1 again? Or say I want scene 3 to be the same as scene 2? Nothing in the manual and on the unit cant figure it out...
I think this is not an issue when using a dedicated Scene button. There is no hold function so I think it engages on the downstroke. I'll check later.Just a few thoughts.
Afaik, there are currently two ways the button switches work:
1. It makes changes once you press AND RELEASE the switch.
2. It makes changes when you just press the switch.
Maybe it is possible to achieve lower switch latency using the 2nd switching option?
Also, a wild idea - maybe it is possible to develop this: when you PRESS AND HOLD the switch, AX8 prepares something in background (your current preset and sound still stay intact) to make the preset change more seamless? Once you RELEASE the switch, system finalizes the preset change and switches to it with shorter lag.
Bummer. This is needed on the unit, Im hoping to avoid having to connect a computer to edit, so far I had been succesful...You have to use AX8Edit to do that.
-
Austin
Bummer. This is needed on the unit, Im hoping to avoid having to connect a computer to edit, so far I had been succesful...
scenes are just statuses of on/off and x/y, so i don't think the hardware really stores anything the same way it stores a preset.Bummer. This is needed on the unit, Im hoping to avoid having to connect a computer to edit, so far I had been succesful...
scenes are just statuses of on/off and x/y, so i don't think the hardware really stores anything the same way it stores a preset.
here's an excerpt of my live stream last night showing what i tried. it's real-time, not edited down, but i basically always doing something i did a bit of work before that with scene controllers, without good results, because the Recto amp model won't clean up at all... as expected. and then i started eating pizza, so i started this video after that
switches 1 and 2 are changing presets.
switch 5 is switching Amp XY specifically
switches 3 and 4 are changing S1 and S2
i'm REALLY excited to be using Beam.pro as my livestream platform and glad i held off just a bit from declaring Hitbox as my new platform. Beam.pro is awesome, only 3 seconds of video delay, great features for streams, and they are working on a protocol with only 250ms of video delay! which is basically INSTANT. it's very new, but has been much more stable than Hitbox (also offers a 3 second only delay, but a bit buggy).
Isn't it kind of simple? If the gear doesn't work for you, it doesn't work for you?
Just because a fender Bassman has the tone soooooo many players out there seek doesn't mean it'll work for me and what I want it to do. For the record, I can't get a usable tone (I like) out of a real one, in any year, any model. Is it fender's problem? Should I complain to fender? No, of course not, I just find something else that works for me.
If the audio dropout is a dealbreaker, so be it. Life's too short to complain about 10-20ms dropouts, find what works for you and play some guitar and write some great music
What I did instead was set reverb to where I want it on dirty, then filled in the clean with more delay in the mix to create the same ambience I was trying to create with adding more reverb in the first place. Problem solved. (I also changed my verb to the small plate verb to squeek out more CPU).
awesome, that's good to hear!It is DEFINITELY workable now.
Ok, I was able to get some time today to work with the AX8 after watching Chris@AxeFXTutorials.com video. That video made me rethink a lot of how I naturally setup my presets, was very helpful. Thanks dude!
What I learned:
1) Almost all of my presets were in need of optimization/tuning. My initial approach was "Hey, if I don't hit 100% and get the warning I must be ok" wasn't the best idea. I recommend everyone keep their CPU below 90% as Chris suggested. The lag gets way worse if its over 90%.
2) NEVER do an X/Y state change on a reverb block at the same time as an amp block X/Y. Ever. Lol. That was the culprit. The reason I had done this was because I generally prefer more verb on my clean tone, than my dirty tone. What I did instead was set reverb to where I want it on dirty, then filled in the clean with more delay in the mix to create the same ambience I was trying to create with adding more reverb in the first place. Problem solved. (I also changed my verb to the small plate verb to squeek out more CPU).
3) Press/Hold for X/Y has to be set to "Disable" for me. I'm just to used to having an effect engage on the downstroke of pushing the switch (instead of the up). I believe when this is enabled you basically miss out on some time while you are waiting for your foot to come back up and it exaggerates the issue. It makes the fade between the amp block seem worse simply because it is starting later than you intend it to.
I'd still love for the change to be more immediate when switching amp X/Y, but it's pretty darn fast now, and without an audible drop in the signal. It is DEFINITELY workable now.
That's... unfortunate.Well the workaround for all those workarounds without compensating here and there, having to cut things you don't want to; is the AxeII
agreedThat's... unfortunate.
That's... unfortunate.