delete generator is not recursiveModerators: Christophe, Mark
17 posts
• Page 1 of 2 • 1, 2
delete generator is not recursiveits v8 and so why doesn't delete of a generator delete all the insert fx attached to it on the mixer strip? if it deletes the mixer strip bound to the generator, it should also delete all fx's in the insert channel of the mixer strip.
Re: delete generator is not recursiveIf memory serves me, it never deleted assigned effects along with generator. It just unassigned them.
SoundCloud ::: Facebook
Re: delete generator is not recursiveYeah I find that mildly annoying but just have to remember to delete the inserts before deleting the instrument.
Or spend a minute or three maximising all the inserts to find out which aren't assigned and deleting them.
Re: delete generator is not recursiveOr you could press CTRL+J to get a list of all generators and effects that tells you what the effects are assigned to and if they are unassigned. You can delete whatever you like from from your project via this list.
Re: delete generator is not recursiveAh, didn't know that shortcut, thanks.
Re: delete generator is not recursiveGreat shortcut!!
Now, is there a shortcut to see which automation (event editor) belongs to which vst ? That should be great! I'm always searching my @$$ off to find the right event editor. OTOH, I like the 'free' style of Orion, I was attracted to it the minute I saw it. I love the floating windows.
Re: delete generator is not recursive
I'm really confused how this could even be possible, but maybe CTRL-E is what you're looking for?
Re: delete generator is not recursiveI know the ctrl-E shortcut, I use it all the time.
Ok, I'll explain a bit more; Right now I'm working on a song and I use Dune twice. I gave both instances a different name and on both versions, I have automated the same parameter (filter cutoff). When I have both event editors of the filter cutoff floating around on the screen, I can't see which editor belongs to which synth (as the event editors have the same name). So I have to close both editors, then go to my desired synth and press ctrl-E. Otherwise it's possible that I'm doing changes in the wrong event editor. AFAIK I can't rename event editors or do something else to visually separate event editors from each other. I hope it's clear what I'm trying to explain. When I have an event editor from an effect floating around on the screen, I can't see to which track it's connected. I use Sugarbytes WOW (filter) a lot. When I have the cutoff filter automated on several instances, they all look the same and I can't see which event editor belongs to which track. It would be great if we could rename event editors, like it's possible to rename tracks and effects. All I want to say is that when I have 3 or 4 event editors floating around the screen, it's virtually impossible to know to which track/effect/synth they belong.
Re: delete generator is not recursivethats correct, however it just means this bug existed long time back. The fact that if a channel strip is deleted along with the generator, it should also delete all the effects attached to it. For example when the channel strip is deleted, it makes sure to delete the knobs, faders..etc other components of a mixer strip. likewise since fx are inserted into the channel strip, when the channel strip is deleted is should by functionality delete the fx attached to it as well. So this a bug. that depends on the scale. take an sfs with 40-50 strips. each strip as some multi fx etc. now say i want to create a template...i would have isolate all strips other than the ones i am interested and delete them. now when i am doing this for 10-20-30 strips the time adds up, mildly becomes insanely annoying. and not just templates, the fact that i just want to delete a generator and not have to worry about preparing myself going to each fx slot and deleting them beforehand, especially when i am deep into the creative process bashing my brains trying to get bass/lead/drums right. I am sure no one wants to waste time at that point trying to do window bookeeping.
Re: delete generator is not recursive
you seem to be a bit confused about what a bug is. maybe automatically deleting effects just because they are inserted into the channel strip for a generator I deleted is not behavior I desire.
Re: delete generator is not recursivethere is no confusion here, just because for some bizarre reason you desire to reuse the fx assigned on a previously deleted mixer strip doesn't make me confused or makes it acceptable to depart from the implicit functional behavior. if you wish to share the fx then use it on a send fx/bus or create a new fx. on the other hand if i want to delete 30 channels you cant expect one to goto each insert slot and delete fx/multi. In contrast if you wanted to just reuse an fx you only need to goto that channel stip and create a new fx only once! There is simply no comparison with your example.
Re: delete generator is not recursiveAnd this here is exactly the reason why it is made to leave the effects intact. Different strokes for different folks - some will want to have them removed, others will want to use them somewhere else. No way of pleasing everyone, no matter how good your argument is (aiming at no one specific here, just talking in general).
Suneel, I don't see how the essential parts of mixer can be compared to effects. They're not attached to the mixer, they're just assigned, they are separate entities. But I see where the frustrations are coming from. In that regard, to keep both sides happy to some level, I think an ability to multi-select items in the Module List would come in handy. SoundCloud ::: Facebook
Re: delete generator is not recursivei really dont think its the question of pleasing anyone, its how the default behavior should have been in the first place. Not sure how to explain it, its pretty basic ofcourse they are! but an fx on its own lying around does not contribute to anything. It only works when its assigned it to a mixer strip. Take the example of a directory(mixer channel) which is container. The files in the directory are assigned to the directory in which they reside. You don't go deleting each file additionally after you delete a directory. If you delete a directory the files are also deleted automatically. You don't leave the files lying around. If one person wanted to reuse the file then they should have made a copy of the file. Likewise if i delete a mixer strip all the fxs assigned or part it should also be deleted. And if they want to reuse the fx just create it or reassign it before deleting. Its really a simple trivial concept
Re: delete generator is not recursive
It is exactly that. Some people might reuse the unassigned effects for something else. Perhaps is should have been like that, but change that now, and I'm sure you'll hear people go "ah shit, where did my effects go" on the forum.
No argues there, although even I have a habit to delete a generator before I put a new one in, which comfortably leaves me with effects I can reuse if I choose to. This leaves you with exactly that - a choice - and is about pleasing people. Of course, the down side of that choice is having to manually remove all the unused effects afterwards. Perhaps a cleanup function would be better, something that would delete all the unused effects? SoundCloud ::: Facebook
Re: delete generator is not recursiveOrion provides the "Are you sure?" dialog box when you delete a generator. Surely there could be a check-box there to "delete assigned effects". It'd save the trouble of finding and deleting all the effects one might have had assigned.
17 posts
• Page 1 of 2 • 1, 2
Who is onlineUsers browsing this forum: No registered users and 425 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |