Lower Bit Rate In 2.10 With the Solah Glitch/Technique....?!

I was cutting up my samples like normal right, so i got to this sample that i lowered the pitch, all the way down to -12, right. so then i found out i overwrote it instead of keeping it, so i tried to up the pitch back to normal and when i went to pitch shift then back to 0.00, the sample sounded like it was still at -12.00 pitch but the sample was lowered in bit rate. and you could see the difference also. has anyone noticed this?

if your clue less try it.....

or im i trippin? im kinda comming down from this acid/cannibus high but im alright though.

I want the Jessiah Glitch back!

Tried this on an acoustic guitar sample, bass sample and drum loop. You're right about one thing - pitching back up doesn't work. In fact on the drum loop, not only did it not pitch back up but it also wiped the right channel of the sample.

But in neither case did it seem like it had reduced the bit depth or anything like it. The only thing I noticed was perhaps a little top end had gone.

ya i know what ur saying, i do this alot to get that grimey sound it destroys the quality of the original sample, say if u sample a kick and stretch it down then bring it back up and do it agin it gets all weird. its like a slab of skin if u stretch it then release it back to its normal state then stretch it agin eventually itll have cracks and so on.

I just realised we're both being a bit stupid really. If you set pitch shift to 0 its not going to do anything. To pitch back to the original you have to set it to +12

I think what is happening is sample degradation.

When you have a sample at 44100kHz 16bit, and then lower the pitch, what you are effectively doing is slowing down the sample rate. if you go down to -12, which is an octave, you will halve the frequency the samples are played at. then when you save that sample, it is saved as a 44100kHz 16bit wav file again, NOT a 22050kHz 16bit sample which is what it actually is (or was before you saved it). I think the different sound you hear is some aliasing artifacts created by saving a 22050kHz file to a 44100kHz file, changing it to 88200kHz (when you pitch it back up again) and then saving that to a 44100kHz file.

If you have photoshop you can try it with a picture file: reduce the resolution, and then save the file under a different name, and then boost the resolution back to its original values, and you should notice a difference between the original and the reduce and then enlarged file.

Its a trip though, it does give it that grimmy sound, what i`ll do is take a sample and sample it at a high speed like 45 on the table, and then pitch shift to -12 and it will sound slowed down but at the original sound (since i sampled it at a higher speed into the MPC), then pitch shift it back to -0.0 and it will sound all distored but sound the same..., ya get what im saying? imma try it...wait but imma have to use timestretch too...imma try something

and thats a good way to save some sample mem as the pitched-up sample will be shorter
For instance theres a nice bass in the 2500 bank (SYNBASS something), that has a wimpy high pitch sound in the original sample, but becomes a mean sub-bass as you pitchshift it back down

but yall know that right?

Not a glitch at all. It's just understanding time stretch, pitches, tunes and sample rates..

None of this is new but it's good you guys are experimenting with it. Whatever makes you happy, do it.

Lampdog wrote:Not a glitch at all. It's just understanding time stretch, pitches, tunes and sample rates..

None of this is new but it's good you guys are experimenting with it. Whatever makes you happy, do it.

i don't think timestretching comes into it. i think it's to do with when you save what is actually a 22050kHz wav file (or any other frequency, as when you pitch a sample without using pitch-shift, it changes the sample rate to get the new note) as a 44100kHz wav file - you get some aliasing......but i could be wrong.