LUNA PreRelease 8b

Official support for: mutools.com
RELATED
PRODUCTS

Post

muzycian wrote:Can you please elaborate? Which FRs? Thanks.
I went back through the old thread and dug out my submissions:
1) I think there will need to be some zoom in/out on the plugin setup area, so that it's easier to concentrate on wiring particular bits up. I'm finding the "grab points" for connecting and deleting cable rather touchy to find because they seem to be very small -- maybe they could grow as the mouse passes over/near them to make them easy to hit and shrink back otherwise?
I think this is better in PR8, but need to spend a little more time. I don't recall getting frustrated when I played a bit the other night, so this one may be a "don't care" at this point.

2) If the lines in the plugin area are analogous to cables, then it would be nice to be able to re-route a signal by grabbing the destination end of a cable and dragging it to a different input. You could possibly use a left drag to move the cable and a right drag to create a new connection from the existing cable's source to the new plugin's input.
You asked how to handle this if there were multiple cables. Maybe the idea would still work if the user clicked anywhere in the last about 1/3 of the cable, toward the destination end. That would eliminate ambiguity about which cable.

3) A highlight mode, enabled and disabled through the plugin area's context menu, so that as you mouse over things, they "light up" along with their connections to nearest neighbors. A variant would be that mousing over a dummy would light up all of the paths from that to the audio output. Something like this would make it easy to trace signal paths and, especially, to locate unintended connections you'd forgotten about in a complicated setup.
This one has been dealt with nicely. :D The second part, tracing all the way from a dummy to audio out, still seems useful to me.

4) A possible approach to clutter control would be to allow a user to group a set of plugs and "box them up", then be able to toggle between "box closed", where you couldn't see the details or edit the connections, and "box open" where all of the bits are there to be fiddled with.
I could still see some value in this, but I'm guessing the implementation complexities are non-trivial.

5) The ability to color the plug-in boxes like you can parts in the Composer, or
Would still go for this, if available.

6) The plug-in's representation in the plugin setup area could be an iconic view of it's GUI (I think EnergyXT does something like that).
Or this. Don't know if the new VST 2.4 spec messes this up?

7) Should be possible to lasso a bunch of plugs with the mouse and drag them as a group, rather than dragging one at at time.
Still a keeper.

8] I think the Audio Output should appears as a bus at the bottom of the plugin area, with a more or less arbitrary number of connections. That would (a) make for somewhat cleaner "wiring" and/or grouping of plugs in a path, and (b) make it straightforward to allow right-clicking on an input to the output for solo / mute purposes. ... I could see the potential for a built-in plug similar to the Dummy that's just a Mute device.
And I still like this idea (audio out as a buss at the bottom). A Lot.

9) Also some way to maybe drag a plugin onto an audio connection and have LUNA automatically insert it into that connection (i.e., break the one connection into two, one into and one out of the new plug). That would speed up workflow while retaining the nice visualization that the modular approach gives you.
And this one, also. Drag the plug onto the wire, hover for a moment and have LUNA pop-up a "Insert this plug into this path?" dialog. If yes, do that automatically. Saves the user several steps of disconnect / reconnect to insert a plug into an existing path.

10) One way I could conceive of to have a semi-modular approach would be to have racks as plugins within the plugin area. Each could have red and blue triangles to represent the audio and MIDI ins and outs both of the rack and of each slot in it, with inputs to the left and outputs to the right. That way there's an easy way to just use a collection of channel strips if that fits your needs, but each plugin could still be accessible as an automation target, and things like side-chaining would become easier. That feels like a way to get pretty close to the best of both worlds.
Mabye this one, too, but I haven't played with PR8 enough to know for sure if I still think this is useful.

So, there you have it, all in one list. :)

DaveL

Post

muzycian wrote:
DaveL60 wrote:C1: I really like the way the highlighting works, but am finding the non-highlighted lines thin enough to almost disappear on my system (17" CRT running at 1024x768). I'd suggest making the lines at little fatter in both the normal and highlighted cases.
I would like to do this, but don't know how to do this yet.

Need to find the algorithm for drawing bezier lines with variable thickness.
Well, I'm hardly a graphics software developer, but I have a suggestion: There's an open source image editing program for Windows called Paint.Net (http://www.getpaint.net). It does a nice job when putting in line; maybe you could take a look at the code to see how they do it and adapt some.

DaveL

Post

DaveL60, just to disagree with you :):
DaveL60 wrote:
DaveL60 wrote:4) A possible approach to clutter control would be to allow a user to group a set of plugs and "box them up", then be able to toggle between "box closed", where you couldn't see the details or edit the connections, and "box open" where all of the bits are there to be fiddled with.
I could still see some value in this, but I'm guessing the implementation complexities are non-trivial.
DaveL60 wrote:
DaveL60 wrote:10) One way I could conceive of to have a semi-modular approach would be to have racks as plugins within the plugin area. Each could have red and blue triangles to represent the audio and MIDI ins and outs both of the rack and of each slot in it, with inputs to the left and outputs to the right. That way there's an easy way to just use a collection of channel strips if that fits your needs, but each plugin could still be accessible as an automation target, and things like side-chaining would become easier. That feels like a way to get pretty close to the best of both worlds.
Mabye this one, too, but I haven't played with PR8 enough to know for sure if I still think this is useful.
With embedded racks in the plug in area, I think you get quite a lot of useful functionality. Okay, you can't wave a magic wand and say "box this lot up", you have to organise the rack by hand. But it does let you have a second level of "hidden away" bits to keep things tidy.

With the "box things up" - you get boxes within boxes... I'm not against it, exactly, I just think it's going too far..! :)
DaveL60 wrote:
8] I think the Audio Output should appears as a bus at the bottom of the plugin area, with a more or less arbitrary number of connections. That would (a) make for somewhat cleaner "wiring" and/or grouping of plugs in a path, and (b) make it straightforward to allow right-clicking on an input to the output for solo / mute purposes. ... I could see the potential for a built-in plug similar to the Dummy that's just a Mute device.
And I still like this idea (audio out as a buss at the bottom). A Lot.
Argh! :) I don't like this. The model is one jack per virtual connection. Maybe a buss build in plugin that automatically grows a new, spare connection each time one is used, and has a single output? (Like a dummy, but with sideways growth potential... ;))

Post

PL,

Happy to have the debate, and you make good points. Both #4 and #10 were based on playing with the experimental modular version, not PR8, and at this point I don't feel strongly about either of them. Given embedded racks, much of what I was thinking is provided, especially if Jo sees fit to implement #7 (grouping for moving), I think there would be enough organizing tools.

I still really like #8, though. Realistically, if you think about it like a mixer, the output is a buss into which everything is dumping to get to the sound card, so why not represent it that way? If you're in the non-modular view, you have a row of mixer strips that effectively are running their audio out the bottom, to an invisible buss. So, why not make it visible. Then, have the input points (the red triangles) offer an on/off feature so that it's easy to mute / solo things right at the output point, at the end of their signal path. I could see some potential to the buss plugin; have to think about that a bit more.

DaveL

Post

Pljones, DaveL,

Thanks for elaborating!

First of all, let me tell you this:

LUNA needs attention on many fields (in no specific order): integrated synth/sampler, integrated effects, breakpoint automation in composer, stretchable audio, ...

I think the MPA already is a very pro feature, maybe even too pro for LUNA now, that's why i was thinking about the "hidden port" thing.

Anyway, point is: The MPA is already working quite nice, imho. Although i agree that many of your suggestions would make it nicer. But again, it costs time resources and LUNA also needs attention on other fields.

So please be patient with improvements to the MPA.

Anyway, so specific feedback on your suggestions:
If I have one plugin selected (focussed), inserting a new one connects the new plugin's outputs to the selected plugin and moves focus to the new plugin. ("Click audio out, insert synth, play.")
To be honnest, i'm not sure if i like this one. Because in fact you need to do something in order to spare something. And is it worth it?
Making 1 connection is almost as fast as first having to click a target. (yes, i know, that's a bit exaggerated)

But also, such automatic behaviour could even lead to unwanted behaviour.

Anyway, lets ripe it a bit...

(taken notice on the whishlist)
Also some way to maybe drag a plugin onto an audio connection and have LUNA automatically insert it into that connection (i.e., break the one connection into two, one into and one out of the new plug). That would speed up workflow while retaining the nice visualization that the modular approach gives you.
And this one, also. Drag the plug onto the wire, hover for a moment and have LUNA pop-up a "Insert this plug into this path?" dialog. If yes, do that automatically. Saves the user several steps of disconnect / reconnect to insert a plug into an existing path.
More suggestions about speeding up making connections.

Added to the whishlist. But it may take a bit of time.
If the lines in the plugin area are analogous to cables, then it would be nice to be able to re-route a signal by grabbing the destination end of a cable and dragging it to a different input.
Added to the whishlist. (must be researched).
The ability to color the plug-in boxes like you can parts in the Composer
But how to highlight then?
The plug-in's representation in the plugin setup area could be an iconic view of it's GUI (I think EnergyXT does something like that).
Would be nice indeed :)

But it's luxury i can't bring yet.
Should be possible to lasso a bunch of plugs with the mouse and drag them as a group, rather than dragging one at at time.
Added to the whishlist.

======================

Conclusion: sorry if i sound a bit conservative about your suggestions (thanks for them!!) but i'm trying to preserve time resources for other LUNA things too.

Anyway, i'll do my best to make the MPA even better.

Cheers!

Post

muzycian wrote:Conclusion: sorry if i sound a bit conservative about your suggestions (thanks for them!!) but i'm trying to preserve time resources for other LUNA things too.
Jo,

All very reasonable and sensible. I'd agree whole-heartedly with some of your other priorities (I seem to recall having pushed tempo changes as being pretty darned important! :D And I love ACID and could get very excited over ACID-like capabilities in LUNA), and I don't feel at all insulted that you either see some of these things entirely differently or as something to tackle at a later date. One can certainly do a great deal of music making with LUNA without ever touching the MPA, so it's very sensible that other things get equal or greater attention. But the MPA is new and fun to play with. My suggestions were just that. I'm happy to play and contribute to the wishlist, and enjoy the ride as LUNA evolves.

DaveL
Last edited by DaveL60 on Fri Mar 16, 2007 2:09 pm, edited 1 time in total.

Post

Thanks DaveL, you understand it as i tried to express it, so that's great :)

And the MPA can/will only get better, step by step!

Post

Hi Jo,

There's a new VST effect mixer plugin with 16 tracks stereo inputs but LUNA do not shows them. Will it be possible to use this kind of mixer in Luna?

http://img255.imageshack.us/img255/4895/ombrescc2.png
http://img382.imageshack.us/img382/8871 ... unaqz3.png

http://www.kvraudio.com/forum/viewtopic ... 46&start=0

Post

I'll investigate this as soon as i got Ombres.

Post

You have a PM with last version. ;)

Post

Thanks, way faster this way ;)

Well, i already got the answer:

Ombres is not responding to the VST opcode "effGetInputProperties".

This means that Ombres does not give any info on how its input channels are organized.

Although the website says that Ombres has 16 stereo inputs.

And so LUNA takes all 32 Ombres channels as 1 big multi-channel input.

I've sent email to the makers of Ombres, because in this case they should respond to "effGetInputProperties".

Note that there is also a bug in LUNA that causes a crash when you connect Ombres to the Audio Output.

This is because LUNA takes all 32 inputs of Ombres as 1 multi-channel stream, but LUNA currently only supports up to 5.1 multi-channel streams.

This bug is fixed in LUNA PR 8.3, coming very soon.

Hope Ombres will be updated soon too.

Post Reply

Return to “MuTools”