• 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 free Log in
    Want zero display ads or expanded classifieds tools? Compare plans.

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

#3,421
gastric said:
So, in the current editor the entire left side of the UI are the first batch of sounds you work with: VCO (synth oscillators) and the distortion/harmonizer block. These run in parallel and are spawned from your bass input signal. Those signals, as well as your raw bass, then go into a mixer that feeds the VCF (filter). That then goes into a mixer that feeds the effects block. Finally the VCF (the filter + effects) goes into the final mixer where you can mix the VCF (whatever you mixed into the filter + the effects block) and your clean input signal (bass).

Seems simple right? :)
Click to expand...

Clear as mud!

Actually, I kind of get it. My question was more about the mixing parameters. So the "Input" block has Bass, Dist., Ar. Dist., Synth, and Noise. These are the levels going in to the VCF, and then VCF and bass are blended in the "Main" block and that's your final output?

And the input block---Bass is direct, Dist. is the distortion/harmonizer block, Synth is all of the synth waveforms?
 
#3,423
Dumb question time: where are the default patches for OS X? They were part of the Windows installation but the Mac download only seemed to include the editor itself...

ficelles

Note to self: next time download the distribution package, not just the editor.
 
Last edited:
#3,424
BroBro said:
Does it have any sort of cabinet sim?
Click to expand...

Adamixoye said:
Clear as mud!

Actually, I kind of get it. My question was more about the mixing parameters. So the "Input" block has Bass, Dist., Ar. Dist., Synth, and Noise. These are the levels going in to the VCF, and then VCF and bass are blended in the "Main" block and that's your final output?

And the input block---Bass is direct, Dist. is the distortion/harmonizer block, Synth is all of the synth waveforms?
Click to expand...

You are correct.

Ar.Dist is an attack-only sound, Noise is a noise only sound. I believe both are triggered from the envelope of your input signal (your bass).

Once you get into the editor this is one of those times you'll definitely want to read and reference the user manual. Even if you have programmed synths before as it doesn't totally follow "normal" synth workflow / functionality, at least based on the one's I've worked with.
 
#3,425
I took 20 minutes and whipped up this JPG that I believe shows the signal workflow in the editor. The main reason the editor is so confusing is that there's no real logical arrangement of the UI in regard to the signal path. I did my best to hack up the UI and arrange it left-to-right as the signal flows. You can see all of the mixers make it complicated. :)

I didn't go back an physically test the editor VS what I think is happening. Hmmm, or look at the user manual. I believe Noise, Ar.Dist are both triggered from envelope of your bass as opposed to from the VCO section. But that might be wrong.

I did this in Pixelmator on Mac. I saved the Pixelmator file and an exported scaled down JPG to the shared TB Google Drive we've been saving our patches to in case anyone wants to take a stab at making it look, errrr, more professional. Or fixing any problems with the flow.


[Invalid or Expired Link Removed]
 
  • Like
Reactions: Bastijnv, jpeck, bassvirtuoso and 5 others
#3,426
Adamixoye said:
Did Chris W. officially endorse it? I know Bootsy did.
Click to expand...

Yes, both. It is obvious in Bootsy's case, as he sent a photo; Chris did not, but his manager sent the quote that we can cite. I will meet them in one week from now when Muse is in Vienna.

Andras Szalay
 
  • Like
Reactions: Randy Ward, BassManPatsFan, Jazz Ad and 6 others
#3,427
@Andras Szalay I have some comments about the new firmware. First off, thank you, having the ability to bypass the pedal via MIDI and a global MIDI channel are two small but important improvement that I (along with many others) were really hoping for.

I notice that when using CC #67 to decrement the preset, the preset can only be engaged by pressing the physical right footswitch rather than engaging the pedal with a CC #66 command of >64. Perhaps this is something that could be changed in a future version?

Along those same lines, perhaps there could be a dedicated MIDI command to do preset increment (normal operation of the left footswitch) so that one could operate the unit completely hands free?
 
#3,431
Adamixoye said:
@Andras Szalay

I notice that when using CC #67 to decrement the preset, the preset can only be engaged by pressing the physical right footswitch rather than engaging the pedal with a CC #66 command of >64. Perhaps this is something that could be changed in a future version?
Click to expand...

I tested it now and I do not see any problem, it works as it supposed to, copying the functionality of the increment pedal in both modes. In Default Mode it changes only the display, and waiting for confirmation with the right pedal, just as the left (increment) pedal; in Direct Mode (which makes much more sense anyway) a confirmation is not necessary, decrementing the program acts immediately, again just as the left pedal.

Andras Szalay
 
#3,432
Andras Szalay said:
I tested it now and I do not see any problem, it works as it supposed to, copying the functionality of the increment pedal in both modes. In Default Mode it changes only the display, and waiting for confirmation with the right pedal, just as the left (increment) pedal; in Direct Mode (which makes much more sense anyway) a confirmation is not necessary, decrementing the program acts immediately, again just as the left pedal.

Andras Szalay
Click to expand...

I'm not suggesting that anything isn't working as you intend it to. But it seems to me that in Default mode the MIDI #66 command should be able to provide confirmation rather than needing to press the physical pedal. Otherwise it isn't quite as useful to use MIDI #67, but then need to press the pedal for confirmation.
 
#3,433
Adamixoye said:
I'm not suggesting that anything isn't working as you intend it to. But it seems to me that in Default mode the MIDI #66 command should be able to provide confirmation rather than needing to press the physical pedal. Otherwise it isn't quite as useful to use MIDI #67, but then need to press the pedal for confirmation.
Click to expand...
If you use a MIDI controller with the FI I don't see any reason not to use it in Direct mode. Even without one there are much more possibilities compared to the Default mode. With the MIDI 67 command and Default mode you can simulate the original Deep Impact with a switch pedal in the Program Down input, so it makes sense. If you want extended possibilities then use the Direct mode, and then you can scroll upwards and downwards, not restricted by bank bondaries, etc.
 
#3,434
Lippi said:
If you use a MIDI controller with the FI I don't see any reason not to use it in Direct mode. Even without one there are much more possibilities compared to the Default mode. With the MIDI 67 command and Default mode you can simulate the original Deep Impact with a switch pedal in the Program Down input, so it makes sense. If you want extended possibilities then use the Direct mode, and then you can scroll upwards and downwards, not restricted by bank bondaries, etc.
Click to expand...

I guess I should experiment with Direct mode then, as I have not done this so far. However, I still think my idea might be worth implementing for Default mode.
 
#3,435
I'm looking for some suggestions... I'm using the new editor, but I have a problem. I am trying to edit the programs on the F1 , utilizing the editor's virtual keyboard to audition the paramaters,
after alterations. But the keyboard only emits a piano tone, and doesn't reflect any of the parameter alterations. I'm attempting to use an Ir Midi bass as a controller, with some degree of success on certain patches. But it appears that I have to edit each patch as to portamento settings, as there does not appear to be a way to globally adjust the midi portamento settings. Also, I have been unable to audition the parameter changes during the editing process by just sending midi out data via isb to the Pc, with the Ir midibass a a controller. Any help resolving this issue would be greatly appreciated!
 
Last edited:
#3,436
aesopslyre said:
I'm looking for some suggestions... I'm using the new editor, but I have a problem. I am trying to edit the programs on the F1 , utilizing the editor's virtual keyboard to audition the para,after alterations. But the keyboard only emits a piano tone, and doesn't reflect any of the parameter alterations. I'm attempting to use an Ir Midi bass as a controller, with some degree of success on certain patches. But it appears that I have to edit each patch as to portamento settings, as there does not appear to be a way to globally adjust the midi portamento settings. Also, I have been unable to audition the parameter changes during the editing process by just sending midi out data via isb to the Pc, with the Ir midibass a a controller. Any help resolving this issue would be greatly appreciated!
Click to expand...

I haven't tried triggering via MIDI NOTE nor the editor keyboard so I can't speak to that.

But I would want portamento on a per-patch basis as I wouldn't want portamento on every single patch.

I wish there was portamento when triggered via audio input.... such a key synth feature that differentiates a synth from a normal instrument.
 
  • Like
Reactions: Basehead and Witness412
#3,437
gastric said:
I haven't tried triggering via MIDI NOTE nor the editor keyboard so I can't speak to that.

But I would want portamento on a per-patch basis as I wouldn't want portamento on every single patch.

I wish there was portamento when triggered via audio input.... such a key synth feature that differentiates a synth from a normal instrument.
Click to expand...


The problem is that it is difficult, if not impossible, to edit the patches without hearing an audio preview, as the patches were created with an E.bass being a substantial portion of the patch. They sound quite different when triggered by a midi controller, without significant low-end frequency content. .. Also, how does one set portamento rate without hearing what would be appropriate?
 

Latest posts

Top Bottom
Back