> Can anybody confirm that if I obtain the free Mac crossgrade > that I can carry on using Mac plus Windows indefinitely or is > there a time limit on windows use. You can use Logic for an unlimited amount of time on *both* platforms.. Just one computer at a time though of course. Hope this helps, Jeremy http://www.ixks.com/~sadus

Hi All, I downloaded that free version of the FXpansion dr005 plugin someone posted yesterday. Logic 5.2 hangs on startup when it is scanning the VST plugins. It gets stuck when it gets to the dr005 and locks up. Any ideas what could be causing this? -- Eli Krantzberg Nightshift Orchestra / Almat Productions http://www.nightshiftorchestra.com

Does external wordclock have anything to say when you do a bounce of a mix inside LAWP5.2? I think the mix sounds brighter when using my Focusrite Octopre wordclock as a master over the RME-Multiface wordclock. Could I be right or am I too tired? To bed now... -- Arvid Solvang http://www.viagram.no/

On 8/30/02 2:56 PM, "CDJ Tracks" <cdjtracks1@...> wrote: > (1) Now with that being said my first question is using the ADAT ports on > the sound card at 192 sample rate, would it split the ADAT ports from 1-8 > inputs per adat port it would be 1-4 inputs per port??? I do not believe it is possible to split the ADAT ports on the RME Hammerfall to get 192khz. I belive that they can bit-split via SMUX to get 96khz, but that is as far as it goes. Sorry, Orren --------------------------- http://www.dvboutique.com http://www.emberafter.com

--- In logic-users@y..., Eli Krantzberg <elik@c...> wrote: > I downloaded that free version of the FXpansion dr005 plugin someone > posted yesterday. Logic 5.2 hangs on startup when it is scanning the VST > plugins. It gets stuck when it gets to the dr005 and locks up. Any ideas > what could be causing this? The only thing I can think of is if you rename some plugin outside of what the installer named them, you will encounter some problems. Others just don't work on some systems, especially free ones heh ;P

For a recent surround project, I bought a $25 subharmonic plugin called PhatProDX (not available for Mac, unfortunately) from Delay Dots, a Ukrainian company. Although highly CPU inefficient, it sounds cool and seems to work well. Since I have no experience with hardware subharmonic synthesizers, however, I have nothing to compare it to. Anybody out there familiar with subharmonic synths who may also be acquainted with this plugin? I'm very curious as to whether it does what it's supposed to do, and how well. Thanks, Sean McCoy Oregon Sound Recording

You know, I still don't understand just how to set input and output operations. I get that it needs to be wired to say audioinst1, i get that it needs to have the second wire to the sequencer input. From there i'm lost, being that when you double click the transformer you can set only one set of conditions, and this text seems to ask for two (input/output), with operations being a completely different task. It doesn't even mention if you're supposed to map them out yourself etc. I was wondering if we could get a non greek version to try out, as I have just about expired all my present resources heh :)

Hi, Still trying to solve this problem with my Logic Control sending out volume messages to my moudules. Try this if your interested: 1. Don't have the little check box for volume checked below the tools palatte in the arrange page. (we're not supposed to use that checkbox when using logic control as Logic control is now handling volume thru the automation. 2. Grab a fader of Logic Control and pull it down so it sends a volume message to your module. Set it to about 20. Record a little piano ditty. 3. Save Your Song 4. BEFORE quiting the program grab that fader and set it to 127 sending a 127 volume command to the module. 5. Quit Logic 6. Open up the saved song file 7. Hit Play Volume 20 is not sent. It's still LOUD! The module still has the 127 value. Yes I have the send Used Midi settings and All Fader Values check boxes selected in the Midi Options Menu but I think that pertains to the checkbox we're not supposed to use anyway? The only way I can get to send the volume message is to manually grab the adaptavive mixer's drop down menu and select send all fader values. Yes I know I can insert events into the track. Was kinda hoping that Logic Control was going to do this for me. Can anyone shed any light? Dave Zeltner David Zeltner Productions

Hi, I'm using Metric Halo Mobile I/O. With Logic's Software Monitoring off (=ASIO direct monitoring on), I can monitor the input signal (of the record enabled track) with near zero (less than 2ms) latency, thanks to its DSP powered mixer. The problem described below occurs with LAMP 5.2.0 and not with 5.1.3. With a microphone plugged into analog input 1, I monitor my voice through Mobile I/O's mixer (Logic's Software Monitoring: off). The input is panned at the center, both in MIO's and Logic's mixers. Now, I click the record button of Logic's audio track. Result: my voice suddenly moves to the right (to some extent - not thoroughly). It goes back to the center when I mute/unmute the signal in MIO's mixer. Even if the panpot of Logic's mixer is at -64 (hard left), the input signal moves to the right. When Logic's fader is at minus infinity (in 'record-ready' state--you know, Logic remembers the levels for recording monitor and playback separately), the voice gets muted by clicking the record-enable button. When the fader is at other levels (0dB, +6dB, -78dB...), the level of the sound doesn't get much influenced by enabling to record. It just moves to the right. Repeating to click rec-ready button in Logic (without resetting MIO by muting/unmuting the input) along with moving Logic's fader causes irregular response. Monitoring state (on/off) loses relation with record-ready state, and the monitoring level doesn't follow the above principle. With 5.1.3, Logic's panpot and fader accurately controls the direct monitoring. Is there a bug in 5.2.0's mixer? Has anyone (with MIO, Hammerfall DSP, etc.) come across problems like this? Best regards, +++++++++++++++++++++++++++++++++++++++++++++ KONDO Tatsuo (Kondo is my family name) website: http://www.netlaputa.ne.jp/~kndt

In the Sample Delay plugin, the resolution of the numerical fader is approx 12bit (4000 samples in single sample increments), yet in Track Automation, resolution is 7bit. Only fader event '0' is recognised. Even setting the start value in automation to a finer res and opening the automation event list does not show the missing parameter. It appears that the only way one can set sample delay to sample level resolution is by the numerical entry in the plugin or dragging the numerical value in the Track list. Unfortunately the value shown in Track Automation does not correspond (the finest res there is 32 samples). What this means is that it seems one can not, for instance, write into automation, a change in delay of one sample for a selcted passage. Or use an external fader to audition fine variations in sample delay. Is this only available to LogicControl ? Or not at all ? Anyone have any clues ? Dave Eager

> The only way I can get to send the volume message is to manually grab the > adaptavive mixer's drop down menu and select send all fader values. Yes I > know I can insert events into the track. Was kinda hoping that Logic Control > was going to do this for me. Can anyone shed any light? Yeah, I just went through this on the list a few days ago and then with one of the Emagic reps (who was pretty surprised...actually he was sure I was doing something wrong untill I asked him to plug in a module). I sure hope it gets fixed. It really isn't usable as is (in my opinion). Being on windows with a couple of these suckers could make you pretty nervous. Someone suggested setting up individual faders in the environment and making them arrange tracks. But with a lot of multi-instruments with patches loaded into them and lots of banks it seems awkward. Personaly, I think it should just be fixed right. I must say that I was pretty dissapointed when I ran into the problem. LC is supposed to make things *easier*. Let's keep our fingers crossed. Nathan

pobrien5769 wrote: > started a pre-production session today, and had the strangest > problem - some of the graphics (selecting a region in arrange/ > select cycle/bounce button on master fader - for example) in > Logic 5.2 were out of position. They were there on screen in > correct position, but for example - if I wanted to select a region in > the arrange window, I had to click just above the region to > actually select it - if I clicked on the actual region, it was like > clicking in free space. > It's possibly an extension conflict. You'll need to do the Extension Manager dance. I had worse graphics problems when I updated to 5.2, all the background graphics and buttons etc were gone. Only the basic frames of the windows etc were there [i.e the stuff which is fixed] After a full days wrangling, I traced it to an extension for a yamaha DS2416 card which I still had in my folder, even though the card is long gone. [the extension was called 'ymix2416'] The extension conflict was not apparent in 5.1.3 at all. [if it does turn out to be an extension conflict, it would be nice to hear which one it was so it could be added to the communal knowlege :) ] Dave Eager

--- Eli Krantzberg <elik@...> wrote: > I downloaded that free version of the FXpansion dr005 plugin someone > posted yesterday. Logic 5.2 hangs on startup when it is scanning the VST > plugins. It gets stuck when it gets to the dr005 and locks up. Any ideas > what could be causing this? I get the same thing, also downloaded demos of their other FX plugins, demos beep every 5 seconds loudly and annoying, when I come across companies like that where it's impossible to demo their stuff, I'm no longer interested in their stuff at all....seems like crap to me anyways! smaller companies like bitshift, REFX and PSP have better downloadable demos and I would rather support their stuff betasonic

> --- In logic-users@y..., Eli Krantzberg <elik@c...> wrote: >> I downloaded that free version of the FXpansion dr005 plugin someone >> posted yesterday. Logic 5.2 hangs on startup when it is scanning the VST >> plugins. It gets stuck when it gets to the dr005 and locks up. Any ideas >> what could be causing this? > happens to me too... /nassau -- Powerbook G3, 333Mhz, SCSI, 128MB Ram, JV-1080, E-Synth, Mackie 1402 VLZ, MidiSport 2x2, MacOS 8.6, LAP 4.7.2, Mac A/V, Crap mic for $20

tomcosmos wrote: > > Example : > Want to control Freq parameter on ES P from rotary knob on > Oxygen 8 midi controller keyboard. > ES P freq is CC no 71 > Have assigned this to knob 8 on Oxygen 8 but... > ES P doesn't respond over midi... > suggestions... Assuming you have updated to 5.2 this is covered in the 'readme'. If you haven't updated yet, save your energy till you do. Dave Eager

At 9:01 AM +0900 02.8.31, I wrote: >I'm using Metric Halo Mobile I/O. >With Logic's Software Monitoring off (=ASIO direct monitoring on), I can >monitor the input signal (of the record enabled track) with near zero (less >than 2ms) latency, thanks to its DSP powered mixer. > >The problem described below occurs with LAMP 5.2.0 and not with 5.1.3. Sorry! The same thing occurs with LAMP 5.1.3. Was I dreaming? Maybe I turned Software Monitoring on with low buffer setting, or simply mistook the input channel for the track... Anyway, the bug seems to exist in both versions (or MIO software). <excessive quotes trimmed by admin> +++++++++++++++++++++++++++++++++++++++++++++ KONDO Tatsuo (Kondo is my family name) website: http://www.netlaputa.ne.jp/~kndt

I said. > << Logic for OS X is that my Unitor 8 won't be supported... >> From: XOtherJesusx@... >> In the middle of a discission I came across this line above. >> Is this true? There is not going to be support for the Unitor 8 on MAC >> OSX? >> Why in the hell? "Lachlan Deck" <ldeck@...> wrote: > You obviously missed the debacle ;-) months ago... Hello Lachlam I do not know why you speak in favor of Emagic, on that point. You should be shouting with other users. WE WANT SERIAL MIDI INTERFACES IN MAC OS X WE WANT SERIAL PRINTERS IN MAC OS X You say there will be no serial devices on OSX, what about the internal Modem is it not serial ? Best Cyril <quotes repositioned by admin>

> Okay I have a question for you RME Hammerfall users.... I am planning on > buying a couple of RME 9652's along with a couple of Apogee AD16 and > DA16's.... I want to run them at 24 bit 192 sample rate for the highest > quality.. And I want a total of 64 inputs and 64 outputs... The highest available sample rate for the 9652's is 96k, you can't use 192k. > (1) Now with that being said my first question is using the ADAT ports on > the sound card at 192 sample rate, would it split the ADAT ports from 1-8 > inputs per adat port it would be 1-4 inputs per port??? Again, you can't use 192k.....using 96k with ADAT requires 2 ports (ie: 48k x 2 96k)...it's know as S/MUX. > Now if that is true.... My second question is.. > (2)Would that mean that I would need a PCI tower for extra PCI slots because > it would take two RME 9652 cards installed just for one AD16 to get the > entire 16 inputs and outputs... which would mean that I would need 8 RME > 9652 and 4 Apogee AD16 and DA16's... Dont worry I have the money..... > HAHAHH Half your luck! :-) > Which would bring me to my last question..(3) Can Logic 5.2 support all > those cards running in ASIO... I don't think Logic will have a problem, but having enough PCI bandwidth and getting the HDD's to keep up would be the main issue. I mean, even recording at 96k/24bit requires (approx.) 25meg per stereo track per minute of audio.....for 64 tracks that's roughly 1.6gig for 1 minute!! (And you can double that again for 192k!!!).......Good luck mate. :-) Personally, I would be hard pressed to hear the difference between 96k & 192k........you'd have to have an extremely accurate monitoring setup, as well as the right source recordings to discern the quality difference. I can hear an improvment going form 44.1k/16bit to 44.1k/24bit....but the jump to 96k/24bit is not as apparent to my ears.......and of course, it depends on the material you're trying to capture. Just 2 cents............Dave

On 7/5/02 3:47 PM, "Lachlan Deck" <ldeck@...> wrote: > Hi there, > > I said. > << Logic for OS X is that my Unitor 8 won't be supported... >> > >> From: XOtherJesusx@... >> In the middle of a discission I came across this line above. >> Is this true? There is not going to be support for the Unitor 8 on MAC >> OSX? >> Why in the hell? > > You obviously missed the debacle ;-) months ago... > Hello Lachlam I do not know why you speak in favor of Emagic, on that point. You should be shouting with other users. WE WANT SERIAL MIDI INTERFACES IN MAC OS X WE WANT SERIAL PRINTERS IN MAC OS X You say there will be no serial devices on OSX, what about the internal Modem ! is it not serial ? What I just read in the Core Audio manual (page 76): > Many MIDI drivers can simply be user-side I/O Kit clients (probably for > serial, > USB, Firewire). PCI card drivers will need their MIDI drivers to communicate > with a separate Kernel extension. Best Cyril

At 23:30 Uhr +0000 30.08.2002, docmidi657 wrote: >The only way I can get to send the volume message is to manually grab the >adaptavive mixer's drop down menu and select send all fader values. Yes I >know I can insert events into the track. Was kinda hoping that Logic Control >was going to do this for me. Can anyone shed any light? This is a small bug, but not a Logic Control bug. It will happen in the same way by modifying volume with the volume fader in the track title column. Will be fixed. -- Beste Gruesse - best regards, Michael Haydn - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Dipl.-Inform. Univ. Michael Haydn mhaydn@... SoundDiver Group Executive http://www.emagic.de/ Logic Developer (Logic Control integration) Emagic Soft- & Hardware GmbH - Germany Phone: +49 4101 495 0 Halstenbeker Weg 96, 25462 Rellingen Fax : +49 4101 495 199 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

--- In logic-users@y..., Michael Haydn <mhaydn@m...> wrote: > You might want to have a track with the Multi Instrument > (playing sequences on multiple channels) and other tracks > using sub-instruments (playing channelized sequences) in the > same song. Sure - but a single automation splitter cabled to the main multi could handle this - you'd just channelize your controller input as appropriate for each subchannel. The only issue would be whether the resulting track automation appeared on the main multi track, or on each subchannel track. An elegant solution would be for it to appear on a subchannel track if there is one corresponding to that channel of controller input, and on the main multi track if not. Sort of like the way a channel splitter's "sum" output outputs anything not cabled from a subchannel. Oh well, it's a stopgap solution, I appreciate that. A request - when the SoundDiver-style controller-assignments arrive in Logic, it would be very good to still be able to patch additional environment processing in there, both before and after the assignment is made - to add extra capability like soft takeover if it's not suported natively, trigger assignment changes from the environment, etc. John Pitcairn

Thoughts from the mind of projekt2501x, 30-08-2002: >You know, I still don't understand just how to set input and output >operations. I get that it needs to be wired to say audioinst1, i get >that it needs to have the second wire to the sequencer input. From >there i'm lost, being that when you double click the transformer you >can set only one set of conditions, and this text seems to ask for >two (input/output), with operations being a completely different >task. It doesn't even mention if you're supposed to map them out >yourself etc. Here's the relevant text from the 5.2 update readme file once more, pertaining to the exmple of how to control the ESP's cutoff with a modulation wheel (controller 1): "In the flip menu select "Track Automation Splitter" as the transformer mode. As the input condition set: | Status: Control | Cha: All | -1-: 1 |. As the output operation set the event type to: | Status: Fader | Cha: 2 | -1-: 7 |." The explanation: A transformer needs 3 pieces of information: 1. Conditions. These determine which events will be affected by the transformer. Events that match the Conditions will be operated upon, others won't. 2. Operations. These determine what will happen to the data matching the Conditions 3. The transformer's top flip-menu. This determines what will happen to non-matching signals: pass them through, ignore them, send them out the 2nd cable, etc. There are thus _not_ two sets of conditions. It's just Conditions that determine which data will be affected, and Operations that determine how that data will be afected. So in the case of this example, the Conditions should be set to "Status = Control", "-1- = 1", leaving the rest alone. This means that all controller-1 (modulation) data on all channels will be transformed and all other data will remain unaffected. The operations: since you want to affect the ESP's cutoff, which needs fader-7 events on channel 2, the operations are set to "Status = Fader", "Cha = 2", "-1- = 7". [Hint: connect a monitor object to a channel strip, and move one of the VSTi/VST's faders to determine which fader event on which channel you need for a particular parameter.] Finally, you want to transform cc1-events to fader data, and want other stuff to pass through unaltered. Therefore in the flip-menu you pick "Track Automation Splitter". Now the 1st outlet of the transformer will carry the transformed automation (CC1 -> Fader-7) data, and the following outlets will carry all other data (i.e. data not matching the Conditions). Connnect the Physical Input to the transformer, the transformer's 1st outlet to the VSTi channel strip, and the 2nd outlet to the "to Sequencer" object. Does this make the process any clearer? -- Hendrik Jan Veenstra <h@...> Omega Art: http://www.ision.nl/users/h/index.html

Hi there Cyril, On Saturday, August 31, 2002, at 01:44 PM, Cyril Blanc wrote: > I said. > >> << Logic for OS X is that my Unitor 8 won't be supported... >> > > From: XOtherJesusx@... > >>> In the middle of a discission I came across this line above. >>> Is this true? There is not going to be support for the Unitor 8 on >>> MAC >>> OSX? >>> Why in the hell? > > "Lachlan Deck" <ldeck@...> wrote: > >> You obviously missed the debacle ;-) months ago... > > Hello Lachlam Now there's a cool synthesis: Lachlan who uses LAM --> Lachlam. > I do not know why you speak in favor of Emagic, on that point. You > should be > shouting with other users. How long ago did I write this? The question Cyril, is if you're going to shout (which I tend not to - I prefer to talk/reason) is what, and to whom, do we shout ?! To reiterate: - I would absolutely love it if my Unitor 8 Mk I (no typo) would be compatible with Mac OS X. - I'm absolutely confident that if it _were_ possible that Michael/Markus and Co (aka Emagic Inc) would provide a Unitor 8 Mk I driver for Mac OS X. The facts are: - However, as Markus has already pointed out (after having Coffee with the dude who leads the development for CoreMIDI), serial devices are _not_ supported at all through CoreMIDI. That makes it an impossibility from Emagic's developmental point of view. Do you understand that? You seem to think that because I am simply putting forward the facts of the situation that I support the idea behind it. I was not happy at all when I first found out - but the simple fact of the matter is that until CoreMIDI provides support for serial devices, Emagic can do nothing about it (except maybe try to use its influence now that it is on the Apple team). You need to realise who's responsibility this situation falls with. You are wrongly imho placing it with Emagic (ironically you should be placing it with MotU seeing as you have a MotU interface). But it's not their fault either, yet. (i.e., unless CoreMIDI's support for serial devices becomes a reality). Again, they will not be able to supply the driver unless CoreMIDI provides serial support - but it's their responsibility to provide the driver for their hardware should that be possible. > WE WANT SERIAL MIDI INTERFACES IN MAC OS X I would love this to happen, yes. Will it? Hmm. My Unitor 8 Mk I is a great unit. There's no reason why it needs to be replaced. I can envision the same situation happening with USB midi interfaces. Something needs to happen so that good technology doesn't become obsolete simply because it fails at one point - the connection to the computer! Actually I'd love it if Emagic made their interfaces (the large ones) so that they could easily adapt to changing conditions. That way a simple change of adaptor and you're away. I don't need to buy a new AMT8 or Unitor8 just to be able to hook my existing Unitor up to the computer. Just a suggestion / Wishlist :-)) > WE WANT SERIAL PRINTERS IN MAC OS X This would be great too. But I'm not sure that Emagic are in the printing game... ;-) > You say there will be no serial devices on OSX, what about the internal > Modem is it not serial ? Again the facts: - Firstly, Apple provides the motherboard space for one reason only from their point of view - the internal modem. This is about the only thing that has serial support in OS X. My suggestion (if you can afford it) is to go ethernet for your next printer purchase. Why? it's much less likely that ethernet will become obsolete. Who knows how long it will be before USB is yesterdays technology... - Mac OS X's print system (The software) provides no support for serial devices. I hope that will change but it hasn't yet. There's no reason though why the open source community can't add serial support for things _but_ the issue is 3rd party drivers. I'm doubtful that Epson would provide the drivers if it were possible. (I'm going to try and hack a similar driver as the computer sees the printer via usb/parallel cable but just won't use it...). Anyway - here's a toast to old technology ;-) > Best > Cyril with regards, -- Lachlan Deck ldeck@...

Hi again, On Saturday, August 31, 2002, at 03:21 PM, Cyril Blanc wrote: > What I just read in the Core Audio manual (page 76): > >> Many MIDI drivers can simply be user-side I/O Kit clients (probably for >> serial, >> USB, Firewire). PCI card drivers will need their MIDI drivers to >> communicate >> with a separate Kernel extension. I'll have a look at this reference. If this is the case then I guess that could (I say could) mean that we have hope... At least hope is better than no hope in my book. > Best > Cyril with regards, -- Lachlan Deck ldeck@...

I'm sure I've done something stupid, and that this was working just yesterday, but... Why would recording track automation for midi instrument parameters other than pan/volume not be working? For any midi instrument, if I set the track to Latch, Touch or Write, and move controls in the track mixer, volume and pan record to track automation just fine. Anything else (modulation, say) doesn't record. I can pencil in some track automation for modulation, chorus, whatever, and it plays back as expected, but I cannot record it by moving the onscreen controls. This happens in my Autoload, it happens in a default song, it happens if I trash prefs. I'm pretty sure it was working yesterday, while I was testing track automation splitter transformers... Any ideas? John Pitcairn