New ICON P1-NANO ...

[Jon White]

Just hooked up my new P1-Nano and wonder if anyone knows what the Cakewalk commands in the Cakewalk Template are sourced from.  I'm having to map Keystroke Commands via HOTKEYS to do any custom setup, because much functionality is to be desired. 

I can't figure out, for instance, what "Punch" means in the template, other than switching the transport arrows to selecting set punch points.

Are these templates uneditable and coded by ICON in ways we can affect?

Thanks for any help.  The unit might become very popular for only $300.

 

Jonas

[57Gregy]

I believe the 'punch' you're seeing is for 'Punch-in recording'. 

[Bill & Wendy Hester]

Hi Jonas

Very curious to know how you are getting on with the P1 Nano? I’m considering this instead of X Touch One and SSL UF1.

Really appreciate any insights you can share. 
 

Thanks and regards, Bill Hester

[Jon White]

Hi Bill,

It's doing quite well, although I haven't figured out some aspects of it.

I've programmed everything I like to use into it via key-commands, and use it freely with Samplitude Pro X and Cakewalk and Nuendo.

It's quite a nice unit.  I didn't need multiple faders and overall control-console functionality -- just wanted to get my hands off the mouse or in tandem with the mouse, and this is great.  Well-devised hardware!

The price is amazing, so we'll see about the durability.  It only needs slight touches versus "button-press" pressure. 

Feel free to ask me where I am with things.  I may need your help, too, if you get one!

 

Jonas

Edited February 10 by Jon White

[Bill & Wendy Hester]

Hey Jonas

Thanks SO much for the kind and considered reply!  You've made me want to pull the trigger on this, and I think I will join you in the club!

I completely agree with you around the aspiration - I actually feel pretty comfortable with mouse and keyboard and have a quick workflow and use a number of shortcuts which feels pretty good.  It's just that if there's a way to make it better/faster, why wouldn't I explore that?  I like the idea of being able to use both hands in concert, and I guess the having hardware buttons for a number of the main functions is going to a bit (but not vastly) quicker than locating on the screen...

Could I please trouble you with a couple of questions?  Curious to know whether I can select any track in CbB and whether the controller then seamlessly follows - so I can be confident that the changes I'm making are actually the correct ones in the DAW?  I guess this would be the minimum standard for anyone right?  Do you feel that you can trust the hardware, and you're not making inadvertent errors?  Is the navigation quick/easy/intuitive?  Hopefully even faster than without the hardware?

In terms of writing automation, does this work as expected?  At the moment I'm all about adding pairs of nodes with the mouse, raising/lowering, listening back and adjusting.  I guess that with hardware automation there's always going to be a little bit of a lag, eg "I can't hear vocal, I lift the fader".  Would you take the resulting envelope and shift it forward in the timeline a few miliseconds, so that it acts more like a 'look-ahead' if that makes sense?  Or is this over-thinking it!!?  haha.

The other thing I was worrying about was whether the fader is noisy (apparently a concern with more budget units) and also whether the layout of the transport buttons is ergonomic - looks from the picture like the jog wheel is slightly in the way?  

REALLY appreciate any insights you can share right now.  I will try to pay this forward when I get my unit and happy to help you with anything I can, come the time

Thanks again and warm wishes, Bill Hester

Edited February 12 by Bill & Wendy Hester

[Bill & Wendy Hester]

Ps Jon - so sorry for the long-winded questions!!! I would LOVE  to hear any experience you can share (I have credit card in hand 😅🤩😂). Thanks again and warm regards from chilly 🥶 UK

[minminmusic]

Just picked up the P1-M. Automation seemed to be written ok. Weird to see it actually "drawn" rather than nodes and lines.
Fader noise...I did an automation write where I tried to go crazy with the faders and encoders so I could replay. Faders are a noisy and watching them, the movement had a little jitter to it. I also did a similar test in Luna and I felt the fader movement  "translation" might have been a little smoother and therefor a little less noisy.

Again...only had this for a few hours.

[msmcleod]

5 hours ago, minminmusic said:

Just picked up the P1-M. Automation seemed to be written ok. Weird to see it actually "drawn" rather than nodes and lines.
Fader noise...I did an automation write where I tried to go crazy with the faders and encoders so I could replay. Faders are a noisy and watching them, the movement had a little jitter to it. I also did a similar test in Luna and I felt the fader movement  "translation" might have been a little smoother and therefor a little less noisy.

Again...only had this for a few hours.

When you're recording automation, you're shown a preview of the automation - more to give you some confidence that the automation is being recorded than anything else.  The automation points are then "smoothed" after recording, picking curves that best fit the recorded points.  

In the new Sonar you have more control over this process:  in the "Automation Smoothing" menu under Track View Options, you can choose:

• Smoothing:  same behaviour as CbB / SONAR Platinum - This reduces the number of recorded automation points by picking curves that best fit the recorded points. Useful if you expect to manually edit the automation afterwards, as you end up with a smoother automation lane than hundreds of automation nodes.
• As Recorded (Linear):  preserves all the recorded points received from the controller as individual nodes, and joins them with linear lines. Use this when you need a smooth transition between points, and accuracy is more important than editing afterwards (there will be far more individual nodes than the smoothing behaviour).
• As Recorded (Jumps): similar to above.. it preserves all the recorded points received from the controller as individual nodes, but doesn't join them.  Use this when you don't want a transition between the points - i.e. when recording "mode" type parameters such as synth oscillator waveform, EQ modes or on/off parameters.