|
From: <mid...@co...> - 2007-08-18 14:28:43
|
Yeah, I figured that one out. I had it set to loop thinking it would work like an EDP. A small, and in hindsight, a completely meaningless difference. Per, do you think Bidule is less CPU intensive then Live 6? Thanks MFC -------------- Original message -------------- From: Per Boysen <pe...@bo...> > > On 8/15/07, mid...@co... > > wrote: > >> Ive attached a screen shot of SL in Live 6.07. I can't seem to > >> figure a way for SL to work properly. All I want to do is Sync SL > >> to Live. All that happens is, it says its "waiting for sync". Then > >> it wont start. I think everything is set correctly. Sync is on. > >> Sync source is set to Jack/Host, the host being Live. Any thoughts? > >> Thanks, > >> MFC > > > On 17 aug 2007, at 22.21, Jesse Chappell wrote: > > I don't have access to the software right now, but IIRC you need to > > have the transport running in Live (which it looks like you do, > > actually). You could try setting the quantize to Cycle in SL instead > > of Loop, but that's just a guess. > > > I have access to the software right now and tried it out. Jesse's > guess was right on; you cant start record a loop in sync mode with > the setting "quantize = loop". It's logical - how will SooperLooper > know the length of your loop BEFORE you have recorded it? ;-) When > I changed the quantize setting to "8th" SL worked fine here in Live > 6.07. > > Greetings from Sweden > > Per Boysen > www.boysen.se (Swedish) > www.looproom.com (international) > http://www.myspace.com/looproom > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > sooperlooper-users mailing list > soo...@li... > https://lists.sourceforge.net/lists/listinfo/sooperlooper-users |