Locking Acid 1.0 up with Cakewalk pro -ACID Product Family

Subject:Locking Acid 1.0 up with Cakewalk pro Posted by: dg Date:3/17/2000 3:45:00 PM Does anyone have any info on locking up Acid 1.0 with Calewalk Pro or Voyetra Gold plus?
Subject:Re: Locking Acid 1.0 up with Cakewalk pro Reply by: Kelly_S Date:3/17/2000 7:37:00 PM Hello! Cakewalk cannot be the master in any sync situation with ACID. It must be the slave for both MIDI Time Code and MIDI Clock. The only thing that Cakewalk can be the master of is MMC, MIDI Machine Code. This is different from MTC and MIDI Clock; it is an alternative way of controlling hardware that is MMC-capable. Sonic Foundry has received reports from Virtual MIDI Router users that they are receiving the error "Virtual MIDI Router Port Is in Use." This is because Cakewalk has a MIDI configuration section where users select the IN and OUT ports simultaneously. Often times by instinct, users will select both the IN and OUT for all ports of their devices, including the ports for the VMR. This causes Cakewalk to use both the IN and OUT port of the VMR, thus preventing ACID from sending to the OUT port and giving users the "port is in use" error message. User need to go into their MIDI configuration and deselect VMR Port 1 from the MIDI Out category list. In doing this, users are telling Cakewalk to listen on the VMR IN port for MIDI Time Code or Clock and not to use the OUT port at all. The OUT port is reserved for ACID, as the master MIDI Time Code or Clock source. If you experience MIDI Time Code or Clock drifting, please consult the Cakewalk help file. It provides some really nice information on MIDI synchronization ins & outs and fairly complete instructions on how to sync Cakewalk to other applications. It also provides a lot of good information on why drifting occurs and how to minimize it. Thanks. doug gray wrote: >>Does anyone have any info on locking up Acid 1.0 with >>Calewalk Pro or Voyetra Gold plus?
Subject:Re: Locking Acid 1.0 up with Cakewalk pro Reply by: gcook Date:4/4/2000 9:51:00 PM I Don't know if this response is from Sonic foundry or not but it's a cop-out answer. I've been plagued by this problem from the beginning. ACID does NOT sync to external software. It's easy to blame the other guys. I've been using Cakewalk from the ol' DOS days and have used ACID from it's beta days. ACID has NEVER synced properly. MTC or Midisync. My simple question is: does Acid 2.0 FIX this problem or not? K.Shaffer wrote: >>Hello! >> >>Cakewalk cannot be the master in any sync situation with ACID. It >>must be the slave for >>both MIDI Time Code and MIDI Clock. The only thing that Cakewalk can >>be the master of is >>MMC, MIDI Machine Code. This is different from MTC and MIDI Clock; it >>is an alternative way >>of controlling hardware that is MMC-capable. >> >>Sonic Foundry has received reports from Virtual MIDI Router users >>that they are receiving >>the error "Virtual MIDI Router Port Is in Use." This is because >>Cakewalk has a MIDI >>configuration section where users select the IN and OUT ports >>simultaneously. Often times >>by instinct, users will select both the IN and OUT for all ports of >>their devices, including >>the ports for the VMR. This causes Cakewalk to use both the IN and >>OUT port of the VMR, >>thus preventing ACID from sending to the OUT port and giving users >>the "port is in use" >>error message. User need to go into their MIDI configuration and >>deselect VMR Port 1 from >>the MIDI Out category list. In doing this, users are telling Cakewalk >>to listen on the VMR >>IN port for MIDI Time Code or Clock and not to use the OUT port at >>all. The OUT port is >>reserved for ACID, as the master MIDI Time Code or Clock source. >> >>If you experience MIDI Time Code or Clock drifting, please consult >>the Cakewalk help file. >>It provides some really nice information on MIDI synchronization ins >>& outs and fairly >>complete instructions on how to sync Cakewalk to other applications. >>It also provides a >>lot of good information on why drifting occurs and how to minimize it. >> >>Thanks. >> >>doug gray wrote: >>>>Does anyone have any info on locking up Acid 1.0 with >>>>Calewalk Pro or Voyetra Gold plus?

Subject:Locking Acid 1.0 up with Cakewalk pro

Posted by: dg

Date:3/17/2000 3:45:00 PM

Does anyone have any info on locking up Acid 1.0 with
Calewalk Pro or Voyetra Gold plus?

Subject:Re: Locking Acid 1.0 up with Cakewalk pro

Reply by: Kelly_S

Date:3/17/2000 7:37:00 PM

Hello!

Cakewalk cannot be the master in any sync situation with ACID. It
must be the slave for
both MIDI Time Code and MIDI Clock. The only thing that Cakewalk can
be the master of is
MMC, MIDI Machine Code. This is different from MTC and MIDI Clock; it
is an alternative way
of controlling hardware that is MMC-capable.

Sonic Foundry has received reports from Virtual MIDI Router users
that they are receiving
the error "Virtual MIDI Router Port Is in Use." This is because
Cakewalk has a MIDI
configuration section where users select the IN and OUT ports
simultaneously. Often times
by instinct, users will select both the IN and OUT for all ports of
their devices, including
the ports for the VMR. This causes Cakewalk to use both the IN and
OUT port of the VMR,
thus preventing ACID from sending to the OUT port and giving users
the "port is in use"
error message. User need to go into their MIDI configuration and
deselect VMR Port 1 from
the MIDI Out category list. In doing this, users are telling Cakewalk
to listen on the VMR
IN port for MIDI Time Code or Clock and not to use the OUT port at
all. The OUT port is
reserved for ACID, as the master MIDI Time Code or Clock source.

If you experience MIDI Time Code or Clock drifting, please consult
the Cakewalk help file.
It provides some really nice information on MIDI synchronization ins
& outs and fairly
complete instructions on how to sync Cakewalk to other applications.
It also provides a
lot of good information on why drifting occurs and how to minimize it.

Thanks.

doug gray wrote:
>>Does anyone have any info on locking up Acid 1.0 with
>>Calewalk Pro or Voyetra Gold plus?

Subject:Re: Locking Acid 1.0 up with Cakewalk pro

Reply by: gcook

Date:4/4/2000 9:51:00 PM

I Don't know if this response is from Sonic foundry or not but it's a
cop-out answer. I've been plagued by this problem from the beginning.
ACID does NOT sync to external software. It's easy to blame the other
guys. I've been using Cakewalk from the ol' DOS days and have used
ACID from it's beta days. ACID has NEVER synced properly. MTC or
Midisync. My simple question is: does Acid 2.0 FIX this problem or
not?

K.Shaffer wrote:
>>Hello!
>>
>>Cakewalk cannot be the master in any sync situation with ACID. It
>>must be the slave for
>>both MIDI Time Code and MIDI Clock. The only thing that Cakewalk
can
>>be the master of is
>>MMC, MIDI Machine Code. This is different from MTC and MIDI Clock;
it
>>is an alternative way
>>of controlling hardware that is MMC-capable.
>>
>>Sonic Foundry has received reports from Virtual MIDI Router users
>>that they are receiving
>>the error "Virtual MIDI Router Port Is in Use." This is because
>>Cakewalk has a MIDI
>>configuration section where users select the IN and OUT ports
>>simultaneously. Often times
>>by instinct, users will select both the IN and OUT for all ports of
>>their devices, including
>>the ports for the VMR. This causes Cakewalk to use both the IN and
>>OUT port of the VMR,
>>thus preventing ACID from sending to the OUT port and giving users
>>the "port is in use"
>>error message. User need to go into their MIDI configuration and
>>deselect VMR Port 1 from
>>the MIDI Out category list. In doing this, users are telling
Cakewalk
>>to listen on the VMR
>>IN port for MIDI Time Code or Clock and not to use the OUT port at
>>all. The OUT port is
>>reserved for ACID, as the master MIDI Time Code or Clock source.
>>
>>If you experience MIDI Time Code or Clock drifting, please consult
>>the Cakewalk help file.
>>It provides some really nice information on MIDI synchronization
ins
>>& outs and fairly
>>complete instructions on how to sync Cakewalk to other
applications.
>>It also provides a
>>lot of good information on why drifting occurs and how to minimize
it.
>>
>>Thanks.
>>
>>doug gray wrote:
>>>>Does anyone have any info on locking up Acid 1.0 with
>>>>Calewalk Pro or Voyetra Gold plus?