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

[adagiocm]

hi lads...
sorry guys, after 28hours (including 12h night shift)...
11 x MinimogueVA + ...
...
another silly project...

Very nice sound! But it looks like your submission went to the Minimoog V group by mistake. Hopefully V'ger or Irion can correct it.

[cactoos_dahoo]

i don't know mate... it was uploaded/shared before deadline, but thanks anyway

regards,
cts

[adagiocm]

i don't know mate... it was uploaded/shared before deadline, but thanks anyway

regards,
cts

Yeah, I know you shared before the deadline. Probably they opened the Minimoog-V one before the deadline, and you selected it by mistake? Since the two alternating Soundcloud groups have almost identical names, it is too easy to mix them up. I'm sure it can be corrected.

[IrionDaRonin]

Yeah, I know you shared before the deadline. Probably they opened the Minimoog-V one before the deadline, and you selected it by mistake? Since the two alternating Soundcloud groups have almost identical names, it is too easy to mix them up. I'm sure it can be corrected.

Yes, it can be done. I just sent a message to cactoos to share the track in the correct group. I will accept it (or V'ger) today i must go.
And then the other track can be deleted without problem.

There is a trick when you share tracks to not get wrong.

When you are going to share a track, just share the track with the group WITHOUT the orange asterics, that means that is being moderated (it is closed to submissions), so share the track to the group without the orange little asterics.

Have a good day

[V'ger]

Ok submissions now closed. Voting thread is here. Good luck all.

@Cactoos: Just share with this group: http://soundcloud.com/groups/kvr-one-sy ... ge/dropbox (and unshare with the other one)

[cactoos_dahoo]

well done. thanks for your help guys.

[gunnare]

Having problems with this synth, i still don't know what special thing people see on this one.

Crashing, FL Studio errors, Synthedit timeout when suspend error, presets which don't want to load (doesn't sound), CPU peaks when opening new instances...

Anyway i will try it, but i lost all my patterns, automations for now... And is not funny, to be honest...

Even with the multicore option deactivated, still giving me problems...

Back from holiday. Trying to do a little debugging in FLS. I have problems to play the synths from my midi-keyboard. All midi-ports are OK in the settings window. And I understand the system that mixer slot1 is midi channel 1 , and slot 2 is channel 2 and so on. But no midi seems to go into the slots.

I spent 1 hour to get the plugins scanned. Seems like FLS is quite unique and totally unlike any other hosts I have tried. I did some debugging 2 years ago, and was through the same problems.

To compare with reaper: Set audio and midi settings and scan for plugins under settings.
Then select "Insert new vst instrument", and you are ready to record. The instrument is automatically mapped and armed. FLS seems to be more aimed at pattern programming with mouse.

Any help about how to play a VST instrument in FLS?

All the best
gunnare

[gunnare]

Ok, I got it sorted. How to play hardware keyboard with FLS: There is a little button below midi-inputs in the settings page. You have to click the "Enable" button to activate each midi-input. In Reaper you have to go to preferences - midi_devices, then right click and select "Enable" from the dropdown list. And select "enable+control" if you want to use it for transport and CC control. Maybe useful information for someone just starting out.

All the best
gunnare

[V'ger]

Cheers again for the support and prizes Gunnar, it was a good competition I think with many and good entries. There will always be some issues with plugin/DAW, can't think when that wasn't the case, even for the last ones from big companies like Arturia and now Synapse and it's with typically FL too so don't put too much into it as it may be that it's really FL that should do something about their 'wrapper' thing maybe.

[gunnare]

Cheers again for the support and prizes Gunnar, it was a good competition I think with many and good entries. There will always be some issues with plugin/DAW, can't think when that wasn't the case, even for the last ones from big companies like Arturia and now Synapse and it's with typically FL too so don't put too much into it as it may be that it's really FL that should do something about their 'wrapper' thing maybe.

I never told you what actually happened. As a Synth-edit betatester I decided it was time to get more real-life testing, so I released the MinimogueVA with oversampling intentionally to get bug reports. I had been betatesting it since october and it worked fine in Reaper. I am feeling very alone in the debugging process. Most SE developers do nothing. (There are some exceptions like Tubeohm) I dont mean to cause any problems, but somebody has to do the dirty work. Then you mailed me about the competition, and I almost knew what to expect. Ok, many of the freeware synths are Synth-edit, so you have helped the debugging of SE 1.2. So big thanks to One Synth Challenge for helping. Many of the bugs would have taken maybe more than 6 months to find. I have recreated all bugs reported in FLS today.

We must have SE 1.2 finished as soon as possible so we can begin with the 64 bit version. Jeff is already working on it.

All the best
gunnare

[V'ger]

Yes but then at least some good came out of it for the synth too. Would also like to point out that having the Arturia Moog right after was because of the timing of the freebie's release date and prize donation etc so just a coincidence really.