One-Synth-Challenge 41: Minimogue - Submissions and gossip

[IrionDaRonin]

That happened to me about one year ago with MiniMogue VA. I remember that i said to V'ger long time ago.

Did you sort it out?

No in that time, because we just were scoring synths, and making short tests. Due i didn't use Minimogue in that epoque i didn't try to sort it out.
I hope you can do it. And anyway the developer is here with us, so he should know what to do in any case

[Doc Jon]

I'm getting the muting issue as well in Cubase 6.5 (64bit) on Windows 7, can't quite work out what triggers it yet

Not a complete deal breaker at present as reloading the project makes all good again, will see how it goes...

[bzur]

I'm getting the muting issue as well in Cubase 6.5 (64bit) on Windows 7, can't quite work out what triggers it yet

Not a complete deal breaker at present as reloading the project makes all good again, will see how it goes...

Try disabling the multicore support, it seems to work.

[EDIT] no, it doesn't work I think actually is a midi issue, as Cubase receives the midi input, but the data is not seen by / passed to Minimogue.

[gunnare]

Nice to see here the developer in person

I've a problem in Cubase Studio 4 on win7, LUXUS version: after some minutes the synth mutes itself; it seems it still receives midi data, but no sound at all.

I don't know if this issue is in common with the VA version, as Cubase sees the LUXUS only - I'll change the dll folder, let's see.

I'll try again disabling multicore features, and the usual troubleshooting tricks I'm used to.

The multicore problem was solved 3 years ago. I dont think that is the problem.
VA-and LUXUS has the same VST-ID number. Otherwise it would be impossible to load VA patches in LUXUS. Some hosts will display VST-instruments with same VST-number and different name, some will not. I think Reaper and Mixcraft will display all versions, and you are correct, Cubase will not, so you have to choose one version.

I am a SE betatester and we are in the final bebugging stages. The SE community is very small these days, and I have to do this dirty work. A lot of SE developers are waiting for me to finish the betatesting. It is not like it was in the old days. Some problems is to be expected when using the new SE 1.2 beta. I am almost surprised that things work so good. The big news are oversampling and polyphony control. We have betatested since november 2011.

I have reported all bugs (and the FL bug) to Jeff. This is probably bugs in the synth-edit beta that we have to sort out. He already has a list from me this week.
Hopefully he can solve the FL bug this month. He updates Synth-edit almost every 14 days.

Please do the crash reports as detailed as possible, with host and windows version.

All the best
gunnare

[gunnare]

I'm getting the muting issue as well in Cubase 6.5 (64bit) on Windows 7, can't quite work out what triggers it yet

Not a complete deal breaker at present as reloading the project makes all good again, will see how it goes...

The synth is not 64 bit host compatible. Did you bridge it with J-brige?

All the best
gunnare

[gunnare]

One thing to check:
Please install the synth in the correct way - copy both the dll. and the folder that has the same name as the dll. to your VST-plugins folder.

Crashes may be caused by missing instrument folder.

All the best
gunnare

[dwringer]

Well for what it's worth, I have been saving my presets as "external" through FL Studio 8, and they do seem to be saved properly.

When I have more than one or two of these VSTi's running, especially with oversampling as discussed above, presets do start sounding different, occasionally loading multiple instances of the VST or switching between presets a lot during a single session will result in certain parameters not being set properly, and it leads to a sound other than what the patch is supposed to be.

I do believe it is indeed all a CPU issue, because I have taken to rendering each part in its own FL Studio project file, importing .wav files of the other parts to mix with, then exporting the part and rebooting FL from scratch. I then repeat the process/move around between projects to change stuff.

This does seem to be a bit of a headache, but I cannot live without the 32x oversampling feature as the richness in tonality is absolutely incomparable and ultimately this seems like a small price to pay. If they'd had digital multitracking with sequencing of this caliber, and the ability to switch their mono synths into polyphonous mode, back in the 70's, there'd have been a studio willing to pay six or seven figures for that kind of "convenience".

So I'm having loads of fun so far. It would be pretty awesome if this synth had been hand coded in assembly with all kinds of cutting edge metaprogramming techniques, but I do not look a gift horse in the mouth.

If it helps anyone, I left FL Studio in WinXP SP3 mode with multithreading off as an artifact of last month's Augur competition (in native Win7 x64). Some of my problems may be a result of this, I may have avoided other problems this way - it's anyone's guess.

But it definitely seems that a heavy CPU load causes inconsistent performance in all aspects of this synth; only solution - lower it!

[V'ger]

Unexpected issues but thanks for helping out with them Gunnar.

Both versions works fine here in REAPER Win XP 32 and sounds great oversampled. Even at x32 it's not crazy on the CPU. And a joy to tweak a 'normal' layout again.

[mr president]

Ive just completed a quick tune with minimogue and a few effects, where do you send your finished tracks and what do you win?? i just saw the title and had a go since it was a good idea to just be using the one synth. Amazing what you can do when limited to just one synth

[V'ger]

Cool, just click the link under 'Submissions' here.

The prizes are listed on the same page and also in the first post of this thread.

[gunnare]

I am a Reaper user, so it should work fine in Reaper. FL-studio users may use the old version until we have sorted it out. Be warned: The old version has the dual-core bug with multiple instances.

[gunnare]

Well for what it's worth, I have been saving my presets as "external" through FL Studio 8, and they do seem to be saved properly.

When I have more than one or two of these VSTi's running, especially with oversampling as discussed above, presets do start sounding different, occasionally loading multiple instances of the VST or switching between presets a lot during a single session will result in certain parameters not being set properly, and it leads to a sound other than what the patch is supposed to be.

I could recreate this in Reaper. It is a bug - some parameters sounds like they have changed when using oversampling with several instances. Everything should work fine with all instances oversampling set to "off". Thanks for the help!

All the best
gunnare

[mr president]

Cool, just click the link under 'Submissions' here.

The prizes are listed on the same page and also in the first post of this thread.

Cheers, ill upload today

[mr president]

I am a Reaper user, so it should work fine in Reaper. FL-studio users may use the old version until we have sorted it out. Be warned: The old version has the dual-core bug with multiple instances.

Ive bought memorymoon and messiah and i like very much. I dont want to make this out wrong but i dont know if the oscillators are affected by aliasing in the very top frequencies. this is the only problem i have with them, they nearly match some proper synthesizers at 10 times the cost. I was wondering if you might
implement anti aliasing oscillators in the not too distant future. Im currently waiting to buy the ME80 and wish i had got it first after i tried demo.
Nice work by the way

[SKYZONE]

Yes V'ger i do have the same problem like irion when i close down fl studio , but during playing have no problem so far , has it something to do that i still use
a older computer pentium 4 ?
I use mouge va and mouge luxus in combination so far no problem .

So i try to play further and see the effect i let you know , so far i made one piece .

Intresting to follow this further............



With regards


Fabrizio