[edit] looks like Luddy just came up with a great solution!
Akshara wrote:
This may be your experience and is true from your vantage point; yet the majority of situations that I have encountered which use a combination of outboard hardware and in-the-box software use some form of direct monitoring solution, at least to some degree, whether through a console or a hardware interface.
OK then, in those cases you were using some other DAW rather than Live I assume. Live has some unique hurdles when it comes to this sort of set up, and again to a degree it's asking for issues to direct monitor MIDI sequenced hardware synths while at the same time running a heavy plug in load.
That was the point of my comment about the studio which you quoted and didn't like earlier, likely due to my equally condescending tone in reply.
Not at all, I just didn't find it relevant to mention a much much more complex two computer multi dependent recording studio situation when addressing a composers issues on a single computer set up, not trying to be rude about that, but it's like arguing for a 12 cylinder economy car that seats 10 people.
Yet truly, there are situations where direct monitoring is either preferred or necessary, where software monitoring is either not possible or not desired.
Yes there are, although I'm still not seeing how it's a good thing to deal with this when it's not working?
I just got the feeling that the OP fell into this category, based on the original request and the curt rebuttals. It was actually the, "Jesus, there is no reason to post on forums..." comment which made me think this. Just had that familiar ring about it.
You've been doing a lot of assuming about the OP and his issue, and rightly so,
since he still hasn't explained why he feels the need to, or has the situation where it's important to monitor his hardware outside of Live.
or me, "a <plugin which causes latency> will create latency when inserted," is one of those "obvious answer is obvious" kind of things, and comes across a bit like telling a marathon runner how to tie their shoes properly. I just presume that someone with success managing a direct monitoring solution likely falls into the marathon runner category.
Here's a news flash for you, when someone states that they wish introducing a linear phase EQ didn't mess up a single track in a DAW, it's not my duty as a reader to interpret their flat statement for euphemisms, allegory, substitutions or sarcasm content, and it's not my experience that people posting problems in forums are inherently 'marathon runners' because they are trying, or have used, a complex set up. There are plenty of people out there that come up with complex messes that they demand a solution to that refuse to do any troubleshooting or listen to any advice because they already have the answer, that "software X is fucked and unprofessional!", that the end users (besides themselves of course) are all plebs, and that misplaced advice (often given because the user doesn't flesh out their issue with enough details) is an indication of the uselessness of the forum. This thread in it's entirety is a fucking loop of this plus the usual fanboy reactions of disbelief that Live can't cover all bases and therefore the question is lame.
This is the META quagmire thread:
OP posts problem due to unique set up and a possible DAW issue.
OP never explains why they have to use this particular set up, and refuses all advice to change set up.
Without further explanations on his unique set up and why he need to do it this way, OP starts moaning about bad advice.
Users chime in that OP is "doing it wrong", defend DAW.
User chimes in that they are PRO, and that all the other users are not able to read between the lines at OPs issue, user debates everything based on the limited information they have.
Thread turns into a conversation about nothing, because it never started with much information to begin with. Fucking quagmire...... that Luddy might have just saved from being completely useless!