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

[Quatschmacher]

Just had a crack at learning this. Using patch 86.


Realised I was playing one note in the wrong octave. Fixed now.
[Invalid or Expired Link Removed]

 

[maisbass]

I’m so disgusted. I finally sat down to update to v3. Ninety minutes later and I still can’t update. It shouldn’t be this hard and quirky. I’ve tried on both PC and Mac with three different midi interfaces.

Roland um one
Irig midi
Iconnectivity


I also tried with the editor and through the browser on both PC and Mac. Each platform recognizes my midi devices. Chrome browser on both platforms recognize my midi devices but fail when I try to update. I receive the lost communication error. The editors on both platforms do not see my FI. No idea why when my computers see the interfaces.

My midi cables are tested and working.

As you all know I have made many patches before using all the equipment stated above. I’m starting to wonder if it’s an issue with my pedal even though my pedal functions perfectly for performance. All I know is I lost valuable time and I have a ton of songs to learn for this weekend. So disappointed in this outcome. Hopefully I will be able to revisit this next week.

Ugh.

 

[Bassheart365]

I’m so disgusted. I finally sat down to update to v3. Ninety minutes later and I still can’t update. It shouldn’t be this hard and quirky. I’ve tried on both PC and Mac with three different midi interfaces.

Roland um one
Irig midi
Iconnectivity


I also tried with the editor and through the browser on both PC and Mac. Each platform recognizes my midi devices. Chrome browser on both platforms recognize my midi devices but fail when I try to update. I receive the lost communication error. The editors on both platforms do not see my FI. No idea why when my computers see the interfaces.

My midi cables are tested and working.

As you all know I have made many patches before using all the equipment stated above. I’m starting to wonder if it’s an issue with my pedal even though my pedal functions perfectly for performance. All I know is I lost valuable time and I have a ton of songs to learn for this weekend. So disappointed in this outcome. Hopefully I will be able to revisit this next week.

Ugh.

Sorry to hear. Anyone else having these problems? I'm on the fence about updating to 3.0. I have a lot of presets, including some of yours, that I depend on regularly for my cover band.

 

[fivestringgecko]

I finally updated to 3.0 as well. Fortunately, my experience went a little better than @maisbass, with a fairly big "however..." I got my FI updated pretty quickly and got my presets re-imported in the .pr3 format, but now I'm noticing a little clipping in patches that haven't had any previously.

The However:

When I updated my patches, I hit the Write All thinking it would just load the 15 patches in the selected folder (my cover band patches) into the respective slots on my pedal. It gave me a message that there were gaps and I should hit cancel to skip, so that's what I did. It took a while to think, so I re-wrote all my cover band patches to my Impact individually just in case, because I wasn't sure what that was about. As it stands now, my cover band patches are working (with some minor clipping), but none of the factory patches are working correctly... it's like they're empty, barely or no sound comes through on some or most of them.

@Bassheart365, I'd suggest holding off on updating since your FI gets heavy gig use. I've got a gig tomorrow night and my main personal patches are working at the moment, so I don't want to tempt fate further. I'll get through the gig tomorrow night and do some more exploration... probably put my main Impact back to 2.22 which I know works, and experiment with my 3.0 on my backup. First world problems of course, but frustrating nonetheless.



5sg.

 

[Bassheart365]

@Bassheart365, I'd suggest holding off on updating since your FI gets heavy gig use. I've got a gig tomorrow night and my main personal patches are working at the moment, so I don't want to tempt fate further. I'll get through the gig tomorrow night and do some more exploration... probably put my main Impact back to 2.22 which I know works, and experiment with my 3.0 on my backup. First world problems of course, but frustrating nonetheless.

Please update re your experience. Thanks

 

[fivestringgecko]

Please update re your experience. Thanks

Well, it was bugging me, so I took another whack at the pinata... I just tried loading my patches onto my backup FI, with a clean install of 3.0 and all factory patches confirmed working.

I avoided the WRITE all button this time and loaded my patches individually, and they worked again with the light clipping, but this time all the factory patches were replaced just with a dry bass signal. I reloaded ALL the factory patches using the WRITE ALL button, reset my FI and confirmed everything was back to original 3.0 and working. Then I loaded just one of my personal patches, reset my FI and everything was still working. So, just for kicks, I loaded my personal patches again, but went slower this time. (like, load a patch, stop wait a few seconds, load another patch, etc). I wouldn't think it would make a difference, because the write all function went quite quickly. Maybe I was just going too fast when loading individually? Now both personal and factory 3.0 patches are working on my backup FI.

Moving back to my main FI, I followed the same process... reloaded all 3.0 patches via the WRITE ALL, reset, confirmed, etc etc. Selected a different directory to load my last three patches, and... editor crashed. This was a little different, because when I loaded the last three on my 2nd FI, I navigated to the other folder AFTER hitting the WRITE ALL button. This time, I loaded the first twelve, then tried selecting the different directory through Editor's file menu. Had to restart my PC to load the last three, but achieved success!

All personal patches loaded and all remaining factory patches working on both Impacts.

To satisfy curiosity about the light clipping, I loaded 2.22 back on my 2nd FI to see if that solved the issue. Reset, and... no sound. A quick WRITE ALL of all 1.00 sounds via the 2.22 Editor, reset, and all factory 1.0 sounds working. Loaded my personal patches individually, and everything is working on 2.22 as well.

I'll have to do some more troubleshooting to find that pesky clipping issue is because it's still there even in 2.22, but all patches loaded and working on both Impacts in 3.0. Very strange about the factory patches disappearing after loading personal ones.

5sg.

 

[Quatschmacher]

Well, it was bugging me, so I took another whack at the pinata... I just tried loading my patches onto my backup FI, with a clean install of 3.0 and all factory patches confirmed working.

I avoided the WRITE all button this time and loaded my patches individually, and they worked again with the light clipping, but this time all the factory patches were replaced just with a dry bass signal. I reloaded ALL the factory patches using the WRITE ALL button, reset my FI and confirmed everything was back to original 3.0 and working. Then I loaded just one of my personal patches, reset my FI and everything was still working. So, just for kicks, I loaded my personal patches again, but went slower this time. (like, load a patch, stop wait a few seconds, load another patch, etc). I wouldn't think it would make a difference, because the write all function went quite quickly. Maybe I was just going too fast when loading individually? Now both personal and factory 3.0 patches are working on my backup FI.

Moving back to my main FI, I followed the same process... reloaded all 3.0 patches via the WRITE ALL, reset, confirmed, etc etc. Selected a different directory to load my last three patches, and... editor crashed. This was a little different, because when I loaded the last three on my 2nd FI, I navigated to the other folder AFTER hitting the WRITE ALL button. This time, I loaded the first twelve, then tried selecting the different directory through Editor's file menu. Had to restart my PC to load the last three, but achieved success!

All personal patches loaded and all remaining factory patches working on both Impacts.

To satisfy curiosity about the light clipping, I loaded 2.22 back on my 2nd FI to see if that solved the issue. Reset, and... no sound. A quick WRITE ALL of all 1.00 sounds via the 2.22 Editor, reset, and all factory 1.0 sounds working. Loaded my personal patches individually, and everything is working on 2.22 as well.

I'll have to do some more troubleshooting to find that pesky clipping issue is because it's still there even in 2.22, but all patches loaded and working on both Impacts in 3.0. Very strange about the factory patches disappearing after loading personal ones.

5sg.

A brief reply - loading an older firmware back onto the pedal (that previously had v3 on it) without filling all 99 slots with non-v3 patches will of course cause problems as the patches will be in the wrong format.

When you say light clipping issue, do you mean the LED is peaking into the red zone? Couldn’t you just adjust the input knob on the FI?

 

[Quatschmacher]

When I updated my patches, I hit the Write All thinking it would just load the 15 patches in the selected folder (my cover band patches) into the respective slots on my pedal. It gave me a message that there were gaps and I should hit cancel to skip, so that's what I did. It took a while to think, so I re-wrote all my cover band patches to my Impact individually just in case, because I wasn't sure what that was about. As it stands now, my cover band patches are working (with some minor clipping), but none of the factory patches are working correctly... it's like they're empty, barely or no sound comes through on some or most of them.

As per the update instructions, when updating the FI to v3 you MUST write the complete factory v3 set of 99 patches to the pedal and you MUST do this in boot menu mode- this ensures that the pedal doesn’t load a v2 file stored in the pedal and that all old-format data is cleared out of the memory. If you don’t do this you will experience errors.

 

[Quatschmacher]

I’m so disgusted. I finally sat down to update to v3. Ninety minutes later and I still can’t update. It shouldn’t be this hard and quirky. I’ve tried on both PC and Mac with three different midi interfaces.

Roland um one
Irig midi
Iconnectivity


I also tried with the editor and through the browser on both PC and Mac. Each platform recognizes my midi devices. Chrome browser on both platforms recognize my midi devices but fail when I try to update. I receive the lost communication error. The editors on both platforms do not see my FI. No idea why when my computers see the interfaces.

My midi cables are tested and working.

As you all know I have made many patches before using all the equipment stated above. I’m starting to wonder if it’s an issue with my pedal even though my pedal functions perfectly for performance. All I know is I lost valuable time and I have a ton of songs to learn for this weekend. So disappointed in this outcome. Hopefully I will be able to revisit this next week.

Ugh.

Did you put the pedal into update mode by holding down both switches when powering on?

Which version of the editor are you using?

What current firmware is your pedal on?

Are you able to test the FI MIDI IN port is working correctly by running an expression pedal or program switcher into it to see if your FI receives MIDI messages?

 

[dieselbass42]

Putting the pedal in update mode is key! I couldn't get mine to update to 2.22, got frustrated and waited for v.3. After reading @Qautschmaker's update instructions, I realized I was missing the update mode step. Once I did that, everything went smoothly. Just my experience...

 

[Quatschmacher]

Putting the pedal in update mode is key! I couldn't get mine to update to 2.22, got frustrated and waited for v.3. After reading @Qautschmaker's update instructions, I realized I was missing the update mode step. Once I did that, everything went smoothly. Just my experience...

Updating via browser should avoid this problem as it clearly instructs the user to put the pedal into update mode before clicking the next step.

 

[maisbass]

Yes yes yes. I appreciate the help. Not my first rodeo here. I’ve done all of the above.

As stated earlier, my FI works live perfectly and receives program changes. I confirmed that again last night.

v 2.22

If I have time, I’ll try again tomorrow evening.

thanks for your help.

 

[maisbass]

As I stated earlier, my pedal is no longer connecting to the editor on both PC and Mac with 3 different midi interfaces. And obviously I have done this successfully in the past with the present editor I have installed on my computers.

thanks.

 

[Quatschmacher]

As I stated earlier, my pedal is no longer connecting to the editor on both PC and Mac with 3 different midi interfaces. And obviously I have done this successfully in the past with the present editor I have installed on my computers.

thanks.

Did you connect the pedal and interface before or after launching the editor? If you connect it after launching then it doesn’t show up.

Is your interface showing in the list of available interfaces in the MIDI/preferences menu?

Have you set the FI global MIDI channel to all? Anything other than “all” causes issues with editor communication. A fix has been made and will be released.

 

[bassvirtuoso]

@Adamixoye have you updated yet? Gotta say, I'm a bit worried and haven't yet - but I'm VERY excited about the patches that @Quatschmacher has made, they sound amazing.

 

[Quatschmacher]

@Adamixoye have you updated yet? Gotta say, I'm a bit worried and haven't yet - but I'm VERY excited about the patches that @Quatschmacher has made, they sound amazing.

Thanks!

For the most part it’s fine. Most of the problems users have had stem from not having read/followed the update instructions properly (though there have been some exceptions to this, such as the initial Catalina problem).

 

[fivestringgecko]

As per the update instructions, when updating the FI to v3 you MUST write the complete factory v3 set of 99 patches to the pedal and you MUST do this in boot menu mode- this ensures that the pedal doesn’t load a v2 file stored in the pedal and that all old-format data is cleared out of the memory. If you don’t do this you will experience errors.

I know, I know... "read the damn manual." lol I obviously missed that, but it's working now!

5sg.

 

[Adamixoye]

@Adamixoye have you updated yet? Gotta say, I'm a bit worried and haven't yet - but I'm VERY excited about the patches that @Quatschmacher has made, they sound amazing.

Yes. I had a little bit of trouble getting my Roland UM-One to show up but once I did the update was smooth. I've only sampled the new sounds, I didn't notice a big difference in tracking but some of the sounds are great.

 

[maisbass]

Did you connect the pedal and interface before or after launching the editor? If you connect it after launching then it doesn’t show up.

Is your interface showing in the list of available interfaces in the MIDI/preferences menu?

Have you set the FI global MIDI channel to all? Anything other than “all” causes issues with editor communication. A fix has been made and will be released.

I have used the FI editor successfully ever since the inception of this pedal. I am not a novice. I’ve made hundreds of patches using the editor dating back to L0KKI‘ S editor lol. Believe me I know what I’m doing and yes I did read the manual anyway just in case.

yes all of the midi interfaces that I tried were plugged in before launching the editor as I have always done.

yes I made sure that my midi interface was selected in both the chrome browser when I tried it with that, and of course with my computers themselves. I also made sure it was selected when I tried it with the editor.

i’ve rebooted the computer several times with the same unfortunate result.

yes I had the FI set to global MIDI.

as I stated earlier I’ve had this pedal since it was first released a few years ago. I’ve programmed and shared hundreds of patches successfully with the editor. But I will admit from day one the editor has always been buggy. This is nothing new. Usually after a few tries I will get it to work. Sometimes I was lucky and would work right from the beginning.

I don’t know what else to say. I read the manual. If I’ve never successfully connected to the editor or programmed patches then I could understand there being a question here, but that is not the case.

I understand you’re trying to help but please don’t make a blanket statement that the problem always because Someone didn’t read the manual. Perhaps that is the case most of the times, but I can assure you it is not the case now.

i’m also not a newbie when it comes to midi. I’ve been working with Midi since the 1970s, and started programming sequences on a Amiga computer and Alesis MMT8.. So midi is not foreign to me.

Sorry for the lengthy reply but I’m frustrated. I will have a go at it again tomorrow night

 

[maisbass]

I just re-read my post and I’m sorry if it’s come off a bit defensive and harsh, and I truly appreciate the help. I’m just not a noob and been successfully updating and programming this pedal for years now.