Thanks. All done parametrically in Photoshop with Blending options on Layers. makes it easy to adjust. Only weird thing is that the labels look horrible on the faders with a background, so I turned them all off. The panorama itself has minimal labels anyway. I'm going to update with the motorized fader and the extra fader control, plus some more mappable buttons.
We can't start limiting the sharing of combinator patches to only be for stock stuff that everyone has..Onkel Paul wrote: ↑23 Sep 2021And who doesn't have the Panorama cannot benefit from this either.
What do I miss here?
Don't forget to complain about these as well:Onkel Paul wrote: ↑23 Sep 2021WHY?
I am happy to have the hardware to touch.
Back to the mouse seems silly.
And who doesn't have the Panorama cannot benefit from this either.
What do I miss here?
Thanks. I wasn't trying to be mean. I just saw others doing these and thought I'd do one for MY controller of choice.Onkel Paul wrote: ↑23 Sep 2021I do not complain, I am just asking if I do miss something.
I cannot see the benefit, but I might be too stupid.
Anyhow, nice graphics, a lot of work well done. If this is a proof of concept as its sole purpose it is still ok.
I got it to work. Just needed to change to Instrument vs Mixer mode. The motorized fader does not work though.Onkel Paul wrote: ↑23 Sep 2021I see. Thank you for this explanation.
I wish you the best for getting it work with the faders as well.
For me it's a bridge between my MIDI controller and Reason, which makes hardware control of software parameters much more closely interlocked. So I create a Combi2 patch for my MIDI controller (in my case an Arturia Minilab 2). I make it part of my default Reason song then it's good to go every time I open Reason. I add devices to the Combi, map device parameters to the Combi2 controls (that are mapped to my MIDI controller's controls) label the Combi2 parameters appropriately. It's sublime. The nice backdrop is just the cherry on the cake. But what not have your cake ...... and eat itOnkel Paul wrote: ↑23 Sep 2021WHY?
I am happy to have the hardware to touch.
Back to the mouse seems silly.
And who doesn't have the Panorama cannot benefit from this either.
What do I miss here?
What I do is make sure I am in "Instrument" mode on the Panorama. Then I right click on a control and select "Edit Remote Override Mapping...". I then select "Nektar Panorama" as the control surface. I then browse to the control in the LOOOOOONNNNGGGG list until I get to the correct one. For example, if you want Fader number 3 on the combi to map to the Fader 3 on the Panorama, you need to select "Fader 3" in the pulldown list.Carrere wrote: ↑01 Oct 2021Nice work. Excited to try it, but not sure how to do the mapping on the nektar end. Currently the rotary knobs on the right side of the physical device are moving the faders in your combi. Any hints on how to correctly map the physical controls to the correct controls on your combi?
Thank you! I enjoy a good Photoshop challenge. All of mine so far are very parametric and done with creative blending options on Layers.
Thanks! I got it to work that way. Eventually someone will update the Nektar remote map file, which might make it a bit easier. Appreciate your work on this. Will make it easier to use the P4 for more flexible and creative controls in the new combinator.Despondo wrote: ↑02 Oct 2021
What I do is make sure I am in "Instrument" mode on the Panorama. Then I right click on a control and select "Edit Remote Override Mapping...". I then select "Nektar Panorama" as the control surface. I then browse to the control in the LOOOOOONNNNGGGG list until I get to the correct one. For example, if you want Fader number 3 on the combi to map to the Fader 3 on the Panorama, you need to select "Fader 3" in the pulldown list.
I'm trying to find a way to have this work more automatically, but need more time (and help?) to get it automapping to the controls. I guess with some kind of Remote Mapping.
Thanks! I'm more of a graphics person, so wasn't able to get to the remote map, so glad to see you did this. Will try it out.
I was thinking the same... I don't have a P4 (wish I did) but seems like a great way to create/save/load 'patches' for the P4, say to control a particular synth. Even if you never touch the combi controls, seems a useful too for setting up/saving routings. And then there's automation of the combi... Have to think outside the box on these thingsFaastwalker wrote: ↑24 Sep 2021For me it's a bridge between my MIDI controller and Reason, which makes hardware control of software parameters much more closely interlocked. So I create a Combi2 patch for my MIDI controller (in my case an Arturia Minilab 2). I make it part of my default Reason song then it's good to go every time I open Reason. I add devices to the Combi, map device parameters to the Combi2 controls (that are mapped to my MIDI controller's controls) label the Combi2 parameters appropriately. It's sublime. The nice backdrop is just the cherry on the cake. But what not have your cake ...... and eat itOnkel Paul wrote: ↑23 Sep 2021WHY?
I am happy to have the hardware to touch.
Back to the mouse seems silly.
And who doesn't have the Panorama cannot benefit from this either.
What do I miss here?
Users browsing this forum: No registered users and 0 guests
user since 2002
Share and download patches!
Join ReasonTalk on Slack!