Logic Pro And Motu Traveler Issue, No audio after long periods of use |
mer. 8 mars 2006, 01:12
Message
#1
|
|
Newbie Groupe : Members Messages : 2 Inscrit : 08 mars 06 Lieu : Chesham - UK Membre no 77,874 |
This is a wierd one. I've been using this setup on a live TV show running click to band rhythm section and additional sequencing to two other stereo pairs out of the Traveller. It can be fine all day - 5/6 hours - then when it comes to the broadcast, I can check the track several times - all is fine - then at some point, it will just not send audio from the outputs of Logic, and the Traveler shows and outputs nothing. Re-launching Core Audio does not resolve the issue, nor does re-booting the Traveler, factory resetting the Traveler, or re-launching Logic Pro. I have re-created the issue at home by leaving the configuration on overnight. In the morning the issue occurs - it appears to be a time thing, not dependant on whether the program is being used or not i.e. it can happen during use as well as after a long period of inactivity. I have not tried previous versions of logic to work around this yet, but I used to use 7.0.1 with MOTU Firewire driver 1.2.5 (2005-05-10) before and don't recall the same issue. This issue occurs in Logic 7.1.1 with MOTU drivers 1.2.5 (2005-05-10) and 1.4.1 (2006-02-28). I have nothing else running, e.g. Widgets, Screen Savers, No Energy Saver settings, all non-essential software is disabled/closed. It occurs with or without firewire bus power or a separate power supply. If I swap back to Built-in audio as my Audio driver I can play stuff through the internal speakers, but if I then switch back to MOTU Traveler as the Audio device the problem is still there. The only way out is to re-boot the machine - which is re-loading the driver, I guess.
Any help would be gratefully received |
|
|
Les messages de ce sujet
lepetitmartien A few things out of my head (I'm sick these da... mer. 8 mars 2006, 04:58
cornutt My guess is it's a driver bug. It sounds like... mer. 8 mars 2006, 17:48
slackhammond2 Thanks Cornutt No reply for over 3 days from MOTU... jeu. 9 mars 2006, 10:44
cornutt My guess is it's a driver bug. It sounds like... mer. 8 mars 2006, 17:48
slackhammond2 Thanks Cornutt No reply for over 3 days from MOTU... jeu. 9 mars 2006, 10:44
2 utilisateur(s) sur ce sujet (2 invité(s) et 0 utilisateur(s) anonyme(s))
0 membre(s) :