importing from MPC REN to PRO TOOLS

i made a beat on my MPC Renaissance and then imported it to PRO TOOLS but pro tools plays it back to fast and it doesn't allow me to change the tempo to what it should be. can some one please walk me through on how to import a beat from the mpc ren to pro tools with out having this problume
[email protected]

Lampdog, so when i convert on the mpc i can choose either of these 48khz or 44khz? What about when i imput it into Pro Tools do i have to do anything else besides convert audio file?

PT will not let you speed up .wav, .mp3 files with just the tempo. You will have to timestretch/elastic audio those audio files to the speed you need.

Take advantage of the free copy of MPC Elements where you can open individual tracks in PTools. Aux them over to separate audio tracks if needed.

This will most likely give you the speed desired because you are still controlling everthing from your Ren. Just make sure you sync the REN and Protool midi clock.

Lampdog wrote:

Louie lou wrote:You will have to timestretch/elastic audio those audio files to the speed you need.

This is a destructive process. Changing the project sample rates (non destructive) will not help?

Just a suggestion. I use MPC REN with Protools and the only way to change an audio files to the BPM/Tempo you like is to stretch or elastic audio that sucker. Lol. At least thats the way I know how. I've gotten good results from this.

ProTools is a pain in the ass. I believe if you make a new project in protools a dialog will appear asking for details, and you should put the sample rate in there, making sure it matches to the rate you're copying over from mpc software.

i think if you drag n drop files into protools it will go to the default sample rate, which is probably 48khz. you should make protools default to 44.1khz, the only reason to do 48khz is if you compose music for film or something, it's pointless. pro tools makes everything harder than it should be....

also re: elastic time, that doesn't apply, this problem has to do with different sampling rates, which can be compared with the framerate of a movie or videogame. if the sampling rates aren't consistant it will either speed up or slow down the play back of the audio depending on whether the SR is bigger or smaller than the original media was produced at.

Lampdog wrote:Is there a way to change project sample rate (ren/pt)?

Vegas can, Reaper can, etc. If you import a sample that mismatches with
the project sample rate it will be sped up or slowed down (this can happen in any daw). Also, op can just convert the sample(s) to the matching sample rate of the project (destructive).

OR...

Patchphrase the audio sample in the Ren, then export/ sidechain to Pro Tools at whatever BPM you desire.

no, stop talking about anything other than sample rates. you're making it way too complicated bringing up patchphrasing, and what in the heck does sidechaining have to do with this problem**?!

seriously look up how sampling rates work, it's pretty important if you're working with digital audio!! I already mentioned that a sample rate is like a frame rate for video or animation, if you import a 25 frame per second video clip into a 50 frames per second video project in Final Cut or another video editor, it will play that clip twice as fast (essentially playing 25 frames per half second instead of per second). the same thing is happening here with the audio, playing back a 44.1khz audio file within a protools project that has a sampling rate of 48khz will increase the speed beyond the chosen bpm.

i remember very clearly that protools is very inflexible towards sample rates, there was no way i could see to change the sample rate for a project after making the project. that may have changed but the fact will never change that you need to match sampling rates to preserve the correct playback speed. any work-around or fix that isn't matching sampling rates is going to give you terrible quality... for no reason


**(sidechaining isn't another word for export, sidechaining refers to triggering one effect (usually just a compressor but more and more people use envelope triggers for filters and stuff as well) based on the audio signal of an unrelated track, nothing to do with exporting/importing audio)

This is often caused by creating the session at the incorrect sample rate - for example, creating a session at 44.1k and then transferring tracks in digitally from a device that has a clock set at 48k.
The problem with this is that the audio files have been 'tagged' at the incorrect sample rate - in the case above the audio files are 48k files, but are tagged at 44.1k.
When you are no longer clocked to the digital source (by turning it off or switching Pro Tools back to 'internal' clock), the files will play back at the incorrect speed (sample rate).

Here are a few methods for correcting this problem:

If you are using Pro Tools v6 or higher you can use the built-in Digibase to correct the sample rate.
Launch Pro Tools and go to Windows>Show Workspace.
In the Workspace window locate the audio file(s) that need to be corrected and under the Sample Rate column change the sample rate to the correct sample rate for the file.
Windows users running versions of Pro Tools prior to v6 could try using a utility like Header Investigator to 'fix' the sample rate in each of the audio files.

Mac users running a version of Pro Tools prior to v6 on Mac OS9 can use an application called ResEdit:
Launch ResEdit and go to File>Open
Locate the audio file that needs to be fixed
You will get a window with 3 (or more) boxes. Double click on the one marked 'STR' which will show you the resource string for the file.
Look for the line labeled 'Sample Rate' and change the sample rate to the correct sample rate for the file (if it's 48000.00000, change it to 44100.00000 and vice versa, assuming you're working with 44.1 and 48k files).
Save the file and repeat until you've fixed all the files.
You will then need to create a new Pro Tools session at the CORRECT sample rate and choose 'Import Session Data' from the original session.

and set protools default project settings to 44.1 khz for the future, thats the standard rate for audio that is for music. for some reason films often use 48khz rates which is super annoying and has caused so many problems... i've seen people struggle with the sped up audio issue in protools for almost a decade. 48khz doesn't give you any benefit sound wise, it's the dumbest thing every because 44.1khz was chosen specifically to exceed the capabilities of human hearing, anything with a higher sampling rate is just giving you a bigger file size with no improvement in quality and just headaches down the line...

also i'm gonna put my opinion out there that Pro Tools is a piece of junk! seriously in 2014 you shouldn't have this many headaches to get around sampling rates... Reaper automatically converts media sample rates on import, so you can mix and match sampling rates. sometimes i download samples that are off archive.org and were ripped at 22 khz sampling rates... and i basically never even notice because reaper just works with it. if i was still using protools that would just be headaches. seriously reaper does everything protools does but it makes it actually easy to do

... OR, instead of messing about a lot and using drag & drop, for the time being just use the IMPORT AUDIO dialogue (see IMG.1), select the appropriate files and hit CONVERT (lower section & bottom right of IMG.2):


IMG.1


IMG.2

In the future, make sure your Pro Tools project and your MPC project use the same sample rate and bit depth. Otherwise you'll be forced to use the import dialogue all over again instead of drag & drop feature. Some DAWs and sequencers convert automatically on drag & drop, while PT does not.

thank you all for helping me out.