Pro-tools Midi Problem

  • Thread starter Thread starter dnkygirl
  • Start date Start date
dnkygirl

dnkygirl

M42 Entertainment
Hi all,

I just added a Motif Rack along with a Triton Studio to my setup. I want to be able to use Pro-tools as my sequencer. How can i do this? Right now i have the motif rack running in/out to the Triton and I have my digi 002 receiving from the thru of my motif rack. That seems to allow me to receive signals, but i can't playback what i have recorded. I also have my triton setup to only use 9-16 midi channels and the motif only 1-8. I hate that studio recall is only supported in cubase... because that would really be kewl to use the motif as a plugin. Any ideas on this one?

I also wish that reason would allow you to use external devices... with the sequencer because i have fallin in love with the easy of use of it's sequencer. Oh well.... can't have it all i suppose.


Demi
 
Last edited:
I don't tend to use midi that much, in fact barely at all. I record a lot of guitars & drums

I'm sure that there are pro tools people who can help you though within this forum

frankly I find midi the biggest bug bear ever to be in my studio& have only recently just got it sussed to the point where I can use it in protools comfortably but I'm not using a triton or a motif

how many midi i/o's do you have from the 002 & is the motif a sound unit?? (pardon my ignorance). if it is (a sound module) running the triton & the motif as individual units would be better. & then selecting the appropriate devices in midi setup.............or is it studio setup................can't quite remember

I think Tragikremix is a PTs person along with others,

sorry I couldn't be of any real help.........

boing out Demi & good luck

slidey
 
Thanks slidey,

The digi 002 has 2 outs and 1 input. Oh so if i run both outs to the motif and triton then.... how do i get signals back to the input? It's starting to look like i need a midi interface maybe. I would be able to run in/out direct to the digi 002 then in/out direct to both the triton and motif. That would give me back the 16 channels per device i would be losing the way i have it setup now. Is this right?



Demi
 
dnkygirl said:
Thanks slidey,

The digi 002 has 2 outs and 1 input. Oh so if i run both outs to the motif and triton then.... how do i get signals back to the input? It's starting to look like i need a midi interface maybe. I would be able to run in/out direct to the digi 002 then in/out direct to both the triton and motif. That would give me back the 16 channels per device i would be losing the way i have it setup now. Is this right?



Demi
Click to expand...

Heck I think.............seriously I'm not sure but I think that is right

OI TRAGIK do you know what this ere lady is talking about.

I tend to treat the machine as analog as possible & as I said mainly strung & skinned instruments

I'll come clean, I'm just tryin' to chat you up

PS don't tell your other 1/2 :D
 
Demi,

This is probably beyond me but here goes. You might want to solve your problem by the process of elimination. I assume the Triton is your controller and also has sound samples like your Motif Rack, and that the digi 002 acts as an audio interface between the Triton and protools, similar to an Mbox? If so, try connecting the Triton to the digi 002, record something in midi, then play it back through the Triton. If this works, then the problem is your connection to the Motif Rack.

Regarding the Motif Rack, I would assume the process would be:

1. Controller sends midi signal to Protools where it is sequenced (recorded).
2. Midi signal is played back thru Motif Rack where it triggers the selected sound sample.

Hope this helps.

V
 
Midi setup problem resolved

Hi all,

This was a pain in the butt to setup. Here's how to do it:

Korg Triton in/out direct digi002
Motif Rack in/out direct to usb on pc installed yamaha usb driver and turn on the midi usb on the motif rack.
M-audio oxygen installed usb driver

Setup the midi studio with all 3 devices. Under the midi input make only the triton and oxygen input devices.

Under the track menu turn on input only monitoring... this was my real problem all along.... once that was switched on everything started working properly.


Also the midi patch names don't match for the motif rack es in the midinams folder. So i went to digicake.com and downloaded the correct midinams list. You have to setup the motif rack without a model number in the studio setup to use the new track names list. Go to the patch select then select change then point to your new midinams and then you will have the correct patch list names.


After playing with my new setup.. i have far more possibilities with using protools as my sequencer than only using reason. By the way reason 3.0 does not allow midi outputs.. which means you can not drive external midi devices from it. You can only use midi devices to act as a controller for the internal software devices. I checked the tech forums and alot of people are complaining about it. Any who.. i'm happy again.


Demi
 
GREAT!!!!!!....................so no chance of a date then MWAHA

nah glad you got it sussed
 
It seems like you have it figured out but something that might make your life easier would be a midi interface. It just allows for better "communication" between devices, or atleast a more direct path. It probably won't offer you much functionality wise not that you got everything setup but it might be easier. One problem i had was that my soundcard only would work as a midi through when a program was opened. So i couldn't control anything without my computer not only on but an application like protools open. Kind of sucks when you just want to mess around without going through all that. My mpc had two midi I/O so i could use midi but still kind of a pain. I don't know if you have enough midi i/o to do that, or if it's a problem. Just a suggestion.



Reason not having midi out is a tragedy, lol. It's my main program so i just am so used to it. I guess the philosphy is that since it doesn't record audio that the function is useless. It would be so much easier to do things in reason. It sucks because the midi in works so well to sequence midi off another device. The best way is to rewire into protools. I still hate that. Now reason is a slave, you loose alot of it's functionability because of that, plus going back and fourth, etc, using mulitple programs. That's the way to deal with it. We should petition for midi out for 4.0 lol.
 
talontsiawd said:
Reason not having midi out is a tragedy, lol. It's my main program so i just am so used to it. I guess the philosphy is that since it doesn't record audio that the function is useless. It would be so much easier to do things in reason. It sucks because the midi in works so well to sequence midi off another device. The best way is to rewire into protools. I still hate that. Now reason is a slave, you loose alot of it's functionability because of that, plus going back and fourth, etc, using mulitple programs. That's the way to deal with it. We should petition for midi out for 4.0 lol.
Click to expand...


Yes! they really should implement midi out..they could make the sequencer accept midi notes... not audio if they want to stay away from a full audio suite. I agree rewire sucks... I would much rather control protools instead of it controlling reason. I have lots of tempo problems with rewire and protools. Also problems with syncing up tracks in protools along with tracks i sequenced in reason and am dumping via instrument tracks into protools.

Working 2 programs.. is the pits... especially when you are trying to use multiple keyboards and rack gear along side it. I'm taking my time learning midi sequencing in protools. I find it to be weird... although version 7.3 is alot better than 6.9 with the midi.


Demi
 
You must log in or register to reply here.
Back
Top