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

[Quatschmacher]

Same issue after updating the FI4 and editor. On a clean Windows boot, with no other apps running, and my audio interface disconnected, I can go into FIEeditor4 MIDI preferences and the WIDI Jack is the only visible option here. No other USB MIDI devices connected or in use. When I click Download from FI in the Manager, the first tile 01 populates and then the program closes. No error message. If for example I have one of the WIDI Jack;'s cables disconnected from the FI, I get a message that the FI is not detected, so the editor doesn't seem the be crashing just because it's trying to access the WIDI jack. It crashes once it has started transferring patch data. It works fine if I connect physical cables to my M-Audio interface. I just have to unpatch a couple of things each time I want to hook up the FI4.

Do you have both the input and output selected in the editor?

Is the widi thing the device that draws power from the MIDI port? I’m not sure FI does supply power over the MIDI port so that may be the issue.

You could try hooking the physical cable to one port and wireless to the other to see if you can isolate what isn’t working.

 

[ZonMan]

Do you have both the input and output selected in the editor?

Yes

Is the widi thing the device that draws power from the MIDI port? I’m not sure FI does supply power over the MIDI port so that may be the issue.

Yes, the WIDI Jack draws power from the MIDI port, and FI4 is able to power it. The way I use it is I have the WIDI Out to the MIDI In of my HX StompXL. MIDI Thru to the FI4, FI4 Out to the WIDI Jack IN to power the WIDI Jack, since I'm not trying to send MIDI anywhere else beyond the FI4. This allows me from my phone or tablet to send patch changes to my HX and the FI4 without having to pedal dance. Nothing worse than the bandleader calling off a song and I have go up or down several banks to find the patch I need.

The FI Editor says the FI is not detected when I have it set up this way (MIDI hitting the HX first and going Thru). If I bypass the HX and connect the WIDI Out directly to the FI4 MIDI In, the Editor crashes once it starts importing data.

The WIDI Jack can also be powered by a USB-C cable, so I hooked one up to eliminate it being a potential power issue. Same result.

You could try hooking the physical cable to one port and wireless to the other to see if you can isolate what isn’t working.

That's a good idea. I connected a physical cable from my M-Audio interface to the FI MIDI In, and left the FI MIDI Out connected to (and powering) the WIDI Jack. I get the same result. FIEditor crashes after loading only the first tile. Tried again with external power to the WIDI Jack. Same result.

I then connected the WIDI to FI4 MIDI In and FI4 MIDI Out to a physical cable to my M-Audio. This worked fine.

So to recap, if I connect FI4 MIDI Out over a physical cable back to my M-Audio interface (PC MIDI In), the Editor works fine no matter if I have the FI4 MIDI In connected to the WIDI Jack or the M-Audio. Interesting.

 

[meatball]

I just received my FI4 with 4.03 firmware. I connect it to my Windows 10 PC via an old Tascam US-122 Audio/Midi USB interface. With FIEditor 4.12 I can read from the FI and also write patches to the FI. Also the keyboard on the FIEditor works.
However, when I try to update firmware to v4.11 via the FIEditor or google chrome the update gets stuck at "Firmware update process: 0%" although the LED blinks more quickly. Any idea?

Regards,
Markus

 

[Quatschmacher]

I just received my FI4 with 4.03 firmware. I connect it to my Windows 10 PC via an old Tascam US-122 Audio/Midi USB interface. With FIEditor 4.12 I can read from the FI and also write patches to the FI. Also the keyboard on the FIEditor works.
However, when I try to update firmware to v4.11 via the FIEditor or google chrome the update gets stuck at "Firmware update process: 0%" although the LED blinks more quickly. Any idea?

View attachment 7073859

Regards,
Markus

Had you put the FI into update mode? (Hold both footswitches while powering it on.)

Make sure only the editor or chrome browser is open when trying to update firmware (not both).

Also, where did you find the standalone v4.11 firmware file? It isn’t visible on the Panda website.

 

[meatball]

Had you put the FI into update mode? (Hold both footswitches while powering it on.)

Make sure only the editor or chrome browser is open when trying to update firmware (not both).

Also, where did you find the standalone v4.11 firmware file? It isn’t visible on the Panda website.

Thanks for your fast reply!
Yes, I've put the FI into update mode. LED was flashing slowly. When starting the update via chrome or Editor the LED flashes more quickly but update gets stuck at 0%.
I only have either Chrome or the Editor active.
Sorry, my mistake, it is firmware v4.12.
Would it make sense to try to update to v4.10 before?

 

[Quatschmacher]

Thanks for your fast reply!
Yes, I've put the FI into update mode. LED was flashing slowly. When starting the update via chrome or Editor the LED flashes more quickly but update gets stuck at 0%.
I only have either Chrome or the Editor active.
Sorry, my mistake, it is firmware v4.12.
Would it make sense to try to update to v4.10 before?

There is no pedal firmware v4.12.

Latest pedal firmware is v4.11.

Latest windows editor is v4.12.

It shouldn’t matter what firmware you try to load first.

Where did you find the separate v4.11 pedal firmware file (FI411.ldr)? It’s not listed on the website. (I’m concerned you might be trying to load the incorrect file.)

Make sure you have no other USB MIDI devices attached.

Maybe try different cables.

Or try a different interface.

 

[meatball]

There is no pedal firmware v4.12.

Latest pedal firmware is v4.11.

Latest windows editor is v4.12.

It shouldn’t matter what firmware you try to load first.

Where did you find the separate v4.11 pedal firmware file (FI411.ldr)? It’s not listed on the website. (I’m concerned you might be trying to load the incorrect file.)

Make sure you have no other USB MIDI devices attached.

Maybe try different cables.

Or try a different interface.

Sorry, again mixed it up.
Firmware is v4.11, Editor is 4.12.
The firmware file is from here [Invalid or Expired Link Removed]
No other USB Midi devices attached.
The weird thing is that reading and writing patches from and to the FI works with the editor.
As I understand, the Editor otherwise works properly, except updating the firmware.
Therefore, it seems both, the USB interface and the cables are working.

 

[Quatschmacher]

The firmware file is from here

Where is “here”? Please show/tell me exactly.

Are you saying the FI411.ldr file is in a folder as part of the editor download package?

I need this info if I’m to try helping you.

 

[meatball]

Where is “here”? Please show/tell me exactly.

Are you saying the FI411.ldr file is in a folder as part of the editor download package?

I need this info if I’m to try helping you.

Sorry, I have pressed post reply too early. Edited my post with the link

 

[Quatschmacher]

Sorry, again mixed it up.
Firmware is v4.11, Editor is 4.12.
The firmware file is from here [Invalid or Expired Link Removed]
No other USB Midi devices attached.
The weird thing is that reading and writing patches from and to the FI works with the editor.
As I understand, the Editor otherwise works properly, except updating the firmware.
Therefore, it seems both, the USB interface and the cables are working.

On v3 there was often a problem with some interfaces not being able to handle the volume of data for the firmware update, even though they functioned fine for everything else.

However, in V4, the data packet size was made much smaller precisely to avoid such problems. During testing we used really cheap, generic interfaces to make sure that even those worked.

Are you connecting the interface directly to the FI4 or are you running MIDI through other devices in a chain? Connect it directly.

Only thing I can suggest is to see if there’s an updated driver for your interface (if it isn’t class compliant).

Or try another interface.

 

[meatball]

On v3 there was often a problem with some interfaces not being able to handle the volume of data for the firmware update, even though they functioned fine for everything else.

However, in V4, the data packet size was made much smaller precisely to avoid such problems. During testing we used really cheap, generic interfaces to make sure that even those worked.

Are you connecting the interface directly to the FI4 or are you running MIDI through other devices in a chain? Connect it directly.

Only thing I can suggest is to see if there’s an updated driver for your interface (if it isn’t class compliant).

Or try another interface.

I have no other devices connected. Only the FI via the two MIDI cables to the Tascam USB interface.
The Tascam interface is petty old. The driver is the latest, from 2007.
Will try with another interface.
Do you think it might be the cables?
Thanks for your support!

 

[Quatschmacher]

I have no other devices connected. Only the FI via the two MIDI cables to the Tascam USB interface.
The Tascam interface is petty old. The driver is the latest, from 2007.
Will try with another interface.
Do you think it might be the cables?
Thanks for your support!

I don’t know what it could be. Try eliminating the variables: cables then interface.

 

[meatball]

I don’t know what it could be. Try eliminating the variables: cables then interface.

Will do. Thanks!

 

[bassbrad]

A Shout out and mondo kudos to @Quatschmacher for his continuing support on this forum, you must not be an unsung hero.

I hope SA and Panda show their love for you for all you do.

BTW have you recovered from your health issues?

 

[Quatschmacher]

A Shout out and mondo kudos to @Quatschmacher for his continuing support on this forum, you must not be an unsung hero.

I hope SA and Panda show their love for you for all you do.

BTW have you recovered from your health issues?

Thanks, Brad.

Sadly not out of the woods yet; treatment could take another couple of years. Last cancer biopsy results were clear, which is great news. I was due to start the next round of treatment this week but have had to postpone due to a horrendous flu (now in my 10th day of it and still producing vile green gunge); I’ll have to skip this week’s treatment too if I’m not better in the next two days.

 

[bassbrad]

Thanks, Brad.

Sadly not out of the woods yet; treatment could take another couple of years. Last cancer biopsy results were clear, which is great news. I was due to start the next round of treatment this week but have had to postpone due to a horrendous flu (now in my 10th day of it and still producing vile green gunge); I’ll have to skip this week’s treatment too if I’m not better in the next two days.

I will keep a happy thought for you on your battle with Cancer and to get over that nasty flu. FWIW my 90 year old Mom has been battling and winning lung cancer form over 5 years now, proving both the resilience of the human spirit as well as the major advances in cancer treatments.

 

[Quatschmacher]

I will keep a happy thought for you on your battle with Cancer and to get over that nasty flu. FWIW my 90 year old Mom has been battling and winning lung cancer form over 5 years now, proving both the resilience of the human spirit as well as the major advances in cancer treatments.

Thank you.

That’s amazing news about your mom’s strength; long may that continue.

 

[bassbrad]

Thank you.

That’s amazing news about your mom’s strength; long may that continue.

Much appreciated. We are going on a mini vacation with her to Palo Duro Canyon. It still amazes me that a nearly 8 hour drive and still be in Texas.

Palo Duro Canyon State Park |

palodurocanyon.com

 

[meatball]

I don’t know what it could be. Try eliminating the variables: cables then interface.

An update.
I've tested this interface
https://www.amazon.de/dp/B00K4UXH5Q?ref=ppx_yo2ov_dt_b_fed_asin_title
which did not work at all, not even for reading patches from the FI.
This interface
https://www.amazon.co.uk/ESI-Audio-ESMMTEX-MIDIMATE-eX/dp/B071HPLJPZ/
worked nicely, also for updating the firmware via chrome or FIEditor.
Setting the MIDI ports was a bit tricky but luckily I found this Korean video

I will also check other MIDI cables with the Tascam interface.

Thanks again for your support!!

Edit: I also tested some more expensive Roland Midi cables with the Tascam but Firmware update didn't work either.
So I will stick with the ESI interface.

 

[Quatschmacher]

An update.
I've tested this interface
https://www.amazon.de/dp/B00K4UXH5Q?ref=ppx_yo2ov_dt_b_fed_asin_title
which did not work at all, not even for reading patches from the FI.
This interface
https://www.amazon.co.uk/ESI-Audio-ESMMTEX-MIDIMATE-eX/dp/B071HPLJPZ/
worked nicely, also for updating the firmware via chrome or FIEditor.
Setting the MIDI ports was a bit tricky but luckily I found this Korean video

I will also check other MIDI cables with the Tascam interface.

Thanks again for your support!!

Edit: I also tested some more expensive Roland Midi cables with the Tascam but Firmware update didn't work either.
So I will stick with the ESI interface.

I’ve also previously posted a video in several places of how to perform the update, including on my (rather scant) YouTube channel:


Don’t know what to say about that generic interface not working for you as it’s the same as one I tested as working and others have used successfully.