Beginning DP8 basic setup

[comp15]

I've completed the hardware configuration with my connected Audio Interface. When I'm in the pre-made DP guided lesson, when I press my MIDI keyboard keys I can each instrument track that I record enable. However, when I start fresh and make my own file, I load an instrument track but hear nothing when I press the MIDI keys.

I've been watching the Groove3 videos, but those videos assume you a good sum already about routing. Is there anything more basic that you can recommend?

For example, when the video goes over Bundles, the audio interface listed under inputs, and under outputs the MIDI keyboard is listed asa well. I don't think the problem is there.

Under MIDI Devices, the name of my MIDI keyboard wasn't on the list but I entered it.

Ports, properties and patches are unclear to me. Under Patches should I choose "General MIDI" in the drop down menu?

Since I made these changes, now each time I open up a DP files a dialogue box prompts which reads "Some MIDI assignments could not be found in the current MIDI Configuration. Make sure that these substitutions are correct." It lists both the Audio Interface and the MIDI keyboard I input. I choose the audio interface and click okay and move on. Yet, I hear nothing after I load an instrument. If I return to the DP Guided lesson, I do hear the instruments when I activate the MIDI keys.

Again the important difference is that in the pre-made template I hear sound but in one I start simply by choosing "create instrument track" I hear nothing.

Is there a more in-depth resource that talks about setting up in Digital Performer? I came from Propellerhead Reason. Reason was practically hook up your MIDI device, enable it from a drop down and play - a wonderful tool for someone who wants to make mock-ups or final audio renditions of compositions effortlessly. I'm long due for this upgrade to Digital Performer, which I have no doubt is arguably deeper than any other DAW out there. However, these very basic things are not "clicking" with me. Any help is very much appreciated, even if you can refer me to beginners source that doesn't assume I know so much, especially about the hardware hookup.

thanks

[bayswater]

Hard to know where to start, but I'll try this: have you taken into account that you can't play an Instrument track (the way you might in Logic)? You play a MIDI track.

You have to create an Instrument track, and a MIDI track that uses the Instrument track as its output. You have to put the MIDI track into record status. Then when you play a MIDI device that your computer recognizes, you should see some MIDI activity happening in various places (like the MIDI Monitor), and hear the Instrument, assuming the output of the instrument is routed to an audio output you can monitor.

[cuttime]

Under MIDI Devices, the name of my MIDI keyboard wasn't on the list but I entered it.

It sounds as if the keyboard might not be present in the Audio MIDI Setup app. Are these devices there, configured, and connected? Does the MIDI monitor in DP (shift W) show an input? Also, what Bayswater said.

[comp15]

Under MIDI Devices, the name of my MIDI keyboard wasn't on the list but I entered it.

It sounds as if the keyboard might not be present in the Audio MIDI Setup app. Are these devices there, configured, and connected? Does the MIDI monitor in DP (shift W) show an input? Also, what Bayswater said.

When I bring up the MIDI Monitor I see the audio interface listed. Under Software Devices, I see MIDI Keys listed. To the right of both of these I see dark boxes under numbers 1 through 16. The last box in line with the audio interface, under CORT, is blue.

Does this mean it's connected?

Since I can hear sound in the DP Practice file, wouldn't this mean it verifies the proper connection?

[comp15]

Hard to know where to start, but I'll try this: have you taken into account that you can't play an Instrument track (the way you might in Logic)? You play a MIDI track.

You have to create an Instrument track, and a MIDI track that uses the Instrument track as its output. You have to put the MIDI track into record status. Then when you play a MIDI device that your computer recognizes, you should see some MIDI activity happening in various places (like the MIDI Monitor), and hear the Instrument, assuming the output of the instrument is routed to an audio output you can monitor.

Okay. Check. It's working. Thank you.

[comp15]

Under MIDI Devices, the name of my MIDI keyboard wasn't on the list but I entered it.

It sounds as if the keyboard might not be present in the Audio MIDI Setup app. Are these devices there, configured, and connected? Does the MIDI monitor in DP (shift W) show an input? Also, what Bayswater said.

When I bring up the MIDI Monitor I see the audio interface listed. Under Software Devices, I see MIDI Keys listed. To the right of both of these I see dark boxes under numbers 1 through 16. The last box in line with the audio interface, under CORT, is blue.

Does this mean it's connected?

Since I can hear sound in the DP Practice file, wouldn't this mean it verifies the proper connection?

Okay, MIDI is coming through and working. For clarity, back to what I stated above, as crudely as I describe it. Does the MIDI monitor sound like it's set up correctly? Should I see rows of black "boxes" next to the audio interface listed? I should also mention that each time I press a key on the keyboard I see the first box in the row activate in the color blue. This box is under Row 1. No matter which keys or how many keys I press, only this box highlights. Does this first box represent port 1?

Clearly I'll keep reading and watching. Thanks.

[bayswater]

Should I see rows of black "boxes" next to the audio interface listed?

If your audio interface also has a MIDI port.

[cuttime]

To the right of both of these I see dark boxes under numbers 1 through 16. The last box in line with the audio interface, under CORT, is blue.

I should also mention that each time I press a key on the keyboard I see the first box in the row activate in the color blue. This box is under Row 1. No matter which keys or how many keys I press, only this box highlights. Does this first box represent port 1?

Glad you got it working! The first box represents MIDI channel 1. If you change the transmit channel on your keyboard, the box should change.

[Timeline]

Not sure why but I remember an Apple tech telling me that about three years ago they changed the USB protocol only allowing clean USB data standards. Since that time I have had to use a MTPAV MIDI interface and create a connection in Apple MIDI Setup to get MIDI to work. It used to work just from my USB M-Audio keyboard no problem. Don't know why things had to change at Apple. PITA for sure. I have had it suddenly work from USB for a while then stop with all the symptoms described here in this thread. I just gave up and made the setup. So far so good.

[mikehalloran]

Not sure why but I remember an Apple tech telling me that about three years ago they changed the USB protocol only allowing clean USB data standards. Since that time I have had to use a MTPAV MIDI interface and create a connection in Apple MIDI Setup to get MIDI to work. It used to work just from my USB M-Audio keyboard no problem. Don't know why things had to change at Apple. PITA for sure. I have had it suddenly work from USB for a while then stop with all the symptoms described here in this thread. I just gave up and made the setup. So far so good.

There's a misunderstanding somewhere. Apple didn't change anything but the class standards for USB tightened up and developers had to catch up. iOS requires USB devices to be Class Compliant (so does Android but it's not followed as rigidly).

USB devices can be Class Compliant. These do not require third party drivers to work. Conversely, those devices that aren't Class Compliant require drivers to be installed.

So why isn't everything Class Compliant? There is a lot of functionality that can be designed into a piece of hardware (multi-channel audio, for example) that isn't supported by the USB Class spec -- for these devices to work as advertised, drivers must be designed and installed.

Add to that the confusion that is caused by some companies incorporating shortcuts in the firmware that ignore standards. This is fine in the short run but can make things difficult for their customers later. MAudio and JL Cooper have bad reputations in this regard.

Oh... Apple has nothing to do with the USB spec itself and neither do PC makers. A lot of what they can and cannot do is determined by how Intel implements it into their chip sets.

[comp15]

I'm trying to rewire Reason with DP. Here's what I've done:

1) I start DP
2) Create a stereo track (i've also tried these same steps creating an AUX track)
3) Choose the audio interface as the output
4) Select "ReasonMix L 1-Mix R 2 (stereo)" as my input
5) Record enable the track
6) Start Reason

Then I receive this error: "Could not connect to the reason engine. The Reason engine is already in use. Make sure you only run one instance of Reason."

I'm following the steps listed on page 281-282 in the DP User Guide. What might the problem be?

thanks

[comp15]

I've also followed all the steps in this youtube video. I've disabled the MIDI keyboard within Reason. Now I am able to open Reason after DP, but after following the steps in this video, still no sound:
https://www.youtube.com/watch?v=c0WpavgaSyw

What am I missing?

[comp15]

I've also followed all the steps in this youtube video. I've disabled the MIDI keyboard within Reason. Now I am able to open Reason after DP, but after following the steps in this video, still no sound:
https://www.youtube.com/watch?v=c0WpavgaSyw

What am I missing?

Okay, I'm answering my own questions by experimenting. I figured it out. I hear the rewired patches now. Apparently I was choosing the wrong MIDI instrument from the output drop down. For example, when I create, say a Violin in Reason, I see two "Violins" listed in the output drop down list in DP. Why are there two outputs listed, shouldn't there only be one? That could get confusing when I add many more instruments.