image description


how should i really be setting up my keyboard/controller for full use in S1?
  Forum Index » Studio One General Discussion 
Author
Message
overcoat
Presonic
[Avatar]

Joined: 03/03/2013 20:19:25
Messages: 256
Location: SF
Offline

Alright, I'm curious how you all use your midi keyboard/controllers within S1 and VST's. I recently grabbed a Arturia Keylab controller and while i like the feel of everything (pretty solid knobs and sliders etc.) i'm having a bit of trouble wrapping my head around what it is i'm exactly supposed to do when it comes to mapping all these knobs and faders inside a vst. Lets say for instance that i open up an instance of Arturias Jupiter 8V and then map all of the knobs and faders where i want using control link. everything works great on that instance of the 8V but if i open another instance of it it doesn't seem to know what to do and i have to map all over again. I'm starting to work more with tweaking knobs rather than just drawing in automation so it's pretty essential for me to have this all worked out. Now, i guess my question is, am i needing to save presets inside my keylab for each VST i use most? Then every time i open an instance or switch tracks i need to call up that snapshot or preset form Keylab? I mean, this would be the same no matter what keyboard/controller i'm using correct?

btw, i tried the arturia forums but that place is a total ghost town and nobody offers any help. EVER. I hate that place. It's too bad too cause i like their instruments but the customer service is non existent.

Anyhoo, I'll be reading the Keylab manual in the meantime but if any of you could steer me in the right direction it would be very much appreciated.

One last thing, The Keylab has transport controls that i can't seem to get to work in S1. Could this be because I also have a faderport connected and it's already using those MMC's or something like that?

-thanks
Studio One Pro w/ latest build // i7 2.6 ghz mac mini w/ 16gb ram // RME Fireface UCX // Yamaha HS50m's // GAP Pre-73 modded // Blue Reactor mic // Shure sm7b, 57 & 58 // Roland TR8 // Faderport // Padkontrol & Edirol pcr-50 // Arturia V-collection 3.0, V-station, Synthmaster 2.5, Komplete 9 and various other vst's...
Tacman7
Presonic
[Avatar]

Joined: 01/04/2013 19:36:25
Messages: 422
Offline

I ran into that when I got a BCF2000 some years back.

There are a couple of manufacturers who deal with this issue in software like:

http://us.novationmusic.com/midi-controllers/nocturn/automap-control-software

Their software would hold all the different configurations and instantiate them when you focus on the plug in.

I hear is works but takes some effort getting it going.

I only use midi control for general uses in the project window and I don't need to tweak a vst that often.

Preset kind a guy.

That was something I discovered after I got the BCF hooked up, I like using a mouse better.

Studio One 2 Professional
8.164bit Studio Konnect 48
CPhoenix
Presonoid

Joined: 13/03/2011 00:11:38
Messages: 1993
Location: North Jersey
Offline

When you setup a keyboard in S1 that has controls on it... 1) you create external device for keyboard... 2) you create external device for control surface.

Once you make the external device for control surface, you can open up the device, hit Midi Learn, and twist each knob so S1 recognizes it.

From there, you can open up a VST, use your mouse to move a knob, and then move the knob on your keyboard. They are now selected in Control Link (it's in the top left corner of your sequencer... and it's also within S1's VST wrapper if you press the cogwheel. From there.. link them together by clicking on the chain between them. S1 will remember that connection you made.. so you wouldn't have to do it multiple times.


That's the S1 way of mapping knobs/faders. Sometimes your software has a way to do it also... and obviously you'd need to reach out to Arturia.

I u have a Novation SL board.. and I tend to use Automap more.. b/c it shows me the values on the board. However... the S1 way worked well when i was not using Automap.
Win 8.1 x64 // i7 3930K (@ 4.2GHz) // Samsung Pro 512GB // 500GB SSD (via Raid 0) // 2TB HD // 32GB RAM // Antec Kuhler 620 // Radeon HD 7870 + Radeon 5450 // MSI X79a GD45 Plus mobo// TI chipset Firewire card

DAW(s): Studio One v2.6 // Maschine Studio // Reason 7 via Rewire
Plugs: UAD 2 Quad, Softube CL 1b, Klanghelm, Toneboosters, Soundtoys, Slate VTM, Kramer Tape
Instr.: Addictive Drums, Gladiator2, Sylenth, AAS Bundle, K9U, IK Total Studio 3, Cinesamples, RealGuitar/Strat/LPC, Trilian

RME UCX // AKG c214 // SM57 + Cloudlifter CL1 // JBL LSR 4328p // FMR RNLA // Korg Kaossilator Pro // Novation 61 SL MKii // Korg MicroKey 25 // Presonus Faderport // Contour Designs Shuttle Pro

Next up: Motif XS rack
[WWW]
CPhoenix
Presonoid

Joined: 13/03/2011 00:11:38
Messages: 1993
Location: North Jersey
Offline

Sorry I can't help too much with transport controls. However.... that's possible to do with any controller if you amend the XML template of your device.

Try doing a search... and maybe one of the more knowledgable fellows here can assist if they see this. LMike, Eike, Motoko, TheMuzic.... they may know how to do this.

Also.. you can do a search using keywords like "transport control" "transport map" "XML template: stuff like that... it may pop up. It's been discussed before.

Finally... you can always reach out to Presonus tech support and see if someone can assist.
Win 8.1 x64 // i7 3930K (@ 4.2GHz) // Samsung Pro 512GB // 500GB SSD (via Raid 0) // 2TB HD // 32GB RAM // Antec Kuhler 620 // Radeon HD 7870 + Radeon 5450 // MSI X79a GD45 Plus mobo// TI chipset Firewire card

DAW(s): Studio One v2.6 // Maschine Studio // Reason 7 via Rewire
Plugs: UAD 2 Quad, Softube CL 1b, Klanghelm, Toneboosters, Soundtoys, Slate VTM, Kramer Tape
Instr.: Addictive Drums, Gladiator2, Sylenth, AAS Bundle, K9U, IK Total Studio 3, Cinesamples, RealGuitar/Strat/LPC, Trilian

RME UCX // AKG c214 // SM57 + Cloudlifter CL1 // JBL LSR 4328p // FMR RNLA // Korg Kaossilator Pro // Novation 61 SL MKii // Korg MicroKey 25 // Presonus Faderport // Contour Designs Shuttle Pro

Next up: Motif XS rack
[WWW]
overcoat
Presonic
[Avatar]

Joined: 03/03/2013 20:19:25
Messages: 256
Location: SF
Offline

CPhoenix wrote:When you setup a keyboard in S1 that has controls on it... 1) you create external device for keyboard... 2) you create external device for control surface.

Once you make the external device for control surface, you can open up the device, hit Midi Learn, and twist each knob so S1 recognizes it.

From there, you can open up a VST, use your mouse to move a knob, and then move the knob on your keyboard. They are now selected in Control Link (it's in the top left corner of your sequencer... and it's also within S1's VST wrapper if you press the cogwheel. From there.. link them together by clicking on the chain between them. S1 will remember that connection you made.. so you wouldn't have to do it multiple times.


That's the S1 way of mapping knobs/faders. Sometimes your software has a way to do it also... and obviously you'd need to reach out to Arturia.

I u have a Novation SL board.. and I tend to use Automap more.. b/c it shows me the values on the board. However... the S1 way worked well when i was not using Automap.



Thanks for the reply. I'm aware of control link and how it works (i'm sure i failed to mention that ). The problem with control link for me is that after i set up an instrument the way i like, Studio one or the instrument i'm using doesn't recognize the previous mapping every time i open a new instance of it. this leaves me having to re-map everything every time i start a new song. ...unless i need to set up a song with multiple instruments, map those instruments with control link and then save that as a template. Unfortunately i don't work with song templates much as that's not really the way i work. maybe it should be though....

I think what i'm looking for is the Automap functionality. CPhoenix, you say you're using it with S1? how is it working for you? I was at guitar center earlier today and it seems like a great controller. a little pricey, but if it does what i need it to do then it's definitely worth the extra coin.
Studio One Pro w/ latest build // i7 2.6 ghz mac mini w/ 16gb ram // RME Fireface UCX // Yamaha HS50m's // GAP Pre-73 modded // Blue Reactor mic // Shure sm7b, 57 & 58 // Roland TR8 // Faderport // Padkontrol & Edirol pcr-50 // Arturia V-collection 3.0, V-station, Synthmaster 2.5, Komplete 9 and various other vst's...
sunmachine
Presonoid
[Avatar]
Joined: 28/07/2010 18:49:29
Messages: 2629
Location: Germany
Offline

overcoat wrote:
Thanks for the reply. I'm aware of control link and how it works (i'm sure i failed to mention that ). The problem with control link for me is that after i set up an instrument the way i like, Studio one or the instrument i'm using doesn't recognize the previous mapping every time i open a new instance of it. this leaves me having to re-map everything every time i start a new song. ...unless i need to set up a song with multiple instruments, map those instruments with control link and then save that as a template. Unfortunately i don't work with song templates much as that's not really the way i work. maybe it should be though....
Make sure that you map the controls in Focus mode (yellow) rather than in Global mode (blue), since global mappings are saved with the song file and thus can only be used in that song.
If you map an instrument in Focus mode you should be able to control any instance of it with your controller as long as the plug-in window of the instance has the focus.

What MIDI messages are the transport buttons of the Keylab sending? Did you already try to assign key commands for the transport commands to the learned controls in the Device Editor?


This message was edited 1 time. Last update was at 10/12/2013 21:10:23

MacBook Pro 2.4 GHz Intel Core 2 Duo | 4 GB RAM | Mac OS X 10.6 | Studio One 2 Professional, 32 Bit
Sonic Core SCOPE | Pentium 4, 2.4 GHz | Windows XP@8 GB Compact Flash Card
tc electronic Impact Twin | novation Remote 61SL Mk II

Get 5 GB free GOBBLER space in the cloud for your DAW projects! For Mac and PC
[WWW]
overcoat
Presonic
[Avatar]

Joined: 03/03/2013 20:19:25
Messages: 256
Location: SF
Offline

sunmachine wrote:
overcoat wrote:
Thanks for the reply. I'm aware of control link and how it works (i'm sure i failed to mention that ). The problem with control link for me is that after i set up an instrument the way i like, Studio one or the instrument i'm using doesn't recognize the previous mapping every time i open a new instance of it. this leaves me having to re-map everything every time i start a new song. ...unless i need to set up a song with multiple instruments, map those instruments with control link and then save that as a template. Unfortunately i don't work with song templates much as that's not really the way i work. maybe it should be though....
Make sure that you map the controls in Focus mode (yellow) rather than in Global mode (blue), since global mappings are saved with the song file and thus can only be used in that song.
If you map an instrument in Focus mode you should be able to control any instance of it with your controller as long as the plug-in window of the instance has the focus.

What MIDI messages are the transport buttons of the Keylab sending? Did you already try to assign key commands for the transport commands to the learned controls in the Device Editor?






OK, so i mapped the controls in S1 to one instance of Jupiter 8V in Focus mode (Yellow). I then opened up a new instance of The 8V in a new track. not a duplicated track and got nothing. weird thing is i don't think this was the case with my pcr-50. I'll have to plug that in and see what happens.

btw, the least of my worries is the transport controls, but when i have the device editor open and hit any of the transport buttons on the Keylab nothing happens. all other knobs and sliders etc.. worked just fine.
Studio One Pro w/ latest build // i7 2.6 ghz mac mini w/ 16gb ram // RME Fireface UCX // Yamaha HS50m's // GAP Pre-73 modded // Blue Reactor mic // Shure sm7b, 57 & 58 // Roland TR8 // Faderport // Padkontrol & Edirol pcr-50 // Arturia V-collection 3.0, V-station, Synthmaster 2.5, Komplete 9 and various other vst's...
sunmachine
Presonoid
[Avatar]
Joined: 28/07/2010 18:49:29
Messages: 2629
Location: Germany
Offline

hmmm... that's weird... no idea at the moment how to solve that...

According to the manual the transport buttons send MMC commands. So you should get them to work by adding a new MMC device from the PreSonus folder.

Arturia wrote:These buttons allow controlling any external hardware or software sequencer.
Buttons send standard MMC messages: Start, Stop, record, Rewind, Fast Forward and Loop. They can be customized in the MIDI Control Center.
[WWW]
overcoat
Presonic
[Avatar]

Joined: 03/03/2013 20:19:25
Messages: 256
Location: SF
Offline

My pcr-50 works the way you'd expect in focus mode. At this point because Analog Lab doesn't play nice with Studio One i'm gonna return it and use my pcr-50 in the meantime.

I would like to hear from users of the Novation SL mkii and Automap still. I'm gonna keep my eye out for a second hand unit if it works well with S1.

Thanks for everyones input so far!
Studio One Pro w/ latest build // i7 2.6 ghz mac mini w/ 16gb ram // RME Fireface UCX // Yamaha HS50m's // GAP Pre-73 modded // Blue Reactor mic // Shure sm7b, 57 & 58 // Roland TR8 // Faderport // Padkontrol & Edirol pcr-50 // Arturia V-collection 3.0, V-station, Synthmaster 2.5, Komplete 9 and various other vst's...
CPhoenix
Presonoid

Joined: 13/03/2011 00:11:38
Messages: 1993
Location: North Jersey
Offline

yea hthat sounds like some kind of software bug then if your S1 ma isn't sticking. I've never had that problem before... it ALWAYS remembers. It stores a running file for it in one of the AppData folders of S1, so it sticks with the program every time you open that instance. If it's not working, and you're obviously doing it correctly... it sounds like a problem w the board. I have no idea why on Earth that would happen, and it doesn't make sense to me, but I think it's the board.


I think i replied in another thread you asked the question about my experieences w/ Automap. It's AWESOME since the 2.6 S1 update. Before that... it has some huge obvious bugs. Now... everything works as advertised. The only annoying thing is some plugins show up twice in your browser. Not a deal breaker for me.

The biggest things I like are being able to see values on the LED screen... being able to automate things smoothy, and being able to automate mutes and volumes in mixer mode.
Win 8.1 x64 // i7 3930K (@ 4.2GHz) // Samsung Pro 512GB // 500GB SSD (via Raid 0) // 2TB HD // 32GB RAM // Antec Kuhler 620 // Radeon HD 7870 + Radeon 5450 // MSI X79a GD45 Plus mobo// TI chipset Firewire card

DAW(s): Studio One v2.6 // Maschine Studio // Reason 7 via Rewire
Plugs: UAD 2 Quad, Softube CL 1b, Klanghelm, Toneboosters, Soundtoys, Slate VTM, Kramer Tape
Instr.: Addictive Drums, Gladiator2, Sylenth, AAS Bundle, K9U, IK Total Studio 3, Cinesamples, RealGuitar/Strat/LPC, Trilian

RME UCX // AKG c214 // SM57 + Cloudlifter CL1 // JBL LSR 4328p // FMR RNLA // Korg Kaossilator Pro // Novation 61 SL MKii // Korg MicroKey 25 // Presonus Faderport // Contour Designs Shuttle Pro

Next up: Motif XS rack
[WWW]
 
Forum Index » Studio One General Discussion
Go to: