Where are you pressing application key on? Are you in the synth rack?
What exactly are you trying to do?
Regards, DJX
________________________________
From: ddots-l-bounce@xxxxxxxxxxxxx <ddots-l-bounce@xxxxxxxxxxxxx> on behalf of
Kevin L Gibbs <kevjazz@xxxxxx>
Sent: Tuesday, April 4, 2017 4:39:37 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: How to expose the automatable parameters in Omnisphere
with Sonar 8.5?
The Applications key yielded nothing useful:
Here is what I got:
Remove from Group, Unavailable.
Clear Group, Unavailable.
Group Submenu
Below that is a group of 24 or so possible subgroups.
Group Manager.
Value Submenu
Below that is:
Set Start as Curent.
Set End as Current.
Set Snap to as Current.
Automation Rad
Automation Write
Automation SnapshotRemote Controldisable Remote Controlk
Similarly, inserting Omnisphere on a track’s effects bin didn’t do anything
useful either. That may have to do with he fact that I really never did learn
the inspector. But I’m progressively of the opinion that this is probably not
the way to go.
Thanks,
Kevin
On Apr 4, 2017, at 3:06 PM, DJX
<megamansuperior@xxxxxxxxxxx<mailto:megamansuperior@xxxxxxxxxxx>> wrote:
Once you load omnisphere and select your sound, close the omni window. From the
track view, press alt 8 to open the synth rack. Now up or down arrow to the
instance of omnisphere you are working with. Now press the context key, also
called the applications key, and it will show you a list of the available
controls. Alternatively, insert the synth on an audio track's effect bin, and
manually assign a midi track to it. Then use the audio track with the inspector.
Note however that omnisphere 1 at least didn't expose too many parameters, at
least not when i tried it last.
Regards, DJX
________________________________
From: ddots-l-bounce@xxxxxxxxxxxxx<mailto:ddots-l-bounce@xxxxxxxxxxxxx>
<ddots-l-bounce@xxxxxxxxxxxxx<mailto:ddots-l-bounce@xxxxxxxxxxxxx>> on behalf
of Kevin L Gibbs <kevjazz@xxxxxx<mailto:kevjazz@xxxxxx>>
Sent: Tuesday, April 4, 2017 3:46:03 PM
To: ddots-l@xxxxxxxxxxxxx<mailto:ddots-l@xxxxxxxxxxxxx>
Subject: [ddots-l] Re: How to expose the automatable parameters in Omnisphere
with Sonar 8.5?
Xavier,
I assume the context menu is Shift A. That gives me Rewire and soft synths. I
can choose the properties page of Omnisphere there. But I have no idea where I
find the list of automatalbe parameters there. Do I have to click on knobs on
the on screen interface of Omnisphere?
I don’t think I’m following. Like I said, I MIDi learned RMx a decade ago.
But I have no idea how to enable automation here.
On Apr 4, 2017, at 2:41 PM, DJX
<megamansuperior@xxxxxxxxxxx<mailto:megamansuperior@xxxxxxxxxxx>> wrote:
Go to synth rack, use context menu on the desired synth, and assign one of the
parameters. Those are automatable.
Regards, DJX
________________________________
From: ddots-l-bounce@xxxxxxxxxxxxx<mailto:ddots-l-bounce@xxxxxxxxxxxxx>
<ddots-l-bounce@xxxxxxxxxxxxx<mailto:ddots-l-bounce@xxxxxxxxxxxxx>> on behalf
of Kevin L Gibbs <kevjazz@xxxxxx<mailto:kevjazz@xxxxxx>>
Sent: Tuesday, April 4, 2017 3:36:49 PM
To: ddots-l@xxxxxxxxxxxxx<mailto:ddots-l@xxxxxxxxxxxxx>
Subject: [ddots-l] How to expose the automatable parameters in Omnisphere with
Sonar 8.5?
Subject says it all. Trying to record what I believe are automation moves in
Omnisphere as generated by my KK keyboard. I guess I need to expose the
automatable parameters of Omnisphere in Sonar. I’ve done it in RMX. But it
was years ago.
Any thoughts?
KevinPLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx<mailto:ddots-l-request@xxxxxxxxxxxxx>?subject=subscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx<mailto:ddots-l-request@xxxxxxxxxxxxx>
and in the Subject line type
unsubscribe
For other list commands such as vacation mode,
click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx<mailto:ddots-l-request@xxxxxxxxxxxxx>?subject�q or
send a message, to
ddots-l-request@xxxxxxxxxxxxx<mailto:ddots-l-request@xxxxxxxxxxxxx>
and in the Subject line type
faq
