Thoughts on 1.4 so far

DJ Hellfire wrote:

JAH wrote:

QuickStrike wrote:lol to all the mpc heads who wanted 64 bit real bad and only have 32bit plugins. I lol at you five times.

This is what we've been saying all along! Multicore is more important!

Yeah...I heard some guy here with a number in his handle going deep into that...


Enjoy the update folks looks pretty good.

JAH wrote:If I had to choose between 64 bit and multicore....I would choose 64 bit first. Why? Because I have been running out of Ram even before I maxed out 1 core while using the 32 bit MPC software.

How???? In a beat I used an instance of Kontakt with about 8 different modules (some heavy shit) and you can see in the screen shot this all only 1.5GB. This is everything; drums, melody, bass, percussion, etc. All Kontakt running in 64 Bit. Even if I loaded a bunch of drums I wouldn't even hit 2GB totalNow in this screenshot, I'm on my 3.4 GHz i7 iMac and you can see the CPU meter get's up to 50%. However, on my Studio PC (which is also an Intel Quad Core), this beat chokes the CPU since it's only a 2.4 GHz Q6600 processor, especially when the automation plays. So using one core on a Q6600 is not the same as using one core on an i7. However, if I were able to use all 4 cores on the Q6600, I'd be better off. Pro Tools 32 bit Pro Tools with mulitcore support handles virtual instruments better on my Q6600 than 64 Bit MPC does without multicore support. For what I do, my projects rarely reach 2GB of ram usage, which still leaves plenty of ram for the actual app to run.

What are you running (real world) that you run out of ram?

JAH wrote:But let the count down begin....which company will add multicore support first....NI or Akai?

This is a hard one. Normally, I would think since we haven't really heard anything big from NI about Maschine since 1.8, multicore is the next big thing for them, and soon. But on the other hand, Akai came out of nowhere with Multitimbral support when no one expected it, while we thought they were working on other things. So, I think this could go either way!

DJ Hellfire wrote:

JAH wrote:If I had to choose between 64 bit and multicore....I would choose 64 bit first. Why? Because I have been running out of Ram even before I maxed out 1 core while using the 32 bit MPC software.

How???? In a beat I used an instance of Kontakt with about 8 different modules (some heavy ****) and you can see in the screen shot this all only 1.5GB. This is everything; drums, melody, bass, percussion, etc. All Kontakt running in 64 Bit. Even if I loaded a bunch of drums I wouldn't even hit 2GB totalNow in this screenshot, I'm on my 3.4 GHz i7 iMac and you can see the CPU meter get's up to 50%. However, on my Studio PC (which is also an Intel Quad Core), this beat chokes the CPU since it's only a 2.4 GHz Q6600 processor, especially when the automation plays. So using one core on a Q6600 is not the same as using one core on an i7. However, if I were able to use all 4 cores on the Q6600, I'd be better off. Pro Tools 32 bit Pro Tools with mulitcore support handles virtual instruments better on my Q6600 than 64 Bit MPC does without multicore support. For what I do, my projects rarely reach 2GB of ram usage, which still leaves plenty of ram for the actual app to run.

What are you running (real world) that you run out of ram?

I use the Mach Five. Some of the instruments uses thousands of samples. I would run out of memory before having any issues with my CPU.

Why on earth would you fight having both like all things in the industry except the two that need it most, Re/Studio and Maschine.

More people use complex FX and synth VST's than use multiple GB sample based instruments.

Or have I just imagined the CPU resource needing plugins outnumber multi GB ones by like 50:1 in the industry and everyone's VST?AU folders?

Sigh....

No one is arguing against multicore. The discussion was about which is more important. I gave an example of how a sampler like Mach Five can exhaust your memory.....


Edit - I can load 3 instruments in the Mach Five (F Grand, J Bass, and Mark 79). These 3 instruments alone consumes 2.5 GB of memory and uses 20% of my CPU.

I spent 15 min. just now and im really diggin it.One thing that bugs me is i gotta reinstall some plug-ins in 64-bit now which is no prob but hopefully they all have 64-bit versions.I loaded a 1.3.1 project with only akai plug-ins and it didnt load! gotta error screen.

Audition in chop mode is on point! no more overlapping when going back & forth on chops.Hopefully the ghost start/end points are gone! That was my main thing i had a prob with.I like the lil GUI changes and the software even feels different in a great way.I just spent $100 on records today so im bout to check out what i got and flip one of them joints in 1.4! Ill report back soon.

If you load a 1.3.1 project in 1.4 64 bit MPC software, I suspect it won't load properly. Try loading it in 1.4 32 bit MPC software.

So... no way to use 32 and 64bit plugins at same time?

Montebello wrote:So... no way to use 32 and 64bit plugins at same time?

No. 32 bit MPC software only uses 32 bit plugins. 64 bit MPC software only uses 64 bit plugins.

Any project created on 1.3.1 and early should be loaded in the 32 bit MPC software. Otherwise, they may not playback correctly (if you used plugins) in the 64 Bit MPC software.

64 bit took priority over multicore support, which is about every system ren is being used on, good logic

Liking a lot of what I'm seeing so far!
Looks slick.

Especially digging the plugin list and sorting samples A-Z!

Anyone else having issues with MPC Studio and the 4 q-links columns ?
They don't correspond. Adjusting the END from the cnotroller, without looking at the computer, it actually zooms.

Fanu wrote:A-Z!

A-Ö!

alexbuga wrote:Anyone else having issues with MPC Studio and the 4 q-links columns ?
They don't correspond. Adjusting the END from the cnotroller, without looking at the computer, it actually zooms.

I am not seeing this issue. Use the the 'SCROLL' wheel above the 4 q-links. The 'SCROLL' wheel selects the group of params the q-links will control.