sample tempo query

Is it possible to speed up or slow down a sample? I apologize if this has already been covered. I tried doing a search and didn't come up with anything. I appreciate the help thanks.

MPC2kxl, shift+6, DRUM?, PARAMS and edit the TUNE of the sample. At this point touch the pads to edit the sound you want..

or you can do it from the trim scriddeen mane....

Like Swissmaster says, this is a more accurate way of tampering with tempo/pitch, though tuning within the program is a valid way of doing things. Benefit to tuning within the Trim screen is it gives approximate tempo information on the loop page once you input the proper number of bars, etc. This means you can slow a beat down to match the proper tempo for your sequence, etc.

-tank.

Thanks guys.

dknows2 wrote:Is it possible to speed up or slow down a sample? I apologize if this has already been covered. I tried doing a search and didn't come up with anything. I appreciate the help thanks.

to quote charlie brown, "good grief". I mean, come on dude, just start pressing buttons if you don't have the manual. I don't mean to be a dyck, but seeing stuff like this is heartbreaking. I don't know, maybe its just me, but I think its quite depressing to see people get a wonderful machine like an MPC and seemingly not even play with it for a month before they start asking simple questions. Isn't there any fun in actually learning the machine without resorting to online tips?? I always felt better figuring things out on my own, but I guess its just me.

I'm the same way, I like to figure things out on my own..
I will normally not ask. I read the book then read it again while
playing with the machine. The third time I didn't need to the book.
Now it is used as a door stop, or a prop thrower (throwing stuff at my boys who are acting stupid/crazy during recordings-haha)

People learn differently. I've spent months figuring out the older Cubase without any help from anyone and got so sick that I quit using it. I then found a site that addressed the questions I had, and have appreciated "online help" every since.

Seriously, this site is the worst in regards to pointing people to their manuals. How hard is it to answer some simple questions that someone has obviosuly not figured out on their own? How do we know they didn't read the manual anyway? I feel bad for those cats who buy the units and can't find the help to use them and end up selling them.

Plus, how do we know some of these cats don't have a reading comprehension level of a 4th grader?

Ego, what site was that?

Cubase 5 is **** wit me. I can't seem to control a midi track with my controller!! the midi monitor on the transport bar react to my key presses, and my input is activated, the midi track is selected, no filtering except for sysex, channels are set right, it just won't record or controll a VSTi.

this shit is itching me...

elmacaco,

This is one of the most common reported problems w/Cubase and VSTi's.
I'll find the link and post it for you. Quickly I did a search under Cubase midi problems and found several threads outlining the same problem. I use Cubase SX, and the conflict I was having was related to my USB Oxygen controller. Some people claim it's an audio driver conflict- but my problems are sporadic, and seemed to go away after setting up Cubase correctly with my audio card (Delta 410)

What audio card are you using?

delta 66.

The thing is, I had it working before, using the same interface (midiman biport 2/4s).

I tried re installing all drivers and Cubase, still nada, makes me think it is a setting I am missing in cubase.

Cubase gets the midi, but miditracks and VSTi's don't respond.

This is crackin my noggin!

It's a good thing I'm not too sensitive Boogie Man. Then again I guess that wouldn't matter, huh. I hope I'm not being a dyck. I'm just kidding, man. No offense taken. Some of you cats are way advanced, not to say that my question was about any advanced technique because it wasn't. I realized that I already know how to speed up/slow down samples but, there may have been a better way to do it.

Thanks for all of the input.