Dune V1.4 released!

[Mark]

Actually, I don't think Orion does that directly

It does have support for micro tuning though, so it is possible

[jorgealba]

Hi , today is November 27/2014 Hi bought few hours ago DUNE 1.4 by downloading. before, I was checking it really worked with my CUBASE 7 ELEMENTS and apparently it did fine, sounds are pretty good. and certainly the type of Sounds I want to work with.

Then I bougth and installed DUNE 1.4 full version and I noticed when working on a MIDI file I can assing the synthesizers included with DUNE as intended but every time I stoped the song DUNE changed to the same position again and again to
"027: ELECTRO KITTY RL"
That's anoying. not matter what sound I assigned, DUNE keps doing the same on every music stop, it returns to a default 027:ELECTRO KITTY RL"
Even trying to exporting a WAV file the sound I asigned wasn´t the one recorded..always was playing the same "ELECTRO KITTY"

it never happens when I use HalionSonic, or Prologe instruments , returning to some default type of synthesizer..that´s something I never dealt with before.

is there a solution for that? because I was thinking in a full refund.
THANKS for your attention to my message

[Mark]

I think it is highly probable that there is a program change message in your MIDI file. Have you tried a different one?

[Teksonik]

If memory serves me correctly wasn't there an issue when the "demo" wasn't properly uninstalled before installing the full version ? I seem to remember reading about this before quite some time ago.......

EDIT: Found this. Cubase related.

http://forum.synapse-audio.com/viewtopic.php?f=1&t=9256&p=95168&hilit=DUNE+1.4+PROGRAM+CHANGE#p95168

[jorgealba]

Thanks Mark and Teksonik:

DUNE keeps doing the same with any MIDI file I tried. I Unistalled DUNE demo and DUNE full, and after that I cleaned Windows7's Registry. then Installed Dune 1.4 again, same issue was still Alive

What I found is that converting PROGRAM LIST to VSt PRESET and ONLY working with these saved presets from the TRACK INSTRUMENT's BOX PRESET things will work as intended, you can not change the Patch from any other place hoping it works, it won't..(i.e. DUNE WINDOW)

That means DUNE doesn´t work in the same way that PROLOGE or HALION does, You need to do ajustments in your DUNE's patch, Save it as a VST PRESET and then use it for your Track Instrument.

With PROLOGE you can make any adjustment to your Patch and CUBASE will "remember" your settings.

I still wish to find a way to make DUNE works like PROLOGUE, If you have any other idea I 'll really appreciate it.

[Kriminal]

Is it because cubarse doesnt support .fxp/.fxb anymore?

[dmassive]

Is it because cubarse doesnt support .fxp/.fxb anymore?

I have Cubase 7 Elements and that files are supported, I use it a lot to share vst presets between Orion and Cubase.

[Kriminal]

Is it because cubarse doesnt support .fxp/.fxb anymore?

I have Cubase 7 Elements and that files are supported, I use it a lot to share vst presets between Orion and Cubase.

maybe its vst3 format that doesnt support it.... or full cubarse....

[Marcin]

Ok, solved. The midi clip contained just the program change message.

[jorgealba]

YES, INDEED MARCIN!!! thanks so much...If you don't mind I would like to add the link you sent me on how to erase the "Program Change" on Cubase.

[Mark]

Great that it's solved

A program change message in your MIDI file, eh? Who'd have thunk it?

[Teksonik]

DUNE keeps doing the same with any MIDI file I tried.

The same program change in every midi file....who'd have thunk it ?