Craig

perhaps i wasn't clear - you only have to restart 7 times once, when the song is first opened, so that OS X can recognize all the memory you wish to use (the samples) and allocate for it.

once the memory is allocated (after the 7 starts), you can playback at will, just like with any other song. you can switch between instruments, logic instances, etc. and everything will playback as normal.

so it is more of a 'boot-up' process than a workflow issue. adds about 10-20 seconds when the song is first booted, then you work as usual.

it really is not a big deal at all - especially given the power it provides.

and keep in mind that 7 starts was required on about as large a single logic song as you can create - one with 3.4 GB of Virtual Memory used. smaller songs, as most would be, playback much faster. but again, even 7 starts is no big deal since you only have to do it once. takes much less time than even booting the machine.

hopefully this makes it clearer.

cheers

edit: i just re-read your post. when i said starts, i didn't mean restarts of the machine or of logic - i just meant hitting play in the transport. you hit play, the program plays then stops, so you hit play again and the cycle repeats.

essentially, after hitting play 7 times, you are done. sorry, in my excitement, i perhaps wasn't clear enough with language.

Cyril

to go over 2 GB limit, just buy a G5 and put 4+ GB in it.

there is no workaround necessary because logic automatically uses almost 3.5 GB of RAM (at least logic 6.3.3 on OS 10.3.2).

if you want to use more than 3.5 GB of RAM with Logic, then you have to use the advice in this thread.

but forget the 2 GB limit - it does not exist. 2 GB is a number with no meaning anymore with regards to Logic/EXS.

does that help?

and no worries on your english - it is a hell of a lot better than my french, german, spanish, russian, japanese, etc.

cheers

>playing on AI 1 in violas also plays AI 1 in the other 3 (only records if i want to, of course). this can easily be fixed, but i'm waiting to see what workflow feels comfortable.

Uncheck the record buttons of each active (ie, selected) track of all background songs.

Do i get this right, that this thinktank here has dropped the idea of one foreground song containing the actual notes which control all background songs that contain all loaded instruments only ?

How about asking John Pitcairn whether his LC-Emulator would help us get rid of even the physical LC as master transport control ?

Or while we're at it, has anyone checked the possibilities MMC and MTC as means to sync the whole mess without an LC ?

Christian


[URL=http://uk.geocities.com/christianobermaier/Gearlist.htm]gear list [/URL] studio pics show reel

Hi guys,

I am on a business trip to LA (conducting Holst PLANETS later this year). But I have been checking in.

Quickly, I HAVE NEVER GIVEN UP ON ANYTHING IN MY LIFE. You will slowly learn that about me. I will NOT throw in any towels. Although you could think of me as the captain that goes down with the ship, I am also someone who could figure out how to breathe under water to survive. I do not ever let any one thing get in my way. I WILL solve this thing.



Keep up the absolutely wonderful work all. I look forward to working with all this new information next week when I get back.

What the heck is LC Emulator? Does it remove latency issues? Hmm.

Evan Evans

Additional ideas:

1) Has anyone tried to reduce the head size minimum in EXS using the method I suggested (or any other)?

2) One way around the shared preference problem (and I don't know if this has been suggested already, but...) : Launch your different copies of Logic as different users.

In the terminal login to a different account:

login

enter the name and password then:

open -a /Applications/Logic\\ 6\\ Series/Logic\\ Platinum\\ 6.3.3.app

Interested to find out if anyone has success with this.

Carlos
---
My music:
http://music.altamar.dynalias.org/

evan

glad to hear you haven't quit, though somehow i'm not shocked at that either. it would obviously still be of great benefit if you can get all the routings to work seamlessly, without too much CPU sacrificed. the logic control (and i'm sure most other controllers) could then be used for global control of all songs, while writing from one, which would certainly make navigation easier, thus enhancing workflow. as always, i'll be happy to tell you it is impossible whenever your fire needs stoking.

by the way, where and when with Holst?

Christian

yes, logic's intelligence (which i love) is the difficulty here. because if i have 4 logics open and select AI 10 on the logic control, all four AI 10s get record enabled. i'd rather not have to go to the 3 songs i don't want to record in and disable their record setting on AI 10 just to write a line for one part without hearing/recording to the others. certainly, if i hit record in the transport of the specific song of the section i want to write the line for, i will only record to AI 10 of that song as it will be the only one which will play. but i will still hear the other 3 channels playing back (assuming, of course, the range of the instruments overlap)

at the moment, my thinking is as above - to just create songs in which the instruments will be 'limited' to one specific midi channel. then this problem will only come up every 17th loaded song. if you have any ideas or suggestions of other things to consider, i'd appreciate it.

actually, one thing which occurs to me now is that the easiest thing might just be to switch to the song i want to write for (say violins), disable record on the Logic Control for AI 10 (which will hopefully disable record on all AI 10 in all songs, including violins) then just record enable the one in violins by selecting record via the mouse on AI 10 in that song. will look into this further when i get back to office.

evan (or anyone)

what about the potential to use something like Cuemix by motu or MIOConsole by metric halo (assuming, of course, a user has one of their interfaces) to route the audio between logics?

is it possible to somehow feed an output to an input within one of those via busses or auxes?

i really doubt it and it would hardly provide enough channels, but thought i'd mention it just in case. in the end, you never know what ideas it might trigger.

i mean, it is kind of the same idea as wormhole/Jack but running off non-apple CPU.

christian - thanks for making me smile with that last post.

i just wanted to add another possible benefit of this 'workaround' (it is getting more groundbreaking all the time) - it might solve this:



because now you *might* finally be able to use logic live as a killer VSTi host.

just load up mulitple songs and layer the parts you want via the same channel in each song (so, if you want to play ES-2 with Atmosphere and Reaktor, just load ES-2 into AI #1 of song 1, Atmosphere into AI #1 of song 2, and Reaktor into AI #1 of song 3). you can then play them together from one master keyboard and, possibly (probably, i think), with no latency.

the reason i say possibly is that i think it works without latency, but i'm not at the office to test. when i was playing multiple AIs in different songs at once yesterday (and trying as i mentioned above to *not* play them at the same time) - i didn't hear any latency like i used to with the I/O plug in trick. even without playback engaged, it seems to me that all selected AI channels would play at the same time. at least that is how i remember it. i will test it when i get back to the studio.

so for live performance, just create many 'multi instruments' across several songs and use something like the logic control to switch between AI channels (thus switching between multi-instruments) in real time. you can have your above ES-2, atmosphere, reaktor on the 3 AI #1s and then reaktor, stylus, EXS-24 on the AI #2s and vanguard, FM-7, EXS-24 on AI#3s, etc.

and you could assign each song different midi channels (all AIs in song 1 respond to midi channel 1, all AIs in song 2 respond to midi channel 2, etc.) so you could use your master controller to control them all by sending midi out to all channels, but individually by sending out only specific channels.

of course, the potential also exists then to use multiple live inputs on the same audio channel in different songs - so a guitar could be routed 'live' to input one of audio channel one in song one. a bass to audio channel 1 of song 2, drums to audio channel 1 of song 3, etc. and all would have access to separate effects which are tempo synced.

again, i haven't tested for this 'live' potential and i'm only free thinking this, but the potential is there to finally use logic (multiple logics, actually) for true live perfomance.

of course, this will require much RAM and CPU. now where are those G5 powerbooks?

all in all, very exciting, i think.

cheers

christian

that's great news. i assume the end user would merely need to set-up the LC emulator once in an autoload, then use that song to build all instruments template songs and then they'd be set to go?

cool.

wow, that's even cooler than i thought. much easier for users without logic controls.

regarding the ability to separate controls out for each instance - i can't imagine at the moment if that would be a good or a bad thing. it is certainly a good thing to have the option to do. will it prove useful? i just don't know.

perhaps this would be an easier way to - i don't know. but cool that the potential exists. given some time, we might find it a very useful ability indeed.

cheers