Subject:Acid3.0b MTC issues

Posted by: kraznet

Date:8/11/2001 9:08:40 AM

Hi there,
This is very strange..i upgraded to 3.0b and now when i try to sync Acid to MTC from my separate Logic computer this is what happens. I press play in LogicPC 4.72.The Timecode display in Acid begins but the song time time line dosn't move....so i get no playback from Acid.I stop playback in Logic press play again and this time i get no reponse from Acid at all.So i disable "Trigger from Mid Timecode" and then re-enable it.Press play in Logic no response from Acid and the an error message flashes up "Acid.Exe has generated errorsand will be closed by Windows.You need to resart the Program.An error log is being created" I click OK and Acid quits.This seems to happen everytime and is repeatable.This only occurs with 3.0b.The previous version is ok.Anyone else having this problem?. I'm running W2k by the way.
Thanks
Kraznet

Subject:RE: Acid3.0b MTC issues

Reply by: pwppch

Date:8/11/2001 1:01:01 PM

Odd, I can't repro anything like this.

There does appear to be a problem in that you must toggle the Trigger to MTC (Ctrl+F7) twice to renable trigger.

Could you offer up some more details? What hardware are you routing the MTC through?

What version of Windows?

Etc, etc.

I would suggest you call or email our techsupport on this issue. It will be tracked correctly and all details you have will be logged.

Peter

Subject:RE: Acid3.0b MTC issues

Reply by: kraznet

Date:8/11/2001 1:26:29 PM

Hi Peter,
Thanks for your quick reply.I actually phoned up Dave on the help line on friday and he suggested that i uninstall 3.0b then re install it over 3.0.Which i did.It seemed to work but as soon as i put the phone down the same problem came back.Strange but it works ok with 3.0.I'm using Win 2000 fresh install with SP2 Midi/MTC is coming in via AWE64Gold which shows as an MPU-401 in Acid.Logic is sending out MTC from a Creative PCI512 midi out.(I had problems with the AMT8 so i couldn't use it)I think i may install WinME on a fresh partition and see if i get any improvement.Here's a list of my other components.

Gigabyte BX2000+ mobo (latest bios)
P3/600 (non coppermine)
256mb PC100 ram
IBM GXP22gig HD
Ati Rage Turbo 4mb's
WinTV PCI
ADSL Modem
D-Link530TX Ethernet Adapter
LG CD-Rom
Busby USB Hub

I'll update the situation soon.
Many Thanks
Kraznet
(Martin Burrow)

Subject:RE: Acid3.0b MTC issues Update!!

Reply by: kraznet

Date:8/11/2001 5:26:08 PM

Ok so i installed WinME on a separate partition and then Acid3.0b (after ugrading to DX8.0a)Dragged a drum loop into the arrange and enabled "Trigger from Midi Timecode".Pressed play in Logic and it worked!!BUT...what i have been doing previously is setting the Synchronization time delay to 0.000 in the Advanced Preferences.As soon as i do that the problem comes back.Since then i have tested some settings and if i go below 0.300 Acid won't playback and i get the error message.So it seems that as long as i keep this setting at 0.300 minimum everything is ok.I'm not sure if this a bug or what but at least i seem to have sorted it out for now.So i can carry on using Win2000 .I will probably send these messages to email support anyway.
Regards
Kraznet

Subject:RE: Acid3.0b MTC issues Update!!

Reply by: pwppch

Date:8/12/2001 12:09:19 AM

>>Pressed play in Logic and it worked!!BUT...what i have been doing previously is setting the Synchronization time delay to 0.000 in the Advanced Preferences.
>As soon as i do that the problem comes back.Since then i have tested some settings and if i go below 0.300 Acid won't playback and i get the error message.So it seems that as long as i keep this setting at 0.300 minimum everything is ok.I'm not sure if this a bug or what but at least i seem to have sorted it out for now.So i can carry on using Win2000 .I will probably send these messages to email support anyway.
<<

You should actually leave it at the default or no lower than 1 sec.

The purpose of this parameter has little to do with how sync works, but rather how much time before we consider the clock locked. Setting it to zero will cause lousy sync lock at best, and it appears that it is causing a problem with the new sync code for 3.0b.

I have verified this is a bug. If you just leave the setting at the default or 1 sec, you will not have a problem and it will not effect your trigger.

Thanks
Peter