Hey folks, so a new beta is here, fixes/hacks a lot of stuff, plus some more features and the final version of MDrumStrip is pretty much ready!
Check it out and let me know if you find any problems.
Plus a little poll - I enabled the rainbow analysers by default:
I started to quite like it. You? It's one click for disabling of course, but still...
https://www.meldaproduction.com/downloads
CHANGES:
Released MDrumStrip, free for MMixingBundle, MTotalBundle and MCompleteBundle users.
[MSoundFactory] Added tempo sync for the grain rate and duration in the Granular sampler.
[MSuperLooper]: Changed loop length display format to 2 decimal places.
[MDrummer] Sending rooms & ohs to one of the sends now works even if the channel is actually muted. That allows for listening to send channels only.
Added “Rainbow opacity” setting to analyzers.
Added “Normalize above 0dB” option to analyzers, on by default.
[MDrummer] Fix: Clicking Solo for a room/oh tracks in mixer didn’t work properly.
[MSoundFactory] Fix: Several instruments produced unnecessary DC offset. It has been filtered out in the new version.
[MSoundFactory] Fix: Instrument GUI did not resize correctly with high DPI settings in OS or high plugin GUI style percentage size.
[MSoundFactory] Fix: Edit mode plugin GUI didn’t update correctly when a pop-up was active.
[MSoundFactory] Fix: Multiparameter caption buttons sometimes didn’t update their visual state when enabled/disabled by other multiparameters.
[MDrummer] Fix: Rewinding could fail to disable the previous rhythm being played.
[MSuperLooper] Fix: Fixed recording in Sync mode when no loop was selected.
[MSuperLooper] Fix: Note off behaviour on start/stop recording.
Fix: VST2 and VST3 GUI plugin size issues under macOS with multiple displays.
[MDrummer] Fix: Sends of utility channels haven’t been saved properly.
[MDrummer] Fix: Drumset designer couldn’t preview hihat and toms.
16.06a beta + MDrumStrip + a little poll
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 3729 posts since 3 Nov, 2015
As of right now the poll is, in the same order as above :
50%
33%
17%
Which effectively means :
50/50
For that matter having two 'no' options makes no sense except to divide the outcome ?
50%
33%
17%
Which effectively means :
50/50
For that matter having two 'no' options makes no sense except to divide the outcome ?
-
- KVRAF
- 1759 posts since 11 Nov, 2009 from Northern CA
It's very pretty ... but what is it showing us?MeldaProduction wrote: Sun May 21, 2023 11:49 am Plus a little poll - I enabled the rainbow analysers by default:
-
- KVRAF
- 3729 posts since 3 Nov, 2015
What is the actual meaning of the 'No' option ?
I mean, were there for the GUI styles :
Do you like Neon JP ?
Do you like Woody ?
Do you like Vintage ?
Do you like Bakelite ?
Do you like Titanium ?
Before adding them to the plugins ?
"It's one click for disabling of course, ..."
Where is the 1-click option to change the appearance of the graph ? It's already 2 clicks to get to the graph settings w/o making any choice.
I mean, were there for the GUI styles :
Do you like Neon JP ?
Do you like Woody ?
Do you like Vintage ?
Do you like Bakelite ?
Do you like Titanium ?
Before adding them to the plugins ?
"It's one click for disabling of course, ..."
Where is the 1-click option to change the appearance of the graph ? It's already 2 clicks to get to the graph settings w/o making any choice.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- Topic Starter
- 14339 posts since 15 Mar, 2008 from Czech republic
It is basically color coding the frequencies, so that you may get used to red being bass, yellow low mids etc.
-
- KVRian
- 965 posts since 12 May, 2019
I don't mind but when Band Graphs were added, was that suddenly a part of every preset unless disabled? All the sudden I noticed these extra buttons (didn't but 2 and 2 together reading the release notes) and had to disable that feature, iirc. As long as it doesn't change my existing presets, I don't really care.
That said, can you please consider allowing us to add more than one Area? For example, I am now using Keyboard 2 fairly often but want to add another I've been experimenting with. The way you can implement it is, you know how we can customize the y-axis height for user-defined Areas? We could just stack multiple Areas in a similar way. We already have transparency so all we need is y-height (row number). If not, it's ok but I think having the piano plus other zones could possibly help more users than just me.
My number 1 gripe by far for MAutoDynamicEQ is the Q handles on the band nodes. I don't know if they're too thick or what but when two nodes are close together, I find it hard to grab the one I want. Because of this, I often set the nodes' frequency then adjust Q in the Bands panel. It's fine but I feel like it's a minus for usability. Maybe if the nodes' opacity changed during Mouse Over that would help select the node I want. Just an idea.
Overall, the Melda experience feels pretty mature so I'm not craving a ton of features at the minute. Of course, I'm still looking forward to Mix Revolution! Anyway, thanks for the update and congrats. My thousand bucks is really going far!
Cheers.
That said, can you please consider allowing us to add more than one Area? For example, I am now using Keyboard 2 fairly often but want to add another I've been experimenting with. The way you can implement it is, you know how we can customize the y-axis height for user-defined Areas? We could just stack multiple Areas in a similar way. We already have transparency so all we need is y-height (row number). If not, it's ok but I think having the piano plus other zones could possibly help more users than just me.
My number 1 gripe by far for MAutoDynamicEQ is the Q handles on the band nodes. I don't know if they're too thick or what but when two nodes are close together, I find it hard to grab the one I want. Because of this, I often set the nodes' frequency then adjust Q in the Bands panel. It's fine but I feel like it's a minus for usability. Maybe if the nodes' opacity changed during Mouse Over that would help select the node I want. Just an idea.
Overall, the Melda experience feels pretty mature so I'm not craving a ton of features at the minute. Of course, I'm still looking forward to Mix Revolution! Anyway, thanks for the update and congrats. My thousand bucks is really going far!
Cheers.
-
- KVRist
- 247 posts since 24 Aug, 2013 from South Korea
Voted to Yes.
I like new Rainbow style.
But how about 'custom defined default' setting?
If make possible to setting default presets of 'spectrogram', 'processing shape of compressors'... would be nice I think.
I like new Rainbow style.
But how about 'custom defined default' setting?
If make possible to setting default presets of 'spectrogram', 'processing shape of compressors'... would be nice I think.
Ambient artist and sound designer to get chickens.
http://www.weatherm.net/
http://www.weatherm.net/
-
- KVRAF
- 10368 posts since 2 Sep, 2003 from Surrey, UK
The dark grey areas of the and curves look too dark to me.
And,, can the colours of the various "Areas" presets be changed to match the Rainbow colours?
And,, can the colours of the various "Areas" presets be changed to match the Rainbow colours?
-
- KVRian
- 632 posts since 19 Aug, 2020 from the top of the charts
Seriously, Melda guy, I like your software, but you are not a pro when it comes to colors. Colors have meanings. Colors can be contrasting. Color choices make something beautiful or ugly. You seem to use color completely randomly in your software.
Bright red means warning, but you use a saturated red in your VU meter. The red on the left is brighter, but it doesn't mean warning (HP+LP).
Pink means female. So why are saturation and analog pink? The pink and green button colors also clash with the dark blue background. Some people have an eye for this. Some have to learn it by reading. So read about color theory or let someone else make the color decisions.
Green means OK like in a traffic light. So the green Active is alright. But the neon green "Edit" and "Band graphs" clash with the background again.
Rainbow colors mean gay or children.
You can't just assign different meanings to colors like you would in a programming language. Men are hardcoded.
Bright red means warning, but you use a saturated red in your VU meter. The red on the left is brighter, but it doesn't mean warning (HP+LP).
Pink means female. So why are saturation and analog pink? The pink and green button colors also clash with the dark blue background. Some people have an eye for this. Some have to learn it by reading. So read about color theory or let someone else make the color decisions.
Green means OK like in a traffic light. So the green Active is alright. But the neon green "Edit" and "Band graphs" clash with the background again.
Rainbow colors mean gay or children.
You can't just assign different meanings to colors like you would in a programming language. Men are hardcoded.
If you plan on purchasing your first Universal Audio hardware, you can get a free additional plugin. Just send a PM.
-
MirkoVanHauten MirkoVanHauten https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=376111
- KVRist
- 457 posts since 12 Mar, 2016
Makes the plugin more cluttered. And it's also very confusing when the colors of the eq bands don't match that of the rainbow area they're in.
It runs on my machine! Everything else is undefined behavior.
-
- KVRian
- 1281 posts since 3 Jan, 2020
I think the rainbow is pretty, and I like pretty, so I'm all for it.
That would be good.DarkStar wrote: Mon May 22, 2023 5:35 pm And,, can the colours of the various "Areas" presets be changed to match the Rainbow colours?
-
- KVRist
- 377 posts since 19 Jul, 2013 from Chile
Colors have meanings. Yes, cultural meanings that vary quite a lot and MeldaProduction products can be found worldwide.wangeroge wrote: Mon May 22, 2023 6:57 pm Seriously, Melda guy, I like your software, but you are not a pro when it comes to colors. Colors have meanings. Colors can be contrasting. Color choices make something beautiful or ugly. You seem to use color completely randomly in your software.
Bright red means warning, but you use a saturated red in your VU meter. The red on the left is brighter, but it doesn't mean warning (HP+LP).
Pink means female. So why are saturation and analog pink? The pink and green button colors also clash with the dark blue background. Some people have an eye for this. Some have to learn it by reading. So read about color theory or let someone else make the color decisions.
Green means OK like in a traffic light. So the green Active is alright. But the neon green "Edit" and "Band graphs" clash with the background again.
Rainbow colors mean gay or children.
You can't just assign different meanings to colors like you would in a programming language. Men are hardcoded.
If there is a common meaning for the Meldaverse users, that is scientific based, which btw it is so the choice of colors presented to us here. The spectrum from red to purple, that is from low frequency to highest visible, corresponds quite well will the sounds frequency length variation.
As a side note, your particular takes on certain color meanings could actually be considered sexist or ageist; "Pink means female" and "Rainbow colors men gay or children" and hence offensive for people of all ages and sexes tuned to present times' perceptions.
For a more science based view on this stereotyping see; https://www.researchgate.net/publicatio ... munication together with a summarized article; https://www.bbc.com/future/article/2014 ... ender-myth
Plus, for the data that shows that this is a quite recent prejudice read the following Forbes article: https://www.forbes.com/sites/shelleyzal ... henomenon/
-
- KVRian
- 703 posts since 28 Oct, 2014
Personally, I would say:
Bass = dark blue or purple
Mids = dark green, fading to lighter greens
Highs = yellow! (fading to white, if you like)
This is the colour coding I use when building tracks, and it feels totally intuitive
Bass = dark blue or purple
Mids = dark green, fading to lighter greens
Highs = yellow! (fading to white, if you like)
This is the colour coding I use when building tracks, and it feels totally intuitive