Apple Logic Pro /LogicExpress Discussion group photo

Yahoo Groups archive

Apple Logic Pro /LogicExpress Discussion

Index last updated: 2026-04-28 23:06 UTC

Thread

solo cycle bug

solo cycle bug

2007-11-05 by GAmoore@aol.com

If you are in cycle mode it works fine, but if you access the solo tool 
and click on something, the playing no longer cycles - it will happily 
keep moving past the cycle boundaries as if they are not there.
________________________________________________________________________
Email and AIM finally together. You've gotta check out free AOL Mail! - 
http://mail.aol.com

Re: solo cycle bug

2007-11-06 by Gil Gillian

--- In Logic_Cafe@yahoogroups.com, GAmoore@... wrote:
>
> If you are in cycle mode it works fine, but if you access the solo tool 
> and click on something, the playing no longer cycles - it will happily 
> keep moving past the cycle boundaries as if they are not there.
> ________________________________________________________________________
OSX 10.4, Logic 8. Are you Leoppard? On mine it works OK if you solo
within cycle mode timeline, and also OK if you solo earlier than than
the timeline, and it jumps to the selected point if you solo after the
cycle point. This is sort of what I would to happen, but have no idea
if that is what the manual says should happen. - Just about to up to
Leopard.
Keep on keeping on
Gil
www.DesignNotes.co.uk

Re: [Logic_Cafe] Re: solo cycle bug

2007-11-06 by GAmoore@aol.com

No, I am using 10.4.10. There are several different solo methods in Logic - 
track solo, global solo mode, etc. I am referring to using the solo tool (among 
the pencil tool, marquee, hand tool, etc.) When I select an item with that 
tool, Logic overshoots the cycle limit. Its not an earth shaking item, but just 
a little bug.

> > If you are in cycle mode it works fine, but if you access the solo tool
> > and click on something, the playing no longer cycles - it will happily
> > keep moving past the cycle boundaries as if they are not there.
> > ____________ ________ ________ ________ ________ ________
> OSX 10.4, Logic 8. Are you Leoppard? On mine it works OK if you solo
> within cycle mode timeline, and also OK if you solo earlier than than
> the timeline, and it jumps to the selected point if you solo after the
> cycle point. This is sort of what I would to happen, but have no idea
> if that is what the manual says should happen. - Just about to up to
> Leopard.
> 




**************************************
 See what's new at http://www.aol.com


[Non-text portions of this message have been removed]

Re: solo cycle bug

2007-11-06 by Gil Gillian

Yes, so was I. How strange, I wonder what we doing differently. I was
soloing audio. Is anyone else finding this?
Regards,
Gil

--- In Logic_Cafe@yahoogroups.com, GAmoore@... wrote:
>
> No, I am using 10.4.10. There are several different solo methods in
Logic - 
> track solo, global solo mode, etc. I am referring to using the solo
tool (among 
> the pencil tool, marquee, hand tool, etc.) When I select an item
with that 
> tool, Logic overshoots the cycle limit. Its not an earth shaking
item, but just 
> a little bug.
> 
> > > If you are in cycle mode it works fine, but if you access the
solo tool
> > > and click on something, the playing no longer cycles - it will
happily
Show quoted textHide quoted text
> > > keep moving past the cycle boundaries as if they are not there.
> > > ____________ ________ ________ ________ ________ ________
> > OSX 10.4, Logic 8. Are you Leoppard? On mine it works OK if you solo
> > within cycle mode timeline, and also OK if you solo earlier than than
> > the timeline, and it jumps to the selected point if you solo after the
> > cycle point. This is sort of what I would to happen, but have no idea
> > if that is what the manual says should happen. - Just about to up to
> > Leopard.
> > 
> 
> 
> 
> 
> **************************************
>  See what's new at http://www.aol.com
> 
> 
> [Non-text portions of this message have been removed]
>

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.