Seems like it would be a simple development solution, but perhaps it's that old saying easier said than done. I have a feeling this idea of breaking-out outputs to Maschine (whether it's a battery or maschine limitation) is simply not possible at this point in time.
By breaking out in Maschine, this would essentially give me access to the same mix abilities as if I was working in a DAW. eq, dynamics, and effects on individual cells.which are limited and on a sonic level not always ideal. And I can save custom battery setups versus saving Maschine sessions if and when I make changes throughout a session. Sometimes I like to run battery because it's a quick, easy, and an organized way of getting a groove together for various reasons, from ease of use and how sound libraries are categorized. Here's my reason for wanting to do what I'm asking about.
If I'm understanding what you're saying correctly in regards to bouncing, this would be a time consuming and a bit of a clunky workaround. I usually have to deal with enormous sessions, and this setup has been excellent both creatively and technically. My system is a dual networked computer setup, one of the computers is for my DAW and the other is for hosting VI's plus Maschine via Vienna Ensemble Pro 6. Why not just bounce out what ever it is you have in battery and use maschines samplers? Not being funny, but it's like asking how to park your motorbike in your car.Thanks for chiming in on this. It would involve running the two standalone apps separate and using virtual ins and outs. There is, but it's a very messy workaround.
0 kommentar(er)
