Hi Phil,
Are you sure were talking about the same thing? I was talking about the
physical connection between the Mackie and computer. I knew about the virtual
midi cables between sonar and surface reader. And the Mackie documentation
they talk about two ways to do the physical Connection between the board and
the computer. One way is with the USB cable the other way is using one set of
their midi ports through a midi interface. However, that means he would not be
able to use more than two extensions.
The surface reader instructions say to use the same midi ports that worked
between sonar and surface reader in the first test before running surface
reader for the first time. I thought I was being extremely careful to follow
the directions, and I tried it all at least three or four times before calling
for help because it didn’t work.
On Apr 8, 2019, at 1:26 PM, Phil Muir <info@xxxxxxxxxxxxxxxxxxxxxxxxxxx>PLEASE READ THIS FOOTER AT LEAST ONCE!
wrote:
No that won't work. Those MIDI ports need to be virtual.
-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Fran Franks
Sent: 08 April 2019 17:45
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Trouble installing MCU Pro and Surface Reader
Yes, I did reboot the computer. What I'm wondering is if Surface Reader
would work if I connected the MCU Pro by way of a MIDI interface rather than
directly by USB. I have not tried this because it seems like one too many
devices in the chain.
-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Phil Muir
Sent: Sunday, April 07, 2019 1:17 AM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Trouble installing MCU Pro and Surface Reader
WHen you restarted your PC, did you also restart Loopbe30 before starting
Surface Reader? failure to do so will throw up an error message like that
in Surface Reader.
On 7 April 2019 03:23:43 "Fran Franks" <fm.guitarlady@xxxxxxxxx> wrote:hope
Hello everyone,
I am installing my very first control surface, a Mackie MCU Pro and one
extension, plus Surface Reader to get it talking. I have done my best to
follow the Surface Reader documentation, but I'm hitting a snag, and I
someone in the group here has time to look at this email and suggest whatis
going wrong.control
My system is running Sonar 8.5 on Windows 7, 64 bit, Jaws 16, and Cake
Talking, and the MCU Pro is connected to the computer via USB.
Here is what I have done so far:
1. Set the mode on the MCU pro to Mackie control.
2. Installed LoopBe30, with default settings and 2 virtual cables,
which Windows calls Internal MIDI.
3. I added the control surface to Sonar with the initial port settings
to test communication between Sonar and MCU pro as follows. Mackie
1, Input port, MCU Pro USB v3.1, Output port, MCU Pro USB v3.1. The MCUPro
main unit showed positive functionality and communication with the DAW,port
however I'm not getting anything with the extension, a problem to work on
later. Then I reset the input port to internal MIDI 1, and the output
to internal MIDI 2, the two virtual MIDI cables from LoopBe30. Then Ishut
down Sonar before the next step.to
4. Opening Surface reader, I added a new surface as Mackie MCU Pro with
the Mackie Control protocol. In the Hardware MIDI Setup, I set the input
MCU Pro USB v3.1 and output port to Internal MIDI 1. In the Display MIDIv3.1
Setup, I set the input port to Internal MIDI 2, and the output port to MCU
Pro USB v3.1.
5. Then, when restarting Sonar, there was no functionality with the MCU
Pro, and later after rebooting the computer and first running surface
reader, I got the following Surface Reader error message. "MCU Pro USB
could not be opened." Followed by still no function when running Sonar.is
Even though Sonar and the MCU Pro initially worked together with the
seemingly same input and output port, MCU Pro USB v3.1, I wonder if this
somehow part of the problem in Surface Reader despite the care I took in
following their documentation. But, that is a very uneducated guess at
this point.
I hope someone here can point me in the right direction.
Best regards,
Fran Franks
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
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?subject=faq or
send a message, to
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
faq
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
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?subject=faq or
send a message, to
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
faq
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
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?subject=faq or
send a message, to
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
faq
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
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?subject=faq or
send a message, to
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
faq