Why custom maps are crucial for synth plug-ins on Push 2

Discuss Push with other users.
AdamJay
Posts: 4757
Joined: Thu Mar 11, 2004 7:17 pm
Location: Indianapolis, USA

Why custom maps are crucial for synth plug-ins on Push 2

Post by AdamJay » Thu Nov 26, 2015 2:14 am

One thing to remember with using Push 2 to program synth plug-ins, especially when the desire is to mimic a hardware synth experience, is that it takes time to develop the muscle memory needed to take things over to "hardware synth land". To truly develop that muscle memory and still take advantage of having numerous synths at your fingertips will require some custom mapping.

Even though Monomachine has 5 different types of synthesis methods inside, 6 of its 7 programming pages are the same no matter what method is employed. So for filters, FX, AMP, LFOs you know from experience exactly where to go to accomplish what you wish. The navigation becomes second nature.

To become well trained for speedy synth programming on Push 2 will require taking the time to design your own custom maps with commonalities for your favorite plug-ins. For instance, populating the 4th page with filter parameters on Monark the same as you do for the 4th page on Diva, or DiscoveryPro, etc...

There's a big payoff in designing a uniform custom layout to all your synth plug-ins. My design consists of dedicating the first two banks of 8 to the unique parameters of that particular synth (wavetables, or FM operators, or unique modulation options), then making uniform assignments on the subsequent banks for all the synth plug-ins I'll use with Push 2. If "LFO 1 rate" is the first parameter of Page 6 on every synth plug-in I use with Push 2, then I'll never have to search for "LFO 1 rate".
It takes a little planning and maybe an hour of executing to get it just right across two or three different synths, but in a lot of ways it is like designing your own synth interface within the Push 2 environment.

The alternative is drowning in all the possibilities that this black slate with a screen gives us. Navigating through numerous VSTs and searching for the parameter you need because each one has different features and therefore very different mappings.... using a mouse would be better.

jbone1313
Posts: 578
Joined: Wed Dec 12, 2007 2:44 am

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by jbone1313 » Thu Nov 26, 2015 3:05 am

Is it possible to insert spaces between parameters, or does it force you to add them sequentially? For example, can you map to page 6 before you map anything to page 1?

jestermgee
Posts: 4500
Joined: Mon Apr 26, 2010 6:38 am

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by jestermgee » Thu Nov 26, 2015 3:23 am

jbone1313 wrote:Is it possible to insert spaces between parameters, or does it force you to add them sequentially? For example, can you map to page 6 before you map anything to page 1?
No and that is one of the things I am hoping will be possible (like on the Komplete S series keyboards)

AdamJay
Posts: 4757
Joined: Thu Mar 11, 2004 7:17 pm
Location: Indianapolis, USA

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by AdamJay » Thu Nov 26, 2015 3:27 am

jbone1313 wrote:Is it possible to insert spaces between parameters, or does it force you to add them sequentially? For example, can you map to page 6 before you map anything to page 1?
Afraid not, and that makes uniform custom maps more of a challenge.

Sometimes I will leave unique but rarely used parameters out of the map, or just put them in the first two banks to fill things out evenly. It's a balancing act.

Fortunately envelopes (Amp ADSR and Filter ADSR) will populate one bank with 8 common parameters.
My Filter parameters are often Mode, Frequency, Resonance, Drive (if available), Keyrack, Env amount, Velocity, Modulation.
If there are 2 filters, then I may only use a limited amount of available Filter 2 parameters.

login
Posts: 1870
Joined: Sat Jul 16, 2011 12:41 am

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by login » Thu Nov 26, 2015 3:59 am

I totally agree and it is one of the reasons I find "automapping" limited and honestly can't get why people ask for it so much. To me it is far more important to have information feedback (as the screen on push) but what is now missing are more controls to avoid jumping through so many pages.

A controller with 32 controllers and a nice screen as Push has would be great.

S4racen
Posts: 5822
Joined: Fri Aug 24, 2007 4:08 pm
Location: Dunstable
Contact:

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by S4racen » Thu Nov 26, 2015 9:51 am

jbone1313 wrote:Is it possible to insert spaces between parameters, or does it force you to add them sequentially? For example, can you map to page 6 before you map anything to page 1?
This is one of the features of our PrEditor Utility which we'll be bringing to Push 2 over the coming weeks...

http://isotonikstudios.com/sigabort/isotonik-preditor/

Cheers
D

AdamJay
Posts: 4757
Joined: Thu Mar 11, 2004 7:17 pm
Location: Indianapolis, USA

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by AdamJay » Thu Nov 26, 2015 2:42 pm

S4racen wrote:
jbone1313 wrote:Is it possible to insert spaces between parameters, or does it force you to add them sequentially? For example, can you map to page 6 before you map anything to page 1?
This is one of the features of our PrEditor Utility which we'll be bringing to Push 2 over the coming weeks...

http://isotonikstudios.com/sigabort/isotonik-preditor/

Cheers
D
Wonderful!
Maybe my question is answered in the video, but I was unable to watch it... will it be possible to name the Banks for Push 2? Such functionality, combined with the blank spaces, would be a dream.

tedlogan
Posts: 1347
Joined: Thu Dec 20, 2012 7:23 pm
Location: Leamington Spa, UK
Contact:

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by tedlogan » Thu Nov 26, 2015 2:54 pm

AdamJay wrote:
S4racen wrote:
jbone1313 wrote:Is it possible to insert spaces between parameters, or does it force you to add them sequentially? For example, can you map to page 6 before you map anything to page 1?
This is one of the features of our PrEditor Utility which we'll be bringing to Push 2 over the coming weeks...

http://isotonikstudios.com/sigabort/isotonik-preditor/

Cheers
D
Wonderful!
Maybe my question is answered in the video, but I was unable to watch it... will it be possible to name the Banks? Such functionality, combined with the blank spaces, would be a dream.
Absolutely - that would be wonderful.

While I don't do deep patch programming on Push as I prefer the mouse+keyboard by far for that (try programming Zebra 2 effectively from a device such as Push...no thanks), I do very often tweak existing patches on it. I also use your method atm - storing filters/ADSR/etc from different synths in the same banks and so on, as I have no intention of memorizing different default configs for different VSTs across unnamed banks.

S4racen
Posts: 5822
Joined: Fri Aug 24, 2007 4:08 pm
Location: Dunstable
Contact:

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by S4racen » Thu Nov 26, 2015 3:33 pm

AdamJay wrote:
S4racen wrote:
jbone1313 wrote:Is it possible to insert spaces between parameters, or does it force you to add them sequentially? For example, can you map to page 6 before you map anything to page 1?
This is one of the features of our PrEditor Utility which we'll be bringing to Push 2 over the coming weeks...

http://isotonikstudios.com/sigabort/isotonik-preditor/

Cheers
D
Wonderful!
Maybe my question is answered in the video, but I was unable to watch it... will it be possible to name the Banks for Push 2? Such functionality, combined with the blank spaces, would be a dream.
Yes, bank naming and blank spaces are both possible! My favourite bit is the Multi settings so that i can have multiples of the same parameter in different banks, so whatever bank i'm in for example the first encoder is always volume!

Cheers
D

AdamJay
Posts: 4757
Joined: Thu Mar 11, 2004 7:17 pm
Location: Indianapolis, USA

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by AdamJay » Thu Nov 26, 2015 3:45 pm

S4racen wrote:
Yes, bank naming and blank spaces are both possible! My favourite bit is the Multi settings so that i can have multiples of the same parameter in different banks, so whatever bank i'm in for example the first encoder is always volume!

Cheers
D
Sold!

Just signed up for your mailing list updates to get informed when it is available for Push 2.
And if you need a beta tester, let me know.

The multi assignments of same parameter is great too. Looking forward to it. This is going to help turn Push 2 into the digital hardware synth I've always wanted.

S4racen
Posts: 5822
Joined: Fri Aug 24, 2007 4:08 pm
Location: Dunstable
Contact:

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by S4racen » Thu Nov 26, 2015 4:00 pm

Shouldn't be too long for that...

Cheers
D

tedlogan
Posts: 1347
Joined: Thu Dec 20, 2012 7:23 pm
Location: Leamington Spa, UK
Contact:

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by tedlogan » Thu Nov 26, 2015 4:09 pm

Yes, sold here too :)

Can parameters be renamed as well?

S4racen
Posts: 5822
Joined: Fri Aug 24, 2007 4:08 pm
Location: Dunstable
Contact:

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by S4racen » Thu Nov 26, 2015 4:31 pm

tedlogan wrote:Yes, sold here too :)

Can parameters be renamed as well?
No they're taken from the source...

Cheers
D

tedlogan
Posts: 1347
Joined: Thu Dec 20, 2012 7:23 pm
Location: Leamington Spa, UK
Contact:

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by tedlogan » Thu Nov 26, 2015 4:38 pm

Ok cheers. Still sold though :)

S4racen
Posts: 5822
Joined: Fri Aug 24, 2007 4:08 pm
Location: Dunstable
Contact:

Re: Why custom maps are crucial for synth plug-ins on Push 2

Post by S4racen » Thu Nov 26, 2015 5:10 pm

S4racen wrote:
tedlogan wrote:Yes, sold here too :)

Can parameters be renamed as well?
No they're taken from the source...

Cheers
D
Edit... That function should be added at a later date, we've currently focused on our own scripts and are adding VST and MaxforLive device support in the next week or so, the rest should be around Mid to late December...

Cheers
D

Post Reply