Cool - thanks for the info - Dave On May 17, 2006, at 1:16 PM, James Richmond wrote: >> Are you saying that clicking the bypass button does not bypass the >> delay caused by the plug-in? Is that documented somewhere, or have >> you tested it? >> > > I've tested it as I do this all the time- I posted this a few days > ago also, I think. > Bypassing the plugin in TDM does not positively affect DSP resources > or plugin latency, so you can use it to parallel process the way > Peter describes. > > James > > > > > > > > > ______________________________________________________________________ > __ > Logic TDM Users Group - new forums! http://logic-users.org/forums/L- > TDM > - To UNSUBSCRIBE: email logic-tdm-unsubscribe@yahoogroups.com > - Search the entire archive: http://logic-users.org/forums/L-TDM/ > search > Yahoo! Groups Links > > > > > > >

Thanx James, but all my drives (3 LaCie's) are Apple formatted... i have obviously tried to verify and repair all disks but all ok. The problem, however, is still there and just getting worse and worse..... HELP ANYBODY!!!!! --- In logic-tdm@yahoogroups.com, James Richmond <richmondjames@...> wrote: > > > I will be working on a song and suddenly with no warning Logic > > freezes for about 30sec or > > so. After this all audio files playing back on DAE tracks will not > > play back or white noise > > plays back from those track. The DTDM tracks and instruments tracks > > work fine. The > > message which comes up when this is all about to happen is: > > > > Disk is too slow or > > System Overload. > > (-10010) > > I had this ages ago when I used a Formac FW drive and formatted it > with it's own drivers, rather than Apples. > > Had me scratching my head for ages- I reformatted it with Disk > Utility and it was all OK after that.

> Thanx James, but all my drives (3 LaCie's) are Apple formatted... i > have obviously tried to > verify and repair all disks but all ok. The problem, however, is > still there and just getting > worse and worse..... HELP ANYBODY!!!!! Beats me. You tried trashing pref? Tried disabling DTDM and just using DAE? If you are at your wits end then I'd say B.F.R - Backup, Format, Reinstall. While you are at it try reseating the cards- you might even want to try that before the BFR. Are you tracking to a FW drive- if not then try it, if you are then stop and try recording/playing internally. James

Hi everyone, haven´t been here for a while. What OSX version are you on? Is 10.4.6 working? /E 2x1.8, 4Gb RAM, OSX 10.4.5,HD Accel 3, PT 7.1cs5, L7.2 _______________________________ Erik Häusler Future Love Productions AB erik.hausler@mac.com

Ahaaa.... tried to run on a different FW drive than i normally do and things seemed to run smooth. The drive i mainly use IS pretty full (about 30GB left on a 240 GB drive) and i now think it's probably very fragmented...I, however, didn't think this was something we had to worry about anymore but i guess i was wrong there!!! Whats the best way to de-frag a drive these days (apart from obviously removing things). Thanx for you help so fare. Getting there!! Pete --- In logic-tdm@yahoogroups.com, James Richmond <richmondjames@...> wrote: > > > Thanx James, but all my drives (3 LaCie's) are Apple formatted... i > > have obviously tried to > > verify and repair all disks but all ok. The problem, however, is > > still there and just getting > > worse and worse..... HELP ANYBODY!!!!! > > Beats me. > You tried trashing pref? > > Tried disabling DTDM and just using DAE? > > If you are at your wits end then I'd say B.F.R - Backup, Format, > Reinstall. > While you are at it try reseating the cards- you might even want to > try that before the BFR. > > Are you tracking to a FW drive- if not then try it, if you are then > stop and try recording/playing internally. > > James > > > > >

Working just fine here. all the latest, greatest versions. b On May 18, 2006, at 5:05 AM, slutsomartist wrote: > Hi everyone, > haven´t been here for a while. What OSX version are you on? Is > 10.4.6 working? > > /E > 2x1.8, 4Gb RAM, OSX 10.4.5,HD Accel 3, PT 7.1cs5, L7.2 > _______________________________ > Erik Häusler > Future Love Productions AB > erik.hausler@mac.com

Try repairing permissions first. 30GB should be fine- but a BFR sounds like the ticket here imho. It certainly won't hurt. JR On May 18, 2006, at 7:48 PM, facefamily3000 wrote: > Ahaaa.... tried to run on a different FW drive than i normally do > and things seemed to run > smooth. The drive i mainly use IS pretty full (about 30GB left on > a 240 GB drive) and i now > think it's probably very fragmented...I, however, didn't think this > was something we had to > worry about anymore but i guess i was wrong there!!! Whats the > best way to de-frag a > drive these days (apart from obviously removing things). Thanx for > you help so fare. > Getting there!! > Pete

I need to run Core and DAE at the same time which Core interface seems to be the most stable Running Logic 7.2 , PT 7.1 HD2 Excel (latest cs update) OS 10.4.6 G5 Dual 2.0 4 gig ram Thanks John C.

Thank's Very match for info

Hi!... Finally upgraded to ProTools HD - Accel III with a PowerMac G5 4 x 2,5 GHz, 4,5 GB DDR2 SDRAM, and was looking 4-ward to flawless functionality, smooth operation and in the end... more money pouring in. Thats when i got DAE/DSI Error 1146... It makes PT (and of course Logic) bug out at launch, DigiTest isn't working, Accel-cards suddenly don´t load Plug-Ins, audio-playback stops, and worst of all... The S****r is intermittent FRUSTRATED!!! Anyone have a clue??? In Answerbase it says that DAE-Error i related to The Masenburg EQ... something... I don't even have that installed!... It seems to be a heat-problem and also related to the SDRAM's... Rig: Powermac G5, 4 x 2,5 GHz, 4,5 GB DDR2 SDRAM, 2 x 250 GB Harddrive on S-ATA. ProTools HD - Accel III 192 I/O SYNC I/O Protools 7.1cs7 (rev2) Logic 7.2.1 __________________________________ Fredrik Beckmann Beckmann & Co Rostastrand 51 703 44 ÖREBRO Tel: 019-18 50 02 Fax: 019-18 50 04 Mob: 0708-35 47 36 Hemsida: www.beckmann-co.se mailto: fredrik@beckmann-co.se __________________________________

Vonedward.... is your g5 a pci, or pcie machine?

Has anyone had this bug or found a workaround? After SMPTE position of many regions, select all, and unlock SMPTE position. --- BUT not all of them unlock, some stay locked. Selecting those individually and choosing unlock SMPTE position does not help. Opening alternate views in other editors like the event list - also no help. Reorganizing song memory - no help. In this particular song, I had to go into each of the locked regions and copy the MIDI events, pasting them to a new region. With the audio regions I had to make new regions and trim to match. Sheesh! - Dave

Here's another bug I just ran into - anyone else had this one? Any workarounds? I have a song with track automation. I need to cut and insert time. When I do so, most but not all of the automation moves. I can't find any pattern in which tracks have the automation moved and which ones don't, but it seems to be the same ones each time I try it. Any ideas on this one? Thanks Dave

My problem has always been that smpte lock does not work at all. Try putting the audio tp a movie on a track and manipolating the offset or bar 1 time code. I inquired about this before with some othe members who thought it a pretty well established non functionality of logic. --

Hey greg No pt 7 is proprietary to hd hardware or digi002 (le version). I am facing the same can of worms. Be sure to remain at os 10.3.4 (some push it to 10.3.8) and off of quicktime 7 if you are interested in your Protools/dae functioning correctly. If you need anything I will be out looking for a bag of money, I will let you know if I find one for you!!! Matt --

My auto-tune 3 crashes my system since my upgrade to PT 7, I know this is more of a digi thing but wondering if anybody else has the same problem. I do not use auto tune as much as I like the LP pitch correction better. But still want to load up old song and do not want to upgrade to V4 just to do this. Alex Dual 2.0 , 2 gig, PTHD Accel 2, 828 MKII 10.4.6 cs6, PT 7.1, LP 7.2

The latest Autotune version seems to be 4.4.0, I am currently using 4.2.3 - have you tried if the problem persists when you upgrade to a newer version? Also, I see you are using a native MOTU interface alongside your Digi hardware - would you mind telling me if you suffer from random timing offsets between the two audio engines? Thanks, and HTH, Brio Taliaferro On 22 May 2006, at 01:24, alexgreggs wrote: > My auto-tune 3 crashes my system since my upgrade to PT 7, I know > this is more of a digi > thing but wondering if anybody else has the same problem. I do not > use auto tune as much > as I like the LP pitch correction better. But still want to load up > old song and do not want to > upgrade to V4 just to do this. > > Alex > > Dual 2.0 , 2 gig, PTHD Accel 2, 828 MKII > > 10.4.6 > cs6, PT 7.1, LP 7.2

Same here. I ended up buying Melodyne for only a little more money than the upgrade to Autotune 4 would have cost. I ended up just trashing the Antares plugin. I also got the Waves Tune Lite as part of my WUP, and that seems to do an awfully nice job as well. -mark On May 22, 2006, at 4:52 PM, logic-tdm@yahoogroups.com wrote: > > > My auto-tune 3 crashes my system since my upgrade to PT 7
Mark Henderson  mark@dirtydogproductions.net 952.210.4801

Everytime when I try to quit Logic I get the message "Error code -1 was returned by the Direct TDM driver". I can not quit Logic on the normal way, everytime I have to "force quit". I use DAE and Direct TDM. Any idea's how I can solve this problem? I've run already Yasu without positive results. Wim Claes Dual G5 2,7 ghz, 4,5 GB RAM, OS 10.4.7 Logic 7.2.1 HD3 Accel, Protools 7.1cs7 192, 2 x 96i, 1x 96 interface

Autotune crashes on my system in TDM mode when I use bowed lines in the edit mode. In the AU version it works well. This problem is there already since Logic 7.0, and I don't think Apple and Antares will ever solve this problem... Wim Dual G5 2,7 ghz, 4,5 GB RAM, OS 10.4.7 Logic 7.2.1 HD3 Accel, Protools 7.1cs7 192, 2 x 96i, 1x 96 interface --- In logic-tdm@yahoogroups.com, Mark Henderson <m.hender@...> wrote: > > Same here. I ended up buying Melodyne for only a little more money > than the upgrade to Autotune 4 would have cost. I ended up just > trashing the Antares plugin. I also got the Waves Tune Lite as part > of my WUP, and that seems to do an awfully nice job as well. > > -mark > > > On May 22, 2006, at 4:52 PM, logic-tdm@yahoogroups.com wrote: > > > > > > > My auto-tune 3 crashes my system since my upgrade to PT 7 > >
> Mark Henderson > >  > mark@... > 952.210.4801 > > > > > > >

Hi, First of all the good news. I have now finally upgraded from my beloved OS9/Mix system to HD 2 Accel PCIe, G5 Dual 2.3, Pro Tools 7.1cs7 & Logic 7.2.1. I braced myself for the worst, but so far, in the first 3 days the system has been 100% stable, not a single crash, ESB working fine etc. I just have 2 small questions: Can ReVibe (or any other surround reverb) be used in surround in Logic TDM? Question 2: Can Digidesign EQ 3 be used in stereo? It comes up on mono channels, but stereo channels only give (awful) EQ II as an option. Many thanks, Dom

--- In logic-tdm@yahoogroups.com, David Gordon <music-pro@...> wrote: > > Here's another bug I just ran into - anyone else had this one? Any > workarounds? > > > I have a song with track automation. I need to cut and insert time. > When I do so, most but not all of the automation moves. I can't find > any pattern in which tracks have the automation moved and which ones > don't, but it seems to be the same ones each time I try it. > > > Any ideas on this one? > > Thanks > Dave > DUDE... This one is a sore spot with me. I lost a big gig because this happened in front of a client at a very crucial time. UGH !!! I had random problems with cut and paste when automation is involved. There is no logic (no pun intended) when it happened. A byproduct of this event was that the "bad" area or piece of music that was affected by this automation bug couldn't not be fixed. I could not repair the damage... meaning i could not retry the cut and paste operation once the bug grabbed this section. I may not be very articualate with this problem because it still baffles me. I do not know what really happend... just that the automation at a random point would not cut and past with the audio and then rendered that section of audio not editable (wacky automation) after it went bad. Ramble Ramble Ramble ... anyone else??? [:-B]

--- In logic-tdm@yahoogroups.com, forums@... wrote: > > Message posted by Dom <lug@...>: > > Hi, > > First of all the good news. I have now finally upgraded from my beloved > OS9/Mix system to HD 2 Accel PCIe, G5 Dual 2.3, Pro Tools 7.1cs7 & Logic > 7.2.1. I braced myself for the worst, but so far, in the first 3 days the > system has been 100% stable, not a single crash, ESB working fine etc. > > I just have 2 small questions: Can ReVibe (or any other surround reverb) be > used in surround in Logic TDM? Question 2: Can Digidesign EQ 3 be used in > stereo? It comes up on mono channels, but stereo channels only give (awful) > EQ II as an option. > > Many thanks, > > Dom > Hi, The EQ3 is only mono which means you have to run dual mono mode. I don't even know how to do that in Logic. Hmmmmm. anyone?

The only times I've had problems with automation is when the Region Automation, available through the Hyper Draw, was in direct conflict with the Track automation. Once I discovered this, I was able to fix a couple of sessions that were driving me batty. Maybe this is the issue you are encountering? Bob On May 24, 2006, at 1:47 PM, myronpoo wrote: > > --- In logic-tdm@yahoogroups.com, David Gordon <music-pro@...> wrote: >> >> Here's another bug I just ran into - anyone else had this one? Any >> workarounds? >> >> >> I have a song with track automation. I need to cut and insert time. >> When I do so, most but not all of the automation moves. I can't find >> any pattern in which tracks have the automation moved and which ones >> don't, but it seems to be the same ones each time I try it. >> >> >> Any ideas on this one? >> >> Thanks >> Dave >> > DUDE... > This one is a sore spot with me. I lost a big gig because this > happened in front of a client at a very crucial time. UGH !!! I had > random problems with cut and paste when automation is involved. There > is no logic (no pun intended) when it happened. A byproduct of this > event was that the "bad" area or piece of music that was affected by > this automation bug couldn't not be fixed. I could not repair the > damage... meaning i could not retry the cut and paste operation once > the bug grabbed this section. > > I may not be very articualate with this problem because it still > baffles me. I do not know what really happend... just that the > automation at a random point would not cut and past with the audio and > then rendered that section of audio not editable (wacky automation) > after it went bad. > > Ramble Ramble Ramble ... > > anyone else??? [:-B] > > > > > > > > ______________________________________________________________________ > __ > Logic TDM Users Group - new forums! http://logic-users.org/forums/L- > TDM > - To UNSUBSCRIBE: email logic-tdm-unsubscribe@yahoogroups.com > - Search the entire archive: http://logic-users.org/forums/L-TDM/ > search > Yahoo! Groups Links > > > > > >

Thanks for both of your responses. I did check the hyperdraw as Bob suggested, but that was not the issue. Now, I found out what happened. I thought I posted something about this in the last couple days but don't recall for sure. It turns out it is a Logic bug, but it's not specifically related to automation. Actually this bug affected many of the events in the song and turned into a much bigger problem. I worked around it, but it is not solved and this song file is now damaged. Here is what happened: Someone gave my a file of 6/8 drum parts recorded into Logic with the time sig set to 4/4. So to get the drum parts properly lined up in 6/8, I used the Region > Lock SMPTE Position command, then I changed the time sig and tempo to what was needed. This worked great. The audio and midi parts were all lined up nicely. I completed the song which has many tracks and plenty of automation. Next, I needed to do a shorter version of the same song, so I used the Region > Unlock SMPTE Position command and proceeded to cut some stuff and drag around some regions. That's when I noticed the automation bug and posted my query. Later I noticed that some of the midi notes inside the sequences themselves had not moved when I dragged the sequences - they still had the little SMPTE-Lock icon. So I selected those notes and tried to unlock them in the event editor. No luck, they stayed locked. I tried copying and pasting the notes to a new regions. No change. Some randomly selected notes through many sequences had become permanently locked. As I did more tests and continued working on the remix, I noticed that the automation was even acting strangely when dragging with the automation select tool. Multiple nodes would move just fine, but some of the individual nodes would not move. So I opened the automation event editor (control-option-command-space in my keyset). That showed the same problem as the midi regions of some but not all of the events permanently locked. So the bottom line - I had to reconstruct some elements of the song and I had to work around the regions with the locked notes and construct my remix there. That solved this emergency, but it does not explain how this happened. I also tried locking some SMPTE positions in another test song and found that this bug is intermittent, but it does happen regularly though not every time. What concerns me about this is that there are often reasons to lock SMPTE positions and now I wonder if it's possible to use that function. Certainly, whenever I do use it, I will first duplicate the regions and keep copies that have not been locked in case I need to reconstruct what happened. - Dave David Gordon Composer/Producer Sequoia Records http://www.sequoiarecords.com On May 24, 2006, at 2:16 PM, Bob DeMaa wrote: > The only times I've had problems with automation is when the Region > Automation, available through the Hyper Draw, was in direct conflict > with the Track automation. Once I discovered this, I was able to fix > a couple of sessions that were driving me batty. Maybe this is the > issue you are encountering? > > Bob > > On May 24, 2006, at 1:47 PM, myronpoo wrote: > >> >> --- In logic-tdm@yahoogroups.com, David Gordon <music-pro@...> wrote: >>> >>> Here's another bug I just ran into - anyone else had this one? Any >>> workarounds? >>> >>> >>> I have a song with track automation. I need to cut and insert time. >>> When I do so, most but not all of the automation moves. I can't >>> find >>> any pattern in which tracks have the automation moved and which ones >>> don't, but it seems to be the same ones each time I try it. >>> >>> >>> Any ideas on this one? >>> >>> Thanks >>> Dave >>> >> DUDE... >> This one is a sore spot with me. I lost a big gig because this >> happened in front of a client at a very crucial time. UGH !!! I had >> random problems with cut and paste when automation is involved. >> There >> is no logic (no pun intended) when it happened. A byproduct of this >> event was that the "bad" area or piece of music that was affected by >> this automation bug couldn't not be fixed. I could not repair the >> damage... meaning i could not retry the cut and paste operation once >> the bug grabbed this section. >> >> I may not be very articualate with this problem because it still >> baffles me. I do not know what really happend... just that the >> automation at a random point would not cut and past with the audio >> and >> then rendered that section of audio not editable (wacky automation) >> after it went bad. >> >> Ramble Ramble Ramble ... >> >> anyone else??? [:-B] >> >> >> >> >> > > > > ______________________________________________________________________ > __ > Logic TDM Users Group - new forums! http://logic-users.org/forums/L- > TDM > - To UNSUBSCRIBE: email logic-tdm-unsubscribe@yahoogroups.com > - Search the entire archive: http://logic-users.org/forums/L-TDM/ > search > Yahoo! Groups Links > > > > > > >