On Sun, Mar 9, 2014 at 11:57 AM, Atte <[email protected]> wrote: > Hi > > I have a project where I need to lower the volume of the piano in the > chorus. So I inserted a ladspa "simple amplifier" in the strip. First I > should say that it was extremely hard *not* to crash non-mixer working with > this. Not sure what I had to do, but it was easy :-) A few other comments:
If you're experiencing crashes then please submit a bug report as described here: http://non.tuxfamily.org/wiki/BugReports Just because it's easy for you to trigger the bug doesn't mean it will be for me, so a backtrace from you can save me a lot of time in figuring out where the problem lies. > > 1) The simple amplifier has values in db, 0 is neutral, -70 i minimum. I > found that the 0 of the control curve translated to 0db all right. However > the closest smaller amount I could convince the mouse to insert was -0.04, > next 0.07, next, 0.11 and next what I settled for) 0.15. The later > translates to -10.4 db. So two problems here: 2.5db are rather large > intervals and second; very odd to edit in one scale when it actually is > transformed into another scale. I guess it's a bug... Yeah, I have a plan to deal with this kind of issue by allowing the user to define the automatable range of controls in Non Mixer, but it's not exactly a simple matter. > > 2) In the heat I also tried to insert a gain instead. This led to some > confusion when I was to connect it to a parameter since it was tricky to > distinguish my "lower-the-chorus" gain from the master fader on the strip. > Again (as mentioned in an earlier post) renaming the modules would be really > great here. One sure way to crash the mixer, btw, was to connect to the > "wrong" gain, remove the connection, and connect the right one... What was the confusion? Between "Gain" and "Gain.1" you mean? They are named in order of appearance in the signal chain. > > 3) Again with simple amplifier: Although the curve shows a flat line to the > first control point, the control is actually sending the minimum value (in > this case setting the simple amplifier to -70db). Same in the end. So one > needs to insert a control point before and after the song. Would be great if > the sending would correspond with the graphics of the line, so these at the > start/end of song points are not needed. Submit an enhancement request... > > 4) In ardour one can grab the middle of a control line segment and > raise/lower the whole line including the points that defines its endpoints. > Would be great to have something similar in non. Submit an enhancement request... > > 5) Actually the way I would have preferred to do this was to set the > attenuation in a simple amplifier and then switch it on in all choruses and > bypass is elsewhere. All choruses needs the same treatment and this way I > would be able to change one value and have it affect all choruses. > Unfortunately it's not possible to control bypass switch of a module in non. > Would this be possible to add? I think there's already an enhancement request for this ;-) It's not quite as simple as it sounds, because few LADSPA plugins are actually capable of bypass. And not all module routings are either (for instance, how would you bypass an Ambisonics panner? Not really possible). So to make a long story short A) making all LADSPA plugins bypassable is not possible and B) those that can be made bypassable will require extra buffers and copying in the bypassed mode and this will have memory and performance impacts. Don't forget that you can already automate gain/mute, though, so doing in/out mixing on entire strips is possible and may be simpler than bypassing individual modules anyway.
