What is Nektar's DAW Integration anyway?
-
- KVRer
- Topic Starter
- 13 posts since 10 May, 2019
Their keyboards come with an installer for the integratioin that I don't see doing any more than putting a DLL in place. Is there more to it than that? If not, why the installer?
- KVRAF
- 12449 posts since 7 May, 2006 from Southern California
It depends on which DAW you are using but on the Windows side, our integration for Cubase, Reaper, Cakewalk and Digital Perfomer is based on .dll files. These files allow our controllers to be detected as controller surfaces in those DAWs. Other DAWs have script based control surface APIs, so the installed files may be LUA, Python or Java script.
The installers ensure that the files are placed in the correct directories. With our Cakewalk support the installer also creates a registry key (otherwise Cakewalk/Sonar would not read the file). Depending on which DAW you are using, our plug-in map files may also be installed.
The installers ensure that the files are placed in the correct directories. With our Cakewalk support the installer also creates a registry key (otherwise Cakewalk/Sonar would not read the file). Depending on which DAW you are using, our plug-in map files may also be installed.
- KVRAF
- 2918 posts since 13 Apr, 2008 from Charleston, SC
I have a Panorama P6, and it is quite deep. I use with Nuendo 11 and it works fantastically.
-
- KVRer
- Topic Starter
- 13 posts since 10 May, 2019
Thanks. I bought an Impact GX Mini since I liked the LX25+ I've had for a while. I'm on Win10, Reaper 6.40. The GX Mini has a weird issue in that I have to keep adding it to Reaper Control surfaces every time I open Reaper. It's remembered OK in MIDI Devices. Integration functionality seems fine, but I really only use the Transport.justin3am wrote: ↑Wed Nov 24, 2021 12:07 am It depends on which DAW you are using but on the Windows side, our integration for Cubase, Reaper, Cakewalk and Digital Perfomer is based on .dll files. These files allow our controllers to be detected as controller surfaces in those DAWs. Other DAWs have script based control surface APIs, so the installed files may be LUA, Python or Java script.
The installers ensure that the files are placed in the correct directories. With our Cakewalk support the installer also creates a registry key (otherwise Cakewalk/Sonar would not read the file). Depending on which DAW you are using, our plug-in map files may also be installed.
I checked with Support at Nektar beginning of October, and after some back and forth I was told the issue would go the Devs. That was the last I heard, and there have been no new dll updates or firmware. I was thinking there might be since it is so new. I'd like to know if there's anything else I could try on my end.
- KVRAF
- 12449 posts since 7 May, 2006 from Southern California
Funny you mention that. I'm in the process of posting new installers to our internal servers for customer release. The issue you mentioned is fixed in the new version of the files, which should be posted to the Nektar website in the coming days. If the new installer doesn't get posted today, it will be there next week (we'll be out of the office for the Thanksgiving holiday, here in the US).
- KVRian
- 700 posts since 19 Jan, 2008
Any news about firmware update for Panorama T6? There are some bugs that I reported almost a year ago.justin3am wrote: ↑Wed Nov 24, 2021 11:03 pm Funny you mention that. I'm in the process of posting new installers to our internal servers for customer release. The issue you mentioned is fixed in the new version of the files, which should be posted to the Nektar website in the coming days. If the new installer doesn't get posted today, it will be there next week (we'll be out of the office for the Thanksgiving holiday, here in the US).
![Prayer :pray:](./images/smilies/icon_pray.gif)
-
- KVRist
- 167 posts since 3 Jun, 2016
Watching and waiting, let us know when you post.
Hopefully for P1 too?
I have had that issue with Reaper before, I did a factory reset and added my extras back. Never had the problem since.
Use mine with Reason 11, Cubase 11, Reaper, Studio One 4.5
Hopefully for P1 too?
I have had that issue with Reaper before, I did a factory reset and added my extras back. Never had the problem since.
Use mine with Reason 11, Cubase 11, Reaper, Studio One 4.5