• TalkBass has been independent since 1998. Add your voice.
    Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
    Join freeLog in
    Want zero display ads or expanded classifieds tools? Compare plans.

Future Impact now available!! WAS: deep impact reissue!!! interested?

Mine has done this as well. Sometimes it's on the last patch I used, sometimes not. Something else that has been happening with mine is the modifiers not resetting when a new patch is saved in a particular slot. I'll have a patch that I have adjusted parameters on the pedal, I'll save a new, entirely different patch in that slot, and the parameters won't all be reset to 5. I have to change them manually. Has this happened to anyone else?
 
Has anyone experienced the FI not starting on the last patch you were using? For the last couple of weeks mine always seems to go to bank 3 patch 0 no matter where I was... is there an internal battery that might have been a dud one? (this happens with batteries from time to time as I'm sure we all know)
the settings on the f.i. are persistent without any power (some kind of eeprom i guess). so that is not the issue. i have my f.i. not here a.t.m. so i cannot check, but i am pretty sure it does not use the sound, that you played last for startup. i can't remember how you set the startup sound though....
 
the settings on the f.i. are persistent without any power (some kind of eeprom i guess). so that is not the issue. i have my f.i. not here a.t.m. so i cannot check, but i am pretty sure it does not use the sound, that you played last for startup. i can't remember how you set the startup sound though....

Interestingly the manual says a reset sets the startup sound to patch 1, but I can't find any other reference to it... and that didn't seem to happen in my case anyway!
 
At the bottom of pg. 2 in the quick start guide it says the pedal defaults to the last preset saved. Ex: modify preset 65, save it, power down, it will go to preset 65 when you power back up again regardless of what preset you were on when you powered down. Doesn't make a whole lot of sense in my mind, but I tried it and it does work that way.
 
  • Like
Reactions: BIG97BEN and lokki
At the bottom of pg. 2 in the quick start guide it says the pedal defaults to the last preset saved. Ex: modify preset 65, save it, power down, it will go to preset 65 when you power back up again regardless of what preset you were on when you powered down. Doesn't make a whole lot of sense in my mind, but I tried it and it does work that way.
and i was looking at the manual, but forgot the quick start guide :-) i think it makes sense, since it's nicer to have a persistent startup patch instead of the last one used. but that may be different for others.
 
and i was looking at the manual, but forgot the quick start guide :) i think it makes sense, since it's nicer to have a persistent startup patch instead of the last one used. but that may be different for others.

Yes I like to always start on the same one... it's working for me now so I guess just user error before :)
 
Also easy to achieve just by turning the input control to zero... having it footswitchable or midi-selectable would be great of course :)

I think that approach is far from easy (I've tried it live and its a lot of hassle), you need a blender pedal, more cables, reach for the pedal to set the input to zero every time you want independent synth and bass sounds. It would be awesome just to set in the editor the source of the trigger per preset. I think its a waste for such an advanced pedal not to use all those little features.
 
I think that approach is far from easy (I've tried it live and its a lot of hassle), you need a blender pedal, more cables, reach for the pedal to set the input to zero every time you want independent synth and bass sounds. It would be awesome just to set in the editor the source of the trigger per preset. I think its a waste for such an advanced pedal not to use all those little features.
what would you expect from the future impact in such a situation, where you trigger the pedal from a midi source? mix the bass signal with the synth signal and send it to the output? or mute the bass signal completely?
 
Also, in this hypothetical example, are we talking about a Geddy Lee-level talent who is playing bass with the fingers and a MIDI-controlled foot keyboard like a Softstep?
 
Also, in this hypothetical example, are we talking about a Geddy Lee-level talent who is playing bass with the fingers and a MIDI-controlled foot keyboard like a Softstep?

Not sure I'd compare myself with Geddy Lee in a million years (!) but with minimal practice this setup actually isn't that hard to manage... one octave foot controller for drone notes though the FI, higher and busier stuff on un-synthed bass guitar. Easy :)
 
what would you expect from the future impact in such a situation, where you trigger the pedal from a midi source? mix the bass signal with the synth signal and send it to the output? or mute the bass signal completely?

A mix both signals, that way you could even play 2 different things. I really think it would be a super usable feature that could expand even further the musical possibilities of the pedal.

I'd personally lobby for a per-patch input source selection. Simple, easy to comprehend, no worries about competing input triggers.

That's exactly what I don't like the "Competing Input Sources".

Also, in this hypothetical example, are we talking about a Geddy Lee-level talent who is playing bass with the fingers and a MIDI-controlled foot keyboard like a Softstep?

Could be that or you just have a MIDI Sequence running from a Laptop or an MPC.
 
i would also like this feature. but i don't know how much work it would be to separate clean blend from the synth-input (software wise). this could be quite a big change in the code...

i like the idea of selecting the input on a per patch-basis. will submit to andras :-)
 
  • Like
Reactions: ficelles