DP6.02 No RMX multi Outs FIXED & Template issue

[frankf]

1. Stylus RMX 1.6 can no longer (ala 6.01, DP5) publish its outputs to DP6.02 bundles
windows, reducing RMX to a single output VI. (Kontakt 3, Mach5v2,
Sampltank2, Omnisphere publish multiple outputs ok). So, if you rely on RMX multi
outs, I don't reccomend the 6.02 update. Don't know if this is an RMX or MOTU issue, but it doesn't matter if you need and can't use the multi outs.

This can be FIXED by installing RMX AU 1.6.1 The RMX installer recommends 1.6.1 only for Logic 8, but DP6.02 needs it as well it seems

2. Also, When template is saved with multiple VIs that publish
multiple outs, (3x Kontakt3, Mach5, Omnisphere, Stylus) and a NEW
Project is created using that template, ALL Instrument BUNDLE
ASSIGNMENTS open UNASSIGNED (same as 6.01) and can be jumbled (eg,
output 3 and output 4 of a VI NOT next to each other or next to 15/16
(ala 6.01). Have to manually reassign all bundles each new project if I use Templates, a
real drag. Restarting Audio System will often unjumble the outs, but
the assignments remain unassigned. I tried this with only 1 Kontakt3,
with similar results.

( I re scanned and trashed preferences, created Templates from scratch - no difference)

Because of this repeatable behavior, I've given up on using Save as
Template or any template that included my multi output VIs (single output VIs are fine as no Instrument bundles are published).
Instead, I have to create a file with the configuration I want to use or Open existing
with configuration I want, delete all MIDI and audio, Flush Undo,
then Save As this empty file to an folder I call My Templates (I check
the Duplicate Audio box to get a project folder). Then I Open this
file and immediately Save As [my project name]. This method retains the Instrument Bundle assignments for the multi VIs.

I reported #2 to MOTU pre-6.02 release. I consider this a bug, in
that in using VIs templates have become useless to me (read way too much workflow interuption).
I must say, it's frustrating that MOTU has not addressed this repeatable issue (and others), one
which disables use of a major function for VI users and one which has been reported.

Still running my VIs with pre-rendering OFF in 6.01, because of re-
load time whenever different VI MIDI track is record-enabled.

[jeepbird]

I don't have problem with RMX multi-out and the corrupted multi-out of my DFH Superior 1 is fixed.
Also I found that the Quickscribe text disappear problem fixed.

New problem found:
Track name becomes "Track-1" when I select "Add similar track" from the project menu. Originally, it should be the same name as the highlighted track with "copy" word added at the end.

So far other things seems fine to me.

[BobK]

frankf: Are you aware that you can export bundles from one project and import them into another? Try that before you rebuild bundles from scratch in a new project.

Track name becomes "Track-1" when I select "Add similar track" from the project menu. Originally, it should be the same name as the highlighted track with "copy" word added at the end.

I don't think this is a 'problem' - it's a change made to 6.02. See the 'New Features' pdf, found in the Help menu.

[Simsy]

Problem 2 happens with Vienna Ensemble 3. Only everuy time I open a project half the instrument outputs are unassigned and I have to reassign them again. Nightmare!!!

[dinobass]

I only get output A with Stylus RMX in 6.02 as well. I also have had the template issue (with input assignments jumbled or grayed-out) in every version of DP6.

[frankf]

I only get output A with Stylus RMX in 6.02 as well. I also have had the template issue (with input assignments jumbled or grayed-out) in every version of DP6.

Solution to this, it turns out is to upgrade RMX plug to 1.6.1 which the RMX installer recommends for Logic 8 only

[James Steele]

YES!!!!!!!!!!!!!

Upgrade! Upgrade! Upgrade!!!!

That's the solution. There's nothing harmful about using 1.6.1 on DP. I even saw a post on MOTU-MAC this morning with someone complaining about this problem and they were using Stylus RMX 1.5! The multiple outs thing is a non-issue if you upgrade to version 1.6.1. I changed the header on this thread to not give the impression that there's no solution to this. There is: use the latest version 1.6.1.

[frankf]

frankf: Are you aware that you can export bundles from one project and import them into another? Try that before you rebuild bundles from scratch in a new project.

Yes, bundles can be exported/imported, but note that when you import bundles, the import doesn't replace the existing, they are added to those existing (in the issue I was describing, Unassigned Instrument bundles) and your busses and Ins/Outs, which necessitates going back and deleting. You then have to go to each pane and delete the doubles. It works, but not a great time saver.

[James Steele]

Okay... I see you changed the header back. I didn't look closely that Templates was still an issue. "Fixed" makes it sound sort of like MOTU fixed it, but if you installed 1.6.1 originally it was never really broken. But yeah... if you held back because it said the fix was for an issue with Logic, I can understand that. I can't recall now, but they may have stated that it wasn't harmful to systems besides Logic to install 1.6.1. I think that's why I went ahead and did it.

[dinobass]

Thanks! RMX 1.6.1 fixed it. I had set up a techlink with MOTU (who told me they couldn't recreate the behavior), and I just sent along this fix to them.

[chaim]

FrankF, I feel the exact same way about the clippings and output stuff.

I thought for a moment that since motu fixed the 'copy' added to all dragged in clipping tracks, that all is good now for dragging templates but I was wrong TERRIBLY WRONG.

This is VERY important and MOTU p l e a s e look in to this ASAP!

When dragging tracks from clipping window, DP should automatically OPEN/activate those associated inputs and outputs.

Same about the Bundles window. This wasn't always like this. But it can be even better. Besides the fact that DP should recognize the ins-outs with the same names when importing bundles and then 'wake them up', dp should allow us to export 'selective ins and out' sort of clipping windows for ins and outs. Right now the whole import export bundles thing is some what un-useful.

[zaque]

I just got bit by the template issue. My orchestra templates from DP5 were not working in DP6 and I was going to scream and/or cry if I had to re-do all of the bundles with each new project. I did find a work around of sorts that seems to get me off the hook of having to reassign all of the bundles which is good...but it's not quite as handy as the [former] "Save as Template" feature.

Create a project that you want to be a template. Make sure you clear the undo history and that you've stripped out everything you don't want (MIDI data, soundbites and audio files, clips, chunks, etc). Save it as a normal DP project but perhaps give it a name like "MyDIYTemplate". Close the project. Next, locate "MyDIYTemplate" project file on your HD. Right-click on go to "Get Info". Click the little box that says "Stationary Pad". This will turn your DP project into a read-only template - not a template in the DP sense, but the Finder will now force you to save a copy of that project the next time you open it in DP. Go back to DP and "Open" the "MyDIYTemplate" project again (notice I said Open and now New). DP will open MyDIYTemplate and load all of the instruments, patches, etc from when you created it but after it is done loading it will open a Save dialog and force you to save a copy of the Template project - call it MyDIYProjectTest or something like that. You'll notice that all of your bundles are in tact (or at least they are on my machine) but the ability to save a template is sort of screwed up - now if you want to edit MyDIYTemplate you need to un-click the "Stationary Pad" option on MyDIYTemplate file, open it in DP, make your changes, save it, close it, and re-add the "Stationary Pad" option. A pain in the @ss to be sure...but not nearly as bad as reassigning an entire orchestras worth of bundles....I can't believe MOTU has left that unfixed after two updates...grrr...

[pacquito]

I'm experiencing this Templates issue as well. When creating a new project file from a template with vi's, all the MIDI track outputs are unassigned. And this is happening not just with multi-out vi's but with all vi's. This renders the Template feature useless, because reassigning output of 16+ MIDI tracks is tedious. In the meantime the aforementioned workaround of just using project files as templates is good.

The curious thing is that earlier templates, created in dp5 I think, open with the outputs assigned.