Dungeon Studio wrote:I always remember the sign above the studio door - "Sure, we can put a lot of effects on your shit. Just keep in mind it will sound like shit with a lot of effects after." - Words to live by IMO.
I like it!
Lance wrote:I said tabbed UI, sou you'd see as many mixer strips in the Master section as right know, and no-one would force you to see the another 4 strips.
How would that work? I can't see it working without hiding things and the best thing about Orion is that nothing has to be hidden - it's all right in front of you where you can see what it's doing and get straight to any problems.
You have no clue, how useful the more flexible limitless mixers, because you never use them.
I've owned Cubase, Fruityloops, Cakewalk and EnergyXT, so I think I have a clue or two. What you fail to appreciate is the value of being able to see it all at once, to see how it all fits together and what makes it work or otherwise. It makes it an order of magnitude easier to identify and fix problems as they arise, which allows you to get more done in a given time and to do it to a higher standard.
And do your math how many sends we'll need if we import a couple of templates and merge a couple of project fishbones from songs.
No more than I need now because what I'll end up with is one song, it's just that I won;t have to spend half-an-hour individually copying bits from one song to another.
What you and a large number of other users who see this stuff as an end in itself, rather than a means to an end, never fail to do is find ways to make everything more complicated. OTOH, those of us who actually use this stuff to make music are constantly trying to simplify the process. So where you see that you don't have enough of this or that, I see an opportunity to find a way to simplify something which ultimately allows me to get more done in the limited time I have available and to do it to a much higher standard.
Templates and song merge will be properly and usefully implemented only if it's including the import of the send fx too.
No, it won't. In fact, I wouldn't even include them as an option in a merge feature. The user can always decide which is the base project and which is the donor, thereby choosing which sends to preserve and which to discard. Send effects are things you use across multiple channels - global effects - so I really do fail to see how you could possibly find more than two or three that you might need to use across multiple channels. It makes no sense if you have even a basic understanding of the production process.
This is how it works in other hosts
Which is one of the very biggest reasons I have rejected each and every one of those hosts. It is very poor workflow. It's hard to see that you have any idea what you're doing. Have you ever even been in a real studio?
Richard wrote:Don't forget the idea of sends is to share an effect. Supporting unlimited sends just to be able to merge 5 different songs is completely stupid, as it would create a huge mess, consume a lot of CPU, and downgrade sends to inserts to some extent. It might be interesting from a geek perspective, but not for actually making music.
Couldn't have said it better myself [as you can see above].