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

[Quatschmacher]

I'm still using The Future Impact V.1 and about to upgrade to a V.4 device.

There is an issue I've always had with V.1, but I'm unsure if it's a bug?

I have a specific "supersaw" patch that sounds completely different every time it's selected.

I have to select a different patch and then return to the supersaw patch, two to four times before it plays back correctly.

It's like the phase of the oscillators are locked to a different, random position every time the patch is engaged, until it is eventually engaged (by chance) at the right 'start position'.
Once engaged at the right phase position, the patch does not change - (no 'beating' or oscillator drifting/phase cancellation).

I really love this patch when it plays back correctly, and I'm wondering if there is any remedy for this issue?


Here is a link to the patch in question:


I'd also like to thank Mr Szalay for creating such an amazing device, and I'm really looking forward to experiencing the improvements and FM synthesis of V.4.

Is this a patch you’ve created yourself? If not, which patch is it?

What firmware are you on? If you’ve upgraded from a pre-v3 and didn’t flush out the old patches, it can cause odd behaviour. I’d recommend reinstalling the firmware and factory patches using the online updater tool, following instructions to the letter.

 

[Frellin Smesh]

Hi,

Thanks for the prompt response.

I have the latest firmware for my model (F1 V3.61).

Already flushed everything and did the full reinstall of factory patches a long time ago.

Everything else works as it should except for this one patch that i provided the link to.

I can't remember exactly were I found the patch, but I modified it to my tastes/instrument.

If anybody has a Future Impact V.1 that they could test this patch on and see if this randomization behavior happens on your device also.

It would really help to identify if it's user error, a badly designed patch, or simply a software bug that causes patch/oscillator randomization upon patch instantiation.


Gastric also mentioned this problem years ago, as quoted below:

Please email your bug reports and enhancement requires directly to Panda. They're responsive.

Note that for the random tone fluctuations when using the editor Panda requested me to test it with various MIDI connections but I didn't personally have the time nor the additional MIDI connections to do that. So if other people can report the same issue, provide their MIDI hardware details, OS / platform details, and a short sound clip detailing the issue, along with the patch used, that'd be super great as there's definitely a bug in the editor or pedal itself that should be corrected.

What happens for me typically is I load a saved patch in the editor and it sounds NOTHING like it should. Change one VCO param and viola it's back to sounding proper. This could be a real buzz kill for people loading our shared patches. "This sounds TERRIBLE." they move onto a different patch and miss out on some awesomeness. I would've never noticed this except I found it while re-listening to my own patches so I as familiar with what they should sound like.

 

[Quatschmacher]

Hi,

Thanks for the prompt response.

I have the latest firmware for my model (F1 V3.61).

Already flushed everything and did the full reinstall of factory patches a long time ago.

Everything else works as it should except for this one patch that i provided the link to.

I can't remember exactly were I found the patch, but I modified it to my tastes/instrument.

If anybody has a Future Impact V.1 that they could test this patch on and see if this randomization behavior happens on your device also.

It would really help to identify if it's user error, a badly designed patch, or simply a software bug that causes patch/oscillator randomization upon patch instantiation.


Gastric also mentioned this problem years ago, as quoted below:

For clarity, is this a patch you are loading from an editor file directly? I mean this as opposed to that it’s one that’s on your pedal and that you’re navigating to it on the pedal then trying to modify it.

Also, if loading directly from an editor file, is this a local file on your computer or one via the cloud?

Also is it the first patch you are trying to load immediately after launching the editor?

 

[Quatschmacher]

Already flushed everything and did the full reinstall of factory patches a long time ago

And was this done “properly” where you boot the pedal in global menu mode and write the factory sound set while still in the global menu? Simply loading the factory patches in the normal way is not sufficient to flush the memory; it must be done in the described above.

 

[Frellin Smesh]

For clarity, is this a patch you are loading from an editor file directly? I mean this as opposed to that it’s one that’s on your pedal and that you’re navigating to it on the pedal then trying to modify it.

Also, if loading directly from an editor file, is this a local file on your computer or one via the cloud?

Also is it the first patch you are trying to load immediately after launching the editor?

And was this done “properly” where you boot the pedal in global menu mode and write the factory sound set while still in the global menu? Simply loading the factory patches in the normal way is not sufficient to flush the memory; it must be done in the described above.

All of my editor patches are stored and accessed 'locally' from my Windows computer.

All update (firmware and factory bank) instructions were followed to the letter.

Everything in the editor and hardware works as expected, except for this one supersaw patch

Whether I load the patch from the editor or simply select it from the pedal, the result is always the same - (a different sound every time it's selected).

I always have to jump to another patch and then return to this supersaw patch multiple times to get it to play back correctly.



If, on somebody else's device/editor - the patch consistently plays back with the same sound, after alternating between different patches, then this would prove that the error only exists within MY software/device.

This could be resolved in a matter of minutes if anybody has a Future Impact V1 and is kindly willing to test the patch for themselves.

Thanks.

 

[DaniloWendel]

I purchased a Future Impact v3 and I'm having trouble connecting the pedal to my computer. The computer doesn't recognize the pedal. Could you help me?

 

[Quatschmacher]

I purchased a Future Impact v3 and I'm having trouble connecting the pedal to my computer. The computer doesn't recognize the pedal. Could you help me?

Windows or Mac?

If you are on windows, make sure all other MIDI connections are disabled, including Google chrome.

What interface are you using?

What firmware is the pedal on (shown at power-on)?

What version of the editor are you using (shown in the “about” tab)?

Is your interface showing as an option for input and output in the MIDI preferences menu? If it is visible and detected, likely you have the ports hooked up the wrong way round.

 

[DaniloWendel]

I'm using Windows. When I turn on the pedal, version 3.60 appears, which is the same version I'm trying to use from the editor. I'm using the interface model from the link, and yes, the MIDI menu in the program detects the interface. Yesterday, while trying to connect, I noticed that at one point the pedal's display showed - -5.

Invalid Link Removed

 

[Quatschmacher]

I'm using Windows. When I turn on the pedal, version 3.60 appears, which is the same version I'm trying to use from the editor. I'm using the interface model from the link, and yes, the MIDI menu in the program detects the interface. Yesterday, while trying to connect, I noticed that at one point the pedal's display showed - -5.

Invalid Link Removed

If the display shows - - in the first two digits then you are connected to the editor. I believe it is functioning.

Describe what you are trying to do and why you think it isn’t working. I suspect you may be trying to get it to do something it doesn’t do.

When connected to the editor, you need to browse patches using the editor and manager software, rather than by scrolling patches on the pedal.

As always, please refer to the user manual which is located under the “help” tab in the editor.

 

[Chizzops]

I'm using Windows. When I turn on the pedal, version 3.60 appears, which is the same version I'm trying to use from the editor. I'm using the interface model from the link, and yes, the MIDI menu in the program detects the interface. Yesterday, while trying to connect, I noticed that at one point the pedal's display showed - -5.

Invalid Link Removed

Make sure you assign the midi in and outs in the FI Editor!

 

[Averell]

Hey there!
I’m looking for a lead sound, something similar to the sound of the main riff of Take On Me. Is there a preset somewhere to reproduce that sound with the Future Impact 4 ?

 

[Andras Szalay]

Hey there!
I’m looking for a lead sound, something similar to the sound of the main riff of Take On Me. Is there a preset somewhere to reproduce that sound with the Future Impact 4 ?

It will be part of the 4.5 sound set.

 

[Quatschmacher]

It will be part of the 4.5 sound set.

The lead sound too? (I know we are including the FM bass part.)

 

[smeet]

I need some bass sounds to cover a few of the hits by the Gap Band (Party Train, You Dropped the Bomb on me, Early in the Morning, etc). They don't seem to be too hard but I haven't had a chance to delve into it yet. Does anybody (or the new sound set) have presets like these?

 

[Andras Szalay]

Hello everybody,

The greatest development in the long history of the Future Impact, software 4.5 is almost ready!

Close to the Edge, YES!

Both the FI software and the Editor software are ready, we just need another 8-10 days for deep beta testing and documentation. The two greatest news, 99 Yamaha DX7 compatible new FM sounds and Setlist Mode are working wonderfully. Setlists can be programmed very easily on board, without a computer. FM sounds are combined with the VCF section and the Effect section of the FI (Chorus, Delay, Overdrive, EQ), and a new Zero Latency mode is also available, just to mention some of the most important new features. New VIP devices that will be delivered with 4.5 will have new footswitches. On request from our customers, we eliminate the risk of accidentally pressing the encoder button together with the ON/OFF switch by using 4.5 millimeters higher footswitches with improved quality and lighter switching action.

Coming soon!

During this time we need to focus on the testing, thus we really have no time now to answer individual inquiries. All information will be posted and FAQs answered on our web pages and the forums.

Andras Szalay

Panda-Audio

 

[Andras Szalay]

FM page of the editor

 

[Andras Szalay]

Setlist mode

 

[Chizzops]

Hello everybody,

The greatest development in the long history of the Future Impact, software 4.5 is almost ready!

Close to the Edge, YES!

Both the FI software and the Editor software are ready, we just need another 8-10 days for deep beta testing and documentation. The two greatest news, 99 Yamaha DX7 compatible new FM sounds and Setlist Mode are working wonderfully. Setlists can be programmed very easily on board, without a computer. FM sounds are combined with the VCF section and the Effect section of the FI (Chorus, Delay, Overdrive, EQ), and a new Zero Latency mode is also available, just to mention some of the most important new features. New VIP devices that will be delivered with 4.5 will have new footswitches. On request from our customers, we eliminate the risk of accidentally pressing the encoder button together with the ON/OFF switch by using 4.5 millimeters higher footswitches with improved quality and lighter switching action.

Coming soon!

During this time we need to focus on the testing, thus we really have no time now to answer individual inquiries. All information will be posted and FAQs answered on our web pages and the forums.

Andras Szalay

Panda-Audio

Thanks for the update! Now those of us frothing at the mouth can bide our time a little longer!

 

[Quatschmacher]

The FM capabilities are great. I’ve finally been able to make some upright bass sounds to rival the ones I made on the C4 that folks love so much. Made with a P bass with Labella 760FS flat wound strings.

 

[sunbeast]

The FM capabilities are great. I’ve finally been able to make some upright bass sounds to rival the ones I made on the C4 that folks love so much. Made with a P bass with Labella 760FS flat wound strings.
View attachment 7449993

Wow that sounds awesome, even through a phone speaker!