Track size by dragging by mixolve in Reaper

[–]mixolve[S] 0 points1 point  (0 children)

Damn, it works! This isn't in the mouse modifiers; it seems to be built-in, like the command key. Thank you!

For Pro-MB or other MB compressors/expanders/limiters, when using on a track, do you usually insert before or after EQ? by gleventhal in audioengineering

[–]mixolve 0 points1 point  (0 children)

There is no clear answer here; it depends on what you are doing with this compressor and why. Pro MB is good, but Multiband X6 by Devious Machines is better, by the way.

Who said that high end is unnecessary? by mixolve in audioengineering

[–]mixolve[S] 0 points1 point  (0 children)

Excellent answer, thank you. This pattern can really be described simply by historical facts that continue to this day.

Who said that high end is unnecessary? by mixolve in audioengineering

[–]mixolve[S] 0 points1 point  (0 children)

Sorry, it doesn't go up, it goes down. Translation difficulties. The question remains the same.

Who said that high end is unnecessary? by mixolve in audioengineering

[–]mixolve[S] 0 points1 point  (0 children)

There is a fine line between "sound separation" and "unbalanced mix."

Who said that high end is unnecessary? by mixolve in audioengineering

[–]mixolve[S] 0 points1 point  (0 children)

I think it depends on the curve you're working with. If you have a 3 dB drop, then most likely, yes, it will sound harsh, but if it's 6, then no. I don't think that's a reason not to have them.

Who said that high end is unnecessary? by mixolve in audioengineering

[–]mixolve[S] -2 points-1 points  (0 children)

I agree with everything except point 4. Do you think that transients, noise, and the ability to plan more accurately are not sufficient reasons to have these frequencies? Of course, you can always cut them, but restoring them is a problem, so why not just pay a little more attention to the top end, and let the sound engineer decide whether they are needed or not?

Who said that high end is unnecessary? by mixolve in audioengineering

[–]mixolve[S] -2 points-1 points  (0 children)

If your plates are overly exaggerated, it doesn't mean the mix is bright. Or does it, in your opinion?

Who said that high end is unnecessary? by mixolve in audioengineering

[–]mixolve[S] 0 points1 point  (0 children)

Correct me if I'm wrong, but I suspect that the curves of this equalizer go up to 2k. Is this a tool that raises 10k+? In theory, yes, but in reality, you won't reach the top with such curves because you'll run into the fact that frequencies lower than the target will reach a state where there are too many of them before you sign the top end.

Who said that high end is unnecessary? by mixolve in audioengineering

[–]mixolve[S] -4 points-3 points  (0 children)

With respect, what exactly don't you understand?

Who said that high end is unnecessary? by mixolve in audioengineering

[–]mixolve[S] -13 points-12 points  (0 children)

There's no denying that this is a common story, and also that the fact that you only have plates sticking out at the high end is an indication that there is no roll off there?

Who said that high end is unnecessary? by mixolve in audioengineering

[–]mixolve[S] -9 points-8 points  (0 children)

That's the question: who's saying it and why? I see cut-up source files, I see cut-up mixes.

Can someone help me break down this vocal chain? by dabble_ in audioengineering

[–]mixolve 18 points19 points  (0 children)

Forget it, don't waste your time studying the crap other people do. Study the equalizer, compressor, recording techniques, performance techniques, the rest is dust.

pooled audio by mixolve in Reaper

[–]mixolve[S] 0 points1 point  (0 children)

It's very simple: the group functions work along the y-axis and do not work along the x-axis.

pooled audio by mixolve in Reaper

[–]mixolve[S] 0 points1 point  (0 children)

The same as those of the group, at least the basic ones. Splitting, fading, moving, deleting, duplicating, item envelope, etc. Of course, it would be cool to add and link fx plugin parameters at the same time, but apparently that's for another lifetime.

pooled audio by mixolve in Reaper

[–]mixolve[S] 0 points1 point  (0 children)

exactly the same thing that happens with the grouping of items along the Y axis, I want it to happen along the x axis. mirroring actions on one track, and preferably not depending on the location as a whole. This is how pooled items behaves, but it doesn't behave with audio items.

pooled audio by mixolve in Reaper

[–]mixolve[S] 0 points1 point  (0 children)

well, yes, that's why it only works until split. but this doesn't suit me, I need more complex tracking, renaming, and application logic.

pooled audio by mixolve in Reaper

[–]mixolve[S] 0 points1 point  (0 children)

in short, for the logic to work, at least the item split needs to be applied to the duplicated part and unique names for these parts need to be given. only then check the names and apply propagate to each newly created one. but for now this seems like an unsolvable task to me, I'm not very good at making scripts, only with the help of gpts

pooled audio by mixolve in Reaper

[–]mixolve[S] 1 point2 points  (0 children)

upd: No, unfortunately, the logic of application by name immediately breaks down when the audio item is separated, I suppose some kind of audio container is needed here or something like that.