zestyOrange

Very glad it helped. Yes, the struggle with this one was real - haha.

I was going to say yes, but after playing around with DMD a bit more I don't think it's worth it! I was previewing sounds and it kept replacing either my entire kit or the pads. So I then made sure to select a specific pad, previewed another sound and it filled that pad then moved on to the next, overwriting it. It seems to easy to lose sounds it's crazy.

Yes, I seem to get the same results as you. Interesting that the filter isn't always activated.

Apologies. I was instantiating a new instance of DMD either using the New Instrument dropdown (DMD is finally listed there now, in Logic 10.8 - in previous versions I don't believe it was), or by dragging a sample from an external folder and hovering over the area below existing tracks, then chosing it from the pop-up. In both cases I was then dragging samples onto the DMD slots which automatically creates a track, inside of the DMD stack, with QuickSampler on it, but this instance always has a filter engaged and a -8dB volume dip.

My solution so far is to create an empty DMD & drag Q-Sampler instances into the slots manually, then save it. Not ideal, so I won't mark this resolved yet in case there's a better way.

Hello all. I thought I'd get around to using Drum Machine Designer, rather than continue doing things the old school way, but it does some ghastly things to samples out of the box (I figure the programmer responsible for 'Record MIDI to Tack Here' must have had a hand in it!). Anyway, it loads instances of Q-Sampler, so I tried loading up Q-Sampler, modifying the defaults and saving them as the new default, and then creating a new instance of DMD and hoping it applied it to those instances too, but noooo. DMD just says 'f*%@ you, I'm going to continue filtering every sample you load in and adjusting its volume, because I know what you want better than you do'. Is there a workaround? Or do you guys not bother with it.

It's just a terrible name choice isn't it. Let's hope whoever came up with that particular gem doesn't have kids ... - "Hi, this is my son, Egg-Fertilised-By-Sperm Smith".

Agreed - much better solutions. For what it's worth I 'reported' the auto-volume-changing as a feature request (but unfortunately I didn't think of this as a viable alternative. I simply said 'hands off my sliders!' ;) )

Not sure how much use this'll be, but I'm not experiencing it on 10.7.9 (I say 'may not be much help' because although it was an issue I encountered, I've also done a clean build onto a new computer, and so I've changed multiple variables). If anyone wants to try upgrading to 10.7.9, goto your existing Logic app (in Applications) first, right-click it and compress it, so that you can revert to it if you run into bigger issues with the latest version.

Just encountered this. Ha. What a ghastly 'feature'!

What a delightfully unhelpful feature! Thank you very much for pointing me in the right direction! I'm guessing there's no 'Resolved' button in this forum, but thank you for resolving the post.

Logic 10.7.9 | Mac M2 Rosetta Sanity check before I report this, please: Here's a very short video DESCRIPTION: When using the built-in Browser, audio dragged onto a track resets the volume to unity. same thing happens with a new project (not from template)

Yes it's ridiculous. Weirdly it wasn't an issue for me at all on the previous machine, but it is on this one - so much so that I'm practically forced into remaining in Rosetta mode. The only thing I can suggest is for anyone experiencing it to take a moment to report it here if they haven't already.

Thanks @des99. There shouldn't be any permissions issues on this build - everything is a default installation (literally every single plugin and every bit of software is a clean install of the latest version). Logic also has full disk access. Are those plugin folders you're referring to in Audio Music Apps by default, or are the in various locations depending on the plugin? Yes, on my old build I seemed to have all the folders for the plugins. Perhaps it's a Ventura issue (seems to be locked down very tightly, which is a bit of a pain).

[Ventura 13.5 | Logic 10.7.9 | Rosetta on M2 Studio] It would be great if someone could remind me of the default behaviour for this action ... Open any 3rd party audio FX plugin that doesn't have existing user presets From the plugin window dropdown (see screenshot) choose FILE → SAVE AS (if you don't have any presets the SAVE option is greyed out) See where it tries to save the .AUPreset file BUG? After a clean installation of everything (OS/Logic/Plugins etc) the save location I'm being given is the root of ~DOCUMENTS I thought it used to automatically create a folder for you with the plugin name somewhere - obviously if all presets are in the same location and you forget to create a subfolder you won't know which plugin the preset is for. I didn't create AUPresets that often, but from the look of my backups when I did, folders were created. I certainly don't recall creating them myself). At the moment it seems like it is up to me to create a folder with the plugin name.