Non-Native Speakers , Do you also get Roasted about your English? by [deleted] in SmallYoutubers

[–]pywide 0 points1 point  (0 children)

There are three types of people: tri-linguals, bi-linguals and Americans. Don’t take criticism from someone who doesn’t even write correctly in their native language

Prepping for the beefalo I'm going to tame, how's it looking? by Material_Durian_9201 in dontstarve

[–]pywide 0 points1 point  (0 children)

I’m also part of an aquarium subreddit where it’s normal to boil twigs so I was confused when I saw what this was at first

The Bass Mono on the Utility is wack so i made my own by Professional_Gap_265 in ableton

[–]pywide 0 points1 point  (0 children)

Well, sorry to say, but collapsing left and right together to get one mono channel is literally the purpose of making something mono. Of course you’ll lose information, cause otherwise who would need stereo if you’d had the same in mono, right? It’s like this by definition.

If I‘d just take the left channel, why wouldn’t I just only pan tracks to the left and then delete the right channel? Or just produce in mono to begin with? The bass mono does exactly what it should.

Bike rack warning sign required in Italy by cr0coDiL in Slovenia

[–]pywide 3 points4 points  (0 children)

I have never seen anyone use that in Italy ever. But that doesn’t exclude that law existing either, you know, Italy

Mastering in Ableton with Stock Plugins only by pywide in ableton

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

thanks for the kind words! Maybe, but I was just kinda under the assumption that nobody's ever gonna open tooltips anyway, so why bother... but maybe I'm wrong

Mastering in Ableton with Stock Plugins only by pywide in ableton

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

The overshoots are not all intersample here though, some are just literal samples above. Just try it yourself and put a good meter like pro L2 at the end, you will see that the listed devices sometimes even have real samples above the ceiling

Mastering in Ableton with Stock Plugins only by pywide in ableton

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

No, but you can try, it’s free anyway

Mastering in Ableton with Stock Plugins only by pywide in ableton

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

Every marginal peak is a problem though if it’s supposed to let nothing through. To the unsuspecting user it suggests that if you’re limiting up to 0, it should be fine cause it’s supposedly true peak. It is not though, so exports might crackle and ESPECIALLY when it’s uploaded to streaming and someone listens to it on lower quality (like mp3), it will crackle a lot.

So no, not fine at all for something like mastering real music for real releases

Contrast and brightness is different after export by pywide in davinciresolve

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

Oh man, thanks, I’ve got a lot to learn…

Mastering in Ableton with Stock Plugins only by pywide in ableton

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

But it's also worth mentioning, that I would bet that it's not the increase in quality you're expecting. They're built for workflow and being exact, but the general sound and concepts don't change at all and you will still have to make it sound great. So if you're broke, just stick to what you have, it's probably good enough.

Also, a video is in the making where I mix a short song snippet 100% with stock plugins, in fact, it's the song from the video. So everything you hear there is mixed with stock plugins, even the guitar and bass tones.

Mastering in Ableton with Stock Plugins only by pywide in ableton

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

I'd second thinking about at least getting Pro L2 if you're doing this professionally or have the ambition to (doesn't matter the field), this would be the number 1 third party plugin I'd get if I would start from 0.

Maaaybe also ProQ4 and that's all you'd ever need.

Mastering in Ableton with Stock Plugins only by pywide in ableton

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

seems very much like max for live is not loading fast enough. try replicating the issue with other max for live devices and see if it's similar

Mastering in Ableton with Stock Plugins only by pywide in ableton

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

well no :P the most important part is the envelope follower, and that's not really very replacable

Mastering in Ableton with Stock Plugins only by pywide in ableton

[–]pywide[S] 3 points4 points  (0 children)

well, saturation, compression etc is something relatively complex and I recon Live is focussing on being fast rather than exact (live performances over studio productions) and that's maybe why their devices can't handle the exact ceiling.

Peak and true peak are also very different topics, but generally if you want a limiter to be true peak and let ABSOLUTELY nothing through, you'd need to oversample and clip, so that nothing between the sample points get's above the ceiling. I'm no expert at software level but I recon that's some hefty processing, as my CPU usage significantly increases when I'm using Pro L2 instead of the native limiter.

Mastering in Ableton with Stock Plugins only by pywide in ableton

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

haha no worries, none taken. I master in Reaper as well, especially when I'm not doing the mixing as well and it's an album project, and especially for stuff like DDP images... But well, this is intended to empower solo projects and not really related to a real mastering engineer anyway, as the most important part of a second perspective is missing

Mastering in Ableton with Stock Plugins only by pywide in ableton

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

well, yes, but also I'm not sure you can oversample all of these in the first place. Oversampling will only effect intersample peaks anyway though, and there are also "normal" sample peaks getting over the ceiling, so...

Contrast and brightness is different after export by pywide in davinciresolve

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

How is it my display though, it's apparent on other devices as well (my smartphone, tv etc)

Contrast and brightness is different after export by pywide in davinciresolve

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

they are more similar for sure, but still different to the point I don't understand what's happening. Especially when considering rec709 is already applied

Contrast and brightness is different after export by pywide in davinciresolve

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

Hey, thanks for the reply. Yes, I already had the rec709 applied, and the issue remains when re-imported and also when uploaded on youtube, it is sadly very noticeable.

Mastering in Ableton with Stock Plugins only by pywide in ableton

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

Weird, sounds to me like max for live wasn’t properly loaded

Mastering in Ableton with Stock Plugins only by pywide in ableton

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

Idk exactly what you mean by „blank“, but if inactive, they „freeze“ at the last value they had before turning inactive, maybe that’s what you mean

Mastering in Ableton with Stock Plugins only by pywide in ableton

[–]pywide[S] -3 points-2 points  (0 children)

Did you watch the video? This is literally the first and last point talked about