MSoundFactory concept & template round #3

[MeldaProduction]

Ha! Such a conversation about volumes . Ok, so I hope I'll clarify things:

- CC#7 is MIDI standard for volume and if should imho control the volume. But the current situation isn't ideal, because it is hardwired to the volume knob, which is also the one available on the easy screen via MP, but changing volume doesn't change the MP, so... So I propose that it won't be hardwired and instead mapped via MIDI settings to the volume MP directly, hence available from the easy screen and via volume CC at the same time.

- Volume normalization should be done via the Gain parameter and is automatic! You don't need to normalize stuff manually, because all you need to do is click the "Set" button in the right toolbar . It would internally play same notes, render the output, measure its LUFS and set the gain to match some hardwired value. Simple, quick and effective.

- Volume parameter MP location - I still think Globals tab is ideal for now, but please vote here:
viewtopic.php?f=138&t=516506
Since the volume normalization is automatic, designers shouldn't use it and should leave it default for the end users anyways.

nichttuntun: Actually our main concern now is to allow the easy screen to be a proxy for an universal instrument easy to use for everyone. Sure, creative minds can dig into the edit screen and do some superwild stuff, but it needs to be easy to use and exhaustive in the first place.

[nichttuntun]

Okay. I got that. Makes sense from the developers view

[Chandlerhimself]

I didn't know the set button worked like that. That amazing and will save a lot of time.

Has anyone else checked out the new features in MSF? I'm loving the wavetable import. I tested it with some wavetables made for serum and it seems they are importing more accurately than before. Having this ability to import pre-made WT and make our own easily is great. Does anyone know the difference between Wavetable8. Wavetable40 and Wavetable256. I can't figure it out, but I'm sure there is a difference. Also I finished making about 20 wavetables. I'll attach them below. If you like some of them hopefuly we can use some of them as the factory wavetables in MSF. I hope others also contribute some they make.

https://drive.google.com/file/d/1f-YmrZ ... sp=sharing

[nichttuntun]

I didn't know the set button worked like that. That amazing and will save a lot of time.

Has anyone else checked out the new features in MSF? I'm loving the wavetable import. I tested it with some wavetables made for serum and it seems they are importing more accurately than before. Having this ability to import pre-made WT and make our own easily is great. Does anyone know the difference between Wavetable8. Wavetable40 and Wavetable256. I can't figure it out, but I'm sure there is a difference. Also I finished making about 20 wavetables. I'll attach them below. If you like some of them hopefuly we can use some of them as the factory wavetables in MSF. I hope others also contribute some they make.

https://drive.google.com/file/d/1f-YmrZ ... sp=sharing

Hi Chandler,
yes. WT-import is great

8, 40 and 256 is the amount of slots you have within a WT which can contain a single cycle. 256 = 256 possible waveforms in a row for your WT. But thats optional. You can choose to have e.g. only 10 if you like but you can´t choose 10 if you are in WT8-mode.

Cheers

@Voijtech:
did you improve the sound generating engine in version 12xx? I was blown away yesterday by the sheer sound quality MSF produces now. Tested on Sennheiser HD650.

A BIG THANK YOU for the MDrummer Studio 2018 update...that is generous and the amount and quality of the samples is simply amazing!

[Touch The Universe]

- Volume normalization should be done via the Gain parameter and is automatic! You don't need to normalize stuff manually, because all you need to do is click the "Set" button in the right toolbar . It would internally play same notes, render the output, measure its LUFS and set the gain to match some hardwired value. Simple, quick and effective.

Brilliant Tested this on mpowersynth and works just great This will save time for sure

[Touch The Universe]

Really... who will buy and use MSF to make a super-saw?

I don't see a need to think this way. A lot of people, including me, test a synthesizers capabilities on how well it can produce a supersaw sound. It's a good idea to build up from the supersaw's capabilities. Make that as good as possible and it'll help add to the success of the synth as a whole, imo. It's not just a sampler like kontakt right, so make make the synth stuff great. I can't really request anything too specific, but make it good

I know a lot of devs are busy and don't spend time on other competitors products, but I think it's a mistake. I'd suggest spending an afternoon or two with Lush-101, Spire, Dune 2, Sylenth and test there supersaw stuff. Then work your magic, listen again and compare, tweak, until you make something even better

[dmbaer]

I'd suggest spending an afternoon or two with Lush-101, Spire, Dune 2, Sylenth

Ahem ... don't you mean Dune 3?

Dead on about Lush-101, however. I really don't know that magnificent sound virtual instruments doesn't get a whole lot more love.

[MeldaProduction]

Hey folks, thanks for the feedback .

nightuntun: No no, the engine is the same, so I doubt it sounds better . But if so, even better

Touch the Universe: I'll check the other synths. Btw. would you mind getting me some feedback to the current supersaw? Any ideas? Would you like to improve it?

[Touch The Universe]

It's pretty good, pretty bright and sounds clean like some of the mids are scooped out. I'm trying to figure out where all the highs are coming from and it seems linked to the resonance, like there is a lot of saturation going on.

I'll need a bit more time to explore it though. I've been meaning to ask, is the synth engine the entirety of mpowersynth?

It might be helpful to have the widening feature on the main gui preset page, especially if the idea is to stack the oscillators. I like to have each oscillator or layer have its own stereo depth. Particularly, I like to add much more detune to the lower oscillators then make this as narrow as possible, so the width of the detune/unison is important enough to include on the gui imo. Hopefully, others agree.

The massive detune preset is also pretty interesting. It definitely has its own sound and its very bright.

Need more time with it...

[nichttuntun]

It's pretty good, pretty bright and sounds clean like some of the mids are scooped out. I'm trying to figure out where all the highs are coming from and it seems linked to the resonance, like there is a lot of saturation going on.

I'll need a bit more time to explore it though. I've been meaning to ask, is the synth engine the entirety of mpowersynth?

It might be helpful to have the widening feature on the main gui preset page, especially if the idea is to stack the oscillators. I like to have each oscillator or layer have its own stereo depth. Particularly, I like to add much more detune to the lower oscillators then make this as narrow as possible, so the width of the detune/unison is important enough to include on the gui imo. Hopefully, others agree.

The massive detune preset is also pretty interesting. It definitely has its own sound and its very bright.

Need more time with it...

"massive detune-preset"? Did I miss something in 12.10? Can´t find such a preset.

[Touch The Universe]

Apologies, it's Mega Unison

[nichttuntun]

Okay. Thank you

[dmbaer]

dmbaer- you actually can hook things up to MPs by using the modular module. You can save them and recall them easily.

I finally see what Chandler is talking about - but I presume he meant the ModularEx module (a fairly new development that I just discovered yesterday) which has 64 MPs that can be stored and recalled with a ModularEx preset. Brilliant!

However, I seem to be unable to get those MPs to show up on the Easy screen. Maybe this is by design, or maybe I'm missing some key way to make this happen. If the latter, what's the trick?

If the former, this is not at all unreasonable. It would not be overly labor-intensive to get all the tricky stuff done in the modular level MPs and simply connect top layer MPs on a one-to-one basis. Although, what would be extremely powerful would be a group select/copy function that could establish top-level-to-lower-level MP linkages in one quick operation.

I do think that, if the modular MPs cannot be visible, a number of fields in the MP editor window should be disabled when the MP is a lower-level modular MP. I'm talking about fields like Group Name, Group Color ... basically anything having to do with display characteristics.

Don't get me wrong - I'm not complaining here. This is an awesome new capability that I'm sure I'll get a great deal of mileage out of.

[dmbaer]

I finally see what Chandler is talking about - but I presume he meant the ModularEx module (a fairly new development that I just discovered yesterday) which has 64 MPs that can be stored and recalled with a ModularEx preset. Brilliant!

OK, I tried putting together a real-life semi-final preset using a ModularEx in the Generator section. Unfortunately, I found it to be much less effective than originally hoped. Specifically, the inability to use the lower-level MPs to control envelopes and LFOs means that most of the hoped for encapsulation of controls can't happen. Maybe this was just that I picked a bad situation to try this on, but I'm not seeing this as something that one can get a lot of mileage out of at the moment.

[MeldaProduction]

touch the universe: We can certainly add the widening and stuff to the Supersaw if that's what you mean, but I wouldn't add to everything really. I'd leave it to the preset designers probably.

dmbaer: I'm not sure what you were discussing, but what is the problem with using ModularEx and accessing it?