• 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 free Log in
    Want zero display ads or expanded classifieds tools? Compare plans.

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

#7,641
  • Like
Reactions: JRT, mdalamond, RHA III and 2 others
#7,642
If any one has any input on this problem, please chime in.

I have successfully loaded patches onto my FI once in the past.
I can successfully download patches from the FI to the manager.
I can successfully do a firmware update.

But now - I cannot load patches to the FI
The FI patches that are on there aren't all working; some work, some are just all dry bass, some mute all sound.
I can download from the FI and all patches show up on the Manager.

I am using Roland Midi cables (firmware update works)
Midibeam Out to FI Midi In
Midibeam In to FI Midi Out

I have tried different combinations of power cycling FI, connecting FI before opening Editor, Reconnecting Midibeam.

I receive a message that says That "no FI is present or there is a communication error". I also receive a message sometimes that says the process has "Finished Successfully", but the patches aren't on there correctly. At this point I'm trying to load the original patches back on just as a test.
 
#7,643
PaulD3 said:
If any one has any input on this problem, please chime in.

I have successfully loaded patches onto my FI once in the past.
I can successfully download patches from the FI to the manager.
I can successfully do a firmware update.

But now - I cannot load patches to the FI
The FI patches that are on there aren't all working; some work, some are just all dry bass, some mute all sound.
I can download from the FI and all patches show up on the Manager.

I am using Roland Midi cables (firmware update works)
Midibeam Out to FI Midi In
Midibeam In to FI Midi Out

I have tried different combinations of power cycling FI, connecting FI before opening Editor, Reconnecting Midibeam.

I receive a message that says That "no FI is present or there is a communication error". I also receive a message sometimes that says the process has "Finished Successfully", but the patches aren't on there correctly. At this point I'm trying to load the original patches back on just as a test.
Click to expand...
That sounds very much like what happens if you don’t flush the internal memory after updating from v2.xx to v3.xx. Make sure you write all 99 factory v3.5 patches first to clear out the memory. I suggest doing this via the online updater tool.

Presuming you are using the receiver as an interface, that it is connected via usb to your computer and that it is selected as the input and output in the FI editor. The transmitter unit must be turned off.

“communication error” is usually what appears when the cables are plugged in the wrong ports.
 
#7,644
FI is new and came with 3.6. Last night updated to 3.61. So I’m assuming the V2/V3 isn’t an issue.

Pretty sure the transmitter is off. Will double check that, thanks.

wouldn’t the fact that the firmware update was successful indicate that the cables are connected correctly. Plus the Manager messages that I’ve “Finished successfully” intermittently.

I believe I’ve saved and tried writing the V3.5 patches properly. Will try again.
 
#7,645
PaulD3 said:
FI is new and came with 3.6. Last night updated to 3.61. So I’m assuming the V2/V3 isn’t an issue.

Pretty sure the transmitter is off. Will double check that, thanks.

wouldn’t the fact that the firmware update was successful indicate that the cables are connected correctly. Plus the Manager messages that I’ve “Finished successfully” intermittently.

I believe I’ve saved and tried writing the V3.5 patches properly. Will try again.
Click to expand...
If it came new from panda with v3.6 then patches should load correctly.

And yes, if you’ve managed the firmware update, cables must be correct.

If you are on a windows pc, make sure any other MIDI usb devices are unplugged as windows only allows a single instance of MIDI usb to be active at any one time.

Another thing to check is that patch names don’t contain special characters as that can cause patches to not transfer. I had to rename a couple of mine before I could get them to load correctly.

I haven’t tried using midiBeam as an interface as I have other interfaces I use. However, I did get some buggy behaviour when I used it wirelessly to control a polysynth so I’m not sure if there’s an occasional issue with data transfer reliability.
 
#7,646
PaulD3 said:
FI is new and came with 3.6. Last night updated to 3.61. So I’m assuming the V2/V3 isn’t an issue.

Pretty sure the transmitter is off. Will double check that, thanks.

wouldn’t the fact that the firmware update was successful indicate that the cables are connected correctly. Plus the Manager messages that I’ve “Finished successfully” intermittently.

I believe I’ve saved and tried writing the V3.5 patches properly. Will try again.
Click to expand...

Isn't MIDI THRU on?
 
#7,648
Midi thru is a setting that determines how midi messages not destined for the FI are handled by midi output. Messages can be passed thru (enabled), or not. Helpful for daisy chaining midi devices, but can also create infinite loops, which presents as an adapter working overtime but not doing what you expect
 
  • Like
Reactions: Kubicki Fan
#7,649
Andras Szalay said:
Isn't MIDI THRU on?
Click to expand...
MIDI THRU was off.

I did some more research on the thread and followed instructions for starting in Boot mode, and wrote the factory files back to FI. After that the synth performed as expected and I was able to write new patches from the editor.

Not sure what glitched but I'm happy to be back in working order.
 
  • Like
Reactions: JRT, Quatschmacher, Randy Ward and 1 other person
#7,650
Hey guys, I have a V1 on the way. Anyone have any advice as I begin to figure it all out in the near future? I have read a lot here and it sounds like I can update the firmware to whatever the current one is for the V3 and I'll be all good. I do need to download the "editor". Thanks all.
 
#7,651
JRT said:
Hey guys, I have a V1 on the way. Anyone have any advice as I begin to figure it all out in the near future? I have read a lot here and it sounds like I can update the firmware to whatever the current one is for the V3 and I'll be all good. I do need to download the "editor". Thanks all.
Click to expand...
Get a Roland UM-One Mk2 interface. Get the correct driver off the Roland website and install it.

Hook up the interface to the computer.

If not on v3.61 when you get the FI then use Chrome and go here and follow all instructions:
Future Impact Firmware Update

Allow it to write the factory soundset too.

Download the editor from here:
Support — MIDI products by pandaMidi
 
  • Like
Reactions: Snake101st, Randy Ward and mdalamond
#7,652
Thanks for all of this. I just tried to download the editor and get this message when opening the .dmg file. Any ideas why? Thanks.
IMG_0465.jpeg


I should ad that I’m on a 2015 Mac with 10.4.6 iOS. Maybe that’s why but seems like it shouldn’t be.
 
Last edited:
#7,653
I should ad that I’m on a 2015 Mac with 10.4.6 iOS. Maybe that’s why but seems like it shouldn’t be.[/QUOTE]
JRT said:
Thanks for all of this. I just tried to download the editor and get this message when opening the .dmg file. Any ideas why? Thanks.
View attachment 5325649

I should ad that I’m on a 2015 Mac with 10.4.6 iOS. Maybe that’s why but seems like it shouldn’t be.
Click to expand...
See here. Basically right-click to open instead.
https://www.talkbass.com/threads/fu...sue-interested.1115025/page-345#post-25375094
 
  • Like
Reactions: JRT
#7,658
JRT said:
Congrats! Did you get the V3? Maybe I should have but I found a new-in-box V1 and I just like the simple graphic better so that's what I got, ha ha. Seems both pedals are the same, the V# just has a different graphic and newer firmware which I can update to anyways.
Click to expand...

They are the same and if you get a Future Compact enclosure, it doesn't matter.
 
  • Like
Reactions: fourstringdrums, JRT and Quatschmacher

Latest posts

Top Bottom
Back