jculp3

I don't have a great solution at this time other than File/Project Management/Clean Up. This works once in awhile, but not all the time. I'm not sure why this is.

I have the issues as you've all described while using heavy latency plugins, pitch shifters, UAD, upsampling plugins etc. So, when I switch plugin latency in general prefs to "Audio and software instrument tracks" (instead of All), it fixes the sidechain issue, but off course then busses are off. Why would they include both these as options when niether solve the issues? I've submitted my bug report to apple again and now waiting patiently, but also weighing options with other DAW's. Good to see others are getting fed up with this as well. Hopefully they'll fix this soon.

It still saves them when I do this. Looking into a few other things, I've had some luck with File/Project Management/Clean Up. Although this didn't work all the time.

I turned off all check boxes in the assets section of project settings, and it didn't make a difference

I love quick sampler. But, when I am in the process of auditioning drum samples in a quick sampler instrument by dragging them into it from the browser, Logic creates a copy of that sample to the quick sampler folder in my project as soon as I save my Logic project. The problem is, after auditioning 25 or more snare drums for instance, the quick sampler folder fills up with all the drum samples that I've auditioned. Wish there was a way to purge the quick sampler folder of these unused files. You have the ability to "clear history" in the quick sampler plugin of all the samples that you've loaded into it, but this does not remove the physical files from the quick sampler folder. Am I missing something here? This is the reason I'm returning to Battery 4 for drum sounds because it's easy to exchange sounds and audition them. Ableton's hot sawp feature is a dream for this as well.

This definitely needs fixed. Thanks for the visual demo.

Yeah, 250 sends is a lot and gives one many options for creating areas of types of auxes you might need as you were saying fuzz. I do think the DAW of the future (like Ableton, Bitwig, Fruity L., etc. are trying to do) is going to be totally modular, but also easy to see where stuff is going and what automation is happening on groups of tracks in a mixer-like setup. Best of both worlds.

Thanks David and fuzzfilth for chiming in. I used to create a template with busses and aux channel strips already in the mixer (hidden until I needed them). But I found this restrictive when I needed more or less of those - reverbs, delays, fx, etc... depending on the individual needs of the project. Some projects would need a ton of reverb and delay sends (like this one), and others not really at all. Then I cleaned up my template, put in a few aux tracks I use every project, and now I just add aux and busses as I go in numerical order. Seems to work better for me. Looks like crap in the environment mixer, but I don't look at that too often anyway. I like what you're saying though about using excel spreadsheets so I can keep track of what tracks are being sent to the bus.

Thanks fusbar. Problem is, I still can't see all the tracks that are being SENT to the bus. Only a few are listed until space runs out on Logic's drop down bus list, and then you get an ellipsis ...

On a few bigger Logic Project I'm working on, I'm having trouble keeping track of what tracks are routed to busses. This is because when the list of these tracks grows, Logic will only list so many tracks until space in the dropdowns run out, and then Logic resorts to using an elipse ... Any suggestions? Take a look at my pics and you'll see what I mean.

Smart Control external assignments in track stacks still not working in 10.4. I put in a bug report to Apple. Even if it still worked, not sure that I would use the workaround in the Controller Asssingment settings of choosing "software instrument" and it's #, instead of "selected track". I WANT to use "selected track". That's the way I have my template setup, with my 8 external control knobs mapped to 1-8 in smart controls for any and every track.

Thanks for the help everyone. I'll be submitting a feature request at the Logic Pro Feedback site today.

I did what you said and it still calls CC#12 "Ch.1 Effect#1 MSB". I only want Logic to display it as "CC#12" and not "Effect #1 MSB." What am I missing here?

In your first pic oddball, it is showing the automation as "Ch. 1 Modulation". In the past, this would be shown as "CC#1". Now, we all know that "modulation" is CC#1, but when you get into the higher numbers it becomes less apparent what CC# you are dealing with, which makes it more difficult to know which parameter you are trying to adjust. For instance, Logic now calls CC#12 "Ch.1 Effect#1 MSB". This description seems useless to me. I'm wondering if there is a way to change this back to showing just the CC#.

Thanks David! Another thing with this new way to view midi automation... I found that Logic is not displaying anymore (in the track header, nor the region) the midi CC#. In previous Logic versions, Logic would show the CC# in the region and this is what I would go by. Now for instance, Logic calls CC#12 - "Ch.1 Effect#1 MSB". Seems useless to me. Is there a way to change this back to showing just CC#? thank you!