• 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?

The biggest problem with the creators of many of today’s pedals is that they assume that everyone has the same technical expertise as they do when in fact most of us are quite simply musicians, not technical gurus.
MXR got nearly everything right on the bass synth. The sounds are top notch and operation is a breeze. If the tracking would have been a lot better the new Future Impact V4 VIP would be a non-factor. We “plug-n-play” guys, which we are many, need help and guidance.

Would someone please produce some in-depth videos on how to download, program and access everything in the V4? I bought the new V4 with the 4.5 update already installed and I’m still lost. Please “dumb it down” for many of us.
I dumbed it down 2 posts before this. Connecting and managing presets is actually not too hard. Its if you wanna program your own sounds and use external controllers with MIDI which the MXR doesn't have. MXR is a synth pedal whereas FI is a synth generator on its own. The Software has 4 VCO,VCF, LFO, Harmonizer and effects like filter chorus Flange distortion etc all that can be applied in various ways which the MXR cannot do. Plug n play MXR yes but limited. FI little more tech for custom sound but very manageable with user and factory presets. If you run into a problem ill do the best I can to help. Cheers!
 
Accidentally loaded an old V3 file to the V4.5 editor. editor refused to open once closed. needed to delete and re-install. Following addendum instruction to go from FM using "HOLD ON/OFF in NOTE OFF , turn to NOTE ON parameter to switch from GLB to InS. Nope. Stays in GLB. have powered down the pedal and still, no movement off GLB.

Ponderous man.
 
Accidentally loaded an old V3 file to the V4.5 editor. editor refused to open once closed. needed to delete and re-install. Following addendum instruction to go from FM using "HOLD ON/OFF in NOTE OFF , turn to NOTE ON parameter to switch from GLB to InS. Nope. Stays in GLB. have powered down the pedal and still, no movement off GLB.

Ponderous man.
If you mean a v3 patch file, that’s no problem; the editor converts it.

The editor refusing to open is usually when you have a MIDI USB conflict in Windows as the latter only allows a single USB MIDI connection at a time. (However I did have one instance of the editor refusing to open but didn’t capture the data to help work out what the issue was.)

To enter global (while pedal is already powered on):
Hold the ON/OFF footswitch until GLb appears in the display.

Press the PROGRAM footswitch.

Set the PARAMETER dial to NOTE-OFF level to see the menu item name.

Use the PROGRAM footswitch to step through the menu. You can only move through the list if you can see the item name.

Turn the PARAMETER dial to NOTE-ON LEVEL to see the value.

Turn the EDIT encoder to adjust the value.

Press ON/OFF to exit Global.
 
theres a series of V4.5 docs on this page. download em all .

But again...there it is.

there is no V4.5 manual listed in the downloads. Its titled "addendum",

Its maddening.
If you open the 4.5 addendum and read the opening bit, it tells you to use it in conjunction with the v4.11 manual.

(I know that’s a cludge but life has been throwing so much crap at me that I didn’t have the time or energy to integrate all the new stuff into a full revision of the manual. This is unfortunate for such a big update, but it’s magnitude is also part of the reason it was difficult to tackle.)

All necessary documentation is built into the editor under the HELP tab.
 
Last edited:
Every time you open the software editor you have to go to MIDI/Preferences tab and make sure it's Input-USB MIDI 0 and Output-USB MIDI.
You don’t need to do this every time. The last-used settings are stored from the previous session.
 
The biggest problem with the creators of many of today’s pedals is that they assume that everyone has the same technical expertise as they do when in fact most of us are quite simply musicians, not technical gurus.
MXR got nearly everything right on the bass synth.
The problem you are encountering is that the FI is an actual synth with real editabilty. The MXR is easy because it just has a few parameters that can be changed, and thus a very limited sound palette. It also has just one oscillator, no ability to name or share patches, can’t be controlled via MIDI, and can’t be updated.

Two sets of features and compromises for different audiences. To me, the MXR was easy to get started with, but frustratingly limited after that. The frustration curve is kind of reversed with the FI, so I’d suggest sticking with it, it will get easier.
 
please produce some in-depth videos on how to download, program and access everything in the V4?

Please “dumb it down” for many of us.
I’m not sure these two approaches are entirely compatible. “Dumbed down” cannot truly be “in-depth”.😀

However, clarity is possible.
 
If anyone wants a one-on-one video call to go through some features, drop me a PM and we can work something out.
You are now my new best friend.

I have opted to trade with another member for the older chassis. I prefer it as the display can be seen while toggling through presets, and I can also avoid accidentally stepping on the editing knob.

Once I receive the older chassis unit, I would be grateful to spend a little time on a Zoom call with you. I think a brief training will answer all my questions. I’ve already had success in connecting the pedal to the editor and simply want to discuss how to Have what is happening in the editor reflect on the pedal in real time if that is an option. I will be in touch and thank you.
 
want to discuss how to Have what is happening in the editor reflect on the pedal in real time if that is an option.
Not sure what you mean here. There’s nothing meaningful in the pedal display when adjusting parameters on the editor.

When connected to the editor, you need to use the editor’s navigation controls to move through presets, not the pedal’s switches.
 
  • Like
Reactions: edwinhurwitz
The biggest problem with the creators of many of today’s pedals is that they assume that everyone has the same technical expertise as they do when in fact most of us are quite simply musicians, not technical gurus.
Within the confines of the limited display, ever-shrinking code space and the existing feature set, I have tried with every update to suggest ways to keep the interface undaunting and user-friendly. My role is partly kind of an intermediary between the programmer and the end users.

The limitations of the screen do make it tricky to handle all the pedal can do and it is a constant compromise. I do hope that any eventual hardware revision is built around a nice OLED screen with more knobs (the Bananana Quimera is a good example of this, but its sound engine doesn’t wow me).
 
Not sure what you mean here. There’s nothing meaningful in the pedal display when adjusting parameters on the editor.

When connected to the editor, you need to use the editor’s navigation controls to move through presets, not the pedal’s switches.
The display on the pedal does not reflect any change in choices in the editor. Meaning, if I select a specific preset on the editor, I want to be able to demonstrate it to myself using my instrument in real time. When I noticed no change on the display of the pedal, while choosing different presets, I assumed no sound differences would have been heard. I will attempt to demo the presets by selecting them in the editor.
 
Meaning, if I select a specific preset on the editor, I want to be able to demonstrate it to myself using my instrument in real time.
You can absolutely do this already. If you are connected to the editor and it shows - - then any changes you make in the editor will be immediately heard on the pedal.
 
If you want to do this (setlist programming) via the editor you kind of can at the moment but it’s a bit of a workaround.

Reset the setlist to default via the pedal’s “ini” menu.

Put the pedal in VA mode (either via the editor or pedal).

Press “Download to FI”. Rearrange the VA patches into which of the 99 slots you want them to appear. Then press “upload to FI”.

Switch to FM and repeat the above process.

Obviously you will out your desired VA and FM patches in different slots from each other. Make a note of which slots you want the pedal to play a VA patch and which to play an FM one.

Now put the pedal in Setlist mode and go to each step and set whether it should be VA or FM by pressing the encoder (edit dial).

By default, setlist 1-50 is VA, 51-99 FM.

There might be a bug between editor and setlist mode. I haven’t checked this as currently the editor isn’t really designed to work in setlist mode.

Again I ask, how are you changing patches. I understand you are connected to the editor but running the pedal in setlist mode. Playing the editor keys is probably reverting to reading the non-setlist mode patch order, hence why you are experiencing odd behaviour.

@Andras Szalay I cannot check if FM mode is forcing the pedal ON when using setlist until later next week.
Found the FI editor bug, not related to set-list mode at all, it's a backed-in FM mode issue.

My OS: Windows 11 64bit
My USB to MIDI: Laptop USB -> 2m USB extension cable -> midiBeam 4Control (with BOSS EV-30 Expression Pedal and Hotone FS-1 Ampero Switch) MIDI I/O -> MIDI O/I on FI V4 VIP v4.5.

1. I use midiBeam 4Control to connect the FI v4 VIP v4.5 to my laptop with FI editor V4.5.
2. The FI v4 VIP is ON and in VA mode. Display showing "01"
(I can hear sounds from FI editor keyboard and my own bass when tracking)
3. Now In the FI editor we're in FM mode, example download FM in banks menu.
4. The display now shows "0.1"
5. Play the FI editor keyboard

1775898551227.png

Pressing that piano key makes the note sound, but more importantly also turns the patch number down on the Pedal.
The display now shows "9.3" after pressing a few times.

Now Pressing this piano key:
1775898668103.png

Makes the note sound, but more importantly turns the pedal on and off.

So it was not time based at all it's when playing these notes.

All other piano keys behave normally.

Loading a patch, so the pedal goes into connect mode and the display shows "--≡" makes no difference.

Also the FI editor still gets some GUI startup issue from time to time, so I have to completely uninstall and new install to fix. So far the repair never worked.

These issues might just be my specific setup with Windows 11 64bit and midiBeam 4Control?

The set-list mode on switching with FM patch is still that issue, but not an issue when in FM mode. I think it's still related to something specific in the new set-list mode. My guess it's not saving on/off states etc., so just forces the on state.
 
Last edited:
Working in design/media I think everyone needs to realise that “some videos” or online instruction is not a small or cheap job.
It’s whole synth and fairly complex - no amount of videos is going to make it less complex - but just maybe help you learn… but everything is set out and understandable in the manual - you just have to go slowly, read it carefully and get your head around it.

go step by step - use the contents or search and just get on with it!