Logic Pro 9 Track Protect Bug?

B

BeTek

New Member
Hi. I checked all of the track protect button to protect all the tracks from
accident and unchecked one of them to edit one track. But even though it is
unchecked "This track is protected" message appears. In order to edit the track,
I have to uncheck all of the track protect button. I was editing track
automation data. I'm on 10.6.2 and logic pro 9.1.
Is this a bug? Have you guys ever experienced this problem. Same thing happen to
my friend's logic (also 9.1 and 10.6.2).
 
Sort by date Sort by votes
ive had this happen alot, the way i got around it was, on a new track, drag all my audio from the "protected" track onto the new one, copy channel strip settings then delete the older track.
 
Upvote 0
Just ran across this tonight on my laptop. Moving things to a new track didn't help. Nor did removing preferences. Will have to start a new project and try importing tracks......:brkwl:
 
Upvote 0
It could be snow leopard, but I'm on 10.5.8 as well. I had to create a new project and imported everything. I solemnly swear I will never use track protect again until I find it is fixed.
 
Upvote 0
Doug Zangar said:
Thanks!
Click to expand...

I am still on 10.5.8, Logic pro9.1.5 and still get small glitches such as all Quantize parameters gone and Interpretation turned on-with Protect on, may be I should try freeze instead, and start using Logic for what it has been turned into-a nice way to mix audio snippets. After trying the Synful orchestra Demo,which erased all my Play Licenses, I see now that using JamPack 4 is actually better since both must be bounced to audio first and manipulated with track automation using the MOD and Pitch wheels to get what I want,no use in staying in MIDI for ease of editing.I can't afford the Celemony plugin. I am assuming I will be able to make small changes of tempo in the audio bounced regions-No?

New content-Now I am getting a "This track is protected" warning if I try to move the song begin from -0[I don't know how that got there] back to bar 1.
Was there another way to set that begin position by clicking in the transport?
Yes, change was possible via transport display, still a bug IMHO.
 
Upvote 0
I have tested and no such problem with Logic 9.1.5 (either in 32 or 64bit modes, on MIDI or audio tracks) run on a MacBookPro OS X 10.6.8, 2.93GHz, Intel Core2 Duo, 8GB RAM.
 
Upvote 0
You must log in or register to reply here.
Back
Top