MPC Software dithering 24 bit audio to 16 bit in chop mode and 'bounce to sample'

  • 4
  • Problem
  • Updated 3 months ago
This is an ongoing issue that dates back to 1.x versions of the MPC Software. There are currently two areas where the MPC Software (and standalone firmware) where the MPC is dithering 24 bit audio down to 16 bit audio, regardless of the settings in 'Preferences' (which are all set to 24 bit wherever there is an option to - e.g. 'drag and drop' and 'General').

1) Chop mode: 'destructively' chop a 24 bit audio file and the resulting chops are 16 bit. Create a patched phrase from a 24 bit file and the result is 16 bit.

2) 'Bounce to Sample' - the resulting bounce is always 16 bit.

Please note that 'Drag and Drop' works as intended, i.e. if you use the 'Export Audio' icon and 'drag' the icon to your desktop or another application, the resulting file is 24 bit. It's specifically the 'Bounce to Sample' option that always produces a 16 bit file - this is found in MAIN (hardware interface) or right click on the track in 'Inspector' in the software.

BTW, on the subject of dithering, the opposite problem exists with the 'MPC1000/2500 program export' feature. If you have a DRUM program made up of 24 bit samples, the resulting 'MPC1000' export _doesn't_ dither those samples down to 16 bit - hence those samples won't actually load in an MPC1000.
Photo of mpctutor

mpctutor

  • 9 Posts
  • 2 Reply Likes

Posted 2 years ago

  • 4
Photo of Nick D

Nick D, Employee

  • 9242 Posts
  • 860 Reply Likes
Hey Tutor,

Thanks for posting!

Sorry to hear you're having some trouble with that! Be sure to submit this information with the MPC 2 Software's built-in feedback module and let our development team know! The feedback module is represented by a smiley icon at the lower right side of the software next to the browser icons. This information goes directly to the Akai team!

If you need an alternative method of submitting feedback, you may use the following links:

MPC - Submit a Feature Request

MPC - Submit a Bug Report

Thank you for your feedback!
Photo of mpctutor

mpctutor

  • 9 Posts
  • 2 Reply Likes
Hi Nick. I reported the 'Bounce to Sample' bug approximately a year ago using the built in feedback module. I reported the 1000 export bug a couple of years ago. I recently re-reported all these bugs plus the chop bug.
Photo of Nate Andrew

Nate Andrew

  • 107 Posts
  • 8 Reply Likes
LOL they sit on here and tell people to submit it to a smiley face lmao
Photo of jan

jan

  • 54 Posts
  • 22 Reply Likes
they literally do that
Photo of mpctutor

mpctutor

  • 9 Posts
  • 2 Reply Likes
Update: This bug also affects 'flatten pad', so even if your layers consist entirely of 24 bit samples, the resulting flattened sample is 16 bit.

Reported via the MPC Software.
Photo of jan

jan

  • 54 Posts
  • 22 Reply Likes
i learned this the hard way and now see the explanation on here. this is probably the biggest flaw I could think of... i only use my own samples which are sampled in 24bit.. surprised not more people are facing this...
i
@Nick is there any acknowledgement by the dev team? kinda downgrades your product after all for me...
Photo of Nick D

Nick D, Employee

  • 9242 Posts
  • 851 Reply Likes
Hey jan,

I do not receive any updates regarding changes in hardware or software until they are released so I don't have any additional information regarding the treatment of audio samples to offer. The best way to communicate feedback to development is through the feedback module or the links I have posted above.

Thank you!
Photo of jan

jan

  • 54 Posts
  • 22 Reply Likes
i have never been as disappointed as much as others as I literally only sample my analogue gear, chop and re-arrange with it.. and run it through some more analogue gear and straight print to tape. it's perfect for that.. now learning that all my precious samples get converted to 16bit after sampling them in 24bit is a loss... suppose i carry on using non destructive slices but that doesnt really allow me to re-use my chops elsewhere. please AKAI before you add more not so great features no one asked for - please do some serious mopping up and make this a professional tool. I paid pro money and I dont extpect this to be hard to fix.. this should be top of your list. many thanks!
Photo of Jesse Skeens

Jesse Skeens

  • 98 Posts
  • 20 Reply Likes
If you sample a lot of analogue sources the material probably has a noise floor close to 16 bit anyway so might not be that big of a loss.
Photo of jan

jan

  • 54 Posts
  • 21 Reply Likes
sadly not true - it was a notable difference when processing them further and revealed the bug to my ears in the first place. Not sure on what ground you'd think that analogue gear produces noise floor like you describe it. if anything, you'd want to sample analogue gear at the highest possible resolution to stay as close as possible to the original signal. noise floor is the same on 16 bit and 24bit, it's just that you have that much more resolution in 24bit that the noise floor isn't as hurtful as it is in 16 bit when processing it further
Photo of Jesse Skeens

Jesse Skeens

  • 98 Posts
  • 20 Reply Likes
The inherent noise floor in 16bit is around -96db, 24 is -144db.

Most of my analogue hardware produces noise above -96db. I'm recording a Moog right through a compressor and it's about -84db (signal peaking at -4db) well above what 16bit can provide. Even the best converters have a noise floor of about -110db.

Ideally it would stay at 24bit but in practice I can't see it being an issue unless you record at low levels and do a lot of processing later that involves large gain increases to bring up the noise.

When the rate gets reduced from 24 to 16 is it at least being dithered or hard truncated?

I will add a +1 to get this fixed though :)
Photo of jan

jan

  • 54 Posts
  • 21 Reply Likes
"Ideally it would stay at 24bit but in practice I can't see it being an issue unless you record at low levels and do a lot of processing later that involves large gain increases to bring up the noise. "

so we're on the same page? there are scenarios where it's useful?
thanks for contributing
Photo of Jesse Skeens

Jesse Skeens

  • 98 Posts
  • 20 Reply Likes
Yea it should definitely be in there as removes a lot of potential hassle.
Photo of mpctutor

mpctutor

  • 9 Posts
  • 2 Reply Likes
This has mostly been fixed, however it still affects 'patch phrase' - a 24 bit wav file converted to a patched phrase is converted to 16 bit, regardless of preferences settings.
Photo of Dionysis

Dionysis

  • 3 Posts
  • 1 Reply Like
Has this been fixed? I am thinking of buying an MPC live but I am really picky with sound quality and this is a really bad sign...
Photo of taps t3mpo

taps t3mpo

  • 47 Posts
  • 9 Reply Likes
Yes and no. See tutor's post above. Akai mods here never really do any housekeeping on this forum. You'll never know by coming here what's been addressed and what hasn't. You are better off going to the unofficial mpcforums.

This board has a lousy format. The mods are good people by all accounts and make sincere efforts but let's ask ourselves: Who "gets satisfaction" here?
(Edited)