Hate my life right now

[Uros]

A while ago I started mixing this album. It's going pretty cool so far. I have 2 more songs to do (but since others are pretty much finished, those 2 are close to be finished too; band want consistent sound throughout the whole record).

I left these 2 songs for the very end, since they have a couple of blast beat sections. So, I open one of them, hear something is wrong. Look at the snare track. THE FUCK?!? Track is totally unusable even for feeding the drum replacer program, let alone for using it in the mix, even just for blending. Sounds like their engineer miced it from underneath the drum throne/drummers ass or something uke: (it should be noted that other drum tracks are not bad at all, but I am totally puzzled with this one).
There is pretty much zero snare bleed in overheads, apparently they tracked it separately. The other song is the same way too, when it comes to blast beats.
I have to manually cut and mute parts of the tracks, have to build that trigger tracks from scratch. I know in advance there is no other way, but still, are there some other techniques to turn this unusable tracks to somewhat usable for feeding trigger off of it?

FML

 

[decoy205]

Have you tried increasing the gain on the actual audo file to blow up the snare hits? Then cutting out the garbage accept the hits you want and replace from there?

I'm not sure if that will work but it might be an idea.

 

[Jarkko Mattheiszen]

Sounds like the drummer just can't play a proper blast and is hitting the snare like a sissy. If all else fails (*cough clip gain and Slate Digital Trigger cough*), just program the snares on the blast parts.

 

[Uros]

I'll post a part of the track soloed (can't post the whole songs, don't believe the band would agreed with that), 'cause I wanna make you guys laugh

Hey decoy, I tried all the methods. Tried it with manually cutting tracks in smaller parts and raising gain (what Jarkko says), tried smoothing out parameter in Aptrigga...all to no avail. So I have to go and listen to the track, and manually cut when the snare should not have be 'heard' by Aptrigga.
You can hear when the snare is being played from the raw tracks, but because many hits are pretty similar in volume (I'm talking snare vs. cymbals) I know I'm fucked, and that I'll have to proceed with making (er, 'programming') the tracks.
What I usually do when making the trigger track is, I set up the threshold so that Aptrigga picks up as much as it can, and manually cut and raise/lower the problematic hits. I've had expected results with that in the past. Doesn't work here.

Fuck!

 

[Tommy Evans]

Wutzington, lovin your sigquote. My Xbox gamer tag is Tomtaur haha.

 

[amarshism]

In the five hours between your posts you could've drawn in the midi. Come on meow.

 

[kev]

TIme to get yer midi on : O

 

[RedDog]

midi trigger.

equals win.


just don't tell the band.

 

[Clark Kent]

@ topic title!

 

[waltz mastering]

Work on the blast beat sections separate from the other snare parts. Hit them with a transient designer or frequency dependent upwards expansion to bring out the peaks, trigger and edit.. takes time but that's why you get the big bucks.

 

[Uros]

Haha, funny thing you say that Tom and RedDog, 'cause I had tried both things before you guys wrote your posts, and nothing. I actually tried staging three Transient monsters in series, because one was not enough (and place an eq before them to kill all the high frequencies/cymbals), and still wasnt't satisfied (took too much time tweaking the result). Tried it also to export to midi, via Reaper's dynamic split. Too much mistriggers.

I have found the solution. And such a stupid one, that it actually works .
So I took the kick trigger track, offset it (align it with the first snare hit), and used that to feed the Aptrigga, because the kick and snare are symmetrical in blast beat sections, they just start at different time! Win! hahahah

In the five hours between your posts you could've drawn in the midi. Come on meow.

No, I couldn't, 'cause that 2nd time I posted, it was actually from my work office (working as a sound engineer at National TV station).
I couldn't be arsed to program it, found it more time beneficial to do what I did

 

[Uros]

Here are the short tracks. Keep in mind they still need editing ofc, but here are the raws.

Original:
http://dl.dropbox.com/u/1370003/primer2.mp3

The result:
http://dl.dropbox.com/u/1370003/primer.mp3

 

[AboutBlank]

Trigger (Slate) can handle that.

Def. "triggable"...

 

[colonel_claypoo]

i've had something in the same "performance category" too. I ended up programming it after trying everything I could.
shells might be trigger'able but if the timing between kick/snare is off too much, even slip editing won't help.

song seems cool, got the belphegor touch.

 

[KBMoser]

Take your kick, snare and tom tracks and split every single hit. Select all of the splits and normalize them all to -8db. For blasts i would normalize the snare splits to -12db. Apply an expander and use it like a gate to minimize the bleed. Apply you drum replacer and record all of the midi output to a midi track. Insert drum vsti such as superior drummer. Boom. 20 minute fix. If the midi has misfires than correct it. This method saves you time and frustration in the end. All thats left to do is correct velocities and mix/blend your tracks.

 

[crillemannen]

I would have just added the blastbeat section to another track. Gain the actual wav file until you can see all the hits good. Use Slate Trigger and just cut out the noise so it just triggers the actual hits. Shouldn't be such a big problem.

But if you still can't see any actual hits then as the other guys said just midi the bitch and trigger it that way. Just try to align the hits so they are all in phase with the overheads.