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

Hi all,
I'm trying to load sound patches stored in my DX7 MK2 to the FI v4.5 Editor.

So, first of all I have to download these patches from the DX7 to the PC as SysEx .syx file.
Several years ago, for other purposes, I successfully used a very old SoundBlaster Extigy Midi interface with MidiOx sw connected to both DX7 and PC.

Nowadays the problem is that my PC runs with Windows 10 and the SoundBlaster Extigy is not compatible with it.

Threrefore now I use a cheap MIDI to USB midi cable that perfectly worked to update the FI to v4.5 except to dump the SysEx frm the DX7-II to the PC.

In short: with MidiOx the 32 Programs dump from the DX7 is saved in a .syx file not readable (as DX7 patch dump) by both FI Editor and Dexed.
It seems the file is corrupted.

On the net I read to avoid these cheap midi-to usb cables for downloading SysEx trasmission from old synths to PC because .syx file corruption may occur.

I have no problem to buy a better MIDI to USB interface, but I want to be sure the problem of the corrupted SysEx file is related to the cheap midi to usb cable I use now.

Is there any other Yamaha DX7 MK2 owner who could help me?

Thanks in advance
 
Last edited:
Hi! Can anyone help me out?
I have a Future Impact v4 and to update to the most recent v4.5 I bought a midi interface, an ESI Midimate eX.
I've set the midi ports in the editor and connected to the FI but the connection doesn't function. The program says there's a connection failure.
I've tried installing the most recent drivers, restarted the program, restarted the computer, tried with an older version of the editor but I can't seem to get the FI connecting with my computer.
What am I making wrong here?
Is there a problem with the interface I'm using?
What do you guys use?
 
Hi all,
I'm trying to load sound patches stored in my DX7 MK2 to the FI v4.5 Editor.

So, first of all I have to download these patches from the DX7 to the PC as SysEx .syx file.
Several years ago, for other purposes, I successfully used a very old SoundBlaster Extigy Midi interface with MidiOx sw connected to both DX7 and PC.

Nowadays the problem is that my PC runs with Windows 10 and the SoundBlaster Extigy is not compatible with it.

Threrefore now I use a cheap MIDI to USB midi cable that perfectly worked to update the FI to v4.5 except to dump the SysEx frm the DX7-II to the PC.

In short: with MidiOx the 32 Programs dump from the DX7 is saved in a .syx file not readable (as DX7 patch dump) by both FI Editor and Dexed.
It seems the file is corrupted.

On the net I read to avoid these cheap midi-to usb cables for downloading SysEx trasmission from old synths to PC because .syx file corruption may occur.

I have no problem to buy a better MIDI to USB interface, but I want to be sure the problem of the corrupted SysEx file is related to the cheap midi to usb cable I use now.

Is there any other Yamaha DX7 MK2 owner who could help me?

Thanks in advance
Not an expert - but Isn’t DX7 mk2 a slightly different format?
 
  • Like
Reactions: Randy Ward
Hi! Can anyone help me out?
I have a Future Impact v4 and to update to the most recent v4.5 I bought a midi interface, an ESI Midimate eX.
I've set the midi ports in the editor and connected to the FI but the connection doesn't function. The program says there's a connection failure.
I've tried installing the most recent drivers, restarted the program, restarted the computer, tried with an older version of the editor but I can't seem to get the FI connecting with my computer.
What am I making wrong here?
Is there a problem with the interface I'm using?
What do you guys use?
As I wrote before I used a cheap midi to usb cables from Amazon. 100% plug&play, no drivers required.
 
The update to v4.5 on my new FI V4 VIP (from V4.12) went great on Monday night right after rls.
I follow the setup guide and the steps to load defaults, etc.
I can download the VA and FM banks to my laptop and play sounds in the editor keyboard etc. and play my bass tracking the midi sounds active.

My pedal-board setup:
midiBeam 4Control is powered from my Pedal board PSU through small buck-converter (9V to 5V) and has both Expression and 2 button foot-switch connected. MIDI I/O connected to FI V4 VIP O/I. Works great.

I see a some "interesting" behavior on the FI V4 VIP v4.5:
a) The FI V4 VIP is OFF (has 9V, so display is on)
b) We are in set-list mode, FI V4 VIP is still OFF, display showing "01≡"
c) Press "up" from "01≡" and till "07≡". FI V4 VIP is still OFF and display shows "07≡"
d) Press "up" again and now: display shows "0.8≡" and FI V4 VIP is turned ON
(Notice the "." so 1-7 is VA then 8 is FM)
e) I turn the Pedal OFF
f) This also happens when going to set-list 09 ("09≡") since you go from a FM to VA, it still turns the pedal ON.
g) I turn the Pedal OFF
h) go to set-list 10 is "1.0≡" so FM again and it turns ON.
i) The same ON happens from 10 ("1.0≡") to 11 ("11≡") and I trun it OFF again.
J) The next few 12-13 are VA, so no ON, but this behavior continues in 14 "1.4≡" which is FM.

The rest until 50 are VA and after that 50 to 99 are FM, so now expected behavior.

So it seems the set-list mode FM bank enables ON regardless of prior status and doesn't save it either since it sets ON again when changing from FA bank to VA.

I have something related with FI editor v4.5, but that's in the next post.

Is this only on my device?
A bad flash?
 
My OS: Windows 11 64bit
My USB to MIDI: Laptop USB -> 2m USB extension cable -> midiBeam 4Control (with BOSS EV-30 Expression Pedal and Hotone FS-1 Ampero Switch) MIDI I/O -> MIDI O/I on FI V4 VIP v4.5.

1. I use midiBeam 4Control to connect the FI v4 VIP v4.5 to my laptop with FI editor V4.5.
2. The FI v4 VIP is ON and in set-list mode. Display showing "01≡"
(I can hear sounds from FI editor keyboard and my own bass when tracking)
3. Now In the FI editor we're in FM mode, example download FM in banks menu.
4. The display now shows "--≡"
5. Play the FI editor keyboard fast back and forth and the pedal get triggered with this behavior:
6. FI v4 VIP display showing "9.8≡" and is turned OFF.
7. Turn FI v4 VIP ON again and repeat FI editor keyboard fast back and forth
8. FI v4 VIP display showing "9.6≡" and is turned OFF.

This behavior might be related to my previous post with FM/VA change and automatic OFF/ON switching.
So the pedal is suddenly turned off and set-list goes down some steps, so from 01 to 9.8 or 9.6 and 9.2 et.



Also, It seems we still have the two MIDI devices on same OS like a sound-card with MIDI compatibility.

FI editor V4.5 crash and need to re-install:
There is still "the problem" with other MIDI capable soundcards, like my Roland Quad-Capture.
Since I tried it and I can still get the FI editor v4.5 to crash right after i also connect my soundcard.
So I need to completely uninstall and install again to get FI editor to work. Same exact issue I had on FI editor v4,12 and I believe this might be a known limitation.

Would just be really nice if it would play nice with other sound cards not in use with the FI editor, but on same OS :)
 
Will there be a future CC64 (Sustain) support in FM mode / set-list FM mode?

My setup: midiBeam 4Control (with BOSS EV-30 Expression Pedal and Hotone FS-1 Ampero Switch) MIDI I/O -> MIDI O/I on FI V4 VIP v4.5.
The 2 button foot-switch works great in VA mode with CC67 (Program Down on FI) and CC64 (Sustain).

In the "FI_V4.5_Addendum07.pdf" the MIDI commands are shown:
CC 1
CC 7
CC 11
CC 67
CC 88
CC 69
CC 74

So missing CC64 (Sustain).

Any chance of that working in a future FW version for FM like in VA?
 
My OS: Windows 11 64bit
My USB to MIDI: Laptop USB -> 2m USB extension cable -> midiBeam 4Control (with BOSS EV-30 Expression Pedal and Hotone FS-1 Ampero Switch) MIDI I/O -> MIDI O/I on FI V4 VIP v4.5.

1. I use midiBeam 4Control to connect the FI v4 VIP v4.5 to my laptop with FI editor V4.5.
2. The FI v4 VIP is ON and in set-list mode. Display showing "01≡"
(I can hear sounds from FI editor keyboard and my own bass when tracking)
3. Now In the FI editor we're in FM mode, example download FM in banks menu.
4. The display now shows "--≡"
5. Play the FI editor keyboard fast back and forth and the pedal get triggered with this behavior:
6. FI v4 VIP display showing "9.8≡" and is turned OFF.
7. Turn FI v4 VIP ON again and repeat FI editor keyboard fast back and forth
8. FI v4 VIP display showing "9.6≡" and is turned OFF.

This behavior might be related to my previous post with FM/VA change and automatic OFF/ON switching.
So the pedal is suddenly turned off and set-list goes down some steps, so from 01 to 9.8 or 9.6 and 9.2 et.



Also, It seems we still have the two MIDI devices on same OS like a sound-card with MIDI compatibility.

FI editor V4.5 crash and need to re-install:
There is still "the problem" with other MIDI capable soundcards, like my Roland Quad-Capture.
Since I tried it and I can still get the FI editor v4.5 to crash right after i also connect my soundcard.
So I need to completely uninstall and install again to get FI editor to work. Same exact issue I had on FI editor v4,12 and I believe this might be a known limitation.

Would just be really nice if it would play nice with other sound cards not in use with the FI editor, but on same OS :)
Despite the fact that the Roland Quad-Core was discontinued five years ago the software and drivers should work in Windows 11/x64.

Perhaps Memory Integrity in Windows 11 is still tuned on or turned itself back on? Core Isolation doesn't play nice with older kernel-mode drivers.

All the best
 
Despite the fact that the Roland Quad-Core was discontinued five years ago the software and drivers should work in Windows 11/x64.

Perhaps Memory Integrity in Windows 11 is still tuned on or turned itself back on? Core Isolation doesn't play nice with older kernel-mode drivers.

All the best
thx, if driver related I will check ... I still get the Control Panel for the driver from the online update and never had an issue with any software, but I'm completely new to MIDI.

QUAD-CAPTURE Driver Ver.1.5.3 for Windows 10/11
Automatic windows update ...

I will look into any MIDI related info, but to be clear, I am and will only use quad capture for audio, not MIDI.
 
Last edited:
  • Like
Reactions: darev
thx, if driver related I will check ... I still get the Control Panel for the driver from the online update and never had an issue with any software, but I'm completely new to MIDI.

QUAD-CAPTURE Driver Ver.1.5.3 for Windows 10/11
Automatic windows update ...

I will look into any MIDI related info, but to be clear, I am and will only use quad capture for audio, not MIDI.

Well this what the google "AI" summarized.

Roland MIDI devices on Windows generally offer two driver modes:
- Original/Vendor (requires dedicated Roland driver, supports FPT/low-latency)
- Generic/Generic Vendor (uses built-in Windows USB driver, no install needed).
The "Original" mode is recommended for optimal performance, while "Generic" is for easy plug-and-play.

Key Driver Modes & Setup:
- Original / Vendor / Vendor Mode: Requires downloading the specific Windows 10/11 driver from the Roland Support website. This mode enables Fast Processing Technology (FPT) for faster MIDI data transfer and allows both MIDI and Audio functionality.
- Generic / Generic Vendor / Generic Vendor Mode: Compatible with the built-in Windows USB MIDI driver. This allows plug-and-play functionality without needing to install additional drivers, ideal for quick setups, but may offer limited functionality compared to the proprietary driver.
- Switching Modes: "Most" Roland devices allow you to toggle between these modes in the "System" or "USB" menu, requiring a power cycle to take effect

So it's a windows thing and depends how both FI Editor and other devices can coexist, I only know of the std. driver and have zero midi option in it. Maybe more info can help...

While new windows has built-in MIDI and my device potentially has old driver, ie. MIDI 1.0, I think we are at crossroads.

Though I still don't understand the problem specific for windows 11 having 2 MIDI devices connected and the FI editor not being able to only talk to the one selected in preferences.
 
Last edited:
  • Like
Reactions: darev
Today’s playing with 4.5 …
It’s good, very good.
I would say The VA side is the selling point and just works, the FM is an added bonus- and lets me do a pad type sound I’ve been trying to get for years (don’t ask why) - I also think they probably didn’t think of pad sound so I’ll have to do a hunt on Dexed of some alternatives.

Also found, for me sticking it after my broughton Omnicomp is better, even if the detection is down so the compressor doesn’t trigger - presume it’s filtering my signal somewhat
 
Well this what the google "AI" summarized.

Roland MIDI devices on Windows generally offer two driver modes:
- Original/Vendor (requires dedicated Roland driver, supports FPT/low-latency)
- Generic/Generic Vendor (uses built-in Windows USB driver, no install needed).
The "Original" mode is recommended for optimal performance, while "Generic" is for easy plug-and-play.

Key Driver Modes & Setup:
- Original / Vendor / Vendor Mode: Requires downloading the specific Windows 10/11 driver from the Roland Support website. This mode enables Fast Processing Technology (FPT) for faster MIDI data transfer and allows both MIDI and Audio functionality.
- Generic / Generic Vendor / Generic Vendor Mode: Compatible with the built-in Windows USB MIDI driver. This allows plug-and-play functionality without needing to install additional drivers, ideal for quick setups, but may offer limited functionality compared to the proprietary driver.
- Switching Modes: "Most" Roland devices allow you to toggle between these modes in the "System" or "USB" menu, requiring a power cycle to take effect

So it's a windows thing and depends how both FI Editor and other devices can coexist, I only know of the std. driver and have zero midi option in it. Maybe more info can help...

While new windows has built-in MIDI and my device potentially has old driver, ie. MIDI 1.0, I think we are at crossroads.

Though I still don't understand the problem specific for windows 11 having 2 MIDI devices connected and the FI editor not being able to only talk to the one selected in preferences.

One Windows midi services SDK later
1774652885806.png

Will look into it more, but some feedback from more knowledgeable people will be helpful for the windows panda users ;)

Update: It seems to work now?! but I did plug both device in and then start FI editor v4.5 before and it did crash, just now it did not, hmmm perhaps something got updated further .... who knows. if it works, don't try to fix it... lol and in the future I will always try to close FI editor before plug/un-plug devices.
 
Last edited:
My OS: Windows 11 64bit
My USB to MIDI: Laptop USB -> 2m USB extension cable -> midiBeam 4Control (with BOSS EV-30 Expression Pedal and Hotone FS-1 Ampero Switch) MIDI I/O -> MIDI O/I on FI V4 VIP v4.5.

1. I use midiBeam 4Control to connect the FI v4 VIP v4.5 to my laptop with FI editor V4.5.
2. The FI v4 VIP is ON and in set-list mode. Display showing "01≡"
(I can hear sounds from FI editor keyboard and my own bass when tracking)
3. Now In the FI editor we're in FM mode, example download FM in banks menu.
4. The display now shows "--≡"
5. Play the FI editor keyboard fast back and forth and the pedal get triggered with this behavior:
6. FI v4 VIP display showing "9.8≡" and is turned OFF.
7. Turn FI v4 VIP ON again and repeat FI editor keyboard fast back and forth
8. FI v4 VIP display showing "9.6≡" and is turned OFF.

This behavior might be related to my previous post with FM/VA change and automatic OFF/ON switching.
So the pedal is suddenly turned off and set-list goes down some steps, so from 01 to 9.8 or 9.6 and 9.2 et.



Also, It seems we still have the two MIDI devices on same OS like a sound-card with MIDI compatibility.

FI editor V4.5 crash and need to re-install:
There is still "the problem" with other MIDI capable soundcards, like my Roland Quad-Capture.
Since I tried it and I can still get the FI editor v4.5 to crash right after i also connect my soundcard.
So I need to completely uninstall and install again to get FI editor to work. Same exact issue I had on FI editor v4,12 and I believe this might be a known limitation.

Would just be really nice if it would play nice with other sound cards not in use with the FI editor, but on same OS :)

Update: in FM mode FI editor can sometimes lose connection like this pop-up.
1774656028949.png

So you play around on the keyboard and it disconnects, because the pedal has gone back one set-list step from a FM bank to VA bank and that will trigger the GUI with the warning msg. In this specific case i'm on set-list "0.8≡" for FM and then download in bank manager and load a sound and play with the keyboard. then this msg. comes up and the pedal shows "07≡" so VA. Not sure what is causing this. without FI editor the pedal never changes by itself.
 
Update: in FM mode FI editor can sometimes lose connection like this pop-up.
View attachment 7461863
So you play around on the keyboard and it disconnects, because the pedal has gone back one set-list step from a FM bank to VA bank and that will trigger the GUI with the warning msg. In this specific case i'm on set-list "0.8≡" for FM and then download in bank manager and load a sound and play with the keyboard. then this msg. comes up and the pedal shows "07≡" so VA. Not sure what is causing this. without FI editor the pedal never changes by itself.
Update: Yeah 2 hours testing VA "07≡" and then switch to FM "0.8≡" and just testing 20 seconds and it switched back to "07≡" by itself. This is probably FI editor related, at least the data path is almost exclusive Panda Audio for debugging. Now back to Music and new sounds :)