MeldaProduction

dark-i · Post by **dark-i** » Fri Apr 04, 2014 12:56 pm

Hi, you can already do that!

Just change the alpha (opacity) of the color of the track

.[/quote]

HI, I have tried, but even at the highest alpha it is still very transparent.

MeldaProduction · Post by **MeldaProduction** » Fri Apr 04, 2014 3:46 pm

Wait, you want to increase opacity???

dark-i · Post by **dark-i** » Fri Apr 04, 2014 3:50 pm

DarkStar · Post by **DarkStar** » Fri Apr 04, 2014 3:51 pm

MeldaProduction wrote:
DarkStar wrote:That reminds me, when I load the plug-ins, with no audio going through them the meters on the bands show levels > -300. As in (chosen at random):

MP_Meters.png
Is that my noisy system? Or rounding? Or ... ?

-----------------------------
Sneaky FR: I really would like a way to Search the Help pages (even a Ctrl+F would do.)
No no, it's the denormalization fix - simply put, Intel processors don't like to work with certain numbers, particularly very small ones. If you do that, they kind of change it's floating point mode into high precision one, which takes waaaaay more CPU. So hosts & plugins fix that by adding some negligible numbers/noise into it. -300dB is way under audible range of any human (will ever be able ) and audio interfaces, so it doesn't matter at all.

Oops, I should have explained better. -300dB is fine; I was wondering why the other levels were more than -300 dB

MeldaProduction · Post by **MeldaProduction** » Fri Apr 04, 2014 4:15 pm

No idea, some kind of inaccuracy or post processing. In these levels the differences are really irrelevant.

DarkStar · Post by **DarkStar** » Tue Apr 08, 2014 5:34 pm

Short version: I find automating some parts of the plug-ins difficult
---------------------------------------------------------------------

I'm just having a look at automating some of the controls in the plug-ins.

Findings:
The maximum length of the parameter names visible in various DAW hosts is 24 characters. Consequently many appear to have the same name: "Multiparameter X - Param", "MIDI controllers - Contr" and "MIDI Note controllers - ".

If I go to the first Multiparameter in the (MCompressor) plug-in and touch the default parameter (Gain) Value slider, it shows up in the host as "Multiparameter 1 - Value, with the correct dB value. And when I touch the default parameter (Gain) Maximal Value slider, it shows up in the host as "Multiparameter 1 - MaxVa, with the correct dB value.

I then added "Attack" and "Release" to the Multiparameter parameter list. When I touch any of their Value / Max Value sliders, they show up as "Multiparameter 1 - Param" with generic 0-100% values (call them A, B, C and D for the moment).
A and B control the Attack parameter
C and D control the Release parameter
If I then delete "Attack" from the list, so that I now have "Gain" and "Release" only
A and B now control the Release parameter.

It is similar for the MIDI Controllers. Each controller has 5 automatable controls (oddly, they are not detected as parameters in the host when they are changed). All of the controls have the same name in the host.

-----------------------------------------------------
So I have a few problems:
(a) the names visible in the host are not unique; perhaps "Multiparameter X" could be abbreviated to "MPX" (where X is 1 to 4), "MIDI Controllers - Contr" to "MC - something" and "MIDI note controllers - " to MN - something".
(b) the names seen in the host do not reflect the target control; in my scenario above, I would like to see in the host:
MP1: Gain - value
MP1: Gain - max value
MP1: Attack - value
MP1: Attack - max value
MP1: Release - value
MP1: Release - max value
Similar to other plug-ins which can dynamically publish parameter names to the host (no idea how

)
(c) the appropriate values and units for each parameter should be published to the host, just as they are for the default (Gain) parameter in the Multiparameter,
(d) when the Attack parameter is removed from the list for the Multiparameter, the mapping from host parameter control to target parameter in the plug-in should not change.
(e) perhaps the "MIDI controllers" and "MIDI note controllers" should not appear as plug-in parameters at all - after all they are designed for direct control by MIDI CC messages or notes (unless I have misunderstood).
(f) but, if they are published as plug-in parameters, when a MIDI Controller parameter is touched it should be detected in the host , just as touching a Multiparameter control is detected.

Phew!

MeldaProduction · Post by **MeldaProduction** » Tue Apr 08, 2014 7:56 pm

I'm afraid none of this will happen DarkStar. This is a problem of hosts, not the plugin!!! And NOTHING can be renamed, it would stop working in existing projects. So no, absolutely not.

Inside the plugins, everything is checked and has 100% backward compatibility. The names in MIDI settings are not completely visible, you already told me, and it is solved, it's now bigger. It may still not fit in certain styles + certain names probably, but you can always show it by selecting it anyway.

Anyway what host are you using? Some of the things you described I don't really understand

, how about a short screen video?

In any case, the existing parameter names can NOT change.

DarkStar · Post by **DarkStar** » Wed Apr 09, 2014 9:34 am

Vojtech, thank you for your reply.

You are right about the displays in the "MIDI Settings" window; "Futuristic" uses a wider font and the longest names in the list are not fully shown, but, as you say, the full name can be seen be clicking the name in the list.

As for the names seen in the host, I have done some screenshots and will email them to you. But for other readers, here is just one to show what I mean:

<< pic removed>>

It's from XT2 and shows 4 different parameter lanes for MCompressor. I had set up 3 parameters (Gain, Attack and Release) in the parameter list for Multiparameter 1. The screenshot shows 24 characters of each parameter name. Perhaps XT2 can only display the first 24 characters - and longer names may be completely visible in other DAW hosts.

MeldaProduction · Post by **MeldaProduction** » Wed Apr 09, 2014 10:13 am

Well, first of all what you are doing is quite extreme. But most of all, you can even see how much space is available there, so you should ask XT2 devs to use more than 24 characters

. Not me, I cannot do anything about it. You were saying how in hosts (I implicitly added "all"

) it does that (which I wouldn't be able to solve either), and it's just XT2...

CableChannel · Post by **CableChannel** » Wed Apr 09, 2014 2:50 pm

I just checked in Cubase 7. You get displayed the first couple of letters, then dots, then the last couple of letters. If you hoover over the parameter a tooltip with the complete name is displayed.

DarkStar · Post by **DarkStar** » Wed Apr 09, 2014 5:40 pm

Extreme? me? ... well, perhaps

Perhaps I need to change my host

CableChannel · Post by **CableChannel** » Wed Apr 09, 2014 7:10 pm

Here a screenshot in Cubase. Well it is not ideal either, the field for the parameter name is fixed size, it does not take all the space that is available. So the displayed name is shortened pretty badly. Anyway at least the name shortening is intelligent (you see the beginning and the end), and in addition you have the mouse over tooltip with the full name.

goldglob · Post by **goldglob** » Thu Apr 10, 2014 8:20 am

DarkStar wrote:Extreme? me? ... well, perhaps

Perhaps I need to change my host

Reaper can alias parameter names, but hang on, you know that already Darkstar.

_dada_ · Post by **_dada_** » Thu Apr 10, 2014 7:13 pm

MAutoAlign freezes Cubase 7.5.20.
One instance works fine. Add another = freeze.

Jan

MeldaProduction · Post by **MeldaProduction** » Thu Apr 10, 2014 8:02 pm

_dada_ wrote:MAutoAlign freezes Cubase 7.5.20.
One instance works fine. Add another = freeze.

Jan

Thanks! Already solved

(hopefully

) . Just a few more days!

MeldaProduction

KVR Audio

8.00 beta 3 for all MeldaProduction effects has been released!