MOTUnation.com

Hi Guys,

I'm trying to simplify workflow between DAW and ext synth.....

When user bank presets change updating them in DP so I have current (correct)
patches. I'm finding that even though I use cherrypicker to create patch lists. The process is still really time consuming and always involves a great deal of hand typing patches....

so,..does anyone have an easier way to keeping DAW and ext synths coinciding?

Thanks in advance.

M

Depending on your hardware, there's always Unisyn. It works fine for my older Yamaha stuff.

cuttime,...Thanks for posting. Without a demo,...it's a shot in the dark.

From what I gather, it's an editor. cool.

But, I'm looking for a way to keep patch names organized between synth/DAW..

If I change some presets rather than having to edit the patches manually.

It would be killer to have an app,..(READ) the synth and update the patch scripts name list.

I suppose this is asking for a lot,...:{

thx though

Yes, Unisyn will do this, provided there is support for your hardware:

http://www.motu.com/products/software/u ... files.html" onclick="window.open(this.href);return false;

If I understand you correctly, if one changes a patch or bank using Unisyn, that patch or bank will show up in DP's patchlist. I'm not trying to sell you on it, it definitely has its quirks and drawbacks; it works for me, though.

I think I'm doing it the other way around.... meaning...


I might change the user bank of say my motif es,...eg....

USR patch list patch 1 was,..."Rhodes",..2,.Brass,..etc,...

I tweaked some settings and changed,..now patch 1 is Moog Lead,..2, is CS Lead,.etc,...

Now,.. I'm lost,...

so I have to open up cherry picker, change the names of the list export it import it into DP etc,..

It wouldn't be so bad if it were just 1 or 2 patches. Lately though depending on the project,.. I might want to change an entire bank,..so all my B3 and deep synth edited patches are in the USR bank.

Unisyn doesn't read the hardware, and update the list in DP,..does it?

thanks again, I appreciate it.

This is where I need a born teacher like Shooshie to chime in:

Unisyn maintains a database and library of patches and banks. If you send a patch from Unisyn to your synth, say patch 1, bank A, the synth will update to the new patch. Unisyn, at the same time, will update the midnam patch list, which will then be displayed in DP's patch list in the track overview for the MIDI track corresponding to that particular synth. IOW, Unisyn updates the hardware and DP simultaneously.

cuttime wrote:This is where I need a born teacher like Shooshie to chime in:

Unisyn maintains a database and library of patches and banks. If you send a patch from Unisyn to your synth, say patch 1, bank A, the synth will update to the new patch. Unisyn, at the same time, will update the midnam patch list, which will then be displayed in DP's patch list in the track overview for the MIDI track corresponding to that particular synth. IOW, Unisyn updates the hardware and DP simultaneously.

A bit confused because,now,without using Uni,.sending a patch change from DP sends it to the synth and the patch list reflects it.

I'll read around for a review of it.

You mentioned that it has drawbacks? would you mind telling what you think they are.

thanks, I appreciate your time.

Cuttime,

nevermind,..per the motu site,. only OS 10.4 support...
seems like the app is dead....

too bad

minimoog wrote:Cuttime,

nevermind,..per the motu site,. only OS 10.4 support...
seems like the app is dead....

too bad

That's weird. I can run it on my Mac running Snow Leopard. I think you just need Rosetta installed and you're okay.

Thanks James,..but the Motu site says,..nothing after 10.4 is supported....

I think that's telling me to stay away.

minimoog wrote:Thanks James,..but the Motu site says,..nothing after 10.4 is supported....

I think that's telling me to stay away.

Well, I already owned it, so I'm not risking my money. In the meantime I won't believe my eyes when I watch Unisyn work on my Mac Pro 1,1 running Snow Leopard.

For what it's worth:

James Steele wrote:In the meantime I won't believe my eyes when I watch Unisyn work on my Mac Pro 1,1 running Snow Leopard.

Is Unisyn working with the Pod? (or not working as the case may be)

bayswater wrote:Is Unisyn working with the Pod? (or not working as the case may be)

First, I tried adding my PodXT using one of the old Unisyn Pod profiles. No surprise that wasn't going to work.

So, I dug out my old original POD (first generation) and hooked up some MIDI cables and created a device for it in AMS, then added the device in Unisyn. It checks out. As long as you have a POD that has a Unisyn profile specifically for it, it looks like you're good. (Again the screenshot below is on my Mac Pro running Snow Leopard)

James Steele wrote:

bayswater wrote:Is Unisyn working with the Pod? (or not working as the case may be)

First, I tried adding my PodXT using one of the old Unisyn Pod profiles. No surprise that wasn't going to work.

So, I dug out my old original POD (first generation) and hooked up some MIDI cables and created a device for it in AMS, then added the device in Unisyn. It checks out. As long as you have a POD that has a Unisyn profile specifically for it, it looks like you're good. (Again the screenshot below is on my Mac Pro running Snow Leopard)

Thanks. Mine might work then. It's the original POD with the V2 ROM upgrade. I think that just changed the sounds and presets, but not the structure. Now I need to find my old copy of Unisyn under the stairs.