Subject:Acid 3 & MIDI Timecode

Posted by: riwe

Date:5/29/2001 11:03:58 AM

Since Acid 3 there is an audible offset when I want to synchronize with a MTC master.
The master begins at 01:00:00:00 (that means 01h:00m:00s:00f). If I set the beginning
of the project to 01:00:00:00 (via "View", "Time Ruler", "Set time at cursor") I thought that
it works (like the setting "offset" in Acid 2 in the sync dialog). I set the synchroinzation
delay time to 2 seconds. And, if I start the master, Acid 3 begins at 01:00:02:00. That means
that it began 2 seconds late. Do you know any workarounds?

Subject:RE: Acid 3 & MIDI Timecode

Reply by: Pekka

Date:5/30/2001 3:42:26 AM

It is really interesting, that this slaving to timecode is so difficult to them.
Of course, it´s possible, that SF is underestimating, how important thing this
is. They just don´t use enough resources to fix it.
In v2, it was totally nightmare, and now, there is still a problem, how it reads TC.
I´m also using 01.00.00 starting time, and usually Acid reads, that it is 02.00.00.
In other words, there is one hour offset....

Subject:RE: Acid 3 & MIDI Timecode

Reply by: SonyJennL

Date:5/30/2001 10:46:41 PM

Two items-

1. ACID 3.0 does not slave to incoming timecode. It triggers playback to begin.

2. Pekka- could you please tell me a bit more about your MIDI set-up (what you are using)? Did you set the offset in both ACID and the device you are triggering from?
Thanks.

Subject:RE: Acid 3 & MIDI Timecode

Reply by: Pekka

Date:5/31/2001 3:47:37 AM

Thanks for Your response. I´ll try to explain my configuration.
I have Logic Audio as a master timecode generator, in a separate Mac.
Thru the multiport midi-interface (Motu´s midi express) I am sending MTC
to my devices, also to PIII 500MHZ PC, where is dakota audiocard, with two
separate midi-inputs. Input 1 is feeding Gigastudio, and input 2 goes to Acid.
I´m using 01.00.00.00 starting time in Logic. Timecode actually starts to run a couple
of seconds before, so there should be plenty of time to trigger, chase or whatever
you want to call it :)
I´ll put Acid to start in 01.00.00.00 with set time in cursor function. TC format is
Ebu 25fps. Trigger to timecode function is on, and free-wheel in timecode loss
function is on.
I´ll start Logic about 00.59.57.00
Usually Acid triggers well for a while. (from 1 time to 30 times, it varies). Ultimately,
without any reason, it just starts to read my 01.00.00.00 timecode being 02.00.00.00 and
doesn´t start from the beginning anymore.
If I change starting time of Acid to 00.00.00.00 it reads it right, but Acid-file
still doesn´t start from the beginning. It starts from the 01.00.00.00 postition, witch
is not any more the beginning time.
I´m pretty sure, that my setup is ok. Same thing is also without Gigastudio running,
and timecode itself should be ok too. My other devices are reading it well.

Subject:RE: Acid 3 & MIDI Timecode

Reply by: riwe

Date:5/31/2001 3:05:12 PM

I mean that Acid 3 triggers too late via MTC. My configuration is: Fostex D1624 Harddisk-Recorder
as MTC master. This feeds the MTC signal via the M-Audio Audiophile 2496 card in Acid 3.
The D1624 begins at 00:59:57:00 with 25fps. I want that Acid trigger at 01:00:00:00. It seems
that Acid beginsthe synchronization at the time in the time ruler (I set it to 01:00:00:00) plus the
synchronization time I set in the Sync dialog (2 sec). Because when I set the sync time to
1 sec, Acid begins to play at 01:00:01:00, when sync time is set to 2 sec Acid begins
at 01:00:02:00. So Acid will always be too late.

When I feed in the same configuration Cubase VST/32 it works fine ( the sync too).

I have the same problems like Pekka. When I set the time ruler to 00:00:00:00, Acid starts at
01:00:00:00 too and there is no more music.

Subject:RE: Acid 3 & MIDI Timecode

Reply by: Pekka

Date:6/6/2001 4:21:15 AM

How nice! No more replies from SF, when they see, that this
TC-issue is still buggy. Really professional attitude...

Subject:RE: Acid 3 & MIDI Timecode

Reply by: SonyJennL

Date:6/7/2001 11:12:51 AM

First of all, let me thank you for your input and your follow up. I just want to assure you that we ARE looking into this issue.

Please be patient. I was waiting to respond when I could tell you something definite and I cannot right now.

So far we have had mixed results trying to reproduce the problem. Some programs seem to reproduce it and some do not. We have not been able to reproduce the problem with hardware at all so far.

But, rest assured, we are investigating the problem and working on fixing it. I will make sure to drop you another post on this thread once we know more.
Thanks.

Subject:RE: Acid 3 & MIDI Timecode

Reply by: SonyJennL

Date:8/9/2001 12:34:50 PM

Sorry it has taken so long for me to respond.

Just wanted to let you all know that 3.0b version is available and we made a number of fixes with issues of MIDI Trigger, Offsets, and MIDI Clock.

Try it out. Hopefully, everything will run much more smoothly now.

Happy Mixing!
-Jenn