> Please note that SoundDiver works on OS X in the Classic environment. > > Beste Gruesse - best regards, > Michael Haydn > AutoLink is not possible. MIDI works only with OMS. > > Beste Gruesse - best regards, > Michael Haydn Hey Michael, I'm a SoundDiver licensee. Why are you telling us to use SoundDiver in OSX/Classic if it doesn't actually work? Does it work or not? Make up your mind and let us know the truth, please, sir. So far, it seems you are saying it works for copying text for libraries, but you can't use it with Autolink or Midi at all. If that's what you call working, I'm sorry I asked. Teddybut

Teddy Kumpel wrote: >Why are you telling us to use SoundDiver in OSX/Classic if it doesn't >actually work? Does it work or not? Make up your mind and let us know the >truth, please, sir. > >So far, it seems you are saying it works for copying text for libraries, but >you can't use it with Autolink or Midi at all. If that's what you call >working, I'm sorry I asked. > >Teddybut > > > Have you tried it yet? It works just fine, except for Autolink. What he means is you must have OMS setup in OS 9 for it to work in Classic. He said nothing about it not working, just Autolink didnt work. I editied a bunch of patches on my MicroQ and Microwave XT last night under Classic. And finally copied all my patch names to my Enviroment too. Sounddiver seems to work just fine. Oh and for what its worth, I didnt use OMS either. I have an AMT8 and just let Sounddiver keep using the built in drivers for the AMT8. Worked like a charm. Chris

Am 03.12.2003 um 19:34 schrieb Teddy Kumpel: > Why are you telling us to use SoundDiver in OSX/Classic if it doesn't > actually work? Does it work or not? Make up your mind and let us know > the > truth, please, sir. > > So far, it seems you are saying it works for copying text for > libraries, but > you can't use it with Autolink or Midi at all. If that's what you call > working, I'm sorry I asked. SoundDiver 3.0 works in OS X on its own, but not in combination with an OS X MIDI program. Beste Gruesse - best regards, Michael Haydn - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Dipl.-Inform. Univ. Michael Haydn mhaydn@... SoundDiver Group Executive http://www.emagic.de/ Logic Developer (Control Surface Integration) Emagic Soft- & Hardware GmbH - Germany Phone: +49 4101 495 0 Halstenbeker Weg 96, 25462 Rellingen Fax : +49 4101 495 199 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Hello, Suddenly experiencing problems with Logic plug-in audio intermittently dropping out! This happens even in a simple project with a single audio object. Occurs with various processing plug-ins (delays, reverbs, etc), whether Logic's, Apple's built-in AU plug-ins, or third-party plug-ins. All else seems to behave fine (audio playback, MIDI, virtual instruments). The problem seemed to begin after Logic unexpectedly quit once, but perhaps this is just coincidental (Logic crashed while adjusting window sets, of all things). Nothing else has been added or changed, hardware or software. I deleted and rebuilt all the emagic Prefs (plist) files. Restarted all hardware and soft. Created new blank Logic song. Tried running the Logic project froma different hard drive. Tried using different audio files. Not a processor issue, as problem occurs with a minimal project. Not a memory issue or hard disk space issue, plenty of both. Any suggestions? Thank you for any assistance. SYSTEM: Logic 6.3.2 OS X.3.2 Panther HooverMac G4 Dual 867 PCI-424/G5 + 2408mkII External word clock sync Regards, 3

Michael Haydn wrote: >SoundDiver 3.0 works in OS X on its own, but not in combination with an >OS X MIDI program. For a company like Emagic, which is an "Apple" company, this is pretty weak. OSX has already progressed to 10.3.x, but there is no OSX version of SoundDiver after all this time. I have been using SoundDiver since version 1.x, but now in OSX, I have to shut down Logic, boot SoundDiver, do what I need, shut down SoundDiver, re-boot Logic etc etc, every time I want to load sounds from a library or make even the smallest edit. Not very impressive..... Regards - Colin

On Dec 4, 2003, at 3:34 PM, Colin Shapiro wrote: > For a company like Emagic, which is an "Apple" company, this is > pretty weak. OSX has already progressed to 10.3.x, but there is no > OSX version of SoundDiver after all this time. > > I have been using SoundDiver since version 1.x, but now in OSX, I > have to shut down Logic, boot SoundDiver, do what I need, shut down > SoundDiver, re-boot Logic etc etc, every time I want to load sounds > from a library or make even the smallest edit. > > Not very impressive..... > > Regards - Colin > It would really be impressive if people understood just what Sounddiver did. Theyre an Apple OWNED company. They are not Apple. Its still Emagic doing the work. You go rewrite all of the modules inside Sounddiver so it can still work with all of the synths it handles and then some.. Oh and dont forget to make sure you test the app with as much of the hardware youre going to support too before you release it. Do you want Sounddiver to be a nice quality Apple/Emagic product? Or do you want a Native Instruments version of the app? Chris --- www.descentrecords.com www,towelhead.net

On 12/5/03 12:34 AM, "Colin Shapiro" <musos@...> wrote: > Michael Haydn wrote: >> SoundDiver 3.0 works in OS X on its own, but not in combination with an >> OS X MIDI program. > > For a company like Emagic, which is an "Apple" company, this is > pretty weak. OSX has already progressed to 10.3.x, but there is no > OSX version of SoundDiver after all this time. > > I have been using SoundDiver since version 1.x, but now in OSX, I > have to shut down Logic, boot SoundDiver, do what I need, shut down > SoundDiver, re-boot Logic etc etc, every time I want to load sounds > from a library or make even the smallest edit. > > Not very impressive..... > > Regards - Colin > Hello Colin, Sorry to say that you are wrong, if you look in the XSKEY settings "Sound diver" is there ;o) May be, after all, they reserve the usage of Sound Diver only to Emagic's people ;o))))))) May be it will come as a Christmas present ! Best regards Cyril Blanc France Please sign the petition ³Apple to support APPLE LaserWriter 300 in MAC OS X² http://www.PetitionOnline.com/Ap1c1/petition.html If you want to be sure I read your answer leave my name in it ! Spam mails are directly going to trash

Ciao, Well then, nothing like a technical trainwreck to end a music session. Further research into this problem reveals the following: IT DEPENDS ON THE LENGTH OF THE AUDIO REGION --------------------------------------------- The problem only occurs with short audio regions (less than 1/8th note at 120 bpm or so). Probably why I hadn't noticed this issue until now, as today was intended to be a day of major sound design with percussive samples. IT'S NOT THE AUDIO FILE! ----------------------- Same problem playing different audio files, if the regions are made short enough. IT'S NOT THE VERSION OF LOGIC! ------------------------------ The problem occurs with Logic 6.3.2 in OS 10.3.2. I also re-installed 6.01 from the original Logic CD: same problem. IT'S NOT THE PREFS! ------------------- Deleting the prefs led to the same problem. IT'S NOT THE OS! ---------------- The problem also occurs in Logic 6.3.1 in OS 9.2.2! IT'S NOT THE DRIVE! ------------------- Same problem with the project running on other drives. IT'S NOT THE SONG! ------------------ Same problem in any song. Even using the Emagic demo song from the CD would cause the problem, if one makes a region short enough. IT'S NOT THE PLUG-IN! --------------------- Happens with any plug-in: Emagic's delay or reverb, mda plug-ins, Apple's own built-in Audio Unit reverb... IT'S NOT THE MAC (or is it)? -------------------------- Digital Performer's reverbs and delays behave fine on my machine. Unless it's an interaction between Logic and my particular system. I have trouble believing that this problem is a general Logic issue, as I've heard of no other similar complaints, even after searching the forums for such. So: If someone would be kind as to confirm whether or not they have the same problem? Is this a general Logic bug? I will certainly call Emagic tomorrow to investigate. Thank you for any assistance... Regards, 3

>So: If someone would be kind as to confirm whether or not they have > the same problem? > Is this a general Logic bug? > > I will certainly call Emagic tomorrow to investigate. > > Thank you for any assistance... > > Regards, > 3 I had the same problem with Logic 6.3.2 in OS 10.3.1 when trying to do a long reverb at the end of a song with multiple percussion hits on several tracks. The reverb would cut out, like a gate, and then come back in. Very annoying. I had to solve the problem by using the reverbs at the submix insert instead of the channel FX insert. I think it's a Logic "Bug"

Cyril wrote: >Sorry to say that you are wrong, if you look in the XSKEY settings "Sound >diver" is there ;o) > >May be, after all, they reserve the usage of Sound Diver only to Emagic's >people ;o))))))) > >May be it will come as a Christmas present ! Yes, I know about that XSkey thing - but it's useless to me. Christmas.....which year....? 2015?

[Note from admin: -- please keep talk about SD on the LUG focused on SD + Logic, not just SD, thanks! If you guys want to just talk about SoundDiver, please do so on the SoundDiver-users list. ] Chris wrote: >You go rewrite all of the modules inside Sounddiver so it can still >work with all of the synths it handles and then some.. >Oh and dont forget to make sure you test the app with as much of the >hardware youre going to support too before you release it. >Do you want Sounddiver to be a nice quality Apple/Emagic product? Or do >you want a Native Instruments version of the app? Yes, I know about that argument. However, many folks on the SoundDiver forum have offered to be testers for hardware/modules which they own. I have no doubt the program would work fine, with better versions of modules/adaptions being released as and when possible. In any case, Emagic could release a "beta" with a disclaimer. I think it's just too time-intensive with little prospect of financial return for the effort invested. However, Emagic should consider their faithful customers, who are now left with really scrappy options. I wouldn't let them off the hook so easily.... Regards - Colin

On 12/5/03 12:02 PM, "Colin Shapiro" <musos@...> wrote: > Cyril wrote: >> Sorry to say that you are wrong, if you look in the XSKEY settings "Sound >> diver" is there ;o) >> >> May be, after all, they reserve the usage of Sound Diver only to Emagic's >> people ;o))))))) >> >> May be it will come as a Christmas present ! > > Yes, I know about that XSkey thing - but it's useless to me. > Christmas.....which year....? 2015? 3001, Emagic Odyssey ;o) Best regards Cyril Blanc France Please sign the petition ³Apple to support APPLE LaserWriter 300 in MAC OS X² http://www.PetitionOnline.com/Ap1c1/petition.html If you want to be sure I read your answer leave my name in it ! Spam mails are directly going to trash

I'm being plagued by a problem in Logic when using Kontakt (1.51) and wondered if anyone else had a similar problem or any suggestions. Basically, when the song is playing, if I select certain tracks in the arrange window (e.g other Audio Instrument tracks or audio tracks, sometimes even basic MIDI tracks) audio playback from Kontakt becomes disrupted, causing it to stutter and break-up. I've been in touch with Emagic support in the UK, have rebuilt my entire project including rebuilding the environment from scratch and only copying the arrange data across, and it has made no difference. Kontakt plays fine with most tracks selected, but with others the audio break-up issues return and are pretty severe. Basically Logic seems somehow to be interfering with Kontakt playback by allocating resources to other tracks when they are selected. I will Kontakt Native Instruments about the problem, but would be grateful if anyone had any ideas. Gotta say, with the number of problems I've had since moving back to Logic on Mac, I wonder how some of you guys get any work done!! ;) Jules

Next in the list of issues ....... I've been trying to save/recall plugin presets for 3rd party Audio Unit plugins and the system seems not to be working. I stress , these are native Audio Unit plugins, not VST plugins via a wrapper (which I haven't even tried yet). Using the host's Load Setting/Save Setting controls (from the pull-down at the top left of the plugin interface), although the settings are saved (apparently), when they are loaded, the actual settings are not recalled. So far I have tested it with Waves, Ohmforce and Universal Audio plugins and none of the m work using the host's Load/Save controls. With Logic's own plugins it works fine. The only success I have had is using the Load/Save buttons on some of the Waves plugins (ie. NOT the host's Load/Save system), which simply asks if you want to store settings in the 'Preset List', with no ability to specify where the settings are actually stored. This system does work, the saved preset appears in the list, and settings are recalled when you load it, but you have no control over where the preset are actually stored. The Load/Save buttons (again NOT the host's Load/Save system) do not work - no errors, but the settings are not recalled. Many other plugins do not have their own Load/Save buttons, and therefore rely on the host's Load/Save system and these don't work - at least not here. Please can anyone tell me if these are acknowledged issues, or provide a summary of what works and how, as far as plugins presets are concerned. At every turn I seem to bump into another issue - am I really the only one having these problems?!! Sorry for the exasperation - 6 weeks on Mac now, and not a single project completed. Jules

On a fine day, 05-12-2003, Zenon Marko wrote: >So: If someone would be kind as to confirm whether or not they have >the same problem? >Is this a general Logic bug? I just tried: took an organ sample, inserted it on an audio track, shortened it to 1/16th note, and set the tempo to 120 bpm (and later to 200 bpm). Created 4 copies of the region at the 1st/2nd/3rd/4th beat of bar 1. Then I inserted the PlatVerb with a reverbtime of 20 seconds. Hit play: sounds as expected -- 4 short bursts of organ followed by a huge reverb tail... Platinum 6.3.1 on a G4, OS 9.2.2 -- Hendrik Jan Veenstra h @ k n o w a r e . n l Omega Art: http://www.omega-art.com/

> >Is this a general Logic bug? > I just tried: took an organ sample Just tried to prove Zenon's point and couldn't. works fine here. But that's an empty song with nothing else going on... LAMP 6.3.1 on a G4/867 on OS9.2.2 Christian

> > >Is this a general Logic bug? > >> I just tried: took an organ sample > >Just tried to prove Zenon's point and couldn't. works fine here. But that's an >empty song with nothing else going on... > >LAMP 6.3.1 on a G4/867 on OS9.2.2 > >Christian > Hello Christian, Thank you for trying this out. Glad to hear that you don't seem to be having the problem. The problem occurs here even in the simplest case, that is, a new song with a single audio file in a track. The "gating" or drop-outs don't occur every time, but depends on where one starts playback. For example, sometimes playing from right at the region location in the track works fine, while playing from a measure or a beat before results in the drop outs. Best, 3

Ciao, I just confirmed with a collaborator here in New York who is experiencing the same problem. Can't get through yet to Logic tech support... 3

Hello, Sad news: The bug is confirmed by Emagic tech support. Futhermore, there is no fix available and no hope of a fix in the future! This is an issue intrinsic to the plug-in architecture, and occurs with short regions. Apparently something to do with the way plug-ins buffer audio data. The suggested work-around, believe it or not: pad all samples and regions with silence. Sorry to say this, but this is completely unprofessional. Who has time to add silence to all percussive samples in a track? Does anyone else know of another work-around? Logically disappointed, 3

> Who has time to add silence to all percussive samples in a track? > Does anyone else know of another work-around? Bounce the whole track prior to the final cut. Christian

> > Who has time to add silence to all percussive samples in a track? >> Does anyone else know of another work-around? > >Bounce the whole track prior to the final cut. > >Christian > Yes, I suppose one can do that. That entails bouncing twice, once without the FX, and again wih Or one can add silence files in a parallel track on the same audio object. Not very elegant solutions. Apparently this problem is known and documented by many other users. I have now found some threads on the issue for those who are interested: http://community.sonikmatter.com/emagic/ultimatebb.php?ubb=get_topic;f;t16 34 http://community.sonikmatter.com/emagic/ultimatebb.php?ubb=get_topic;f;t04 65#000010 http://community.sonikmatter.com/cgi-bin/emagic/ultimatebb.cgi?ubb=get_topic ;f;t0619 Why hasn't Emagic fixed this bug, which has existed since version 5 if not earlier? There must be a solution the programmers could come up with, even if the solution is only an invisible automation of the aforementioned work-arounds (secretly padding short audio regions with silence). 3

>> Bounce the whole track prior to the final cut. > Yes, I suppose one can do that. > That entails bouncing twice Try using the freeze feature. This might help, as it renders a continuous 32bit file in the background. Tell us if this helps. Christian

> >> Bounce the whole track prior to the final cut. > >> Yes, I suppose one can do that. >> That entails bouncing twice > >Try using the freeze feature. This might help, as it renders a continuous >32bit file in the background. > >Tell us if this helps. > >Christian > Christian, Thank you for the idea. I had tried that, but it doesn't help in this situation. Either one freezes with the effects enabled on the track, in which case the freeze includes the pesky drop-outs. Or one freezes without the effects enabled, in which case one can no longer add the effects back after the freeze! I am trying the approach of utilizing a long silence file (10 minutes). The long silence file (which can be mono) need only be stored once in a wisely chosen location on the hard drive, rather than copied for every new song. What I will do, unless a better solution is found, is put this silence file in doubles of every track in my template, starting it at measure zero (the silence file must begin before any audio files else this approach doesn't work). Then I will hide all these silence tracks. I suppose I should by default mute all the silence tracks, and only unmute them as needed, else Logic will be reading 64 tracks of silence from the hard drive before I've even begun creating actual music tracks for a project! Also wonder whether audio instruments are affected by this problem. So far, quick tests with Kontakt and short samples seem positive, in that the problem has not occurred yet. This is good, as I am not sure how one can use the silence file approch with Audio Instruments. Presumably, one would have to actually manually edit (lengthen with silence) every individual sample used by Kontakt! But perhaps this won't be necessary, as Kontakt seems to behaving so far. Any advice from more experienced Logicians is welcome. This sounds like another good topic for the FAQ, as I imagine most new Logicians run into this problem eventually. Best, 3

> >> Bounce the whole track prior to the final cut. > >> Yes, I suppose one can do that. >> That entails bouncing twice > >Try using the freeze feature. This might help, as it renders a continuous >32bit file in the background. > >Tell us if this helps. > >Christian > Further thoughts on this: Freezing would help in this case if the frozen file still behaved as an ordinary audio track. I wish that freeze worked more like an automatic bounce+add+place, the way it works in DP. The resulting track is still editable, effects can be applied, and so on. Freeze in its current form is essentially useless to me, except perhaps in the end stages of a project, as one has to constantly unfreeze and refreeze in order to make structural changes in the track. Either that, or I wish bouncing were a more immediate activity which one could perform directly from the arrange window rather than from the Output Object. One last wish: that outputs could be routed back into inputs of tracks (if I understand correctly, this is currently impossible in Logic?). Then one could manually bounce in the Arrange window. Cheers, 3

> Either one freezes with the effects enabled on the track, in which case the > freeze includes the pesky drop-outs. Or one freezes without the > effects enabled, in which case one can no longer add the effects back > after the freeze! Right. But Delays and Reverbs are usually accessed through sends, which are still being fed after freezing, thus making the workaround work around. > put this > silence file in doubles of every track in my template, starting it at > measure zero (the silence file must begin before any audio files else > this approach doesn't work). > Then I will hide all these silence tracks. So essentially when the 'real' regions in the arrangement rightly drop out, the track (voice) falls back to the silent file, right ? Howzat for disk and CPU load when all tracks are always playing full on ? > Also wonder whether audio instruments are affected by this problem. I have never had this, while i definitely had the problem on normal audio tracks. > This is good, as I am not sure how one can use the silence file > approch with Audio Instruments. You can't, don't bother. > Presumably, one would have to actually manually edit (lengthen with > silence) every individual sample used by Kontakt! Nope. It's a MIDI track, after all. Christian

> I wish that freeze worked more like an automatic bounce+add+place, Honestly, i've been fantasizing about this since the word Bounce first appeared in Logic, which *is* quite a while now. > The resulting track is still editable A freeze file is too, once you get your head around where it lives and you mamage to figure which is which despite their ($(/&!"$$&/( naming style... > Either that, or I wish bouncing were a more immediate activity which > one could perform directly from the arrange window You can. Create an empty track with the Output's object. Use it's Record button to bounce. > One last wish: that outputs could be routed back into inputs of > tracks (if I understand correctly, this is currently impossible in > Logic?). Then one could manually bounce in the Arrange window. Problem is that you'd change from float to fixed point math and 32bit to 16 or 24 bit several times that way and i don't assume this to be a Good Thing. Christian

Hendrik Jan Veenstra wrote: > > >I just tried: took an organ sample, inserted it on an audio track, >shortened it to 1/16th note, and set the tempo to 120 bpm (and later >to 200 bpm). Created 4 copies of the region at the 1st/2nd/3rd/4th >beat of bar 1. Then I inserted the PlatVerb with a reverbtime of 20 >seconds. Hit play: sounds as expected -- 4 short bursts of organ >followed by a huge reverb tail... > >Platinum 6.3.1 on a G4, OS 9.2.2 > Thank you for trying it out. I also had the problem in that arrangement, Logic Platinum 6.3.1 with OS 9.2.2 on G4 HooverMac. Perhaps the problem would have occurred if you had a single hit in isolation? Or, possibly this problem only occurs on certain system? The Emagic tech with whom I spoke was not sure whether the problem is universal to all configurations. 3

Hey All - I cant get Kompakt to show up in my Logic 5.5 vsti list! All my other native instrument plugs work.. how odd. anyone have this happen? I installed it into the proper vst folder in the logic directory My other NI VSTi's include B4, Reaktor, BAttery, FM7 and Intakt. They all show up no prob. All have the latest updates - including kompakt. My machine - Athlon 1800, WinXP, 1gb RAM, echo layla, logic 5.5.1 Neil

Christian wrote: > >> The resulting track is still editable > >A freeze file is too, once you get your head around where it lives and you >mamage to figure which is which despite their ($(/&!"$$&/( naming style... I didn't know this. Is there more info written about that somewhere, or perhaps you can elaborate if you have time? > > Either that, or I wish bouncing were a more immediate activity which >> one could perform directly from the arrange window > >You can. Create an empty track with the Output's object. Use it's Record >button to bounce. Thank you for this info. I must have missed it in the manual. I just realized that the checkbox was not checked on the Outputs in my environment. All is well know. I just tried this, however, and see that one still has to track down the resulting file in the Audio window and drag it into place in the Arrange window. Rats. 3

On a fine day, 05-12-2003, Zenon Marko wrote: >The bug is confirmed by Emagic tech support. >Futhermore, there is no fix available and no hope of a fix in the future! So you mean Emagic sell their flagship application as being "pro audio", while at the same time acknowledging that you can't use 1/8th note audio regions with effects without running the risk of getting drop-outs? Now that's what I would call having balls... -- Hendrik Jan Veenstra h @ k n o w a r e . n l Omega Art: http://www.omega-art.com/

On a fine day, 05-12-2003, Zenon Marko wrote: > >Try using the freeze feature. This might help, as it renders a continuous >>32bit file in the background. >> > >Tell us if this helps. > >Christian, > >Thank you for the idea. >I had tried that, but it doesn't help in this situation. Either one >freezes with the effects enabled on the track, in which case the >freeze includes the pesky drop-outs. Or one freezes without the >effects enabled, in which case one can no longer add the effects back >after the freeze! Insert the effects on a bus and route the frozen track's output to that bus. Less than elegant, but at least it saves you the hassle of continually freezing/unfreezing. -- Hendrik Jan Veenstra h @ k n o w a r e . n l Omega Art: http://www.omega-art.com/

On a fine day, 06-12-2003, Zenon Marko wrote: >Hendrik Jan Veenstra wrote: > >I just tried: took an organ sample, inserted it on an audio track, >>shortened it to 1/16th note, and set the tempo to 120 bpm (and later >>to 200 bpm). Created 4 copies of the region at the 1st/2nd/3rd/4th >>beat of bar 1. Then I inserted the PlatVerb with a reverbtime of 20 >>seconds. Hit play: sounds as expected -- 4 short bursts of organ >>followed by a huge reverb tail... >> > >Platinum 6.3.1 on a G4, OS 9.2.2 > >Thank you for trying it out. >I also had the problem in that arrangement, Logic Platinum 6.3.1 with >OS 9.2.2 on G4 HooverMac. > >Perhaps the problem would have occurred if you had a single hit in isolation? No, I tried a single hit as well. Maybe there's some other mystery-factor involved. Or maybe it's just "coincidence" -- today it happens, tomorrow not. Sometimes computers simply don't make any sense at all... -- Hendrik Jan Veenstra h @ k n o w a r e . n l Omega Art: http://www.omega-art.com/

On a fine day, 06-12-2003, Zenon Marko wrote: >Christian wrote: > >> The resulting track is still editable >> >>A freeze file is too, once you get your head around where it lives and you >>mamage to figure which is which despite their ($(/&!"$$&/( naming style... > >I didn't know this. >Is there more info written about that somewhere, or perhaps you can >elaborate if you have time? Set the freeze format to 24-bit (somewhere in the preferences) -- Logic can't import its own 32-bit files as if they were regular audio files, so you have to make sure freeze produces 24 bit files. Then when you've frozen a track, you'll have a folder "Freeze files" in your song's folder which will contain the 24-bit files. Just move them out of the Freeze Files folder, rename them to something sensible and import them as regular audio. If you leave them "as is" where they are created, you run the risk of Logic deleting them as soon as you unfreeze the parent track (although Logic ought to be aware that those same files are used in the Audio window... but I wouldn't bet a month's salary on that). -- Hendrik Jan Veenstra h @ k n o w a r e . n l Omega Art: http://www.omega-art.com/

> > >No, I tried a single hit as well. Maybe there's some other >mystery-factor involved. Or maybe it's just "coincidence" -- today >it happens, tomorrow not. Sometimes computers simply don't make any >sense at all... > >-- >Hendrik Jan Veenstra h @ k n o w a r e . n l >Omega Art: http://www.omega-art.com/ > True. I did find that the problem would often depend on the playback start point. Starting at certain areas of the prior measure would induce the problem, starting at other points would not. Also, the problem would not occur every time. But when it did, the drop outs would occur in a repeating time relationship. What I would like to find out is whether the "mystery factor" is something within our control: a difference in configuration of Logic, or differences in the settings of the OS, etc... Best, 3

> I just tried this, however, and see that one still has to track down > the resulting file in the Audio window and drag it into place in the > Arrange window. Rats. - Hit Stop to return to the left locator. - Select the track where you want the new file to be put. - Use Audio>Import Audio File. - Select your file in the following dialog. - Done. This places files on a quantized grid, so make sure you use Set *Rounded* Locators instead of Set Locators By Objects prior to bouncing. While most of the above could be automated through Quickkeys, there's no safe way to automatically *and* intelligantly put and name files, which leaves us just one step short of auto-importing the bounced bits on appropriate tracks. Christian

>> Create an empty track with the Output's object. Use it's Record >> button to bounce. > > Thank you for this info. > I must have missed it in the manual. It's not there, i guess... > I just realized that the checkbox was not checked on the Outputs in > my environment. You can apple-click on any environment object to assign it to the current track. No need to clutter the instrument list. Christian

Ciao - Any idea why the Bounce command in the File menu only seems to allow one to bounce the audio of Output 1-2? Why can one not choose the desired output? Cheers, 3

Op 12 mrt 2005 om 2:45 heeft Zenon Marko het volgende geschreven: > Any idea why the Bounce command in the File menu only seems to allow > one to bounce the audio of Output 1-2? Why can one not choose the > desired output? > > Cheers, > 3 I believe it is only the default filename. All the outputs are bounced. I think te programmers at Logic figured that if you're using more outputs, you would be using external processing or mixing so there would be no need to bounce the internal mix. Maybe something like that. But if you want to bounce outputs 3-4, just mute the other outputs in the mixer (not in the arrange window, that strangely doesn't work right), en it will work just fine. Don't forget to rename the default file, to avoid getting confused. Amir Amir Swaab mail: contact@... www: www.amirswaab.nl tel: +31 (0)6 4499 8099 fax: +31 (0)20 6121 004

Ciao, I am interested in suggestions on how to set up a project in Logic so that one can process a submix of tracks, but still maintain the flexibility of separate outputs for the tracks to utilize an external mixer. (In this case, I would like to be able to modulate/filter the entire rhythm submix during only certain sections of the song: drums and bass). Perhaps I am asking the impossible. One approach would be to bounce the submix to an audio file and put that into a separate track just for the sections where said submix must be modulated. Another approach would be to give up on using the external mixer for the tracks of interest, and perform all mixing in Logic. Neither of these approaches is ideal. Is there a better solution which I have not considered? Thank you in advance for any advice. Cheers, 3 NYC

Zenon Marko <z_marko@...> wrote: >Any idea why the Bounce command in the File menu >only seems to allow one to bounce the audio of >Output 1-2? Why can one not choose the desired >output? There's no ulterior motive behind this... it's just an incomplete feature set. If you need to bounce outputs other than 1/2, use the method also used in Logic 6/5/4/3 and click the "BNCE" button at the bottom left corner of the relevant Physical Output object. It would be nice if the actual Bounce dialogue box allowed you to change the the output path to be bounced (like in ProTools), but that's just a minor convenience and not something high on my wish list. f-erenc szabo, smarty pants Z+E+R+O+B+E+A+T "NOW POWERED BY THE MIRACLE OF THE TRANSISTOR!" <http://home.goodmedia.com/~zerobeat>