Logic 9 not validating AU

[Toronto_Looper]

My logic 9 is being very finicky about the SL AU. It won't validate the plugin on start up. When I run the program anyway I have success using SL inside Logic the FIRST time. Any subsequent opening of Logic and attempt to use SL fails. Odd, yes?

[jesse]

Not odd at all, as it was noted and fixed a few weeks ago. I still need to make an official release of the next version that includes the fix, but here is the test version which is identical to what I will release (except intel only).

http://essej.net/sooperlooper/SooperLoo ... -aufix.dmg

[Toronto_Looper]

Ah! Sweetness! Thank-you for your hard work Jesse.

[Toronto_Looper]

errr... still having a validation problem with that one too.
*** - was able to get it to validate afterall

Perhaps I could ask a few other questions while I'm at it?
I'm trying to use SL instead of my electrix repeater - which is noisy, relatively lo-fi and I'd like to cut down on the amount of hardware I use as I travel a bunch. I use Logic to run sequenced material and as the Master for tempo. I'm getting fairly unpredictable results however from SL - as in:
1.Sometimes the record doesn't kick in until about an 8th note after I think it should... even with the quantize set to cycle and the cycle/8ths setting set to 8 - which I think should mean that the record and trigger functions should be quantized to the downbeat of every bar? It's worked like that for a bit, but for instance today when I load the same project it's different...

2. I can only sometimes get the loops to pause when I stop Logic, and to trigger again when I start it, however the loops are always way off sync when I start Logic.

3. Loop 1 is always 4 -5db louder than the other loops - I have to trim the input gain

4. In a setup with more than 2 loops, loops 1 & 2 seem to work OK, but any loops after that end up repeating late - almost an 8th note later than what I play...

5. In general - the behaviour is erratic and unpredictable - is there some known conflicts or setup tweaks I should know about?

I'd really love to use this software in a professional performance setting as I use the repeater and of course, I'd be happy to put my money into a hard working software developer rather than try to keep my hardware from a now defunct company running!

Thank-you.

[ghostly]

3. Loop 1 is always 4 -5db louder than the other loops - I have to trim the input gain

Try unticking the "Main In" box.

Not sure about your other queries, probably something to do with the way SL works synching with the host (i.e. logic). I generally always sync to Loop 1 and everything is super tight but I guess that may not work for you depending on what you are trying to achieve. Maybe post a screenshot of your SL set-up, I know ticking and unticking some of the quantize and sync boxes does things that I just don't understand!

[Toronto_Looper]

Thanks Ghostly - I'll try unchecking the Main In box and keep experimenting

[jesse]

Sorry for the slow response....

When you have SL set up in Logic, can you do a save session from the SL GUI's session menu and send me the .slsess file?

Re: #1 & 2: I hate it when the word "sometimes" is in a problem description I don't have logic but I will try to reproduce your setup from your session

3: good suggestion from ghostly, let me know. Also are your loops mono or stereo (eg, are there 1 or 2 panners per loop in the SL gui)?

4: can you describe in more detail exactly what you're doing here? synced record again?

[Toronto_Looper]

Thanks for the reply Jesse.
My loops are stereo - there are two panners.
I am using Logic to play preprogrammed beats, send a click to my drummer, and send midi clock and occasionally commands to my guitarists Repeater, and my Repeater, which I'd like to exchange for SooperLooper. I have a Logic Porject file containing all of my bands set of tunes, and we generally jump around - changing the set from night to night. To facilitate improvisation in this setup, I use markers and the cycle locators to loop sections of the tune until the band is ready to move onto the next section.

As I said previously, I'm finding SL to be quite unpredictable in this setup. I'm finding now that it doesn't respond to midi commands all the time (which I am sending from an FCB1010 routed to SL from MidiPatchbay) - I often have to press record twice or three times for it to engage. It seems to engage at the right moment (sync'd to every bar) if it's in a blank Logic project - as soon as I add my beats (wavs or aiffs) and tempo changes, it's all quite unpredictable when record will or will not engage. The tempo changes happen between songs - so not during playback. Additionally, SL will not stop until the second press of the stop button in Logic - however it begins fine.

I'd be curious to know if anybody else is using Logic and SL in this way. I realize that Ableton Live is surely a better choice for this style of performance, but alas I own Logic

My slsess file:
http://files.me.com/aaroncollier/tof0uu

[Toronto_Looper]

The more I experiment, I am finding that the majority of my problems occur when I have different tempos in one project. SL will play and react fairly well during the first song. If I even move the playhead to a different song/tempo while the project is stopped and SL has no loops loaded, SL begins to behave strangely. Any change in tempo of my project seems to make SL crazy. However, start/stop messages never quite work properly, but I have a feeling that's an issue on Logic's end.

[jesse]

That sounds like the probable issue. Do you have official timeline song start breaks in your session? Eg, does the musical timeline actually reset to 1:1:1 at your song breaks (and tempo changes?). Currently, when SL is an AU plugin it references what the current beat time is along with the current tempo to figure stuff out. There might be a few different ways to do it internally that would handle your scenario better though.