Future Impact v3 and now V4

[Quatschmacher]

1 hour ago, Higgie said:

Is this just for V4?

Yes, I’m afraid so. Development for v3 ended at v3.61 (no more code space).

Edited September 22 by Quatschmacher

[Quatschmacher]

Some really interesting discussions happening now around further improvements to onboard patch management/editing. If these come to fruition it’ll be fricking awesome. 

[Quatschmacher]

Curiosity question:

 

What would you rather see?

 

1. Ability to have full parameter editing on the pedal itself (no computer needed)? (Bear in mind the limitations of a 3-digit, 7-segment display.)

 

2. A setlist mode?

Edited yesterday at 18:40 by Quatschmacher

[LawrenceH]

Hi Peter

What is a set list mode?

[MacDaddy]

On 27/09/2025 at 13:45, Quatschmacher said:

Some really interesting discussions happening now around further improvements to onboard patch management/editing. If these come to fruition it’ll be fricking awesome. 

 

 

Will any of this filter down to v3?

[Woodinblack]

16 minutes ago, MacDaddy said:

 

 

Will any of this filter down to v3?

 

I think that is covered 4 posts up!

[MacDaddy]

1 minute ago, Woodinblack said:

 

I think that is covered 4 posts up!

 

Ah, but you never know!

[Quatschmacher]

1 hour ago, MacDaddy said:

 

 

Will any of this filter down to v3?

Absolutely not. V3 has no remaining codespace and all development ended at 3.61 when we began work on v4. 

[Quatschmacher]

1 hour ago, LawrenceH said:

Hi Peter

What is a set list mode?

Basically where you can cycle through a list of presets, say step 1 chooses preset 7, step 2 chooses preset 12, step 3 chooses preset 7 again. 

Edited 11 hours ago by Quatschmacher

[LawrenceH]

Ah ok, thanks. I can see the point of that but personally, full parameter editing would be much more useful. Especially if patch organisation via the pedal is going to be a thing (since I would never use 99 patches for unique voices, I'd just arrange the banks to suit particular sets)

[Quatschmacher]

1 hour ago, LawrenceH said:

Ah ok, thanks. I can see the point of that but personally, full parameter editing would be much more useful. Especially if patch organisation via the pedal is going to be a thing (since I would never use 99 patches for unique voices, I'd just arrange the banks to suit particular sets)

Sadly full patch editing (my personal preference) has been nixed due to being too hard to fully implement the Flexi controllers with the limited panel display. 😔 I’m gutted as I spent quite a long time fleshing out detailed interface ideas for this. 

 

Patch organisation is already in and working though. 

Edited 8 hours ago by Quatschmacher

[LawrenceH]

Ah shame, yeah I did think it was pretty ambitious given the parameter depth/breadth! I remember the 90s S&S synths (eg Korg, Alesis) were really well designed for this - but even they relied on 2x16 LCDs to navigate the menus.

 

Incidentally I have had trouble with the super-cheap midi interface I bought, not sure if it's user error, my computer or the interface itself, but I'm going to order something like the Behringer Go to see if it resolves itself. I've managed to load the odd patch but manual editing seems inconsistent and I wouldn't trust it to update firmware.

[Quatschmacher]

49 minutes ago, LawrenceH said:

Ah shame, yeah I did think it was pretty ambitious given the parameter depth/breadth! I remember the 90s S&S synths (eg Korg, Alesis) were really well designed for this - but even they relied on 2x16 LCDs to navigate the menus.

 

Incidentally I have had trouble with the super-cheap midi interface I bought, not sure if it's user error, my computer or the interface itself, but I'm going to order something like the Behringer Go to see if it resolves itself. I've managed to load the odd patch but manual editing seems inconsistent and I wouldn't trust it to update firmware.

Which FI model do you have? Up to and including v3 can be problematic with cheap interfaces. V4 has worked with every cheap interface I’ve used. The data packet sizes were made deliberately smaller to ensure this. 

Edited 7 hours ago by Quatschmacher

[MacDaddy]

3 hours ago, Quatschmacher said:

Absolutely not. V3 has no remaining codespace and all development ended at 3.61 when we began work on v4. 

 

 

If I can get a sound close to "that" preset on the MXR synth pedal, I'd be happy to use it as a one-sound-pedal.

[LukeFRC]

59 minutes ago, MacDaddy said:

 

 

If I can get a sound close to "that" preset on the MXR synth pedal, I'd be happy to use it as a one-sound-pedal.

On a pedal that can do a billion different things - What’s “that” sound? 

[Quatschmacher]

1 hour ago, MacDaddy said:

 

 

If I can get a sound close to "that" preset on the MXR synth pedal, I'd be happy to use it as a one-sound-pedal.

Frankly it smokes the MXR and can do that sound with ease (presuming you mean the first patch).

Edited 5 hours ago by Quatschmacher

[LawrenceH]

2 hours ago, Quatschmacher said:

Which FI model do you have? Up to and including v3 can be problematic with cheap interfaces. V4 has worked with every cheap interface I’ve used. The data packet sizes were made deliberately smaller to ensure this. 

I have the VIP with recent firmware (possibly current? Would need to check), and the usb interface is I think one you have had working. It does talk to the FI4 but seemed erratic when adjusting settings and loading/initialising patches. One issue is not knowing what 'correct' operation is meant to look like when editing patches especially when learning my way around a new synth architecture.

 

I'm generally not a huge fan of learning from videos, but a clear, dry tutorial on building a 'classic' patch (eg Chameleon) from a freshly initialised patch would actually be very helpful for unlocking and showcasing the power of this pedal.

[Quatschmacher]

31 minutes ago, LawrenceH said:

I have the VIP with recent firmware (possibly current? Would need to check), and the usb interface is I think one you have had working. It does talk to the FI4 but seemed erratic when adjusting settings and loading/initialising patches. One issue is not knowing what 'correct' operation is meant to look like when editing patches especially when learning my way around a new synth architecture.

 

I'm generally not a huge fan of learning from videos, but a clear, dry tutorial on building a 'classic' patch (eg Chameleon) from a freshly initialised patch would actually be very helpful for unlocking and showcasing the power of this pedal.

Are you using Mac or PC?

[LawrenceH]

7 minutes ago, Quatschmacher said:

Are you using Mac or PC?

Windows 11 PC

[Quatschmacher]

10 minutes ago, LawrenceH said:

Windows 11 PC

What interface are you using. If it requires a driver, are you using the latest one from the manufacturer?

[LawrenceH]

3 minutes ago, Quatschmacher said:

What interface are you using. If it requires a driver, are you using the latest one from the manufacturer?

This very cheap one, doesn't seem to need additional drivers

[Quatschmacher]

2 minutes ago, LawrenceH said:

This very cheap one, doesn't seem to need additional drivers

That’s the cheap one I use and it’s been fine. What are the MIDI settings you’re using? Do you have any other MIDI-usb devices connnected? Windows only allows one active at a time. If you have something else open, the editor won’t connect. 

Edited 4 hours ago by Quatschmacher

[LawrenceH]

No other devices - this is the first bit of midi kit I've used for probably over 20 years. I don't actually recall making or altering any settings at all save possibly selecting the device itself within the editor. I think chances of operator error are high. But I don't mind spending £25-odd on a name brand interface just to rule out one set of possibilities.

[Quatschmacher]

1 hour ago, LawrenceH said:

No other devices - this is the first bit of midi kit I've used for probably over 20 years. I don't actually recall making or altering any settings at all save possibly selecting the device itself within the editor. I think chances of operator error are high. But I don't mind spending £25-odd on a name brand interface just to rule out one set of possibilities.

Google chrome is also a MIDI-capable browser so if you have that open, that would also cause the editor to not communicate. 

[LawrenceH]

52 minutes ago, Quatschmacher said:

Google chrome is also a MIDI-capable browser so if you have that open, that would also cause the editor to not communicate. 

Hmm I had no idea about that! A strange and annoying quirk that seems like it would cause all sorts of problems. Can't remember if it has been open or not tbh. Will have another go, thanks for flagging that!