MichaelJM

Thank you Atlas007 - It's good to hear I'm not the only one. Though it's unfortunate that everyone has to deal these. I just sent 2 messages to Apple support. Via: https://www.apple.com/feedback/logic-pro.html (The text box didn't allow for much text so I had to send 2...) I hope they're listening. I know I've encountered others too; I'll be keeping track of them from now on.

I've been using Logic X for about a year now, and I've come across a lot of bugs that bother me on a routine basis. I would love to know if anyone else is encountering these, and if perhaps there's a more efficient way to work to avoid these. These are bugs that I just can't believe still exist, because they drive me crazy. I recorded myself working for about 5 minutes, and caught some of the ones I encounter frequently: https://www.youtube.com/watch?v= Bug #1 - Event List notes don't highlight when they are selected in the Piano Roll. How is this possibly a bug? I use the Event List constantly, and it makes it incredibly difficult to use if I can't see what the notes I have selected are. It takes multiple attempts at selecting the note to see it highlighted in the Event List. Bug #2 - Clicking in the Controller Draw pane changes the view in the Piano Roll. I've encountered this a few times, but when clicking outside the yellow line, just within the CC Draw pane (not sure of the official title), the piano roll view moves in the general direction of where you clicked. It's almost as if Logic thinks I want the view to center around the area I just clicked. Not sure why this happens, or how to avoid it. Bug #3 - It's impossible to draw extreme CC values on first try in Controller pane. When the sustain pedal view is up, it is impossible to click and drag a point down to 0 on the first try. The only sustain pedals that matter are 0 & 127 so this is just crazy. (I know it can still work without it being all the way to 0, but I like neatness in my projects) Additionally, it's impossible to click and drag a point in the Modulation pane to 127. You can change it to 127 in the Event List, but not in the Piano Roll panel. Admittedly a minor, inconsequential bug, but totally baffling all the same. Finally. the bug that rivals all bugs for me is one I didn't include in the video. The last note in a MIDI Region - when selected in the Piano Roll, absolutely does not appear in the Event List. The note is below the scrollable area, hidden. I've resorted to adding a few notes after the last note so it appears in the Event List. Absolutely infuriating bug. None of these bugs existed in Logic 8, and I noticed these almost immediately in Logic X. It can't be just me can it? I will be contacting Apple about these because I do desperately want them to be fixed. It's just hard for me to understand why they even exist in the first place.

Thanks. I did see all those threads. Those issues seem to be unrelated, but I'll re-read more carefully. Spotlight might be the culprit though. Since it's searching the harddrive. I'll try re-indexing, and I pray to God that works. Otherwise, I'll just have to deal with it. It might indeed be Snow Leopard. I'd be happy to revert to Leopard.. if only I decided not to skip it! I'll report back if this solves the problem.

This is a problem that's been annoying me for months; it's finally become unbearable. (using Logic 8.0.2) When I load a factory installed Channel Strip setting (an EXS24 instrument for example), as a new instrument, 99% of the time, the application will hold up, the beach ball will spin, and it continues like this for maybe 3 min, until it finally loads the instrument. If I'm trying to demo different instruments, I really don't want to have to wait 3 min for each one to load. What I think it's doing, as it's "working", is it's searching my entire harddrive for the samples. I can hear my harddrive working, and it's the same sound it makes when I use Spotlight, for example. Why does it have to search for the samples, when all the samples are in the default folders? No idea. Has anyone else experienced this problem? I looked, and looked, but couldn't find any similar posts. I moved the channel strip settings to my user folder, and that didn't work. So I think it's a problem with the .cst file itself... maybe? For some reason it doesn't know where the samples are, or can't find them? I did not have this problem after initially installing Logic, but it started happening at some point. I have Logic 8.0.2 , on a MacBook Pro, running Snow Leopard. Any help would be greatly appreciated. Thanks.

I'm using Logic 8 on Snow Leopard. I recently had problems with my 3 yr old MacBook Pro, and Apple gave me a new one. As a result, I moved my files over to the new computer, and reinstalled Logic 8. I am currently finding that I cannot open certain Logic projects anymore. This is terrifying me, as I would be losing a lot of good work, if I cannot find the solution. I'm learning the hard way, that I should always save the MIDI data for every project I work on. The projects that I can't open, don't seem to be random. The trend appears to be that I can't open Logic projects with which I had used Plogue Bidule (0.9690UB; this is not the newest version). I can open projects with which I had used the newest version of Bidule. Basically, the projects that aren't opening, seem to be from last September and earlier, before I'd started using the newest version of Bidule. The projects that aren't working, don't contain any VST plug-in's; they're just MIDI tracks, pointing to Bidule. Now my suspicion that this is somehow related to Bidule, could be wrong. What happens when I open one of these problem projects, is that Logic seems to open as normal (the logo box appears, it does stuff, and then it disappears). The computer makes a lot of noise, so it sounds like it's doing something, but as time passes, nothing happens; the project itself never opens. Has anyone encountered this problem before? Does anyone know how I might recover any of the data in these projects? Thanks very much, Michael EDIT: Ok, I feel like an idiot now. I did a search of this forum with google, and found a post suggesting to another user to hold down the control key, to disable Core Audio. I tried this, and it solved the problem (well, temporarily). At least I can now move the midi data to another project. Sorry to clutter the forum; someone can delete this if they wish. I'd suggest to anyone to backup the MIDI data for all their projects; probably second nature to most, but it wasn't for me.