mayer99

In Logic 10.5.1, when I drag a region into a folder, it disappears. I went back and checked the same function in Logic 10.4.8, and it works as expected in that version. This is a definite bug. Apple, please fix asap--many of us depend on folders as a main tool! Thanks, Steve

I just upgraded to Logic 10.4.1 and Sierra. I'm still having this problem. Rufuss, did you ever find fix? Anyone else got some ideas? I checked Audio/MIDI and all is fine there. Really frustrating!

I am having this problem too. Rufuss, did you ever find a solution? Thx, Steve

Hi All. I've got smart controls 1-8 successfully assigned to CC control numbers. I usually load the "Modern Black 8" template, and everything works as expected. When I switch to "Modern Black 12," I'm expecting to be able to assign 4 new CC numbers to the four additional unmapped knobs. Instead, when I assign a new CC number to knob 9, knob 1 gets changed to the same number. Knobs 10-12 have similar problems. I've fiddled and fooled around for a long time and I can't figure out a way to get control of smart controls 9-12. Has anyone else experienced this problem? Any fixes suggested? Thanks

Hi All. I just changed my hardware and discovered this problem, since in my new setup, Stereo Outputs are channels 33-34. I've lost my outputs 1 and 2! I'm using Logic 10.2.2. When I try to change the I/O labels, outputs 1 and 2 are greyed out. All attempts to route audio to outputs 1 and 2 have failed. Is there still no workaround? What a bummer.

I've tested this behavior on a number of systems now, using both Logic 9 and Logic X. What I've found is that as the number of threads is increased, so does the "Post-Roll." Also, the size of the Process Buffer Range has an effect. As you'd predict, the larger the PBR setting, the more "Post-Roll" you hear. I think that the effect was exaggerated for me since I moved to a new machine and Logic X at the same time. The combination of more available threads and a default setting of "medium" on the PBR in Logic X (my old Logic 9 PBR setting was "small") led to more "Post-Roll" than I was accustomed to on my old system.

Hi Arnaud. Apologies, I should have had that info in my signature, which I've updated and should appear below. It's a 12-core mid-2010 MacPro 5,1.

Here's the update: I went in to my Logic Pro X preferences and started changing various parameters around. On the "General" tab, I changed "Processing Threads" from "Auto" to "2," and...bingo!, my "Post-Roll" disappeared. I then tried changing the number of threads upward. Once I reached about 8, the "Post-Roll" began to creep back in. The more threads I activated, the longer Logic would continue to play after I hit stop. Does anyone have any ideas what's going on here? I'm worried that lowering the number of threads will negatively affect other areas of Logic's performance, but I'll just have to try it for now. Thanks, Steve

Thanks for weighing in, guys. I've checked my buffer settings and they are low as usual. I even tried lowering it to 64. Same problem. Erik, I know the buffer-emptying phenomenon, and this sounds different than that, particularly since Logic X continues to play midi as well as the buffer contents after I hit stop. I'm beginning to suspect that my Apogee setup has something to do with this. I'll report back.

Hi All. I've just started working with Logic Pro X and I notice that after I hit stop when playing a project, Logic Pro X keeps playing for about .25 seconds longer (about a quarter of a second), even triggering midi notes on all tracks after I've hit stop. I call this "Post-Roll." Whatever the appropriate term, I find it annoying, but I can get used to it if I have to. is this the expected behavior for Logic Pro X? The same files stop playing immediately when I hit stop in Logic 9 on the same machine. I've also created new files in Logic Pro X, thinking that the problem might stem from corrupt older files. Still, the "Post-Roll" persists. My hope is that there is some setting in preferences that I can change to stop this behavior. Thanks, Steve

Hi All. Many hardware synths have "+" and "-" buttons to incrementally scroll through patches. Some examples in my collection are the Oberheim Matrix 1000, Yamaha TX7, DSI Poly Evolver, Yamaha Motif. I could go on. Because I hate crouching over my racks while hunting through patches, I'd like to create an environment object with "+" and "-" buttons that allow me to trigger incremental patch changes in my external synths. Just to be clear, by "incremental," I mean adding or subtracting one from the currently selected patch location. This function would be similar to the "Next Setting" and "Previous Setting" key commands that we use for plug-in synths and fx, duplicating that function for external hardware synths. The best I've been able to do so far is creating a transform object that maps control change messages to patch changes. This is awkward to use. Any ideas?

Thanks a lot for your quick replies, guys. "Universal Track Mode" is a function I was never aware of. When I unchecked it in Logic 9, my old Logic 8 files open up properly. Looks like the source of my problem was NOT opening Logic 8 files in Logic 9, rather it was opening files that had been created without UTM in a new Logic environment that has UTM activated. Now I'm going to have to learn a more about UTM. It looks like a far preferable setup at first glance. Presumably I'll only bypass UTM to open my old sessions.

Maybe "Buss structure" is the wrong term, but the Busses definitely behave differently in Logic 9 for me. Here's a screenshot of the Busses in my Logic 8 Autoload: Logic 8 Busses 1-2 and 3-4 Here's a screenshot of the same Busses when I open the same file in Logic 9: Logic 9 Busses 1-2 and 3-4 In the Logic 8 file, I have a Stereo Waves Trueverb on Buss 1-2. Since Logic 9 seems to split stereo busses into two mono busses, the Stereo Trueverb doesn't load. In the Logic 8 file, I have a Stereo Logic Echo plugin on Buss 3-4. Logic 9 opens that as two Mono Echos with the same setting on each, panned hard left and right. The end result is that my reverb is gone when I open this Logic 8 file in Logic 9. David, can you suggest a workaround to deal with this? Or perhaps there's something in my preferences that I can adjust? Thanks much, Steve

Hi All. I've been using Logic Pro 8 for 6 years on a Quad G5. I just got a 2008 8-core Intel Mac running Snow Leapard, equipped with Logic 9. I'm finding that when I open my old Logic 8 sessions in Logic 9, the new Buss structure in Logic 9 is completely wiping out the effects plugin Busses and settings in my files. I have the same plugins installed, so there is no "slash" line through the plugin name on the Buss, it just shows up blank. Is there a known workaround to fix this? If not, I'm thinking of installing Logic 8 on this machine to run alongside Logic 9 so I can open old files. Any reason not to do this?

When using Torq Xponent in Rewire mode with Logic, Xponent's knobs and faders are sending out tons of unwanted MIDI info which is inadvertently wreaking havoc--changing volume faders on audio channels, muting tracks, etc. I've looked in every preference pane in both programs and can't find a sharp enough tool to filter out this info or turn it off. Torq is sending its MIDI info via USB on generic channels (1, 2 and 3). Logic's MIDI monitor and transform window do not see the info as specifically coming from Xponent, so I can't just filter all this info out. Any ideas?