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

I will say that earlier updates worked for me using an IK Multimedia iRug DUO and then they stopped working at some point and I got myself a Roland um-one mk2 and I was able to update/edit again. The Roland seems a better solution across the board if you have pedals that run MIDI. I use it w my Boss ES-8 and it works way better than the IK ever did (I'd get tons of errors).
 
I will say that earlier updates worked for me using an IK Multimedia iRug DUO and then they stopped working at some point and I got myself a Roland um-one mk2 and I was able to update/edit again. The Roland seems a better solution across the board if you have pedals that run MIDI. I use it w my Boss ES-8 and it works way better than the IK ever did (I'd get tons of errors).

I tried the Hosa, it didn't work. I should have the iConnectivity MIO in a couple of days. I asked about the Mio in the FI Facebook group and someone said that it did work, so I'm hoping. I only picked that one because it's the only one Sweetwater had in stock. If it doesn't work, I'll ship it back and source a Roland from somewhere.

On an exciting note, Darren emailed and said my FI Compact housing should be shipping out this week! Yay.
 
I've been editing, writing sound patches that i've downloaded from the program database with no problem at all. suddenly now i can't seem to open the FI Editor, the app always closes by itself when i try to open it. Any help guys?

running on macbook pro mid 2012 with sierra ver. 10.12.6
firmware 3.03
 
I've been editing, writing sound patches that i've downloaded from the program database with no problem at all. suddenly now i can't seem to open the FI Editor, the app always closes by itself when i try to open it. Any help guys?

running on macbook pro mid 2012 with sierra ver. 10.12.6
firmware 3.03
Do you have any other programs/browsers which are using the same midi device that the editor was set to use?

Read further back in this thread (or use the search function) as I’m sure there was someone else who had this problem and I posted a photo with some tips about how to get it working.
 
Do you have any other programs/browsers which are using the same midi device that the editor was set to use?

Read further back in this thread (or use the search function) as I’m sure there was someone else who had this problem and I posted a photo with some tips about how to get it working.

Thanks for the help. Turns out i needed to uninstall the editor, using cleanmymac, now everything is working fine. Looking forward for more of your awesome sounds!!
 
Last edited:
  • Like
Reactions: Quatschmacher
Thanks for the help. Turns out i needed to uninstall the editor, using cleanmymac, now everything is working fine. Looking forward for more of your awesome sounds!!
Glad that helped and you got it running.

Have you downloaded all the ones from the file share site?
 
I don't know if this is the right thread for this, but...

I have a Casio keyboard power supply, the label says 9v, 1000ma, center negative, etc... But I measure with a voltimeter and it gets 12.6v unloaded... As I add 1 pedal to the chain it drops a little, 3 or more pedals drops about 9.5~9.7...

It is safe to use this power with Future Impact?

Thanks
 
I don't know if this is the right thread for this, but...

I have a Casio keyboard power supply, the label says 9v, 1000ma, center negative, etc... But I measure with a voltimeter and it gets 12.6v unloaded... As I add 1 pedal to the chain it drops a little, 3 or more pedals drops about 9.5~9.7...

It is safe to use this power with Future Impact?

Thanks
Do not use any power supply that is not a fixed, regulated 9V. We had a few repair cases where customers used the FI with higher voltage, and the circuit burned out. Do not risk that.

Andras Szalay
 
Hi!
I'm making an external midi controller for FI, and I can change programs with "shortcuts" in this external controller... Also I can "read" which program is selected in FI and shows it in a external lcd...

Well, almost done... But I would like to know if it's possible to FI sends the "name" of the program and How I can read it...
Below a photo of my current "endeavour", the "FX : XXX" still a bogus text, where I would like to write the actual name of FI program.
visor_FI.jpg

Thanks
 
Last edited:
Hi!
I'm making a external midi controller for FI, and I can change programs with "shortcuts" in this external controller... Also I can "read" which program is selected in FI and shows it in a external lcd...

Well, almost done... But I would like to know if it's possible to FI sends the "name" of the program and How I can read it...
Below a photo of my current "endeavour", the "FX : XXX" still a bogus text, where I would like to write the actual name of FI program.
View attachment 3834410
Thanks

Excellent idea. I wonder if either the program files or the FI store this information (they don’t come back with patchnames on retrieval, just numbers). If not, I’ve also wondered if this kind of useful info can be stored in the header of a patch file as metadata, along with other useful info (eg the patch’s creator, or the sound category, like pad, bass, or lead). Massively useful information to manage what are now folders full of homogenous program files.
 
Hi!
I'm making a external midi controller for FI, and I can change programs with "shortcuts" in this external controller... Also I can "read" which program is selected in FI and shows it in a external lcd...

Well, almost done... But I would like to know if it's possible to FI sends the "name" of the program and How I can read it...
Below a photo of my current "endeavour", the "FX : XXX" still a bogus text, where I would like to write the actual name of FI program.
View attachment 3834410
Thanks

Excellent idea. I wonder if either the program files or the FI store this information (they don’t come back with patchnames on retrieval, just numbers). If not, I’ve also wondered if this kind of useful info can be stored in the header of a patch file as metadata, along with other useful info (eg the patch’s creator, or the sound category, like pad, bass, or lead). Massively useful information to manage what are now folders full of homogenous program files.

In v3 the filenames are indeed stored as part of the patch data. @Andras Szalay might be able to shed light on where the info is stored.
 
When you import programs with FI Editor, (at least since v3.0, I never use FI before that) the names came with all parameters. But I can't figured out how capture this excepting with FI editor.
It'll be part of the sysex data I presume. Run the output of the editor into a midi monitor and see what gets spat out when you change a patch.
 
It'll be part of the sysex data I presume. Run the output of the editor into a midi monitor and see what gets spat out when you change a patch.
@Wagner Felix actually, more sensible might be to monitor the messages that are sent when writing a patch to the pedal or when writing a patch from the pedal to the computer.
 
On a different point, is there a way to change patch with CC messages? I've found the up/down ones but what I really want is direct patch select? I've switched my Soleman for a Boss Ms3 which has a similar footprint but adds a bunch of effects. It doesn't however allow you to assign PC messages to buttons only patch changes. I want to use it in manual mode one patch per song. Cheers.
 
On a different point, is there a way to change patch with CC messages? I've found the up/down ones but what I really want is direct patch select? I've switched my Soleman for a Boss Ms3 which has a similar footprint but adds a bunch of effects. It doesn't however allow you to assign PC messages to buttons only patch changes. I want to use it in manual mode one patch per song. Cheers.
There are no CC commands for directly selecting a patch.

Does the MS3 really not allow PC messages to be assigned as one of the four allowed MIDI messages per patch? That seems like a massive oversight.