a few new guy questions

paul story

paul story

Member
Hi,

I gigged the FX8 this weekend at a casino for two nights. Things went well, but I had a few problems. I had two delays setup. Everything was fine at home, but when I went to the gig, stepping on the second delay muted the entire unit. Switching presets gave me back the delay for a bit, but then the same problem happened. Was I at the hairy edge of CPU overload? I didn't get a message indicating such. I've never had an effect unit that could run out of CPU power, so this is a bit new to me. Does using both X and Y version of an effect take up for processing power? Is there a list of blocks and their associated processing requirements? I didn't miss my old pedalboard by the second night. Great sound.
 
I'll have a look. Basically, I panicked (I was at a gig) a bit and started deleting blocks and saved the preset, but I think I remember how I had it setup. I'll try and post tonight. Thanks!
 
paul story said:
Hi,

I gigged the FX8 this weekend at a casino for two nights. Things went well, but I had a few problems. I had two delays setup. Everything was fine at home, but when I went to the gig, stepping on the second delay muted the entire unit. Switching presets gave me back the delay for a bit, but then the same problem happened. Was I at the hairy edge of CPU overload? I didn't get a message indicating such. I've never had an effect unit that could run out of CPU power, so this is a bit new to me. Does using both X and Y version of an effect take up for processing power? Is there a list of blocks and their associated processing requirements? I didn't miss my old pedalboard by the second night. Great sound.
Click to expand...
X and Y states are always there. you can't "avoid" switching to the Y value to reduce CPU :) however, the parameter choices can have different CPU usage between the X and Y states, so Y can use more than X or vv.

i'm guessing that a block was set to Bypass type of Mute, and then bypassing the block made everything go silent.

chances are you'll create a new preset but not put the original problem in, so we may never know what the issue is. we'll see :)

i have a list of the FX8 CPU usage per block and type and will share it as soon as i am able.
 
Chris@AxeFxTutorials said:
X and Y states are always there. you can't "avoid" switching to the Y value to reduce CPU :) however, the parameter choices can have different CPU usage between the X and Y states, so Y can use more than X or vv.

i'm guessing that a block was set to Bypass type of Mute, and then bypassing the block made everything go silent.

chances are you'll create a new preset but not put the original problem in, so we may never know what the issue is. we'll see :)

i have a list of the FX8 CPU usage per block and type and will share it as soon as i am able.
Click to expand...

No, I don't think the block was set to mute, because when I momentarily switched between presets (to reload the preset) the delay would come back. I thought it was OK, and turned the delay off, only to discover later in the set when I tried to turn on the delay the pedal muted. I did have an effect in every block. Once I deleted a few blocks the problem disappeared. My concern being no warning of CPU overload. Please post your list when you can. Thanks!
 
paul story said:
No, I don't think the block was set to mute, because when I momentarily switched between presets (to reload the preset) the delay would come back. I thought it was OK, and turned the delay off, only to discover later in the set when I tried to turn on the delay the pedal muted. I did have an effect in every block. Once I deleted a few blocks the problem disappeared. My concern being no warning of CPU overload. Please post your list when you can. Thanks!
Click to expand...

Possible you held the switch too long and it switched to y which had no settings and set to mute? One reason why I'll always have something in y, even if it's the same as x.
 
DavidE said:
Possible you held the switch too long and it switched to y which had no settings and set to mute? One reason why I'll always have something in y, even if it's the same as x.
Click to expand...
Not being used to the "engage on release" idea of the foot switches, I have already done this a couple of times. This is a very good possibility, and knowing no more than I do, would be my guess as well.
 
You must log in or register to reply here.
Back
Top Bottom