Every 15 minutes with logic is another set of bugs. 50. arrange page scissor tool - won't work no matter how many times I select it, after selection returns to arrow tool 51. when I use key commands for move SPL +/- bar, part, beat ... it now repeats those like in an infinite loop instead of simply moving that far. Combined with the scissor problem the only way I could chop a loop was to make a small cycle, use the keycommands for move cycle forward, and cut region along cycle lines. Very annoying. 52. audio window - audition. if you play something, then there doesn't seem to be a way to not add the last thing played. even if you hit done. 53. solo on channel strip - doesn't free up resources. I am getting delayed reactions when soloing a single audio track without plugs. 54. In automation - won't snap to bar - and using control doens't help since that puts it into a different mode for automation. Hard to automate to the beat. 55. Oh yeah, the scissor tool just happens now unexpectedly - although it doens't show as the scissor. totally bug city. 56. zoomed in on arrange - can't move the SPL smoothly - have to use the control key to make a smooth movement. 57. the jumping window in cycle mode - i remember people complaining about that 4 years ago - guess its way down the "to fix" list. 58. Bounce To ... location is not remembered and must be navigated to each time.

On Dec 3, 2004, at 17:46, GAmoore@... wrote: > 51. when I use key commands for move SPL +/- bar, part, beat ... it now > repeats those like in an infinite loop instead of simply moving that > far... That's interesting. It might happen with other key commands too. I try to setup a foot controller for recording and need to delete tracks (with the command "Clear"). It often happens that I run into a loop and all tracks below the active one get sequentially deleted. The loop doesn't stop and I have to kill Logic. I blamed my setup or MIDI cabling but now I think that could be a similar or the same bug... > 53. solo on channel strip - doesn't free up resources. I am getting > delayed > reactions when soloing a single audio track without plugs. I believe this is normal. So far I have learned soloing does not switch off other channels. To free resources you have to mute the channel strip itself. > 57. the jumping window in cycle mode - i remember people complaining > about > that 4 years ago - guess its way down the "to fix" list. Hm. Sometimes I want it to jump and sometimes not. I think you can disable the automatic step-in of the "blue running man" in the preferences. If not, disable it after starting or scroll a bit horizontally- that disables it too. Peter Ostry

> > 57. the jumping window in cycle mode - i remember people complaining > > about that 4 years ago - guess its way down the "to fix" list. On Fri, Dec 03, 2004 at 06:36:08PM +0100, Peter Ostry wrote: > Hm. Sometimes I want it to jump and sometimes not. I think you can > disable the automatic step-in of the "blue running man" in the > preferences. If not, disable it after starting or scroll a bit > horizontally- that disables it too. I run into a problem quite often where if my cycle region is completely visible on the screen but i've used the zoom command on a region(s) to get to that point, and the screen will "jump" back and forth every time it gets to the end of the cycle. It shouldn't jump because the whole cycle is visible on my monitor, regardless of whether or not catch is on. Maybe that's what he means... -- Ben Harrison

> > 53. solo on channel strip - doesn't free up resources. I am getting > > delayed > > reactions when soloing a single audio track without plugs. > > I believe this is normal. So far I have learned soloing does not switch > off other channels. To free resources you have to mute the channel > strip itself. Soloing should be the same as muting the rest, but as for freeing up resources: Muting a _channel_ doesn't reduce disk load since the data is still being read in (it does save some CPU load), but muting a _track_ does. Isn't this what we're seeing here? Maurits.

On Dec 3, 2004, at 20:34, Ben Harrison wrote: >>> 57. the jumping window in cycle mode - i remember people complaining >>> about that 4 years ago - guess its way down the "to fix" list. > > On Fri, Dec 03, 2004 at 06:36:08PM +0100, Peter Ostry wrote: >> Hm. Sometimes I want it to jump and sometimes not. I think you can >> disable the automatic step-in of the "blue running man" in the >> preferences. If not, disable it after starting or scroll a bit >> horizontally- that disables it too. > > I run into a problem quite often where if my cycle region is > completely visible on the screen but i've used the zoom command on a > region(s) to get to that point, and the screen will "jump" back and > forth > every time it gets to the end of the cycle. It shouldn't jump because > the whole cycle is visible on my monitor, regardless of whether or not > catch is on. > > Maybe that's what he means... Strange. Nothing jumps when I switch catch off - while Logic runs or in the preferences. Even when I zoom quite far in and out in the arrange window. Are we talking about different zooms? Peter Ostry

> 53. solo on channel strip - doesn't free up resources. I am getting > delayed > reactions when soloing a single audio track without plugs. I believe this has always been this way. I might be mistaken, but IIRC in order to free resources you have to mute the track in the arrange window, not the channel in the mixer. Brian :::::::::::::::::::::::::::::::::::: Logic Audio Pro 7.0.0 PowerMac G4 933MHz OS X 10.3.6 1 GB RAM MOTU 828mkII - driver v1.09 - CueMix v1.4