Pro tools m-powered 8 with any interface?

  • Thread starter Thread starter StudioMxpx
  • Start date Start date
S

StudioMxpx

New member
im asumming that i can use any inteface with m-powred since it has a ilok..am i right? or do i need a m-audio inteface? i have a line 6 Ux2 that im using as a interface for guitar and vocals..and i have a midi interface that i use with my roland eletric drumset..using Steven Slate Drums with cubase, will all this work the same with Protools M-powred 8? sorry for all these protools questions..im very new to how pro tools works.. it seems like another world of recording then cubase lol.
 
You must use one of the supported M-Audio interfaces. No way around it. Period.

You can use the midi interface with Pro Tools.

Not sure about Steven Slate Drums - check their website.
 
Right, you must use an m-audio device and the ilok. Samples are samples and MIDI is MIDI, all that stuff will be just fine on ProTools.

On a sidenote - My curiousity is peaked - Why switch from Cubase to ProTools M-Powered? That's like switching from PT HD to Cubase LE. It seems illogical to go from a full version of one to a crippled version of another - why do it? (I actually have PT M-Powered, too - I got it with my ProjectMix back when it first came out, and I do use it to convert PT sessions into wav files to import into Cubase, and vice-versa for exporting to PT for other people... just wondering what your reasoning is, since, judging by your asking about the Steven Slate thing and the MIDI questions, you are obviously planning on actually recording and mixing in PT-M).
 
im actully just looking for a diffrent program to mix on..i dont like cubase..plus i wanna check out the rta plugins that pro tools offers.

i bought m-audio fasttrack interface that came with pro tools m-powered 8 essential a few weeks back..i wonder if that interface will work?
 
im actully just looking for a diffrent program to mix on..i dont like cubase..plus i wanna check out the rta plugins that pro tools offers.

I see - well, that answers my question. If you don't like it, you don't like it - hopefully you'll like ProTools-M better, then :)

i bought m-audio fasttrack interface that came with pro tools m-powered 8 essential a few weeks back..i wonder if that interface will work?

Well, don't sit around wondering, lol. This took like 27 seconds to find - literally. It has already taken me more time to type this sentence :p - Google is pretty cool like that. http://www.digidesign.com/index.cfm?langid=1&navid=54&itemid=28796
 
On a sidenote - My curiousity is peaked - Why switch from Cubase to ProTools M-Powered? That's like switching from PT HD to Cubase LE. It seems illogical to go from a full version of one to a crippled version of another - why do it?

please explain....what makes M-powered crippled when compared to Cubase? I have never used Cubase, so dont think Im attacking....but Im very curious to see what would make you say that...
 
please explain....what makes M-powered crippled when compared to Cubase? I have never used Cubase, so dont think Im attacking....but Im very curious to see what would make you say that...

The easiest answer to your question is that the full version of Cubase (which used to be called Cubase SX and now is simply "Cubase") is on par with ProTools HD. I mean - Nuendo is Steinberg's "flagship", so a comparison between Nuendo and HD would also make sense, but Nuendo's really geared more towards film and post-production stuff. All of the features that are relevant to recording and mixing music are in Cubase - it's not a crippled version of Nuendo is what I'm getting at. There have been, however, various crippled version of Cubase over the years (SE, LE, Studio, VST, and probably some more I'm forgetting) that all have "reduced functionality" like PT LE and PT M-Powered do. So, comparatively, it's like stepping down from PT-HD to PT-M or PT-LE. Does that make sense?

I considered listing out all the exact differences, but after looking around for a bit - I think it will take more time than it's worth to gather them all up for a full comparison, and I really think the "Cubase is to PT-M-Powered as PT-HD is to PT-M-Powered" analogy sums up the result that would be gained from such a discussion anyway.

And yea - I'm definitely not attacking either - A studio I used to work at had a C24 (with PT-HD, naturally), and I've worked with it extensively. I think PT and Cubase are both very intuitive and it goes without saying that both their audio-engines are top-notch. In fact, if I thought the C24 was worth the money I would probably just run PT HD myself. I really do like the software...and not having to convert to and from PT through my copy of M-Powered wouldn't hurt my feelings either :D. I hope that sums it up.
 
im still not gathering what you mean by crippled...do the same plugs work? other than track count, which you failed to mention, I just dont understand....you said you started to list all of the exact differances....could you give me what you consider to be the top 3 or 5 differances? again...I havnt used the software, but Im very curious as to what cripples my M-powered and what I might be missing out on...
 
im asumming that i can use any inteface with m-powred since it has a ilok..am i right? or do i need a m-audio inteface? i have a line 6 Ux2 that im using as a interface for guitar and vocals..and i have a midi interface that i use with my roland eletric drumset..using Steven Slate Drums with cubase, will all this work the same with Protools M-powred 8? sorry for all these protools questions..im very new to how pro tools works.. it seems like another world of recording then cubase lol.

There's a big Sticky thread at the top of this forum, specifically marked "READ THIS FIRST!!" and strangely enough, the answer to your question is in there. You can't miss it.

:rolleyes:
 
im still not gathering what you mean by crippled...

A crippled version of a program is a version that the developers intentionally removed certain functionality from. Simple as that. If the word "cripple" bothers you, then pretend I said "reduced functionality", or even "full functionality impaired" or whatever you don't take issue with, ffs.

do the same plugs work?
Actually no - at this point you can't compare Cubase directly to ProTools, however. They're just different. VST is not RTAS. Yes, there are "adapters", and whether or not those adapters negatively affect the plugins is not something that I care to discuss because it's boring and I don't care. TDM plugins don't work with M-Powered for hardware reasons. They can with HD systems. So no, the same plugs do not work, but there's still no direct comparison any way you look at it.

other than track count, which you failed to mention, I just dont understand....you said you started to list all of the exact differances....could you give me what you consider to be the top 3 or 5 differances? again...I havnt used the software, but Im very curious as to what cripples my M-powered and what I might be missing out on...

I'm getting the feeling that your non-confrontational tone was BS. I didn't "fail to mention" anything. I clearly explained that I don't care to have a discussion about it. To elaborate further: It's always a boring rehashing of the same old shit. Also, I was trying to be more polite than just saying this: LMGTFY. Further reading: LMG this FY, too.

Now, in the interest of ending this - and with the clarification that I'm simply not going to debate how much any of these handicaps actually matter to engineer X in studio Y recording music style Z: Here you go, top 3 differences (last time I checked) -

1. Track-count limitations
2. No automatic delay compensation for plugins
3. Lower maximum sampling rate

The point is that those are ways that DAW developers cripple cheaper versions of their software, it's not a Cubase vs ProTools issue. It's a full version vs crippled version issue. Neither PT-HD nor Cubase has those restrictions. PT-M-Powered, however, does.
 
Last edited:
sorry you feel like I was tryin to start a pissing contest...im genuinly curious as to what made you say some of what you said...again, I have never used cubase...only Adobe Audition and protools....I can do the same thing in either of them...im just more comfortable doing some things in Audition rather than protools... and i feel like I can learn cubase and accomplish the same there....there may be different ways to getting the same product...what im asking is what can you do in cubase that you absolutly can not do in some way or another in m-powered?
 
sorry you feel like I was tryin to start a pissing contest...im genuinly curious as to what made you say some of what you said...again, I have never used cubase...only Adobe Audition and protools....I can do the same thing in either of them...im just more comfortable doing some things in Audition rather than protools... and i feel like I can learn cubase and accomplish the same there....there may be different ways to getting the same product...what im asking is what can you do in cubase that you absolutly can not do in some way or another in m-powered?

Like I said before, it's not a Cubase VS Pro-Tools thing, it's a full version vs not full version thing - if you read my original comment - it's always been about that.

I don't know why you asked the same question even after I finally gave in and answered it. Are you looking for something like "You can build skyscrapers in Cubase but you can only build doghouses in ProTools M-Powered" ? There's no difference like that, if so.

The three things I listed before are the main three things that you can do in a full version of Cubase (or ProTools HD) that you absolutely can not do in ProTools LE or in ProTools M-Powered (last time I checked, of course, but I bet it's still the same case). I can't believe I'm listing these again, but here you go:

1. You can record and mix unlimited numbers of tracks,

2. All processing delays introduced by effects (whether they be software plugins or external, hardware, effects units used at mix-time) are automatically compensated for, whereas you must set that delay compensation manually in M-Powered.

3. You can record and mix with no software-imposed limits on your sampling rate.
 
Eff it, if we're gonna do this, then let's do it all the way - The next place this conversation goes is to the workarounds for these limitations:

1. You can have multiple sessions, or bounce tracks down more often - some people think that's a pain in the ass, some don't: I do.

2. You can manually measure the delay comp for all your shit, then store the times in a text file and type them into ProTools every time you insert that unit from then on. Some people think that's a pain in the ass, some don't: I do.

3. There's no workaround for this one, so the next place this conversation goes *every time* is "how much does the sampling rate really matter, the nyquist theorem says that sampling over approximately 40,000 hz is unnecessary". Well, some people would still think it was better even if God himself came down and said "Thou shalt not sample over 40 KHz because IT DOESN'T MATTER YOU FOOL". I think it's retarded, but I also think that if some potential client have it in their head that they must record their shitty source material at 192KHz because producer Pimp-Mastah-Fresh said in Recording-For-Playas that it made things more "airy" and "warm" and some other buzzwords that don't mean anything, then I damn well better be able to do it, or he's gonna take his stupid idea, and his not-so-stupid money, to somebody that can.

gaaaahhh, you broke my will to resist this - I hope you're satisfied now! :D
 
oh...well....if thats all...I havnt missed out on much....


thanks...
 
I have used Cubase for about 8 years. I like the interface, I think it's very intuitive, and I think that it's very easy to use.

I have used Pro Tools for the past 4 years, and I think it wins every single time over Cubase.

One of the greatest benefits of Pro Tools over others, is the way in which it deals with dropped samples. Cubase ignores them; you have NO idea whether or not every single sample has been properly processed, and quite often there are mistakes. Pro Tools gives you the option of turning off these error messages, but they are set to come on as default. This way, if there is a computational error, you know about it, instead of sweeping it under the rug. This was certainly the case the last time I used Cubase anyway.

Secondly, the failure rate with bounces when I used Cubase was phenomenal. I'd sometimes have to bounce the same project 4 or 5 times, until I got a complete bounce. In Pro Tools I think I have only ever had one failure. This is simply not acceptable in what is supposed to be a professional programme. There are also a huge number of bugs (which I have experienced.) and they seem to go unfixed - whereas Digi are pretty quick to give out updates if there's a serious bug.

TyphoidHippo:

I'd like to address a couple of points you made in your previous couple of posts. Firstly, Pro Tools HD does not allow you to record an unlimited number of tracks. There are still a maximum number of voices and tracks which you can have simultaneously. But then I would not want there to be an unlimited number. The more tracks you have running, the more it loads the system, and the more likely it is for you to have errors. The limit is there so that you don't try to exceed your system's capability. The "unlimited track count" of other programmes is a myth; there's still a limit, and the closer you get to it, the more crap your system will run. Unlimited track count is also a marketing tool, make no mistake about that. There's also the issue that for a home recording, if you can't make 48 tracks work for you, you're doing something seriously wrong.

Secondly, your argument about sample rates is so unbelievably flawed, and definitely shows a lack of understanding of the sampling theory. Sure, Nyquist says that you need a sampling rate of at least 40 KHz to sample a 20 KHz signal. True. However you cannot sample anything of greater frequency than 20 KHz with that sampling frequency. "Sure, well we can't hear above that so who cares?" Well... if we allow the input signal to exceed the Nyquist rate, then we'll get aliasing. There are plenty of supersonic signals floating about with just about any instrument you care to mention. So... it becomes necessary to design a low pass filter (anti aliasing filter in the A-D converter and reconstruction/anti imaging filter in the D-A) to remove these supersonic signals. Now you go and design me a filter which can have an infinite slope of cut off above 20 KHz. You can't. You can get fairly close, but you cannot do it, especially in analogue circuitry (which this filter needs to be, being in the analogue domain...). The next issue with these steep filters is that they cause phase-distortions across the entire audio band. So it would be nice if we could design a shallow filter, which would be cheaper, and easier, and leave less phase problems, wouldn't it? So there are two options - band limit the audio further down (say 12 KHz?), or increase the sample rate to leave more room above the audible range for this low pass filter. I know which one I would choose.

I'm not advocating the use of super high sample rates, I'm really not. However it really narks me when I see such a fundamental theory to our field so badly represented in text.

Anyone who's interested in more should read two books:
"The Art of Digital Audio" John Watkinson and "Digital Audio Principles" Ken Pohlmann.
 
Hi pezking. Great post, and while I still don't want to debate the merits and how much certain things matter or Cubase vs ProTools - I just want to say that this:
Secondly, your argument about sample rates is so unbelievably flawed, and definitely shows a lack of understanding of the sampling theory. Sure, Nyquist says that you need a sampling rate of at least 40 KHz to sample a 20 KHz signal. True. However you cannot sample anything of greater frequency than 20 KHz with that sampling frequency. "Sure, well we can't hear above that so who cares?" Well... if we allow the input signal to exceed the Nyquist rate, then we'll get aliasing. There are plenty of supersonic signals floating about with just about any instrument you care to mention. So... it becomes necessary to design a low pass filter (anti aliasing filter in the A-D converter and reconstruction/anti imaging filter in the D-A) to remove these supersonic signals. Now you go and design me a filter which can have an infinite slope of cut off above 20 KHz. You can't. You can get fairly close, but you cannot do it, especially in analogue circuitry (which this filter needs to be, being in the analogue domain...). The next issue with these steep filters is that they cause phase-distortions across the entire audio band. So it would be nice if we could design a shallow filter, which would be cheaper, and easier, and leave less phase problems, wouldn't it? So there are two options - band limit the audio further down (say 12 KHz?), or increase the sample rate to leave more room above the audible range for this low pass filter. I know which one I would choose.

I'm not advocating the use of super high sample rates, I'm really not. However it really narks me when I see such a fundamental theory to our field so badly represented in text.


Are good points and I agree - somebody should have corrected me. I posted too hastily and I was incorrect on the points you outlined. Well, like you said, I represented them poorly. Have some green chicklets :D

Also - thajeremy, you're right. You haven't missed out an anything. It's not a big deal, arguably not even a deal at all - not really worth the time to discuss ;)
 
Thanks for reading that all how I intended :)

I just finished my degree thesis/project/dissertation which centred around a particular argument regarding the higher sample rates. Needless to say I had to do an extensive amount of research on the info, so I'm very well versed in it all.

I would definitely recommend those two books to anyone who's interested in digital audio and the science behind it.
 
Hi pezking. Great post, and while I still don't want to debate the merits and how much certain things matter or Cubase vs ProTools - I just want to say that this:


Are good points and I agree - somebody should have corrected me. I posted too hastily and I was incorrect on the points you outlined. Well, like you said, I represented them poorly. Have some green chicklets :D

Also - thajeremy, you're right. You haven't missed out an anything. It's not a big deal, arguably not even a deal at all - not really worth the time to discuss ;)

I didnt get any green chicklets??? :p
 
Secondly, your argument about sample rates is so unbelievably flawed, and definitely shows a lack of understanding of the sampling theory. Sure, Nyquist says that you need a sampling rate of at least 40 KHz to sample a 20 KHz signal. True. However you cannot sample anything of greater frequency than 20 KHz with that sampling frequency. "Sure, well we can't hear above that so who cares?" Well... if we allow the input signal to exceed the Nyquist rate, then we'll get aliasing. There are plenty of supersonic signals floating about with just about any instrument you care to mention. So... it becomes necessary to design a low pass filter (anti aliasing filter in the A-D converter and reconstruction/anti imaging filter in the D-A) to remove these supersonic signals. Now you go and design me a filter which can have an infinite slope of cut off above 20 KHz. You can't. You can get fairly close, but you cannot do it, especially in analogue circuitry (which this filter needs to be, being in the analogue domain...). The next issue with these steep filters is that they cause phase-distortions across the entire audio band. So it would be nice if we could design a shallow filter, which would be cheaper, and easier, and leave less phase problems, wouldn't it? So there are two options - band limit the audio further down (say 12 KHz?), or increase the sample rate to leave more room above the audible range for this low pass filter. I know which one I would choose..



well said =) I was about to post this, till i actually read the rest of the thread =)

I use 48khz and 96bit, far more than i need for an audio cd, and far more than i need for mp3 =)

also, the higher the order your filter, the steeper the curve, so if you made a 5gazillionth order filter then it would be as close to vertical as poss [but still wouldnt be perfect](but would cost a fortune (in parts if it was physical, or in processing power if it was virtual)) you can get round the phase issues using various methods (adding in a sliding window would be one way, but only works with virtual stuff, and causes its own problems, like having to compensate for the sample slip)
 
Starting from scratch

I am starting with a mac and a m-audio sound interface and I don't have the software. At this point all fingers point to Pro tools m-powered 8. My question is: does it come with the Ilok USB in the package?:confused:
 
Back
Top