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

I'm not familiar with the DMC but usually the best way is to segregate your devices by MIDI channel. But that assumes the DMC is highly programmable so you can pick-and-choose which MIDI PC/CC is sent over which channel.
I'd assumed that's what the DMC is doing when setting up with the default Eventide and Future Impact configs... but I also just realized the FI is not passing midi clock through, and it appears that should have been added in an earlier firmware update, so perhaps my problems are all from old firmware (even though I got it in a new shipment from Godlyke so figured it'd have the most recent version). I'll update once I get the usb converter and see if that does it.
 
I'd assumed that's what the DMC is doing when setting up with the default Eventide and Future Impact configs... but I also just realized the FI is not passing midi clock through, and it appears that should have been added in an earlier firmware update, so perhaps my problems are all from old firmware (even though I got it in a new shipment from Godlyke so figured it'd have the most recent version). I'll update once I get the usb converter and see if that does it.

I don’t think FI does MIDI clock yet, can’t remember if that is something which will be in the upcoming firmware update.
 
I don’t think FI does MIDI clock yet, can’t remember if that is something which will be in the upcoming firmware update.
Just realized the firmware flashes on boot, from the factory I'm on 1.33, and it looks like the one after that, 2.03, has support for midi clock thru. So that should at least solve that issue, but I'm still not sure why the expression pedals are affecting FI master volume, and I can't be sure until trying but it doesn't seem like the 1.33 upgrade will solve that...
 
Check the manual for the midi cc implementation. Volume is one that can be controlled via a pedal so your expression pedal is maybe sending that cc to FI (CC 7).
 
  • Like
Reactions: Wallower
Check the manual for the midi cc implementation. Volume is one that can be controlled via a pedal so your expression pedal is maybe sending that cc to FI (CC 7).

Ah thanks, I see it now... sorry all I'm a midiot! The Future Impact appears factory set to global/omni midi, and I (hopefully) just need to set it to midi channel 3 (for Device C on the DMC controller) by editing the "configuration parameters" as described in the manual.
 
Ah thanks, I see it now... sorry all I'm a midiot! The Future Impact appears factory set to global/omni midi, and I (hopefully) just need to set it to midi channel 3 (for Device C on the DMC controller) by editing the "configuration parameters" as described in the manual.

Wallflower - let me know how this goes - i'm looking at a Disaster Area DMC-6 or DMC-4 to select patches on the FI as well as have 1 common tempo clock - use one of the Smartclock outputs to my digital delay pedal to set tempo, and MIDI --> source audio reflex --> FI to set that same tempo (once FI supports its in the next release).

The source audio reflex CV outputs are plugged into a trio of Iron Ether pedals (QF2, FMeron and Xerograph Delux) and if those could match tempo would be amazing.

(I sitll have an issue of whenever i start to do MIDI to the FI it cuts in volume, I haven't had time to debug it yet tho)

Wallflower, do you like the Disaster Area Gear? was also looking at the source audio soleman...
 
Wallflower
Not a wallflower.
let me know how this goes
Went great. After the FI firmware update and setting the FI to a single midi channel, everything works as expected: two H9s and the FI all hooked up in series to the DMC3; two expression pedals also hooked up to the DMC3 that each control a separate H9; and midi clock from the DMC3 passes through the FI to both H9s. Slick!
do you like the Disaster Area Gear?
It's perfect for my needs above. Easy to setup for a midi novice, great compact form-factor, and works like a charm. I'm only using three "screens" (out of its many options): scrolling and engaging FI patches; tap tempo midi clock; and (in CC mode) aux switches for the two H9s. Of course it also connects the expression pedals to the H9s. (My only minor gripe is that the "aux switch" functionality in CC mode has a very slight lag, which I've been told may be fixed in a firmware update... it only matters if, say, using aux switches for a very time-sensitive H9 effect).

After more time with the FI, very happy with the tracking and the musicality/synthiness of its glitches. I had high hopes for the newest synth algo on the H9s, but after some time with it I still couldn't get sounds as good as the FI does out of the box.
 
Wallower -

sorry on the name mixup! that "l" is not an "f", apologies.

thx for the thumbs up on the disaster area gear - they do seem pretty well made, and looking at their forum they seem pretty responsive and willing to put in features that customers ask for (shocking I know). I def like the flexibility of those multijacks as well (they can be MIDI in/out, CV controllers, plug expression pedals or tap pedal in).
 
No worries! Another nice thing with the DMC (as someone earlier let on) is you don't have to unplug midi cables to run the FI editor. I connected my MBP to the DMC via USB and the editor saw the FI! It was all working great for about an hour yesterday (running through user patches from the TB share, an awesome resource).

Then problems began. First was DMC-related (it kept freezing, perhaps first when my computer went to sleep... after some troubleshooting and swapping cables it seems to be sorted). Next, the FI editor started crashing on boot. It won't even open. I've upgraded my OS, erased and reinstalled the editor, re-upgraded the FI firmware, reset the FI, etc... all to no avail. I've tried connecting the FI via both the DMC and a separate midi/usb cable (Roland Um-One). The midi connection is working (I can use the online firmware updater), but the FI editor crashes every time I try to open it:

Screen Shot 2019-03-27 at 10.00.46 PM.png


Has anyone else had this issue? Any ideas? Weird that it was just working and then suddenly stopped like this.
 
Last edited:
No worries! Another nice thing with the DMC (as someone earlier let on) is you don't have to unplug midi cables to run the FI editor. I connected my MBP to the DMC via USB and the editor saw the FI! It was all working great for about an hour yesterday (running through user patches from the TB share, an awesome resource).

Then problems began. First was DMC-related (it kept freezing, perhaps first when my computer went to sleep... after some troubleshooting and swapping cables it seems to be sorted). Next, the FI editor started crashing on boot. It won't even open. I've upgrading my OS, erased and reinstalled the editor, re-upgraded the FI firmware, reset the FI, etc... all to no avail. I've tried connecting the FI via both the DMC and a separate midi/usb cable (Roland Um-One). The midi connection is working (I can use the online firmware updater), but the FI editor crashes every time I try to open it:

View attachment 3369251

Has anyone else had this issue? Any ideas? Weird that it was just working and then suddenly stopped like this.
I suspect the reason could be a damaged config file that contains information about your interfaces. This will not be deleted if you reinstall the software. You did not write anything about the system that you use, in order to give an exact answer we have to know that. Is it a PC or a MAC? What OS version did you have before, and what do you have after the upgrade?

Andras Szalay
 
Thanks, happy to take this offline to DM/email as well, but quick answers are: Macbook Pro 2018, Mohave 10.14.4, FI Firmware 2.03, FI Sound Editor 2.1.0 Mac. I only updated Mohave after it started crashing though (I can't say for certain what version I was on previously, but I'd assume it was the prior version if that was 10.14.3?). It's also crashing with 2 separate midi/usb interfaces that it worked with previously: a Disaster Areas DMC-3XL Gen3, and a Roland Um-One cable.

Also fyi I copied one of the crash reports, not sure what's the most helpful part but here's a seemingly-relevant snippet:

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007ffeefc00000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [718]

I've also speculated in the other thread (albeit without much basis) whether the issue could be related to the fact that, when it started crashing, I was opening/accessing patches from a folder that was being synced via Google software to Google Drive. Dunno if the synced/cloud nature of the folder/patches could have contributed to the issue/corruption.
 
Last edited:
Thanks, happy to take this offline to DM/email as well, but quick answers are: Macbook Pro 2018, Mohave 10.14.4, FI Firmware 2.03, FI Sound Editor 2.1.0 Mac. I only updated Mohave after it started crashing though (I can't say for certain what version I was on previously, but I'd assume it was the prior version if that was 10.14.3?). It's also crashing with 2 separate midi/usb interfaces that it worked with previously: a Disaster Areas DMC-3XL Gen3, and a Roland Um-One cable.

Also fyi I copied one of the crash reports, not sure what's the most helpful part but here's a seemingly-relevant snippet:

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007ffeefc00000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [718]

I've also speculated in the other thread (albeit without much basis) whether the issue could be related to the fact that, when it started crashing, I was opening/accessing patches from a folder that was being synced via Google software to Google Drive. Dunno if the synced/cloud nature of the folder/patches could have contributed to the issue/corruption.

I ran into similar issues; what solved it was deleting the app’s preferences file. If you’re comfortable with going and looking for it and deleting it, it’s a two minute fix, and if not I can walk you through it.
 
  • Like
Reactions: Wallower
Thanks, happy to take this offline to DM/email as well, but quick answers are: Macbook Pro 2018, Mohave 10.14.4, FI Firmware 2.03, FI Sound Editor 2.1.0 Mac. I only updated Mohave after it started crashing though (I can't say for certain what version I was on previously, but I'd assume it was the prior version if that was 10.14.3?). It's also crashing with 2 separate midi/usb interfaces that it worked with previously: a Disaster Areas DMC-3XL Gen3, and a Roland Um-One cable.

Best would be if you delete the whole settings library of the FI editor. You find it at:

Users/Username/Library/Application Support/FIEditor

If you find a settings.ini file here, it would be useful if you can send us for investigation before deleting it. We are rather sure that this will solve your problem.

Andras Szalay
 
  • Like
Reactions: Wallower
That did it! Thanks guys. Andras I'll email you the "settings.ini" file. It actually happened again and the same procedure fixed it so I'll email you both files. Just fyi for your investigation, there's a chance the corruption happened both times around when my midi/usb controller (DMC-3XL) froze, possibly because I didn't have the Mac midi settings window opened (opening that windows unfroze the DMC).
 
Dear friends,

Last time I promised that the new 3.xx Future Impact software will be ready until early April. The good new is that IT IS READY. Among many improvements and minor new features, the most important new features are:
  1. Four Flexi Controllers allow you to control ANY parameter of the FI from VCF Envelope, Noise Envelope, LFO, Pitch, Accent, Envelope Follower, Aftertouch or any MIDI controller, altogether 69 sources. These can be routed to any of 137 destination parameters. Adjustment ranges, offsets and polarities are fully controllable. It can be decided for any Flexi if the adjustment happens in chromatic steps or continuously. Even effect parameters can be controlled by Flexi, so e.g. you can use two more VCFs by controlling the frequency of the two effect EQs.
  2. Full ADSR envelope generators both for VCF and VCA, with exponential decay, like the Moog synths, while the old AD and AR (linear) envelope generators can be used optionally as well. ADSR envelopes can be restarted either in continuous mode, restarting from the point where it was in the moment of trigger, or in reset mode, restarting the envelope always from zero.
  3. Improved pitch tracking; Bass and Guitar mode, Guitar mode covering the full range of the 6 string electric guitar.
  4. Three simultaneous effects: The three effect blocks that were selectable alternatively in the FI software up to now can be used simultaneously, connected in a chain. The sequence of the blocks within the chain can be selected.
  5. Up to now the Future Impact was used almost exclusively by bass players, now with new features we are convinced that it is very encouraging for other musicians as well:
A.) Guitar players: The improved pitch tracking in the full range of the guitar offers the unique possibilities of the FI for guitarists.
B.) Keyboard players: with the Mini Moog compatible ADSR generators and the Flexi controllers the FI fulfills all wishes of a keyboard player for a monophonic synthesizer.
C.) EWI Wind Controller players: Beyond the extremely flexible possibilities of the Flexi controllers some specific MIDI control possibilities are implemented tailored for the use of the Future Impact with a EWI, e.g. VCF cutoff frequency control by Ctrl 11 (Expression), and Ctrl 5 to control Portamento through MIDI.

And now after the good news, there is a bad news as well :( . We cannot release this software to the public yet, for very simple reason. The new software requires a new editor with very significant differences from the current one, and this editor is not yet ready. The new features require many new parameters, so the format of the program file must be different from the current one. This means, that while you could theoretically upgrade your device to 3.xx even with the current editor, it would be useless because your FI would not work at all with the sounds stored in its memory that are in the old format.

The new editor will have the following features:
Perform a software update, just as the current editor.
Edit, Save and Load program files in the new format (*.pr3), and download them into the FI.
Load sound program files in the old format (*.prg), convert them internally to the new format, so then you can save it as a *.pr3.
Write *.pr3 files from the computer to the FI individually, or all from a folder, just as the current editor does.
Read *.pr3 files from the FI and store them on the computer either individually, or all. Note that when a *.pr3 file is downloaded into the FI, then the name of the file (the first 32 characters) will be stored in the FI, so when you recall the file from FI it will be saved with the original name.

If you have stored all your sounds safely on computer, or if you use only the original factory sounds then you will have just to upgrade your software with the new editor, and initialize your FI with the sounds that you have, or with the factory sounds.

If you have favorite sounds in your FI that you forgot to store (I assume this is often the case) then you need to do an intermediate step before upgrading to 3.xx. You have to upgrade to version 2.20, which is still compatible with the current format. This software has the feature of reading out the sounds from your FI, and sending it back to the computer. Of course, this requires the appropriate editor version 2.20 as well. This is not yet ready either, but coming very soon.

Of course an editor exists that supports all features of the new software, otherwise it would not be possible to develop and test the FI software. But this is a Windows 7, 32 bit only program, patched by me, ugly and not user friendly. You can understand that we do not want to confront all of you with an editor software that we cannot and do not want to support officially, it is for temporary internal use only.

But here comes the part where you could contribute to the success of this very important release too. For an official release we need a new set of 99 sounds. From the introduction of the new release these sounds will be included in the new production devices, but of course, just like the software itself the sounds will be just as well available for all users free of charge.

We are asking for volunteers who could help us to develop new sounds for the new factory set (and beyond that, for a free library), and by the way beta testing the new software, which may have some minor bugs for sure. So, we would like to select max. 5 -6 volunteers who are willing to take part in this. The following capabilities are required:
  1. You have experience in using the FI editor for creating sounds of your own from scratch, and you are willing to take time to work on new sounds.
  2. You have a Windows computer with a screen resolution of minimum 1440 x 900, with a MIDI interface that is suited for the FI.
  3. You feel confident enough to read and understand specifications that are much more detailed and much more technical than a user’s manual.
  4. You feel confident enough to use an editor that is not convenient to use.
  5. You are willing to share the sounds that you create with the FI users’ community. Your contribution will be honored on the Help page of the editor.
  6. You are willing to sign an NDA. It is not that there are deep secrets here, we just do not want to generate a flow of questions based on temporary information from the public that we have no manpower to answer. Everything will be published once all is finalized.
  7. We strongly encourage those volunteers who develop sounds not just for the bass but also ones made specifically for guitar, keyboard and EWI (if any of you play EWI).
If you are interested please send your application to [email protected]. Please describe in a few words your musical and technical background, and describe for which musical instrument would you like to develop sounds. Please let us know your nickname in the forum, so we can identify you. Please send one (just one) *.prg file with a sound that you created yourself, together with a 10-30 seconds mp3 demo of it.

Andras Szalay
 
Dear friends,

Last time I promised that the new 3.xx Future Impact software will be ready until early April. The good new is that IT IS READY. Among many improvements and minor new features, the most important new features are:
  1. Four Flexi Controllers allow you to control ANY parameter of the FI from VCF Envelope, Noise Envelope, LFO, Pitch, Accent, Envelope Follower, Aftertouch or any MIDI controller, altogether 69 sources. These can be routed to any of 137 destination parameters. Adjustment ranges, offsets and polarities are fully controllable. It can be decided for any Flexi if the adjustment happens in chromatic steps or continuously. Even effect parameters can be controlled by Flexi, so e.g. you can use two more VCFs by controlling the frequency of the two effect EQs.
  2. Full ADSR envelope generators both for VCF and VCA, with exponential decay, like the Moog synths, while the old AD and AR (linear) envelope generators can be used optionally as well. ADSR envelopes can be restarted either in continuous mode, restarting from the point where it was in the moment of trigger, or in reset mode, restarting the envelope always from zero.
  3. Improved pitch tracking; Bass and Guitar mode, Guitar mode covering the full range of the 6 string electric guitar.
  4. Three simultaneous effects: The three effect blocks that were selectable alternatively in the FI software up to now can be used simultaneously, connected in a chain. The sequence of the blocks within the chain can be selected.
  5. Up to now the Future Impact was used almost exclusively by bass players, now with new features we are convinced that it is very encouraging for other musicians as well:
A.) Guitar players: The improved pitch tracking in the full range of the guitar offers the unique possibilities of the FI for guitarists.
B.) Keyboard players: with the Mini Moog compatible ADSR generators and the Flexi controllers the FI fulfills all wishes of a keyboard player for a monophonic synthesizer.
C.) EWI Wind Controller players: Beyond the extremely flexible possibilities of the Flexi controllers some specific MIDI control possibilities are implemented tailored for the use of the Future Impact with a EWI, e.g. VCF cutoff frequency control by Ctrl 11 (Expression), and Ctrl 5 to control Portamento through MIDI.

And now after the good news, there is a bad news as well :( . We cannot release this software to the public yet, for very simple reason. The new software requires a new editor with very significant differences from the current one, and this editor is not yet ready. The new features require many new parameters, so the format of the program file must be different from the current one. This means, that while you could theoretically upgrade your device to 3.xx even with the current editor, it would be useless because your FI would not work at all with the sounds stored in its memory that are in the old format.

The new editor will have the following features:
Perform a software update, just as the current editor.
Edit, Save and Load program files in the new format (*.pr3), and download them into the FI.
Load sound program files in the old format (*.prg), convert them internally to the new format, so then you can save it as a *.pr3.
Write *.pr3 files from the computer to the FI individually, or all from a folder, just as the current editor does.
Read *.pr3 files from the FI and store them on the computer either individually, or all. Note that when a *.pr3 file is downloaded into the FI, then the name of the file (the first 32 characters) will be stored in the FI, so when you recall the file from FI it will be saved with the original name.

If you have stored all your sounds safely on computer, or if you use only the original factory sounds then you will have just to upgrade your software with the new editor, and initialize your FI with the sounds that you have, or with the factory sounds.

If you have favorite sounds in your FI that you forgot to store (I assume this is often the case) then you need to do an intermediate step before upgrading to 3.xx. You have to upgrade to version 2.20, which is still compatible with the current format. This software has the feature of reading out the sounds from your FI, and sending it back to the computer. Of course, this requires the appropriate editor version 2.20 as well. This is not yet ready either, but coming very soon.

Of course an editor exists that supports all features of the new software, otherwise it would not be possible to develop and test the FI software. But this is a Windows 7, 32 bit only program, patched by me, ugly and not user friendly. You can understand that we do not want to confront all of you with an editor software that we cannot and do not want to support officially, it is for temporary internal use only.

But here comes the part where you could contribute to the success of this very important release too. For an official release we need a new set of 99 sounds. From the introduction of the new release these sounds will be included in the new production devices, but of course, just like the software itself the sounds will be just as well available for all users free of charge.

We are asking for volunteers who could help us to develop new sounds for the new factory set (and beyond that, for a free library), and by the way beta testing the new software, which may have some minor bugs for sure. So, we would like to select max. 5 -6 volunteers who are willing to take part in this. The following capabilities are required:
  1. You have experience in using the FI editor for creating sounds of your own from scratch, and you are willing to take time to work on new sounds.
  2. You have a Windows computer with a screen resolution of minimum 1440 x 900, with a MIDI interface that is suited for the FI.
  3. You feel confident enough to read and understand specifications that are much more detailed and much more technical than a user’s manual.
  4. You feel confident enough to use an editor that is not convenient to use.
  5. You are willing to share the sounds that you create with the FI users’ community. Your contribution will be honored on the Help page of the editor.
  6. You are willing to sign an NDA. It is not that there are deep secrets here, we just do not want to generate a flow of questions based on temporary information from the public that we have no manpower to answer. Everything will be published once all is finalized.
  7. We strongly encourage those volunteers who develop sounds not just for the bass but also ones made specifically for guitar, keyboard and EWI (if any of you play EWI).
If you are interested please send your application to [email protected]. Please describe in a few words your musical and technical background, and describe for which musical instrument would you like to develop sounds. Please let us know your nickname in the forum, so we can identify you. Please send one (just one) *.prg file with a sound that you created yourself, together with a 10-30 seconds mp3 demo of it.

Andras Szalay

Andras, are you willing to post 2.20 for the rest of us? Looks like the default firmware on the website is still 2.03. Would 2.20 have any of the simpler updates like the "toggle bypass" MIDI command?
 
  • Like
Reactions: fivestringgecko
Dear friends,

Last time I promised that the new 3.xx Future Impact software will be ready until early April. The good new is that IT IS READY. Among many improvements and minor new features, the most important new features are:
  1. Four Flexi Controllers allow you to control ANY parameter of the FI from VCF Envelope, Noise Envelope, LFO, Pitch, Accent, Envelope Follower, Aftertouch or any MIDI controller, altogether 69 sources. These can be routed to any of 137 destination parameters. Adjustment ranges, offsets and polarities are fully controllable. It can be decided for any Flexi if the adjustment happens in chromatic steps or continuously. Even effect parameters can be controlled by Flexi, so e.g. you can use two more VCFs by controlling the frequency of the two effect EQs.
  2. Full ADSR envelope generators both for VCF and VCA, with exponential decay, like the Moog synths, while the old AD and AR (linear) envelope generators can be used optionally as well. ADSR envelopes can be restarted either in continuous mode, restarting from the point where it was in the moment of trigger, or in reset mode, restarting the envelope always from zero.
  3. Improved pitch tracking; Bass and Guitar mode, Guitar mode covering the full range of the 6 string electric guitar.
  4. Three simultaneous effects: The three effect blocks that were selectable alternatively in the FI software up to now can be used simultaneously, connected in a chain. The sequence of the blocks within the chain can be selected.
  5. Up to now the Future Impact was used almost exclusively by bass players, now with new features we are convinced that it is very encouraging for other musicians as well:
A.) Guitar players: The improved pitch tracking in the full range of the guitar offers the unique possibilities of the FI for guitarists.
B.) Keyboard players: with the Mini Moog compatible ADSR generators and the Flexi controllers the FI fulfills all wishes of a keyboard player for a monophonic synthesizer.
C.) EWI Wind Controller players: Beyond the extremely flexible possibilities of the Flexi controllers some specific MIDI control possibilities are implemented tailored for the use of the Future Impact with a EWI, e.g. VCF cutoff frequency control by Ctrl 11 (Expression), and Ctrl 5 to control Portamento through MIDI.

And now after the good news, there is a bad news as well :( . We cannot release this software to the public yet, for very simple reason. The new software requires a new editor with very significant differences from the current one, and this editor is not yet ready. The new features require many new parameters, so the format of the program file must be different from the current one. This means, that while you could theoretically upgrade your device to 3.xx even with the current editor, it would be useless because your FI would not work at all with the sounds stored in its memory that are in the old format.

The new editor will have the following features:
Perform a software update, just as the current editor.
Edit, Save and Load program files in the new format (*.pr3), and download them into the FI.
Load sound program files in the old format (*.prg), convert them internally to the new format, so then you can save it as a *.pr3.
Write *.pr3 files from the computer to the FI individually, or all from a folder, just as the current editor does.
Read *.pr3 files from the FI and store them on the computer either individually, or all. Note that when a *.pr3 file is downloaded into the FI, then the name of the file (the first 32 characters) will be stored in the FI, so when you recall the file from FI it will be saved with the original name.

If you have stored all your sounds safely on computer, or if you use only the original factory sounds then you will have just to upgrade your software with the new editor, and initialize your FI with the sounds that you have, or with the factory sounds.

If you have favorite sounds in your FI that you forgot to store (I assume this is often the case) then you need to do an intermediate step before upgrading to 3.xx. You have to upgrade to version 2.20, which is still compatible with the current format. This software has the feature of reading out the sounds from your FI, and sending it back to the computer. Of course, this requires the appropriate editor version 2.20 as well. This is not yet ready either, but coming very soon.

Of course an editor exists that supports all features of the new software, otherwise it would not be possible to develop and test the FI software. But this is a Windows 7, 32 bit only program, patched by me, ugly and not user friendly. You can understand that we do not want to confront all of you with an editor software that we cannot and do not want to support officially, it is for temporary internal use only.

But here comes the part where you could contribute to the success of this very important release too. For an official release we need a new set of 99 sounds. From the introduction of the new release these sounds will be included in the new production devices, but of course, just like the software itself the sounds will be just as well available for all users free of charge.

We are asking for volunteers who could help us to develop new sounds for the new factory set (and beyond that, for a free library), and by the way beta testing the new software, which may have some minor bugs for sure. So, we would like to select max. 5 -6 volunteers who are willing to take part in this. The following capabilities are required:
  1. You have experience in using the FI editor for creating sounds of your own from scratch, and you are willing to take time to work on new sounds.
  2. You have a Windows computer with a screen resolution of minimum 1440 x 900, with a MIDI interface that is suited for the FI.
  3. You feel confident enough to read and understand specifications that are much more detailed and much more technical than a user’s manual.
  4. You feel confident enough to use an editor that is not convenient to use.
  5. You are willing to share the sounds that you create with the FI users’ community. Your contribution will be honored on the Help page of the editor.
  6. You are willing to sign an NDA. It is not that there are deep secrets here, we just do not want to generate a flow of questions based on temporary information from the public that we have no manpower to answer. Everything will be published once all is finalized.
  7. We strongly encourage those volunteers who develop sounds not just for the bass but also ones made specifically for guitar, keyboard and EWI (if any of you play EWI).
If you are interested please send your application to [email protected]. Please describe in a few words your musical and technical background, and describe for which musical instrument would you like to develop sounds. Please let us know your nickname in the forum, so we can identify you. Please send one (just one) *.prg file with a sound that you created yourself, together with a 10-30 seconds mp3 demo of it.

Andras Szalay

This is amazing news, @Andras Szalay! I’m so excited by this. THANK YOU!!!

I’d really like to volunteer to create patches and beta test the new software but am away until next week so can’t get to my stored sounds (and my bass is at the luthier at the moment). Hopefully I’ll be up and running next Saturday. Is there a deadline for applications?
 
  • Like
Reactions: fivestringgecko
Andras, are you willing to post 2.20 for the rest of us? Looks like the default firmware on the website is still 2.03. Would 2.20 have any of the simpler updates like the "toggle bypass" MIDI command?
I did not hurry to publish 2.20 since without the appropriate editor you cannot use the upload feature, but other features like toggle bypass are already implemented. I can send it to you in an email.

Andras
 
This is amazing news, @Andras Szalay! I’m so excited by this. THANK YOU!!!

I’d really like to volunteer to create patches and beta test the new software but am away until next week so can’t get to my stored sounds (and my bass is at the luthier at the moment). Hopefully I’ll be up and running next Saturday. Is there a deadline for applications?
We did not set a deadline for applications, do not worry. But we want to start this as soon as possible.

Andras
 
I did not hurry to publish 2.20 since without the appropriate editor you cannot use the upload feature, but other features like toggle bypass are already implemented. I can send it to you in an email.

Andras
I would like that very much, I will email you. Thanks.