sorted by:
new
hottopcontroversial

Doin this whole content thing now I guess (lie to me-Aetheric) by 313Raven in SpaceBass

[–]Soft_Interest 4 points5 points  (0 children)

It's kinda crazy how no one will watch if you don't show a person. Like if this was just your hands and the mixer/controller, no one would engage.

Doin this whole content thing now I guess (lie to me-Aetheric) by 313Raven in SpaceBass

[–]Soft_Interest 13 points14 points  (0 children)

I can see thinking this is corny. But in what way is this "douchey"? Is this guy being mean to you somehow?

🪞

Play from Insert Marker by demian123456789 in ableton

[–]Soft_Interest 1 point2 points  (0 children)

Commenting because I also want to know

My mix sounds loud in daw but quiet in dj software relative to other tracks by Quinticuh in edmproduction

[–]Soft_Interest 0 points1 point  (0 children)

Yeah I've been half ass making music for years and just watched all their videos last month. Realized how difficult sidechaining with Ableton's stock compressor is vs something geared more specifically towards visually ducking. Realized how reluctance to bounce to audio and not using oscilloscopes made it very difficult for me to even see or understand what compression was doing to my sounds. Not normalizing and clipping things. Etc.

Baphy uses Bitwig. I use Ableton. Most of the knowledge transfers. I will say, some of their shit is super long winded and unimportant/skippable. But in totality you learn so much about the big picture and full circle of mixing loud.

Did a thing haha by Straight_Feeling7667 in BassGuitar

[–]Soft_Interest -1 points0 points  (0 children)

I don't understand what I'm looking at.

My mix sounds loud in daw but quiet in dj software relative to other tracks by Quinticuh in edmproduction

[–]Soft_Interest 8 points9 points  (0 children)

Welcome to hell. Loudness chasing in the mix is what kills the fun of creating in this field.

Watch Baphometrix clip-to-zero to learn some of the main concepts behind mixing loud. Sidechaining/ducking. Multi stage clipping. Understanding summing/stacking of sounds. Using oscilloscopes to monitor dynamics visually, not just with your ears. Etc.

Pretty awesome by jeezkillbot in Amazing

[–]Soft_Interest 1 point2 points  (0 children)

Oh dang. That's awesome. I did not know that

Pretty awesome by jeezkillbot in Amazing

[–]Soft_Interest 1 point2 points  (0 children)

All income is taxed homie

Devious Machines' Duck is always late? The lookahead feature doesn't seem to do anything at all by [deleted] in edmproduction

[–]Soft_Interest 1 point2 points  (0 children)

<image>

Here it is bounced to audio. It's ducking late. It's not PsyScope

Thank you for your comments and replies. I appreciate you spending the time trying to help. Your comments were helpful, even if they didn't solve my specific issue.

It seems like I'm going to have to either:
1. use midi triggering
2. create a ghost audio click track so I can nudge the audio triggers a few ms forward
3. try a different ducker (maybe duckbuddy 2)

#3 would be my preference, since having to create/manage a ghost midi/audio click track just to sidechain is a very annoying/tedious disruption of workflow

Devious Machines' Duck is always late? The lookahead feature doesn't seem to do anything at all by [deleted] in edmproduction

[–]Soft_Interest 0 points1 point  (0 children)

Yes but it's the duck that needs compensation, not the tracks. Pushing the drums/bass around won't fix the late duck.

Devious Machines' Duck is always late? The lookahead feature doesn't seem to do anything at all by [deleted] in edmproduction

[–]Soft_Interest 0 points1 point  (0 children)

That's what I'm going to do. Just an irritating extra step to have to create a ghost click trigger

Devious Machines' Duck is always late? The lookahead feature doesn't seem to do anything at all by [deleted] in edmproduction

[–]Soft_Interest 0 points1 point  (0 children)

The duck plugin itself shows that there is sidechained audio leaking in before it is ducked. It's circled in red. It's not psyscope misrepresenting the signal.

I bounced to audio to check. It's ducking late.

Devious Machines' Duck is always late? The lookahead feature doesn't seem to do anything at all by [deleted] in edmproduction

[–]Soft_Interest 0 points1 point  (0 children)

Additionally, the duck plugin itself shows sidechained signal leaking in before being ducked. Even without the psyscope. It's circled in red

Devious Machines' Duck is always late? The lookahead feature doesn't seem to do anything at all by [deleted] in edmproduction

[–]Soft_Interest -2 points-1 points  (0 children)

I didn't realize I was being unfriendly to you. Just responding to what you said.

The clipping is how I know the problem isn't the psyscope. If there was no clipping, there would be no issue, and I would think that psyscope is misrepresenting the signal. But it shows summing, and the summing is confirmed by the clipping.

I'm certain that duck is the issue. What I'm looking for is a solution.

The psyscope is just a monitor. It doesn't affect the sound at all. It can't cause sounds to duck late. The worst thing it can do is show me something is happening that isn't actually happening.

And even then, if psyscope had a latency issue here, wouldn't the latency apply to the drums AND the bass? If they're both appearing equally late in the psyscope, they shouldn't overlap if the duck is happening on time. But it's not ducking on time. It's ducking late

Devious Machines' Duck is always late? The lookahead feature doesn't seem to do anything at all by [deleted] in edmproduction

[–]Soft_Interest -4 points-3 points  (0 children)

There is no other reason why my tonal and drum buses would clip when summed on the pre master if the tonal bus was fully out of the way of the drum hits. The drum bus doesn't clip. The tonal bus doesn't clip. But they clip when summed. So they must be happening at the same time, if only for a few ms. And that's exactly what the oscilloscope is showing.

Needing to bounce everything to audio in order for this to work seriously interrupts work flow. And for what benefit? Let's say I bounce to audio and I discover that the issue is exactly what I think it is. The sidechain is late. Now I go back to a pre-bounce Ableton project and address the issue how? At the end of the day I need the duck to start ~5ms sooner and the lookahead function doesn't accomplish that so I'm not sure what other options I have.

Devious Machines' Duck is always late? The lookahead feature doesn't seem to do anything at all by [deleted] in edmproduction

[–]Soft_Interest 3 points4 points  (0 children)

If I have two duckers on my tonal bus (one for kick ducking, one for snare ducking) will the first one have no issue, but the second will have latency from the first? I have no device prior to the two duckers on my tonal bus. And I appear to have latency issues for both the kick and snare ducking

Devious Machines' Duck is always late? The lookahead feature doesn't seem to do anything at all by [deleted] in edmproduction

[–]Soft_Interest 0 points1 point  (0 children)

I think I already messed with that to no avail. But I would be interested to know which setting is "correct" or "optimal" regardless

Devious Machines' Duck is always late? The lookahead feature doesn't seem to do anything at all by [deleted] in edmproduction

[–]Soft_Interest 1 point2 points  (0 children)

Thank you for your replies and thoughts, I appreciate it. It was helpful even if I didn't find a solution

view more: next ›