billy

i have run into this bug numerous times where after copying and pasting a selection of audio in the sample editor i receive a strange error message and the audio file becomes corrupted. usually the pasted audio is fragmented and there will be an additional bit of random digital noise at the end of the audio file. sometimes i am able to undo and work around the problem... other times my audio is lost. consequently i now backup audio files before doing wave edits... this is extremely frustrating. this never happened in logic 5, 6 or 7. i have experienced the same bug both tiger and leopard and on a G5 as well as a Macpro using two different sound cards. so it seems to be unrelated to system configuration or hardware. has anyone else run into this? is it a known bug

no.. this is in the sample editor. i'm editing audio waves not regions or midi.

recently i upgraded to logic studio and noticed some different behavior doing audio edits. usually when i cut a selection of the wave it will close the gap by pulling the audio AFTER the edit backwards. but a couple times it did the opposite.. it pulled the audio BEFORE my edit up, thus changing the anchor point for the preceding portion of the region. then when i used UNDO it pushed the audio AFTER the edit forward again. this caused the region anchor point to be wrong. later when i did more edits and logic behaved normally. is this perhaps some new "feature" that changes depending on some variable which i am not aware of? or perhaps a strange bug? also, is there a way to get rid of the annoying warning asking me if i really want to delete a selection of the audio... sometimes i do MANY MANY edits and i hate clicking "ok" over and over again.

problem has always been there since i purchased logic 7. never happened in logic 4 on my old g3.

i'm still used to the old logic way of finding tempo.. which works pretty well. create an audio region which you want to base the tempo on. set the loop to be the same number of bars/beats as the region. select "options > tempo > adjust tempo using region length and locators" pretty easy.. and quite useful when you have an audio recording which varies in tempo.

thanks for the suggestion but my mousepad is fine. dull gray with no pattern. mouse behaves perfectly. david: the matrix snap is set to smart... that was one of the first things i tried changing and it didn't help. the weird thing is this problem is not easily reproducible. in some of my songs the drag and drop works fine.. in others the notes jump around unexpectedly. i guess it's no big deal.. pretty easy to work around. confusing all the same though

yep. this same thing has happened since logic 7.0.. then 7.1 then 7.1.1. now 7.2 starting at os 10.4.1 all the way up to 10.4.5 i always figured it was something to do with my configuration or just some minor bug. but if it were a bug then i assume others would be commenting about it so what the heck?

no.. i don't think you understood. the notes actually move forward a bar or so. not up or down. and i do want them to move forward. maybe a beat or two beats. but when i drop them there they suddenly disappear from where my mouse left them and reappear somewhere else down the line. if i drag them vertically it seems to happen less often.. then i can easily place them where i want once copies have been made. this is something which only seems to happen when using the option-drag function to copy notes. does anyone have any idea what i'm talking about? this seems like something simple which someone would have an easy solution for... it doesn't make any sense to me though.

sometimes i grab a bunch of notes and option-drag them to a new location so as to make a copy. often the copied notes jump up a bar or two from the place i drop them... this is really confusing. so i have to then grab them again and re-drop them in the original place i wanted them. help?

i've disabled spotlight and dashboard and hidden dock in background (transparent dock. this really helps. easyfind is a good app to use as an alternative to spotlight. dashboard is stupid an useless (my opinion disclaimer here), and the dock is essential because apple-TAB switching is tied to it... but i hate to have it popping up over windows (hence transparent dock) To turn Dashboard off: defaults write com.apple.dashboard mcx-disabled -boolean YES To turn Dashboard on: defaults write com.apple.dashboard mcx-disabled -boolean NO You have to restart the Dock after making either change for it to take effect: killall Dock to disable spotlight first modify /etc/hostconfig to read: SPOTLIGHT=-NO- Then to get rid of the existing index, run these two commands from Terminal: mdutil -i off / mdutil -E / The first command disables indexing on the boot volume, and the second erases the existing template. You can then use Activity Monitor to kill any mds or mdimport processes or else just reboot. Futzing with permissions will probably break OS updates that try to update files in the zeroed-out directories and of course won't survive a repair-permissions run. If you later change your mind and decide you want Spotlight after all, it's easy to reactivate. Set SPOTLIGHT=-YES- in /etc/hostconfig, run in Terminal: mdutil -i on / and reboot. good luck

i've disabled spotlight and dashboard and hidden dock in background (transparent dock. this really helps. easyfind is a good app to use as an alternative to spotlight. dashboard is stupid an useless (my opinion disclaimer here), and the dock is essential because apple-TAB switching is tied to it... but i hate to have it popping up over windows (hence transparent dock) To turn Dashboard off: defaults write com.apple.dashboard mcx-disabled -boolean YES To turn Dashboard on: defaults write com.apple.dashboard mcx-disabled -boolean NO You have to restart the Dock after making either change for it to take effect: killall Dock to disable spotlight first modify /etc/hostconfig to read: SPOTLIGHT=-NO- Then to get rid of the existing index, run these two commands from Terminal: mdutil -i off / mdutil -E / The first command disables indexing on the boot volume, and the second erases the existing template. You can then use Activity Monitor to kill any mds or mdimport processes or else just reboot. Futzing with permissions will probably break OS updates that try to update files in the zeroed-out directories and of course won't survive a repair-permissions run. If you later change your mind and decide you want Spotlight after all, it's easy to reactivate. Set SPOTLIGHT=-YES- in /etc/hostconfig, run in Terminal: mdutil -i on / and reboot. good luck

can someone explain why when i route channel outputs to aux's the volume is signifcantly less with the aux level set to 0db? it doesn't seem to be so when routing to a bus output... only with aux's.

interesting. i can't say for sure, but i think you all just might be trippin. then again.. who knows.

i've wondered the same thing! anyone?

word to big bird