The All In One Source Bitwig Information & Speculation Thread

[Ogopogo]

Yes, it runs on an iMac. Boom boom!

I'll think of a comparison test and see what I can come up with. Seems ok to me though. Seriously, my iMac is only core 2 Duo, not much to shout about these days. An i7 is twice as efficient.

I think the sort of acceptable test would be to put a few vsts on a track, then start duplicating that track until you get errors, and just do that in whatever daws you have to compare with the same vsts and see how many tracks you can get with each. You have Ableton, I assume? Also start-up time with Ableton vs Bitwig would be interesting to hear about. I loved that Reaper started up so quick, and it may sound spoiled, but waiting for live on the same system for 5-10 seconds is a bit of a pain.

If you feel like it of course. Soon we'll all be able to see how it runs for us.

[kennyda]

Yes, it runs on an iMac. Boom boom!

I'll think of a comparison test and see what I can come up with. Seems ok to me though. Seriously, my iMac is only core 2 Duo, not much to shout about these days. An i7 is twice as efficient.

I think the sort of acceptable test would be to put a few vsts on a track, then start duplicating that track until you get errors, and just do that in whatever daws you have to compare with the same vsts and see how many tracks you can get with each. You have Ableton, I assume? Also start-up time with Ableton vs Bitwig would be interesting to hear about. I loved that Reaper started up so quick, and it may sound spoiled, but waiting for live on the same system for 5-10 seconds is a bit of a pain.

If you feel like it of course. Soon we'll all be able to see how it runs for us.

I just did a test running 40 audio tracks in Live and Bitwig Studio. In Live my computer was running at about 60-75% CPU, and in Bitwig it was about 25-50%, repeated test, same sort of result. These sort of tests do vary a lot but I did repeat it once and checked nothing else was running except routine background stuff so I think it's reasonably useful.

[Ogopogo]

Super cool. Thanks.

[Lesha]

I just did a test running 40 audio tracks in Live and Bitwig Studio. In Live my computer was running at about 60-75% CPU, and in Bitwig it was about 25-50%, repeated test, same sort of result. These sort of tests do vary a lot but I did repeat it once and checked nothing else was running except routine background stuff so I think it's reasonably useful.

How about VSTs?

[spinlud]

I just did a test running 40 audio tracks in Live and Bitwig Studio. In Live my computer was running at about 60-75% CPU, and in Bitwig it was about 25-50%, repeated test, same sort of result. These sort of tests do vary a lot but I did repeat it once and checked nothing else was running except routine background stuff so I think it's reasonably useful.

How about VSTs?

I can't believe that he is getting 60-75% of cpu in ableton with only 40 tracks without any vst...

[virtualmark]

I just did a test running 40 audio tracks in Live and Bitwig Studio. In Live my computer was running at about 60-75% CPU, and in Bitwig it was about 25-50%, repeated test, same sort of result. These sort of tests do vary a lot but I did repeat it once and checked nothing else was running except routine background stuff so I think it's reasonably useful.

How about VSTs?

I can't believe that he is getting 60-75% of cpu in ableton with only 40 tracks without any vst...

Yeah it seems a bit high. But I find that the CPU meter in Ableton isn't very accurate, as I've had it over 100% a few times... which is impossible.

[Redukt]

I hope there will be some iPad controller app for BWS, like TouchAble for Live - this thing really helps me achieving what i want a lot quicker. Much better than any Launchpad or similar controller.

[Ogopogo]

Interesting, I wonder if that is possible with the scripting. If so maybe the touchAble people will just add support for Bitwig.

[kennyda]

This test was not done using Live's CPU meter. I was measuring total CPU off the Mac. I just did it again and got the following, this time reading total USER CPU on each core. I have two small graphs in the Status Menu, measured over about 30 seconds, updated every 0.5 seconds. I'm using an app called menumeters

Live 60%
Bitwig 20%

[Ogopogo]

Wow that's really encouraging. And just so we're clear, what did you have in the tracks?

[codec17]

Maybe a stupid question... but can you make the inspector or the browser not visible? a shortcut to make them disappear? ah 2 weeks never been so long!

[Ogopogo]

^Yes, you've got key commands to get rid of them.

[kennyda]

Wow that's really encouraging. And just so we're clear, what did you have in the tracks?

Just audio (a drum loop) in the timeline. I had it playing for a minute or so. I had the volume turned right down in all the tracks.

[kennyda]

^Yes, you've got key commands to get rid of them.

Yes, complicated key commands though. Not! The shortcut for the Inspector panel is I or as Bitwig write it. Browser Panel is , Mixer [M], Device Panel [D], Automation Panel [A], Launcher [L] etc

Altogether there are 3 views and 10 panels. (Also 5 multi-monitor views)

[Echoes in the Attic]

I hope there will be some iPad controller app for BWS, like TouchAble for Live - this thing really helps me achieving what i want a lot quicker. Much better than any Launchpad or similar controller.

No doubt there will be iPad apps very soon for it. Perhaps the touchable guys will do something. But I would bet on Lemur having a template very quickly, either from a user or themselves, like their Live Control template.