For some reason my Serum sounds really quiet compared to yours, even with volume at max, and I followed all your steps. Can't figure out whats wrong with it
It's especially egregious with kick drums though. I will often record a kick drum in audacity first and remove the lead-in to get a better impression of the sound before downloading. However with some samples that feature the human voice, you can just straight up record these with audacity because audio compression was developed for human speech, so while you are losing some information, these will more or less sound the same.
i tried it and it still sounds different from the splice sample. idk, may be because am not in the studio and am using a bluetooth headphones? but i followed the instructions. will get home and try in the studio and let you know. thanks tho
Hey Hakobo, thanks for sharing this magic! I have a short question about the sound you made. In my serum plays the sound much faster and sounds really different, how can that being so? is that bc of my BPM? i tried everything and nothing makes it sounds like yours. have a great day!
Nahhh not sure this is the explanation. Could it be that the sample preview is a totally different file to what actually gets downloaded? Like there are lead ins/pre transients on the previews that just aren't on the file you download. Are sample creators making their previews sound better with pretransients/lead ins to get more downloads?
this is actually a different effect! mp3 compression doesn't downsample like a bitcrushing plugin. the smearing effect you get in the example on the video is due to mp3 splitting audio into "blocks" that get compressed individually. these blocks are typically longer than the length of a transient, resulting in them getting washed out. its a similar effect to when you put a transient heavy sample in a spectral stretching app like paulstretch
Nah this is crazy I was just making some lunch and I happened to think about that one time months ago I figured out why splice samples sound different when I download them, I get back to my pc and this video is in my recommended. My thoughts have been read and I feel violated D:
If you don't like the transient you can just saturate the .wav instead of converting it to .mp3. It would probably be higher quality and give you more control. I can't imagine doing this myself but if it sounds better to your ears then who am I to argue.
I'm sure! This video was moreso to uncover what was going on behind Splice than to devise a way to shape drums, although I may try both techniques out on future drums to see the effect.
@@HAKOBO Many great pieces of music were never completed, composers, bands, producers you'll never ever hear, who failed to reach their full potential due to obsessing over a single element like a snare drum. Better to consider snare to be a guide, get on with creating music, then select a snare from many, in the context of the music created, as opposed to selecting in isolation. Creators of music enjoyed by millions still have second thoughts about selective choices they made at recording stage.
Always thought it was just a low bitrate mp3 files for previews my self. Sometimes I’ll throw Goodhertz lossy on the sample to get it back to that compression.
@@HAKOBO maybe it sounds closer, im just saying that my computer showed the samples I was having trouble with to be at 44.1k but a render to 48k made it sound worse, as does ableton’s upsampling. Too dumb to find a solution lol. Feel like theres gotta be one though, but so far its just to work at a lower sample rate because down sampling is much cleaner.
More like rewarding the people that just bounce it straight from the browser w/ audacity. If I liked the compressed sound, why would I even want the wav?
Mood. Lol, i had this issue years ago. I emailed splice, and the answer they gave was that they do light limiting/normalization on their previews, which changes transient content sadly.
The reason it does this is that probably it saves bandwidth and audio player compatibility on the app and browser. Streaming 1,000,000 files at 32 bit 48k is overkill for a server or broadcast system. Also go look at the sample editor... there is a HiQ button. Turn it off. Basically it takes the sample and tries to (idk how else to descibe it) "unclip" the signal. Try it with your favorite tracks you can see if artists had Intended clipping. I made a video explaing the HiQ thing.
I don’t know if this situation is mentioned in the user terms etc but if it isn’t then it should be. Having to resample an mp3 won’t revert to the sample rate of the original wav file without loss. Yours for transparency .