
Help With Fruity Loops???
Forum rules
By using this "Production" sub-forum, you acknowledge that you have read, understood and agreed with our terms of use for this site. Click HERE to read them. If you do not agree to our terms of use, you must exit this site immediately. We do not accept any responsibility for the content, submissions, information or links contained herein. Users posting content here, do so completely at their own risk.
Quick Link to Feedback Forum
By using this "Production" sub-forum, you acknowledge that you have read, understood and agreed with our terms of use for this site. Click HERE to read them. If you do not agree to our terms of use, you must exit this site immediately. We do not accept any responsibility for the content, submissions, information or links contained herein. Users posting content here, do so completely at their own risk.
Quick Link to Feedback Forum
- blizzardmusic
- Posts: 4819
- Joined: Sun May 20, 2007 2:21 pm
Help With Fruity Loops???
Basically - I've started doin subs in my tune behind a bass.. I'm usin Fruit Loops 7 - When I render it to 320kbits or whatever bitrate it is - it completely changes the bass. Might be just a glitch in the software, but If you have a way of preventing this, please tell! 

Soundcloud
If you like jungle / drum and bass you'll like the above!
Twitter: twitter.com/iamblizzard
If you like jungle / drum and bass you'll like the above!

Facebook: facebook.com/blizzarddubsdiss04 wrote:who?Pistonsbeneath wrote:no mention of blizzard?
Twitter: twitter.com/iamblizzard
-
- Posts: 144
- Joined: Wed May 23, 2007 4:09 pm
- Contact:
Dithering is digital noise used to make quantizing error sound less objectionable. Check the link.
http://en.wikipedia.org/wiki/Dithering
http://en.wikipedia.org/wiki/Dithering
^^^, fuck, that's a long, accurate, and no-fun description of dithering.
the in-practice cliffs:
#1, in general, but especially if you're recording any live instruments or hardware synths, you should be working at 24 bit resolution in your projects. the half-again-as much dynamic range will result in you getting punchier, brighter, 'cleaner' mixes with less effort.
(you should also use fairly low levels but that's beside the point)
#2, though you work in 24 bit, cds are pressed at 16 bits. this means that the last 1/3 of each bit of audio you've recorded is going to get chopped off once it's either burned to audio CD, or bounced out at 16 bits.
#3-- If you don't do something about this truncating of bits, you're going to get that horrible, underwater, warbly sound as sounds and reverb tails decay. That's not because you encoded a song w/ VBR, it's because of 'bit truncation.' What do you need to do? DITHER.
In adding dithering at the end of your mastering chain, or on your bounce/render, you're adding some nearly-impercievable noise to your track. This noise masks-- shapes, even-- that nasty sound into something musical.
as you can see from the wiki, there's a whole world of work on dithering. Right now, both apogee and POW-R make the most-used algorhythms, though if you're using the waves L2 or L3 , you can do dithering in there as well (apogee's is HR22 and is included w/ cubase/nuendo; POW-R is included w/ logic and peak). it's an extremely important part of getting a good sounding master.
the in-practice cliffs:
#1, in general, but especially if you're recording any live instruments or hardware synths, you should be working at 24 bit resolution in your projects. the half-again-as much dynamic range will result in you getting punchier, brighter, 'cleaner' mixes with less effort.
(you should also use fairly low levels but that's beside the point)
#2, though you work in 24 bit, cds are pressed at 16 bits. this means that the last 1/3 of each bit of audio you've recorded is going to get chopped off once it's either burned to audio CD, or bounced out at 16 bits.
#3-- If you don't do something about this truncating of bits, you're going to get that horrible, underwater, warbly sound as sounds and reverb tails decay. That's not because you encoded a song w/ VBR, it's because of 'bit truncation.' What do you need to do? DITHER.
In adding dithering at the end of your mastering chain, or on your bounce/render, you're adding some nearly-impercievable noise to your track. This noise masks-- shapes, even-- that nasty sound into something musical.
as you can see from the wiki, there's a whole world of work on dithering. Right now, both apogee and POW-R make the most-used algorhythms, though if you're using the waves L2 or L3 , you can do dithering in there as well (apogee's is HR22 and is included w/ cubase/nuendo; POW-R is included w/ logic and peak). it's an extremely important part of getting a good sounding master.
twitter.com/sharmabeats
twitter.com/SubSwara
subswara.com
myspace.com/davesharma
Low Motion Records, Soul Motive, TKG, Daly City, Mercury UK
twitter.com/SubSwara
subswara.com
myspace.com/davesharma
Low Motion Records, Soul Motive, TKG, Daly City, Mercury UK
Dithering is only relevant when reducing bit depths, not sample rate. Since mp3 is a 32-bit float format natively, you never have to lower your bit depth (or hence, dither) when encoding mp3s.
This is important to consider when mastering mp3's, since mp3 has a larger dynamic range than (16 bit) CDs, and can very realistically yield higher quality results than a CD master. As for sample rates though, lame is optimized for lower samplerates - 44.1kHz being the sweet spot.
Most likely, what you're hearing is a shitty mp3 export with possible bit or sample rate reduction first.
Try rendering a 32-bit WAV and use lame for encoding and see if there's a difference. Also listen to the exported WAV for comparison.
Cheers,
-d
This is important to consider when mastering mp3's, since mp3 has a larger dynamic range than (16 bit) CDs, and can very realistically yield higher quality results than a CD master. As for sample rates though, lame is optimized for lower samplerates - 44.1kHz being the sweet spot.
Most likely, what you're hearing is a shitty mp3 export with possible bit or sample rate reduction first.
Try rendering a 32-bit WAV and use lame for encoding and see if there's a difference. Also listen to the exported WAV for comparison.
Cheers,
-d
Who is online
Users browsing this forum: No registered users and 0 guests