|
asked Feb 10 '14 at 17:26 by ZenPunkHippy (suspended) |
|
Some 3rd party plugins such as FXpansion's Geist feature multiple outputs, which may be routed freely to other audio tracks. Will this be supported in a future version of Bitwig? |
|
I've asked the same question a while ago (and quiet recently again). Multiple outputs will be supported in a future version. Even before 2.0 if I am not mistaking. answered Feb 11 '14 at 18:01 by Solidtrax (967) edited Feb 11 '14 at 18:02 |
|
they should fix it fast !! that stops many people of buying this DAW answered Mar 28 '14 at 23:57 by run2hype (41)
|
|
Multi output from plugins is very high on the priority list of the developers, but not sure which version will add this feature. answered Apr 01 '14 at 23:38 by ZenPunkHippy (suspended) |
|
It would appear that this would be a "required" feature for most owners of "multiple output" software, Kontakt and etc. However, if you have a multi-core processor on your box, careful consideration should be taken regarding this feature. Depending upon your platform, your software and your DAW, multiple outputs from a single track may NOT be able to spread the processing load across the multiple cores on your box. It may be best to create your "scratch" midi track; i.e. a drum/percussion groove or a string or brass section on a single track and then export each sound to its own midi track, create another software instance for those midi tracks and then process in Bitwig when preparing your mix. For the final mix, a rendering of midi to audio would be optimal and an expected deliverable format. Would like to know from Bitwig how this functionality is going to be implemented in their future update and what they recommend regarding best practices for now and when the multiple-out feature becomes available. Thanks a bunch! answered Apr 07 '14 at 06:39 by griffeyt53 (61)
|
|
Yes, Bitwig has said it will be in an update before version 2. answered Apr 01 '14 at 16:00 by pellissier (255) |
|
Seeing this is a priority is reassuring. But, its exclusion in today's environment is pretty laughable. I have no idea how to program a DAW, but I do know what is needed to be taken seriously. This is one of those features. This was a major oversight for a first release. All the sparkle of my shiny new demo was ruined in a matter of minutes with the realization I couldn't use it with my core plugins. wah wah.. answered Apr 21 '14 at 01:20 by mwhays (11) edited Apr 21 '14 at 01:21 |
|
Same reason I stopped playing with the demo. Will not even start considering BW again til this is on the table. edit: in other news, my vsts finally showed up and will probably give it a go tomorrow answered Apr 21 '14 at 01:55 by konfront (101) edited Apr 21 '14 at 06:53 |
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
Markdown Basics
- *italic* or __italic__
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Tags:
Asked: Feb 10 '14 at 17:26
Seen: 3,099 times
Last updated: Apr 21 '14 at 10:20
This is one of the features that Bitwig must have before I even consider buying it. I wouldn't even buy it for a quarter of the price without this feature. For now I'll continue playing with the demo.
— (Mar 28 '14 at 16:30) Matt_Riley