Thoughts on 1.4 so far

finally 1.4!!!

didnt sleep last night

after a day testing out i relly like it as well and i agree it seems snappier in general.

what i really dig is:

THE AMP ENVELOPE!!!! i didnt expect and ahdsr type one!

no more 10 second time limit

load sample on the fly/while the sequence is playing

the new sample edit feature

double tap shift button

and other stuff i dont remember now...(really need to sleep), also im glad they didint cripple "the vintage mode tweak"

So IMHO a solid update.


Now what i really like to see in 1.5 is multicore support and at least 32 stereo output so finally i can mix on the fly as plug-in in ableton/pt

Rewire also it will be the icying on the cake!

Geez... why is everyone assuming i'm an idiot "use the scrollwheel". I know how to use the damn thing very well. It's a bug and Pete finally acknowledged it

you have 4 columns of Q's in the app, but when you edit the Loop from harware you actually edit the END from the software.. they're inversed somehow.

JAH wrote:

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.

You can still run the mpc software 1.4 in the 32bit mode, it was in the release notes in the zip file. Probably for people who still want to use 32 bit plugins. On mac, you have to go to applications, find MPC application, right click, get info... and I forgot the rest

InspectahEX wrote:

JAH wrote:

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.

You can still run the mpc software 1.4 in the 32bit mode, it was in the release notes in the zip file. Probably for people who still want to use 32 bit plugins. On mac, you have to go to applications, find MPC application, right click, get info... and I forgot the rest

...you then just enable "Open in 32-bit mode" and vice versa to re-enable 64-bit mode.

andreat668 wrote:Now what i really like to see in 1.5 is multicore support and at least 32 stereo output so finally i can mix on the fly as plug-in in ableton/pt

Rewire also it will be the icying on the cake!

If Rewire support means that I can record and playback REN midi into and from Logic's sequencer, then +1,000!

GedaBlaq wrote:

andreat668 wrote:Now what i really like to see in 1.5 is multicore support and at least 32 stereo output so finally i can mix on the fly as plug-in in ableton/pt

Rewire also it will be the icying on the cake!

If Rewire support means that I can record and playback REN midi into and from Logic's sequencer, then +1,000!

Giving that a quick thought, the ReWire master and slave implementation is what has to be analyzed.

When ReWire is used one of the two apps has to be the master, the slave app has it's MIDI sequencing disabled.

For example if Live is the ReWire master and Reason is the slave, Reason can only respond and be triggered over MIDI from the master, in this scenario Ableton. Then it has assignable audio outs by skipping Reason's mixers and plugging your Reason modules directly into the Reason routing interface that is always at the top of the rack in all situations. The I/O of the interface module will be list of I/O addressable to the ReWire master for your routing purposes.

So I think that in the question you posted that situation would need the Ren to be the ReWire master so it could still have it's sequencer and MIDI tracks operational and Logic would have to be slaved and have it's MIDI disabled. So you're almost right back where you started in reverse.

ReWire's main function is to give you full MIDI/Audio routing options but in the one direction way I've described above. Essentially most usages are to use one app as a sound module and have the ReWire master application control all MIDI, the appropriate MIDI tracks in the master being sent to the slave and the slave audio output routing sent to armed tracks in the master.

What you describe likely wouldn't work give the limits of the ReWire Master slave operation. Or having to have your main host's MIDI disabled while the Ren is ReWire master enabled to control Logic, which again just seems like a new set of problems to deal with.

What you want is probably best handled in a simpler fashion by changing the internal MIDI operations of the Ren's virtual MIDI outs or some kind of physical MIDI cable workaround and some user routing as people have been doing when hitting a wall with bi-directional MIDI routing and recording of the data.

JAH wrote:

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.

Wow! I have to look into Mach Five. How's it sound?

Well I be damned bruh, this 1.4 just created a slammin beat all by itself

I'm about to be rich

They also did some optimization i think, it takes a lot less CPU power then before! My performance bar in studio one has droped 15-20%

crucial question: is undo button working properly?????

cpm31 wrote:crucial question: is undo button working properly?????

It is so far for me, I've used it quite a bit and it's acted as expected. No WTF moments

Metatron72 wrote:

GedaBlaq wrote:

andreat668 wrote:Now what i really like to see in 1.5 is multicore support and at least 32 stereo output so finally i can mix on the fly as plug-in in ableton/pt

Rewire also it will be the icying on the cake!

If Rewire support means that I can record and playback REN midi into and from Logic's sequencer, then +1,000!

Giving that a quick thought, the ReWire master and slave implementation is what has to be analyzed.

When ReWire is used one of the two apps has to be the master, the slave app has it's MIDI sequencing disabled.

For example if Live is the ReWire master and Reason is the slave, Reason can only respond and be triggered over MIDI from the master, in this scenario Ableton. Then it has assignable audio outs by skipping Reason's mixers and plugging your Reason modules directly into the Reason routing interface that is always at the top of the rack in all situations. The I/O of the interface module will be list of I/O addressable to the ReWire master for your routing purposes.

So I think that in the question you posted that situation would need the Ren to be the ReWire master so it could still have it's sequencer and MIDI tracks operational and Logic would have to be slaved and have it's MIDI disabled. So you're almost right back where you started in reverse.

ReWire's main function is to give you full MIDI/Audio routing options but in the one direction way I've described above. Essentially most usages are to use one app as a sound module and have the ReWire master application control all MIDI, the appropriate MIDI tracks in the master being sent to the slave and the slave audio output routing sent to armed tracks in the master.

What you describe likely wouldn't work give the limits of the ReWire Master slave operation. Or having to have your main host's MIDI disabled while the Ren is ReWire master enabled to control Logic, which again just seems like a new set of problems to deal with.

What you want is probably best handled in a simpler fashion by changing the internal MIDI operations of the Ren's virtual MIDI outs or some kind of physical MIDI cable workaround and some user routing as people have been doing when hitting a wall with bi-directional MIDI routing and recording of the data.

Thanks for the education and advice Metatron. I really appreciate it. What I want to do is to make Logic the master and REN the slave. I just want to be able to, via MIDI, open REN as a VST/ AU inside of Logic, assign internal REN sounds to REN pads inside of REN VST, start record on Logic's sequencer, hit the REN's pads, have the REN's MIDI out data recorded into Logic's sequencer, stop Logic's sequencer, Return to beginning of sequence via Logic's sequencer, hit play on Logic's sequencer and have Logic play back the sequence I just recorded with REN's internal sounds.

I hope that I don't come off as a smart a$$, and I truly love my REN period. It's just that this functionality seems so second nature with today's technologically advanced DAW's, plugins and their respective architectures, that I'm just absolutely and utterly baffled as to why this either can't be figured out with the REN or the functionality was intentionally left out of the REN. If the REN was never designed to be a DAW as some here believe, then why cripple it's ability (it has MIDI ins & outs) to be fully MIDI integrated into a DAW? I understand that REN integrates better via MIDI into PT than Logic but so ******* what? I prefer Logic.
(whew) End of rant.

Pete, if you ever read this, I want to personally thank you for all of the dedication and hard work you've put into 1.4 and making the REN my most beloved piece of gear, seriously. I know you are hard at work making it even better. At some point, would you please address the REN's MIDI implementation into Logic? Again, thanks Pete and be Blessed!

Doesn't seem like a rant to me, this stuff gets complicated even when the thing you want to do is simple at it's core, like routing MIDI over two apps. And I pulling for the Ren just personally it would duplicate too much functionality I already other ways. And I'm cool with that being like Live+Nocturn Automap+HW MPC.

But clearly housing most of that functionality in one place/controller/app has crazy appeal. So I just read all the posts here out of general gear interest and being excited on your guys behalf as it all comes together.

Double check the Rewire info I had just woke up and it was off top, but still pretty sure it wouldn't quite solve the issue with one of the two, but there may be a chance certain apps that can be slave or master in Rewire might even slaved be able to catch the MIDI output so I hope there's exceptions. Trouble is often an app can only operate as one or the other, it's easy to look up the master/slave limitations and There's real clear info at the Propellerhead site, they still own tech and license it.

if you ask me if i'd want this rewire lark at the expense of other features being implemented i'd say no thanks
i just love the ren as a standalone piece first and foremost
i'd just rather see the hrs put into making the ren with more improved features in the tradition of classic machines work flow.
we have no idea how long and time consuming it would be to implement compared to
improvements that would benefit the whole.

the thing is if they bundle pro tools with it their not exactly gonna been over backwards
for a competitor either.
i'd say yes to your request if it was a simple afternoons work.
i have to say i'm no a fan of logic great sounds but illogical to use.
that is no a diss on anyone using it i take my hat off to them

Yeah it's main use would be to use another app as a sound module rack. So for the guys that use Reason it would be fantastic, they could use the standalone with Reason rewired in, and not need the Host DAW until the end.

But as a general solution to MIDI routing it's not really the answer overall. There are some plugins that offer it but it's quite rare. The competition part gets put aside usually because a license fee is paid and it's an expected feature in a full DAW. But this isn't a full DAW and there are much easier ways to solve any MIDI routing limits you guys might have.