John T

I know this was discussed quite a bit in the early access threads, so apologies if I'm misunderstanding something. But... what? I don't get this at all. This seems like an egregiously weird numbering system to impose:

I don't know what y'all did with the plug-in menu fonts, but it's like angels are blowing gentle clouds of comfort and joy onto my tired eyeballs, and I want you to do it to the whole program. Also: didn't expect to like the waveform outlines, but that's really visually agreeable "in the flesh" as it were. Automation display improvements also really great. Has something about the editing functionally changed? Perhaps an illusion because of the nicer visuals, but it feels really great to edit with all of a sudden. Not had something this good for free since the last time I robbed a bank*. * have never robbed a bank, it's a joke.

I think you should consider whether the other tracks aren't fine and the vocals actually are. -18 to -12 is a good benchmark for the raw recording level of everything, not just vocals. It sounds to me as if everything else is too loud. This assumes that other sounds are coming from recorded instruments and not plug in synths and so on, but a similar principle applies.

I've noticed that I can't use the mouse wheel to scroll the control bar modules any more. Is that a setting somewhere, or has it just been removed?

Asking for a colleague, and as we don't have anything like old "computers and hardware" sub-forum any more, thought I'd try here. I'm really out of the loop on this, as I build my own desktop computers and have done for years. Who are the current US-based suppliers / builders of laptops that are set up well for audio? Got an audiobook narrator who I work with who's had a hell of a time with DPC latency glitches on an off the shelf system. She works enough that she can justify paying a decent premium to make the problem go away. Any recommendation? Thanks all.

Got a minor niggle with with the new ALT+X to toggle Aim Assist labels on and off. The setting defaults to off and doesn't persist, either globally or within projects. I do a lot of editing work, and mostly want it on all the time. Would be really nice if it could persist at least within a project. At the moment, having it on, but saving, closing and reloading the project (not even the whole application) will switch it off.

I think this was updated in the previous hotfix, nit the latest update, so apologies if that's the case. Either way, it's still the same in the current version: The new split behaviour, that creates a crossfade on a split is cool. However, it doesn't follow the default selected crossfade for most crossfade options. For example, I generally use "Slow out, fast in", and that becomes "fast out, fast in" when splitting. The first couple of options work ok, but the rest give different (wrong) results. Is this just me, or has anyone else seen this?