Ableton Push 1 vs Nektar Panorama P1

[zfigz]

and you change the start/end/loop length with Push 1, correct?

[lunardigs]

and you change the start/end/loop length with Push 1, correct?

Yes, I believe so. I no longer have my Push 1 though. Otherwise I'd check.

[zfigz]

thanks for all the helpful info. will most likely nab a push 1 and eventually trade up for a push 2 (maybe 3 if that's on the horizon).

[Echoes in the Attic]

The Remote Controls can control Modulators, and your hardware can control Remote Controls, on per device basis.

Does that make sense?

Moreover, a Remote Control can macro-control multiple Modulators/parameter at once.

He doesn't just want to control it from hardware, but assign it in the first place

The answer is no.

Btw, I've never used Push with Ableton, so I cannot say how they differ. That said, I've never needed to assign Modulators from Push on the fly. I can imagine a few cases where this might be useful, but I wouldn't use it to design an effect--mangling samples on the otherhand would be useful. Although, anything more complex, give me a fullscreen monitor.

Can you tell me a good use case here that I'm not seeing?

See the video here at around 7 minutes:


On the hardware he enters a velocity assignment mode where when he tweaks the resonance it is affecting the amount of velocity modulation of the resonance (not the resonance itself). This was before the modulators appeared in bitwig though, this particular velocity assignment was just eh velocity in the polysynth. But if Nektar can do this then there's no reason they wouldn't be able to do it with the modulators as well. And if nektar can do it then why wouldn't Push be able to do it, it must be in the API right?

[Echoes in the Attic]

Actually this one is much better. Check at 16:55 he describes the modulation assignment from the hardware:

[zfigz]

Actually this one is much better.

do you have a nektar panorama? i'm sorta kinda interested in the p1, but the push seems a lil' more flexible/interesting.

[antic604]

Not really helping here, but I think either of those would be a better choice:
- Akai APC40 Mk2, with moss' scripts,
- Maschine JAM with native Bitwig integration: video, official NI user manual,

[Echoes in the Attic]

Actually this one is much better.

do you have a nektar panorama? i'm sorta kinda interested in the p1, but the push seems a lil' more flexible/interesting.

No I don't have one. That's why I'm asking about if you can do this modulation assignment on the nektar with modulators. When these videos were made modulations only came from the devices themselves, there weren't modulation devices yet.

I'm also curious if Push could do this. It must be possible.

[lunardigs]

Actually this one is much better. Check at 16:55 he describes the modulation assignment from the hardware:

Ahh, I see ... Yeah, there used to be 'static modulators' within the Polysynth, etc.--almost forgot about that.

Think about it though, with the new Modulator system a controller would have to browse/select your modulator (there's like 29 or so); then select your target on a given Device, which could be > 200 or so targets, like with the U-he stuff; then be able to set the Modulator parameters (LFO looks to have ~11). Plus, don't forget the Remote Controls device/preset basis paging ... All together, if done properly, would require a lot of work for a controller extension designer.

Yet, Nektar may have done all of the above. You might want to reach out them and ask. I somehow doubt they did. Although, it could be in the works.

The case with Push is the same though; you have to setup your modulators and targets first, then you can taste the sauce by twisting knobs.

Btw, good news is that a lot of Remote Control presets (which include Modulator fun) already exist for various popular devices, including other brands. Hence, Push enumerates these Remote Controls and you can start twisting away upon inserting the device.

My ultimate feeling here is that assigning modulators from a controller may not be such an advantage--especially with the inherent complexity introduced with the new Modulator system. That's not to say I wouldn't encourage such a development; I'm just not missing it really.

[zfigz]

Not really helping here, but I think either of those would be a better choice:
- Akai APC40 Mk2, with moss' scripts,
- Maschine JAM with native Bitwig integration: video, official NI user manual,

i looked on the forums and apparently there was an issue where the maschine settings weren't saved when you saved your bitwig project. it just seems that the push is more stable/flexible than the maschine.

[lunardigs]

Push is badass for launching and recording clips. Plus, making midi content with the sequencers and note scales. It's also got great pressure sensitivity for expression. It's also has two foot pedal jacks (assignable) default as a record/new clip and sustain. This to me is where is shines--composing. All the other features are there too and I've come to use. That's basically my experience with it. I'd highly encourage you to check it out. Plus, if you find it sucks, there's resale value--not just to the Bitwig crowd, of course.

[zfigz]

it's definitely the one i'm gonna get, but i'm trying to get one under $200USD which is proving more difficult than i thought.

thanks for all the recommendations/advice, much appreciated!