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

Did you ever get yours up and running?

I finally got an Apple camera connection cable and was able to test the Midi Macros app with my iPod touch. It works like a charm! Once you create the macros (name them for each patch, set the midi message to PC and the number for your patch), you can just tap the macro and the pedal switches to that patch. No scrolling at all. You can create "presets" with different macros and switch between them, say one preset per set/song list with only the macros you need for that set. I haven't used it enough to see how fast it drains my battery, but I got the more expensive cable that has the usb and another lightning port so I can actually plug it in with a charger if necessary. All I am using is the iPod, camera cable, Roland UM-1 into the FI.
 
I finally got an Apple camera connection cable and was able to test the Midi Macros app with my iPod touch. It works like a charm! Once you create the macros (name them for each patch, set the midi message to PC and the number for your patch), you can just tap the macro and the pedal switches to that patch. No scrolling at all. You can create "presets" with different macros and switch between them, say one preset per set/song list with only the macros you need for that set. I haven't used it enough to see how fast it drains my battery, but I got the more expensive cable that has the usb and another lightning port so I can actually plug it in with a charger if necessary. All I am using is the iPod, camera cable, Roland UM-1 into the FI.
Cool, glad it's working for you. I've had a frustrating time setting up all the macros and then not knowing how to save it. So I've had to completely rebuild them about 5 times now. :rage: I think I've got it now though. After doing all the editing I have to hit the "New Preset" button and then I can save it as something. Seems like they should just have a save button though. Also, are you having things entered automatically in the hex fields?
 
Yeah, that happened to me a couple times before I figured it out. Had to re-do everything. I was just testing, though, so I didn't have that many to do over. There are a couple "save" steps for each macro. It's not necessarily intuitive at first, especially with no manual to reference. None I could find anyway. And yes, when I put the PC number I want in the dec field, it automatically puts something in the hex field. Not sure what it is, but it seems to work so I haven't messed with it. So far, seems to work great. It might just be the answer for a lot of us with patch switching "issues." And all for a dollar! :hyper:
 
  • Like
Reactions: Jonny5bass
Hi Folks,

I have a slight issue with the Future Impact pedal that was briefly addressed, much earlier in this thread.

There is a serious phase issue when stacking VCOs in the pedal editor.
The low frequencies disappear and will cycle in and out every few seconds (even when playing staccato and the notes are not held!).

Hold a note, or play a series of 8th notes, and listen to the low frequencies swell, then dip.....

I've attached an image of a patch/setting that you can test for yourself, and hear the low frequencies frequently swelling and alternating in volume.

The issue seems to be reduced when the 'beat' sliders are all set to 0, but then the sound becomes very thin .
I've already tried varying the waveforms, volumes, and tunings between each VCO, but the dip & swell persists.

This issue definitely revolves around any adjustment of the 'beat' sliders (is this dip & swell supposed to happen?).

Has anybody else encountered this?
Is this a bug?
What can be done to alleviate this, without taking the 'life' out of a sound?

Thanks.......


3413578-2cb55ec101f2ace51d3af3629262c253.jpg

future-impact-patch-image-jpg.jpg
 
It's been a while since I did any patch creation, but what you're likely experiencing is the competing waveforms causing phasing issues. Enabling multiple VCO but setting them each to a slightly different fine/beat is a classic way to create that chorusy synth sound.

You're already on the right track for figuring it out. Disable Noise and VCF entirely so you can hear the raw VCO. Turn Fine and Beat both to zero, set only a single waveform type, like SAW, in each VCO block. Set all VCO volume to zero. Now turn one single VCO volume up, but not past 30. Turn up a second VCO. Before you experiment with the coarse/fine/beat settings, experiment with the VCO volume to see how the overall clipping affects. You can clip each VCO block individually, or the sum of the VCO blocks. Now set one of the VCO blocks to -12 coarse. You should get more girth in the low end. Now play with the VCO block volumes again to see how they compete/compliment/clip. Still with just two VCO blocks enabled play with the fine/beat. And baby step your way through the VCO parameters, it should keep you busy for a few hours. :)

Eventually you can move onto VCF, LFO, and all that fun stuff.
 
Awesome post gastric! Thanks! :thumbsup: As much as I have played with the FI (although not so much lately), I still don' have a real good handle on creating my own sounds. This breakdown is great. I have a week off between Christmas and New Years, plan to play around with this a bit. Hopefully many bits! :D
 
I think it might be user error, of sorts... it seems if you scroll straight out of RS there is no problem, but if you turn the EDIT dial while first in RS you are going to get a reset even if you can set it back to zero (which it doesn't seem you always can). I always keep my parameter leftmost and my NOTE OFF at 4 so it's easy to see when it's reset.

If you turn the dial while you are in RS, then you performed a reset unconditionally, what you cannot undo with turning the dial back. It seems this was the problem.

Andras Szalay
 
Last edited:
Question, is there something I need to change in the editor to make the pedal be able to "hear" program change commands? The person I bought it from switched all the patches to only listen to channel 6 but I don't see on the editor where that is even shown or how to change it.

You do not have to change anything in order to activate "hearing" Program Change commands, this is always active. However, of course, according to the active MIDI channels, which could be any of 1...16, or OMNI for all channels. In the moment you cannot change this in the editor (although we will include this in later version), but you can set it when you configure the FI (see on page 14 of the manual).

Andras Szalay
 
  • Like
Reactions: Jonny5bass
Ok, Huston, I've got a problem. I have an M Audio Midi Uno, I conncet the FI with the computer, the USB Led flashes on the Uno, but somehow in the editor software nothing happens, no program name, and the counter is on 00. I change programs on the FI, but on the software nothing happens.
In the MIDI settings I've set the input and output to M Audio Uno. What else can I do?
 
Ok, Huston, I've got a problem. I have an M Audio Midi Uno, I conncet the FI with the computer, the USB Led flashes on the Uno, but somehow in the editor software nothing happens, no program name, and the counter is on 00. I change programs on the FI, but on the software nothing happens.
In the MIDI settings I've set the input and output to M Audio Uno. What else can I do?
And the M Audio Uno should be fine, I've just made a software update with it on a Nova System.
 
Ok, Huston, I've got a problem. I have an M Audio Midi Uno, I conncet the FI with the computer, the USB Led flashes on the Uno, but somehow in the editor software nothing happens, no program name, and the counter is on 00. I change programs on the FI, but on the software nothing happens.
In the MIDI settings I've set the input and output to M Audio Uno. What else can I do?

Ok have you double checked the Uno is plugged the right way round into the FI? I've made that mistake...
 
Ok, Huston, I've got a problem. I have an M Audio Midi Uno, I conncet the FI with the computer, the USB Led flashes on the Uno, but somehow in the editor software nothing happens, no program name, and the counter is on 00. I change programs on the FI, but on the software nothing happens.
In the MIDI settings I've set the input and output to M Audio Uno. What else can I do?
The FI does not communicate with the editor that way. In other words, changing programs on the FI pedal will have no effect on the editor. You must load a patch in the editor using the load button, and then selecting the patch you want to load from your computer.

Also, you should see dashes -- in the display of the FI which indicates they you are connected to the editor. If you don't see -- on the FI, then you are not connected.
 
The FI does not communicate with the editor that way. In other words, changing programs on the FI pedal will have no effect on the editor. You must load a patch in the editor using the load button, and then selecting the patch you want to load from your computer.

Also, you should see dashes -- in the display of the FI which indicates they you are connected to the editor. If you don't see -- on the FI, then you are not connected.

I see a guy on the youtube, who is just changes the patches on the FI by clicking on the editor. You can see the miracle here:

I've seen the dashes 2 times, didn' know what are they, pushed buttons on the FI, and then they have vanished, but haven't came back. :) I don't know why they appeared, becouse I've been trying the connection already a while, and "suddenly" the dashes appeared, but didn't know what was the reason. Thanks for the response, I'll try again.
 
I see a guy on the youtube, who is just changes the patches on the FI by clicking on the editor. You can see the miracle here:

I've seen the dashes 2 times, didn' know what are they, pushed buttons on the FI, and then they have vanished, but haven't came back. :) I don't know why they appeared, becouse I've been trying the connection already a while, and "suddenly" the dashes appeared, but didn't know what was the reason. Thanks for the response, I'll try again.


Lol not a miracle. That is how the editor works as I stated in my previous post. You can scroll through a folder of patches on your computer with the editor.

No need to touch the FI when using the editor. He even mentions that in the video. When using the editor, All of the program switching and editing is done with the editor. Make sure when you finish creating or editing a program you save it to your computer as a backup, or for future tweaking. Then make sure you write the program to the FI so it stores in the FI. Be mindful of the name format of the program file when choosing a name and saving.
Ex. 85basssynth.prg
 
Lol not a miracle. That is how the editor works as I stated in my previous post. You can scroll through a folder of patches on your computer with the editor.

No need to touch the FI when using the editor. He even mentions that in the video. When using the editor, All of the program switching and editing is done with the editor. Make sure when you finish creating or editing a program you save it to your computer as a backup, or for future tweaking. Then make sure you write the program to the FI so it stores in the FI. Be mindful of the name format of the program file when choosing a name and saving.
Ex. 85basssynth.prg
Hey, it works! Now I start to realise, how it works. I thought, it will load the patches inside the FI, and I can start to edit them. Thanks for the help!
 
I have always wanted to hit a sustain pedal on my bass. Nothing has particularly worked. However, if I can get patch which will give a nice solid sound then if I can programme (that is a BIG if in my case) my Sonnus Voluum pedal to output MIDI sustain things then I can get my desired long notes? If this is the stupidest idea ever then if you can gently ignore it that would be cool :)
 
If there is another free CC it would be nice to have one that toggles the on/off state rather than requiring a certain value to be "on" and another to be "off." For example, CC#100, any value > 0 would be equivalent to hitting the right footswitch.