eyeknow wrote:I don't think that is fair
Fair? What's 'fair'?
eyeknow wrote:I don't think that is fair
Well, that was cool to see Bitwig functioning and doing stuff at least. Like I've said before, I'm excited to see what Bitwig can do and how it'll be. And yeah, they have a long uphill slog to edge out DAW players that have been around for years. However, basically taking ideas from things that other DAWs do well, as well as implementing new and cool features, and putting them into one program, that's no small feat. Even if they did 'steal' some of the larger ideas from other DAWs, that's basically what progress is, is people improving on someone else's ideas. If that wasn't the name of the game, then Ford would still be the world's only car maker.SuburbanThug wrote:http://www.youtube.com/watch?v=rOr4Bxk-ctc
Not much to see here but it's the "first track released into the wild using Bitwig Studio beta." So as you can see... it can at least play audio files and warp them
I have no issue with using multiple DAWs. It keeps things interesting, breaks me of habits. I'm excited to see what these guys do but it will take a while for the product to mature. It doesn't send midi out??? Seems like a crazy big oversight. Sounds like they're just trying to get this baby out the gate.
I never thought of Live as an "either/or" to Sonar, ProTools, Logic or any of those. To me it was always an "and". It seems to me that the competition might be more of FLS, Live, Reason which IMHO are used more to compose in rather than traditional linear, tape recorder styled DAWs.CFM wrote:Hardest job for Bitwig is still to come - that's tempting people to switch from Cubase, Live, Protools, Reaper, Logic...
The midi out thing was in reference to external instruments but now that I think about it there has to be some kind of workaround anyway. They aren't going to support Rewire but are using an alternative called Jack or something to that effect. It sounds like however you like to use your plugins you'll be able to use Jack for it. Maybe with Jack you can figure a workaround for controlling hardware? Seems likely...SpeedKing wrote:Well, that was cool to see Bitwig functioning and doing stuff at least. Like I've said before, I'm excited to see what Bitwig can do and how it'll be. And yeah, they have a long uphill slog to edge out DAW players that have been around for years. However, basically taking ideas from things that other DAWs do well, as well as implementing new and cool features, and putting them into one program, that's no small feat. Even if they did 'steal' some of the larger ideas from other DAWs, that's basically what progress is, is people improving on someone else's ideas. If that wasn't the name of the game, then Ford would still be the world's only car maker.SuburbanThug wrote:http://www.youtube.com/watch?v=rOr4Bxk-ctc
Not much to see here but it's the "first track released into the wild using Bitwig Studio beta." So as you can see... it can at least play audio files and warp them
I have no issue with using multiple DAWs. It keeps things interesting, breaks me of habits. I'm excited to see what these guys do but it will take a while for the product to mature. It doesn't send midi out??? Seems like a crazy big oversight. Sounds like they're just trying to get this baby out the gate.
But yeah, still, it's an uphill battle. And I didn't know about no MIDI out. Seriously? That seems like a big thing, and the way I use some of my VSTs, if I'm understanding what you're saying, that would seriously hamper what I do at some point. Yikes.
Jesus man, read up. Jack is what ReWire dreams of becoming when it grows up. And then it breaks down in tears when it realizes it never will.SuburbanThug wrote:The midi out thing was in reference to external instruments but now that I think about it there has to be some kind of workaround anyway. They aren't going to support Rewire but are using an alternative called Jack or something to that effect.
the only real operating system is the one you compiled yourself, right?Add the following information to the 'Target' property: "C:\Program Files\Jack\jackd.exe" -R -S -d portaudio -d "ASIO::ASIO4ALL v2" [This configures Jack to use the ASIO4ALL v2 driver, if you have another ASIO device then configure the 'Target' property with that device name. For a list of all the audio devices on your system that Jack can connect to, open a Command Prompt, change directory to the Jack folder (i.e. cd "c:\Program Files (x86)\Jack\") then run this command: jackd -d portaudio -l (that's an 'ell' for List, not a 'one') , this will present you with the list of supported devices.]
The Jack v 1.9.8/64bits/JackRouter.dll still has to be registered "manually" with regsvr32 - so please try the following command to register the 64-bit JackRouter:
regsvr32 "C:\Program Files (x86)\Jack v1.9.8\64bits\JackRouter.dll"
Jack doesn't support two-way transport synchronization which is an essential feature of ReWire.wasoota wrote:Jesus man, read up. Jack is what ReWire dreams of becoming when it grows up. And then it breaks down in tears when it realizes it never will.SuburbanThug wrote:The midi out thing was in reference to external instruments but now that I think about it there has to be some kind of workaround anyway. They aren't going to support Rewire but are using an alternative called Jack or something to that effect.
http://lmgtfy.com/?q=jack+audio&l=1
Midi and Audio routing every which way. Every which way.
lol, well we all get what we need. I have no use for two way synchro, but I do 'need' all the wild routing I can get. ReWire feels like a glorified line-in to me, albeit synchronized.SuburbanThug wrote:Damn, Wasoota. You just got told. Just kidding. I only really stay informed on what is essential to what I'm doing or want to do at the moment. I'm sure I'll get a little nerdier in the future since I just quit smoking tons of high quality marijuana a few months ago. It's been an enlightening few months as far as learning more about DAWs and gear in general. Just started learning how to use VFX to use Windows plugins on my Mac. One day at a time, one day at a time...
Nothing to compile. But to each his own. The benefits need to be seen to be believed though.start qjackctl.exe and configure it the following way:
- in Setup/Setting, use "jackd -S" at the "Server Path" item. WARNING: on Windows the "-S" parameter is *mandatory* to have the jack server correctly working!!
- in Setup/Setting, use "portaudio" at the "Driver" item
This was exactly the reason they gave at NAMM for the early announcement.dnbhallifax wrote: (Although who knows, that may very well be something they've had to do in order to continue raising development money ...)
..
oof. i would certainly hope they've come up with something a little more user friendly. manually registering .dll files and the like isn't exactly super user stuff, but it's more than one should have to do to make a piece of software released... we'll just say after 2010 to be fair... work with what is essentially old hat IMHO (i'm glancing at Rewire features).Angstrom wrote:Yeaaah ... Jack enthusiasts always overlook a little something.
From : how to use Jack in Windows:the only real operating system is the one you compiled yourself, right?Add the following information to the 'Target' property: "C:\Program Files\Jack\jackd.exe" -R -S -d portaudio -d "ASIO::ASIO4ALL v2" [This configures Jack to use the ASIO4ALL v2 driver, if you have another ASIO device then configure the 'Target' property with that device name. For a list of all the audio devices on your system that Jack can connect to, open a Command Prompt, change directory to the Jack folder (i.e. cd "c:\Program Files (x86)\Jack\") then run this command: jackd -d portaudio -l (that's an 'ell' for List, not a 'one') , this will present you with the list of supported devices.]
The Jack v 1.9.8/64bits/JackRouter.dll still has to be registered "manually" with regsvr32 - so please try the following command to register the 64-bit JackRouter:
regsvr32 "C:\Program Files (x86)\Jack v1.9.8\64bits\JackRouter.dll"