Take your time, take the time you need to make sure it comes out right for us, good things come to those who wait. I’m so psyched about this, I bought my panorama P6 last year hoping this would happen someday.justin3am wrote: Wed May 29, 2019 9:43 pm No problem, thanks for your enthusiasm! I'm pretty excited about getting this out, too. Now, back to work for me!
Full Nektar support for Studio One now available plus the new Nektarine tool
-
- KVRist
- 418 posts since 26 Feb, 2007
-
- KVRAF
- 9148 posts since 7 Oct, 2005
This is great news! Especially it comes with the news of Studio One bugs fixes!justin3am wrote: Wed May 29, 2019 9:36 pm I'm the one holding up the release. All the development/mapping work is done. I hope to get the Studio One support installers for Panorama P, Panorama T and Pacer posted by the end of this week but I won't make any guarantees.
Thanks for your patience.
Thank you
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
-
- KVRAF
- Topic Starter
- 25037 posts since 12 Jul, 2003 from West Caprazumia
Studio One bug fixes?
Justin works for Nektartech, not for Presonus - he has naught to do with S1's development!
Justin works for Nektartech, not for Presonus - he has naught to do with S1's development!
-
- KVRAF
- 9148 posts since 7 Oct, 2005
I know. I'm waiting for S1 integration with nektar controllers.
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
-
- KVRAF
- Topic Starter
- 25037 posts since 12 Jul, 2003 from West Caprazumia
Oh, I see, so I guess you know something I don't then.
S1 4.5 introduced a few bugs so it would certainly be nice if they'd release a fix soon.
S1 4.5 introduced a few bugs so it would certainly be nice if they'd release a fix soon.
-
- KVRAF
- Topic Starter
- 25037 posts since 12 Jul, 2003 from West Caprazumia
Oh, it's already available - I am downloading as I type. (The S1 bug-fix release I mean)
-
- KVRAF
- 9148 posts since 7 Oct, 2005
Yes those bugs 
I really hope the integration with S1 will be the same as with Bitwig.
After spending these two days with Bitwig, I really find it hard to return to S1 (because of the nektar great work). I still miss several things in S1, but let's see how all that turns in the near future, then I'll decide between Bitwig and S1 according to the nektar integration.
I really hope the integration with S1 will be the same as with Bitwig. After spending these two days with Bitwig, I really find it hard to return to S1 (because of the nektar great work). I still miss several things in S1, but let's see how all that turns in the near future, then I'll decide between Bitwig and S1 according to the nektar integration.
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
-
- KVRAF
- 2772 posts since 28 Mar, 2007
Your assimilation into the Bitwig collective has already begun - too late to turn back nowEnGee wrote: Thu May 30, 2019 10:28 am Yes those bugs
After spending these two days with Bitwig, I really find it hard to return to S1 (because of the nektar great work). I still miss several things in S1, but let's see how all that turns in the near future, then I'll decide between Bitwig and S1 according to the nektar integration.
-
- KVRAF
- 9148 posts since 7 Oct, 2005
Or maybe my assimilation was too late!
Well, I need to decide in some point about my main DAW as I don't want my projects scattered here and there. There are three DAWs competing inside my PC: Bitwig 2.3.5, S1 v4 and Live Standard 9. My choice depends heavily on which one integrates best with both my two nektar controllers, Maschine mikro and my Casio PX-5S.
To be honest, I love all the three DAWs! I can do my music inside them with no problem. However, every one has advantages above the others, but also disadvantages compared to others! So, it depends on my priorities which are:
1. Stability and features
2. Hardware integration
3. Ease of use (especially in drums mappings and workflow)
4. Cost of upgrade to latest version
You can guess now, which one wins and which one loses in each of the above points. It is not easy to decide for me, but I think it would be between S1 and Bitwig in the end.
Well, I need to decide in some point about my main DAW as I don't want my projects scattered here and there. There are three DAWs competing inside my PC: Bitwig 2.3.5, S1 v4 and Live Standard 9. My choice depends heavily on which one integrates best with both my two nektar controllers, Maschine mikro and my Casio PX-5S.
To be honest, I love all the three DAWs! I can do my music inside them with no problem. However, every one has advantages above the others, but also disadvantages compared to others! So, it depends on my priorities which are:
1. Stability and features
2. Hardware integration
3. Ease of use (especially in drums mappings and workflow)
4. Cost of upgrade to latest version
You can guess now, which one wins and which one loses in each of the above points. It is not easy to decide for me, but I think it would be between S1 and Bitwig in the end.
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
-
- KVRAF
- Topic Starter
- 25037 posts since 12 Jul, 2003 from West Caprazumia
Out now! Plus Nektarine! 
-
- KVRAF
- 9148 posts since 7 Oct, 2005
Hmmm, it gives me an error when trying to use NI Massive (or any other instrument):
"INSTRUMENT NOT FOUND
Plugin not in view
or
Panorama not focus device"
I don't know what that means but the plugin is in view. Anyway, it still works with Bitwig after the firmware update
So, I will stick with Bitwig/P4 combo
I hope it works with S1 better in a future update Good luck
Edit: oh and Nektarin is loading forever, so I needed to terminate it (it did that in S1, Bitwig and Reaper).
"INSTRUMENT NOT FOUND
Plugin not in view
or
Panorama not focus device"
I don't know what that means but the plugin is in view. Anyway, it still works with Bitwig after the firmware update
So, I will stick with Bitwig/P4 combo I hope it works with S1 better in a future update
Good luck Edit: oh and Nektarin is loading forever, so I needed to terminate it (it did that in S1, Bitwig and Reaper).
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
-
- KVRAF
- Topic Starter
- 25037 posts since 12 Jul, 2003 from West Caprazumia
Yes, it's a bit of a bummer - similarly to Reaper it seems mainly a case of "what's the point" to me.
I get the same weird error message with Superior Drummer - GUI opens here too though
"View" always opens the last opened plugin GUI in all three modes...
No support for the Fat Channel and not much for normal inserts either.
What's cool is that the Data knob controls any currently selected parameter. I have a touchscreen and so with controlling knobs (which tends to be fiddly on y touchscreen) it's just a case of simply touching any parameter with one hand while keeping the other on the Data encoder - nice!
I get the same weird error message with Superior Drummer - GUI opens here too though
"View" always opens the last opened plugin GUI in all three modes...
No support for the Fat Channel and not much for normal inserts either.
What's cool is that the Data knob controls any currently selected parameter. I have a touchscreen and so with controlling knobs (which tends to be fiddly on y touchscreen) it's just a case of simply touching any parameter with one hand while keeping the other on the Data encoder - nice!
-
- KVRAF
- Topic Starter
- 25037 posts since 12 Jul, 2003 from West Caprazumia
Okay, I tried it again with the demo of Cubase that's installed on my machine right now and it's basically the same with every DAW I tried. There's always some stuff where you wonder "why isn't that working like this" (in Cubase of the built-in channel strip only the EQ is accessible (none of the other modules) - in Reason also the compressor) and some stuff works well in some DAWS but never everything at once.
Of all those I tried I think the integration with Reason works best but even here are significant shortcomings such as e.g. using the select function of the lower channel buttons does not really/visibly select the tracks as switching with the track-buttons does. In other DAWs this works as expected.
I could only speculate why this and that doesn't really work so well (i.e. I have no idea), but in the end I think the result is basically always a half-baked integration that leaves me scratching my head and doubting that fully using the Panorama might ever really speed up/improve my workflow (because too often I have to grab for the touchscreen/keyboard/touchpad anyway).
What I don't like is that they appear to stay relatively (very in comparison to many companies) silent, so it seems one can not really get any feedback as to why this and that doesn't function as expected and if they'll ever improve it.
If someone wants my P1, make me an offer.
Of all those I tried I think the integration with Reason works best but even here are significant shortcomings such as e.g. using the select function of the lower channel buttons does not really/visibly select the tracks as switching with the track-buttons does. In other DAWs this works as expected.
I could only speculate why this and that doesn't really work so well (i.e. I have no idea), but in the end I think the result is basically always a half-baked integration that leaves me scratching my head and doubting that fully using the Panorama might ever really speed up/improve my workflow (because too often I have to grab for the touchscreen/keyboard/touchpad anyway).
What I don't like is that they appear to stay relatively (very in comparison to many companies) silent, so it seems one can not really get any feedback as to why this and that doesn't function as expected and if they'll ever improve it.
If someone wants my P1, make me an offer.
-
- KVRAF
- 13135 posts since 7 May, 2006 from Southern California
If the message appears in Panorama's display, when a plug-in window is open, it likely means that the 'Panorama' device is not in focus. At the top-right of each plug-in window, you should see this:
If you see a different controller listed in that yellow box or if the box is grey, Panorama will not be able to control the plug-in. You will need to make sure that 'Panorama' or 'Panorama T' are selected there (not 'Panorama Keyboard' or 'Panorama T Keyboard'). You can select which device is in focus by clicking the down facing triangle next to the yellow box, then choosing a device from the list.
I have conducted tests with Massive and a long list of other third-party plug-ins. As long as the plug-ins provides automatable parameters to Studio One, Panorama will be able to control the plug-in.
That said, I do recommend using Nektarine as a plug-in host, when it comes to third-party plug-ins. Only Studio One's included plug-ins are mapped by default when using Studio One's control link system.
Regarding Fat Channel... it presents a different set of parameters, depending on which stage is selected and which model is active for that stage. We thought it was best to map the parameters which appear by default when you create a new instance, so that you can see what the controls are doing. It's very easy to change control assignments using the control link system. The user guide described the process.
If you see a different controller listed in that yellow box or if the box is grey, Panorama will not be able to control the plug-in. You will need to make sure that 'Panorama' or 'Panorama T' are selected there (not 'Panorama Keyboard' or 'Panorama T Keyboard'). You can select which device is in focus by clicking the down facing triangle next to the yellow box, then choosing a device from the list.
I have conducted tests with Massive and a long list of other third-party plug-ins. As long as the plug-ins provides automatable parameters to Studio One, Panorama will be able to control the plug-in.
That said, I do recommend using Nektarine as a plug-in host, when it comes to third-party plug-ins. Only Studio One's included plug-ins are mapped by default when using Studio One's control link system.
Regarding Fat Channel... it presents a different set of parameters, depending on which stage is selected and which model is active for that stage. We thought it was best to map the parameters which appear by default when you create a new instance, so that you can see what the controls are doing. It's very easy to change control assignments using the control link system. The user guide described the process.
-
- KVRAF
- 13135 posts since 7 May, 2006 from Southern California
We are a small company. The easiest way to get in touch with us, is to create a support case via the Nektar website. You will either get a response from me or Tim (who develops the Reason, Logic, Bitwig and Studio One integration). We are always happy to answer questions to the best of our ability but generally, we don't discuss anything that hasn't been officially announced via press-release.jens wrote: Fri May 31, 2019 3:31 pmWhat I don't like is that they appear to stay relatively (very in comparison to many companies) silent, so it seems one can not really get any feedback as to why this and that doesn't function as expected and if they'll ever improve it.