MacMusic.org  |  PcMusic.org  |  440Software  |  440Forums.com  |  440Tv  |  Zicos.com  |  AudioLexic.org
Loading... visitors connected
Welcome Guest
 
Reply to this topicStart new topic
> 
danmix
post Fri 6 Apr 2001, 20:32
Post #1


Newbie


Group: Members
Posts: 4
Joined: 04-Apr 01
Member No.: 410




Hi, this is concerning MIDI TIMING on CUBASE MAC v 4.1 and 5.0.
The set up is:
Mac clone POWER CENTER PRO + XLR8 G3 500 Mhz running OS 8.6 352 RAM.
OPCODE studio 64XTC midi interface.
oms 2.3.8
MOTU 2408
latest asio 2.1 from MOTU /

I have tried all the solutions i can think of to solve this issue...
OMS,pci card,Drivers,MacOS,extensions,preferences,etc...

Recording the midi to audio will produce random timing shift as far as 15ms late once recorded on the audio track !

The midi needs to be recorded at some early stages since it will drift as more cpu is used!
This is happening with minimum load on the cpu.

As you can imagine, this render the program almost unusable for midi purposes.


Anybody else experiencing this?
Thanks!
Go to the top of the page
 
+Quote Post
prutulz
post Sat 7 Apr 2001, 16:04
Post #2


Junior Member
***

Group: Members
Posts: 165
Joined: 12-Jan 01
From: Brussels - BE
Member No.: 183




I've experienced the same things with all cubase versions since audio was introduced. Midi play randomly (this is the nightmare) to late or to ealry.

ie: you record a MIDI sound (rimShot, HH) on each beat  during 4 bars, then record the audio output to a DAT, then copy your DAT back to the computer in a file, and edit it with an accurate sample editor like peak or Protools. Select  each beat lenght, and notice its duration (in samples). you will be surprised to see that beat durations doesn't match  !! angry.gifangry.gif

How do you want to get your music to groove if Cubase is'nt allready able to play as tight as a $15 metronome.

I now use Logic which is more complex, IMO, but really accurate about MIDI timing!




(Edited by prutulz at April 7, 2001 - 18:04)


--------------------
Prutulz
RTFM... is usually not enough
Go to the top of the page
 
+Quote Post
lloydforth
post Wed 18 Apr 2001, 09:39
Post #3


Newbie


Group: Members
Posts: 7
Joined: 15-Apr 01
From: London
Member No.: 446




two things are probably causing this

no.1 OMS unfortunatly was coded around the time when 68k code was used and has never been rewritten for PPC machines

Bottleneck 1

Bottleneck 2

XLR8 proccessor upgrade. what is the ratio between the buss speed and the proccessor . and how much backside cache do you have?

the answer to your problem is sell the clone purchse at least a B+W G3 pref G4 and look at other interface's

Motu interface's use a version of OMS that they have had re written it's called 'free midi'

probably not the best news you have had today but what use is a composition tool that swings like a transvestite at a porn convention!
Go to the top of the page
 
+Quote Post
danmix
post Thu 19 Apr 2001, 22:36
Post #4


Newbie


Group: Members
Posts: 4
Joined: 04-Apr 01
Member No.: 410




When I'm listening to my MIDI synth playing along with Cubase audio (LM-4, Model E, vocals),everything is tight. But when I then record the synth (pads, percussion, guitar) to audio, that audio isn't in sync with the existing audio. Does anyone else have this problem?
YOU WILL SOLVE THIS PROBLEM and the other listed here by setting the MAC OS disk cache size(in the memory control panel) to a NON default value like 128k...
This won't solve the midi timing drifts as the cpu demand increase though!
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Lo-Fi Version - Sat 21 Dec 2024, 17:28
- © MacMusic 1997-2008