Re: Automating the Solaris using cubase?
Posted: Fri Jul 05, 2013 6:28 pm
Yes, I've heard from others that Cubase can be tricky...thanks so much for posting!
John Bowen Synths Community
https://forums.johnbowen.com/
But i see CC98 & 99 being identified. The question is what do u do from here? Right now, it doesn't matter if i record automatiom and move one encoder - or 5 encoders while recording. The outcome is always the same. Cubase recognizes: CC6, CC38, CC98, CC99.John Bowen wrote:Yes, as I mentioned, each parameter has to be identified before the value is sent. If you didn't see a CC99 or CC98, then no parameter was being defined, and therefore, the incoming data is affecting the most recent parameter. There's actually 4 entries we seem to be needing: the parameter identifier (CC99 & 98), and the value (CC6 & 38).
That's the part i don't understand. What does it mean to "follow it with the NRPN..."? Where do i "punch in" the NRPN number, specifically for the parameter i want to automate?John Bowen wrote:You have to put the CC99 first then follow it with the NRPN each time you want to send a controlling value.
No I really don't think you need to do anything. The fault is not in your documentation. The NRPN values are already there. The problem is that Cubase is sort of useless in handling them. As I said in an earlier post, Sonar has explicit NRPN handling so there is no math to calculate at all. I can automate as many NRPNs as I want at a time because unlike Cubase, Sonar does not have to see it as an automation of the 4 separate CC messages that define an NRPN. I created the example above by hand but I didn't have to do anything like that using Sonar. I just told it the filter cutoff NRPN value in decimal and the midi channel and it created an automation lane for it and it worked fine. All of 60 seconds as I said for both that and filter 1 resonance values.John Bowen wrote:Thank you for really making a clear explanation!!
It seems I could help things by publishing a list of all the NRPN numbers in hex, or a chart giving MSB/LSB for each so people won't have to do the math. It's just...there are a lot of parameters!
This is not a Solaris issue. ANY synth that uses NRPN's would have issues with Cubase. There are a LOT of synths that use them because it is the only practical way to get an extended range for parameter definition and data values. You definitely cannot compare the GRP A4 midi implementation to Solaris. I have a GRP A4 and honestly the midi implementation is skeletal at best. Automating filter cutoffs using just a CC value alone just doesn't sound right because the cutoff range is huge and has to be divided among 127 values. You can definitely hear the stepping of the controller.Zahush76 wrote:Now i'm triple shocked
So, basically what i should ask myself now is would i change my DAW (after learning it for quite some time) if i want to automate Solaris?
That's why i wrote - in the quote above - that i'm asking myself if i should change my DAW. I wrote "if i want to automate Solaris" because currentlly it is the only synth i got that uses NRPN's. All the rest of the synths on my desk are much simpler in this regard.inaheartbeat wrote:This is not a Solaris issue. ANY synth that uses NRPN's would have issues with Cubase.Zahush76 wrote:Now i'm triple shocked
So, basically what i should ask myself now is would i change my DAW (after learning it for quite some time) if i want to automate Solaris?