Why does ACID lock to MTC so 'mushy' ?? -ACID Product Family

ACID Product Family

Subject:Why does ACID lock to MTC so 'mushy' ?? Posted by: rmeuk Date:6/27/1999 4:28:00 PM I'm syncing ACID to a ProTools system on a Mac with MTC. Unfortunately ACID locks up different, up to 80ms (!) every time. With other programs on the Mac I get a couple of ms, most of the time variations of +/- 3ms. But what ACID does is unusable. I tried to use different MIDI interfaces (the Midi on the Pulsar card and an Opcode Midi Translator PC) I sent MTC from ProTools, then I sent it from Cubase. To no avail. Now I ask you: Is there ANY WAY to sync ACID professional let's say within 1ms to Timecode? (SMPTE or MTC) Cheers, Stephen Rhodes rme London UK
Subject:Re: Why does ACID lock to MTC so 'mushy' ?? Reply by: rfreeman Date:6/27/1999 11:55:00 PM I am having the same problems with Session 8 PC. Have tried several virtual MIDI drivers. Having lots of lock ups and crashes too. Just bought a new PIII 450 thinking my old AMD had something to do with it, but no. Looks like ACID has some problems to be fixed.
Subject:Re: Why does ACID lock to MTC so 'mushy' ?? Reply by: rmeuk Date:6/28/1999 5:01:00 PM Did a couple of tests again and played around with the prefs. The best results I got were +/- 15ms. I'm afraid that doesn't make me happy at all! Stephen Ryan Freeman wrote: >>I am having the same problems with Session 8 PC. Have tried several virtual MIDI drivers. Having lots of lock ups and crashes too. Just bought a new PIII 450 thinking my old AMD had something to do with it, but no. Looks like ACID has some problems to be fixed.
Subject:Re: Why does ACID lock to MTC so 'mushy' ?? Reply by: pwppch Date:7/4/1999 12:51:00 AM Do you mean the ACID takes 80 ms to lock or that it is off by 80 ms when it does lock? Peter Stephen Rhodes wrote: >>I'm syncing ACID to a ProTools system on a Mac with MTC. >>Unfortunately ACID locks up different, up to 80ms (!) every >>time. >>With other programs on the Mac I get a couple of ms, most >>of the time variations of +/- 3ms. >>But what ACID does is unusable. I tried to use different >>MIDI interfaces (the Midi on the Pulsar card and an Opcode >>Midi Translator PC) >>I sent MTC from ProTools, then I sent it from Cubase. To no >>avail. >> >>Now I ask you: Is there ANY WAY to sync ACID professional >>let's say within 1ms to Timecode? (SMPTE or MTC) >> >>Cheers, >> >>Stephen Rhodes >>rme London UK >>
Subject:Re: Why does ACID lock to MTC so 'mushy' ?? Reply by: rmeuk Date:7/4/1999 7:03:00 AM I don't mean it takes 80ms to lock. Let me give you an example: You have one drumtrack in ACID. Now I record that track 4 times with my ProTools system on the Apple (which sends MTC to ACID) If you zoom into these 4 tracks and compare them you'll see that the position of the drums varies up to +/- 40ms. Or if you play these 4 tracks you can hear that they don't play together. With other software (sequencer) I get variations of up to 3ms, which is much better then ACID. (though still not good enough, but I know MTC is not well enough defined). I unchecked the 'chase to MTC' function in ACID, so it just triggers and play at the moment, because with chase MTC I get much worse results. The downside is ACID drifts slowly away, although my Pulsar card is (wordclock) locked to ProTools! Sometimes I got the situation that ACID refuses to play at all, although it shows the incoming MTC. I have to press play and stop on ACID. Sometimes it works then sometimes it don't. The best way to get it working is to quit it and start it again. I used different Midi-interfaces. No difference! My hardware: PII/350, 250Mb RAM (100MHz) Creamware Pulsar soundcard (samplingrate locked to ProTools) Opcode Midi Translator PC Cheers, Stephen rme London UK Peter Haller wrote: >>Do you mean the ACID takes 80 ms to lock or that it is off by 80 ms when it does lock? >> >>Peter >> >>Stephen Rhodes wrote: >>>>I'm syncing ACID to a ProTools system on a Mac with MTC. >>>>Unfortunately ACID locks up different, up to 80ms (!) every >>>>time. >>>>With other programs on the Mac I get a couple of ms, most >>>>of the time variations of +/- 3ms. >>>>But what ACID does is unusable. I tried to use different >>>>MIDI interfaces (the Midi on the Pulsar card and an Opcode >>>>Midi Translator PC) >>>>I sent MTC from ProTools, then I sent it from Cubase. To no >>>>avail. >>>> >>>>Now I ask you: Is there ANY WAY to sync ACID professional >>>>let's say within 1ms to Timecode? (SMPTE or MTC) >>>> >>>>Cheers, >>>> >>>>Stephen Rhodes >>>>rme London UK >>>>
Subject:Re: Why does ACID lock to MTC so 'mushy' ?? Reply by: rmeuk Date:7/9/1999 5:55:00 AM Peter? Stephen Rhodes wrote: >>I don't mean it takes 80ms to lock. >>Let me give you an example: >>You have one drumtrack in ACID. >>Now I record that track 4 times with my ProTools system on the Apple (which sends MTC to ACID) >>If you zoom into these 4 tracks and compare them you'll see that the position of the drums varies up to +/- 40ms. Or if you play these 4 tracks you can hear that they don't play together. >>With other software (sequencer) I get variations of up to 3ms, which is much better then ACID. (though still not good enough, but I know MTC is not well enough defined). >>I unchecked the 'chase to MTC' function in ACID, so it just triggers and play at the moment, because with chase MTC I get much worse results. The downside is ACID drifts slowly away, although my Pulsar card is (wordclock) locked to ProTools! >>Sometimes I got the situation that ACID refuses to play at all, although it shows the incoming MTC. I have to press play and stop on ACID. Sometimes it works then sometimes it don't. The best way to get it working is to quit it and start it again. >>I used different Midi-interfaces. No difference! >> >>My hardware: >>PII/350, 250Mb RAM (100MHz) >>Creamware Pulsar soundcard (samplingrate locked to ProTools) >>Opcode Midi Translator PC >> >>Cheers, >> >>Stephen >>rme London UK >> >>Peter Haller wrote: >>>>Do you mean the ACID takes 80 ms to lock or that it is off by 80 ms when it does lock? >>>> >>>>Peter >>>> >>>>Stephen Rhodes wrote: >>>>>>I'm syncing ACID to a ProTools system on a Mac with MTC. >>>>>>Unfortunately ACID locks up different, up to 80ms (!) every >>>>>>time. >>>>>>With other programs on the Mac I get a couple of ms, most >>>>>>of the time variations of +/- 3ms. >>>>>>But what ACID does is unusable. I tried to use different >>>>>>MIDI interfaces (the Midi on the Pulsar card and an Opcode >>>>>>Midi Translator PC) >>>>>>I sent MTC from ProTools, then I sent it from Cubase. To no >>>>>>avail. >>>>>> >>>>>>Now I ask you: Is there ANY WAY to sync ACID professional >>>>>>let's say within 1ms to Timecode? (SMPTE or MTC) >>>>>> >>>>>>Cheers, >>>>>> >>>>>>Stephen Rhodes >>>>>>rme London UK >>>>>>
Subject:Re: Why does ACID lock to MTC so 'mushy' ?? Reply by: pwppch Date:7/15/1999 9:51:00 PM Steve? I am verifying your problems. It appears to be a hardware specific issue, as I cannot repro the problems you are having exactly. We are getting a Pulsar in as there are many reports of problems with this hardware, so as soon as it shows, I might have more insight. Peter Steve Rhodes wrote: >>Peter? >> >>Stephen Rhodes wrote: >>>>I don't mean it takes 80ms to lock. >>>>Let me give you an example: >>>>You have one drumtrack in ACID. >>>>Now I record that track 4 times with my ProTools system on the Apple (which >>sends MTC to ACID) >>>>If you zoom into these 4 tracks and compare them you'll see that the position >>of the drums varies up to +/- 40ms. Or if you play these 4 tracks you can hear >>that they don't play together. >>>>With other software (sequencer) I get variations of up to 3ms, which is much >>better then ACID. (though still not good enough, but I know MTC is not well >>enough defined). >>>>I unchecked the 'chase to MTC' function in ACID, so it just triggers and play >>at the moment, because with chase MTC I get much worse results. The downside is >>ACID drifts slowly away, although my Pulsar card is (wordclock) locked to >>ProTools! >>>>Sometimes I got the situation that ACID refuses to play at all, although it >>shows the incoming MTC. I have to press play and stop on ACID. Sometimes it >>works then sometimes it don't. The best way to get it working is to quit it and >>start it again. >>>>I used different Midi-interfaces. No difference! >>>> >>>>My hardware: >>>>PII/350, 250Mb RAM (100MHz) >>>>Creamware Pulsar soundcard (samplingrate locked to ProTools) >>>>Opcode Midi Translator PC >>>> >>>>Cheers, >>>> >>>>Stephen >>>>rme London UK >>>> >>>>Peter Haller wrote: >>>>>>Do you mean the ACID takes 80 ms to lock or that it is off by 80 ms when it >>does lock? >>>>>> >>>>>>Peter >>>>>> >>>>>>Stephen Rhodes wrote: >>>>>>>>I'm syncing ACID to a ProTools system on a Mac with MTC. >>>>>>>>Unfortunately ACID locks up different, up to 80ms (!) every >>>>>>>>time. >>>>>>>>With other programs on the Mac I get a couple of ms, most >>>>>>>>of the time variations of +/- 3ms. >>>>>>>>But what ACID does is unusable. I tried to use different >>>>>>>>MIDI interfaces (the Midi on the Pulsar card and an Opcode >>>>>>>>Midi Translator PC) >>>>>>>>I sent MTC from ProTools, then I sent it from Cubase. To no >>>>>>>>avail. >>>>>>>> >>>>>>>>Now I ask you: Is there ANY WAY to sync ACID professional >>>>>>>>let's say within 1ms to Timecode? (SMPTE or MTC) >>>>>>>> >>>>>>>>Cheers, >>>>>>>> >>>>>>>>Stephen Rhodes >>>>>>>>rme London UK >>>>>>>>
Subject:Re: Why does ACID lock to MTC so 'mushy' ?? Reply by: alalal Date:7/21/1999 9:50:00 AM Peter... you say it is a hardware issue. I guess this means that some PC audio hardware provides a good MTC lock and some does not. It would be great to have a list of PC audio hardware that locks well using MTC. Could you or someone else provide such a list. (Even a partial list would be helpful.) Regards, Allen Booth Peter Haller wrote: >>Steve? >> >>I am verifying your problems. It appears to be a hardware specific issue, as I >>cannot repro the problems you are having exactly. We are getting a Pulsar in >>as there are many reports of problems with this hardware, so as soon as it >>shows, I might have more insight. >> >> >>Peter >> >> >>Steve Rhodes wrote: >>>>Peter? >>>> >>>>Stephen Rhodes wrote: >>>>>>I don't mean it takes 80ms to lock. >>>>>>Let me give you an example: >>>>>>You have one drumtrack in ACID. >>>>>>Now I record that track 4 times with my ProTools system on the Apple (which >>>>sends MTC to ACID) >>>>>>If you zoom into these 4 tracks and compare them you'll see that the >>position >>>>of the drums varies up to +/- 40ms. Or if you play these 4 tracks you can >>hear >>>>that they don't play together. >>>>>>With other software (sequencer) I get variations of up to 3ms, which is >>much >>>>better then ACID. (though still not good enough, but I know MTC is not well >>>>enough defined). >>>>>>I unchecked the 'chase to MTC' function in ACID, so it just triggers and >>play >>>>at the moment, because with chase MTC I get much worse results. The downside >>is >>>>ACID drifts slowly away, although my Pulsar card is (wordclock) locked to >>>>ProTools! >>>>>>Sometimes I got the situation that ACID refuses to play at all, although it >>>>shows the incoming MTC. I have to press play and stop on ACID. Sometimes it >>>>works then sometimes it don't. The best way to get it working is to quit it >>and >>>>start it again. >>>>>>I used different Midi-interfaces. No difference! >>>>>> >>>>>>My hardware: >>>>>>PII/350, 250Mb RAM (100MHz) >>>>>>Creamware Pulsar soundcard (samplingrate locked to ProTools) >>>>>>Opcode Midi Translator PC >>>>>> >>>>>>Cheers, >>>>>> >>>>>>Stephen >>>>>>rme London UK >>>>>> >>>>>>Peter Haller wrote: >>>>>>>>Do you mean the ACID takes 80 ms to lock or that it is off by 80 ms when >>it >>>>does lock? >>>>>>>> >>>>>>>>Peter >>>>>>>> >>>>>>>>Stephen Rhodes wrote: >>>>>>>>>>I'm syncing ACID to a ProTools system on a Mac with MTC. >>>>>>>>>>Unfortunately ACID locks up different, up to 80ms (!) every >>>>>>>>>>time. >>>>>>>>>>With other programs on the Mac I get a couple of ms, most >>>>>>>>>>of the time variations of +/- 3ms. >>>>>>>>>>But what ACID does is unusable. I tried to use different >>>>>>>>>>MIDI interfaces (the Midi on the Pulsar card and an Opcode >>>>>>>>>>Midi Translator PC) >>>>>>>>>>I sent MTC from ProTools, then I sent it from Cubase. To no >>>>>>>>>>avail. >>>>>>>>>> >>>>>>>>>>Now I ask you: Is there ANY WAY to sync ACID professional >>>>>>>>>>let's say within 1ms to Timecode? (SMPTE or MTC) >>>>>>>>>> >>>>>>>>>>Cheers, >>>>>>>>>> >>>>>>>>>>Stephen Rhodes >>>>>>>>>>rme London UK >>>>>>>>>>
Subject:Re: Why does ACID lock to MTC so 'mushy' ?? Reply by: pwppch Date:7/21/1999 1:38:00 PM Perhaps I should have said "system specific". (Don't want to blame anybody for what may be our problem.) I have lots of systems that behave differently with the exact same hardware. Sometimes it is the hardware's fault, sometimes it is gremlins of another sort. As soon as the Pulsar arrives we will be testing and determining what the problem really is. MTC lock is really dependent on the MTC and not the audio hardware/ unless the audio hardware/driver takes a very long time or indeterminate amount of time to start. Again, I am looking at all the problems and I will have a response as soon as I know more. If it is hardware specific, then we will notify the vendor of any problems we are experiancing. We don't like to recommend or condem any specific hardware. We inform the vendor and work with them on resolving the issues at hand. Thanks Peter Allen Booth wrote: >>Peter... you say it is a hardware issue. I guess this means that some PC audio hardware provides a >>good MTC lock and some does not. It would be great to have a list of PC audio hardware >>that locks well using MTC. >> >>Could you or someone else provide such a list. (Even a partial list would be helpful.) >> >>Regards, >> >>Allen Booth >> >>Peter Haller wrote: >>>>Steve? >>>> >>>>I am verifying your problems. It appears to be a hardware specific issue, as I >>>>cannot repro the problems you are having exactly. We are getting a Pulsar in >>>>as there are many reports of problems with this hardware, so as soon as it >>>>shows, I might have more insight. >>>> >>>> >>>>Peter >>>> >>>> >>>>Steve Rhodes wrote: >>>>>>Peter? >>>>>> >>>>>>Stephen Rhodes wrote: >>>>>>>>I don't mean it takes 80ms to lock. >>>>>>>>Let me give you an example: >>>>>>>>You have one drumtrack in ACID. >>>>>>>>Now I record that track 4 times with my ProTools system on the Apple (which >>>>>>sends MTC to ACID) >>>>>>>>If you zoom into these 4 tracks and compare them you'll see that the >>>>position >>>>>>of the drums varies up to +/- 40ms. Or if you play these 4 tracks you can >>>>hear >>>>>>that they don't play together. >>>>>>>>With other software (sequencer) I get variations of up to 3ms, which is >>>>much >>>>>>better then ACID. (though still not good enough, but I know MTC is not well >>>>>>enough defined). >>>>>>>>I unchecked the 'chase to MTC' function in ACID, so it just triggers and >>>>play >>>>>>at the moment, because with chase MTC I get much worse results. The downside >>>>is >>>>>>ACID drifts slowly away, although my Pulsar card is (wordclock) locked to >>>>>>ProTools! >>>>>>>>Sometimes I got the situation that ACID refuses to play at all, although it >>>>>>shows the incoming MTC. I have to press play and stop on ACID. Sometimes it >>>>>>works then sometimes it don't. The best way to get it working is to quit it >>>>and >>>>>>start it again. >>>>>>>>I used different Midi-interfaces. No difference! >>>>>>>> >>>>>>>>My hardware: >>>>>>>>PII/350, 250Mb RAM (100MHz) >>>>>>>>Creamware Pulsar soundcard (samplingrate locked to ProTools) >>>>>>>>Opcode Midi Translator PC >>>>>>>> >>>>>>>>Cheers, >>>>>>>> >>>>>>>>Stephen >>>>>>>>rme London UK >>>>>>>> >>>>>>>>Peter Haller wrote: >>>>>>>>>>Do you mean the ACID takes 80 ms to lock or that it is off by 80 ms when >>>>it >>>>>>does lock? >>>>>>>>>> >>>>>>>>>>Peter >>>>>>>>>> >>>>>>>>>>Stephen Rhodes wrote: >>>>>>>>>>>>I'm syncing ACID to a ProTools system on a Mac with MTC. >>>>>>>>>>>>Unfortunately ACID locks up different, up to 80ms (!) every >>>>>>>>>>>>time. >>>>>>>>>>>>With other programs on the Mac I get a couple of ms, most >>>>>>>>>>>>of the time variations of +/- 3ms. >>>>>>>>>>>>But what ACID does is unusable. I tried to use different >>>>>>>>>>>>MIDI interfaces (the Midi on the Pulsar card and an Opcode >>>>>>>>>>>>Midi Translator PC) >>>>>>>>>>>>I sent MTC from ProTools, then I sent it from Cubase. To no >>>>>>>>>>>>avail. >>>>>>>>>>>> >>>>>>>>>>>>Now I ask you: Is there ANY WAY to sync ACID professional >>>>>>>>>>>>let's say within 1ms to Timecode? (SMPTE or MTC) >>>>>>>>>>>> >>>>>>>>>>>>Cheers, >>>>>>>>>>>> >>>>>>>>>>>>Stephen Rhodes >>>>>>>>>>>>rme London UK >>>>>>>>>>>>

Go Back