Bitwig 4.0 announced
-
- Posts: 6021
- Joined: Mon May 15, 2006 12:15 pm
Re: Bitwig 4.0 announced
@Machinesworking, if I remember well, you do use livelooping techniques.
What's your workaround to record audio loops on the fly ?
What's your workaround to record audio loops on the fly ?
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1
Re: Bitwig 4.0 announced
Native Apple M1 silicone
-
- Posts: 11421
- Joined: Wed Jun 23, 2004 9:30 pm
- Location: Seattle
Re: Bitwig 4.0 announced
Bitwig doesn't have a looper, so for sure Live still holds the upper hand there.chapelier fou wrote: ↑Mon May 31, 2021 9:28 am@Machinesworking, if I remember well, you do use livelooping techniques.
What's your workaround to record audio loops on the fly ?
Digital Performer when I do anything with live looping.
-
- Posts: 6021
- Joined: Mon May 15, 2006 12:15 pm
Re: Bitwig 4.0 announced
Thanks. I was more referring to looping in clips.
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1
-
- Posts: 11421
- Joined: Wed Jun 23, 2004 9:30 pm
- Location: Seattle
Re: Bitwig 4.0 announced
Then I'm lost, are you talking about recording clips one after the other? or stacking audio on the same clip?
-
- Posts: 6021
- Joined: Mon May 15, 2006 12:15 pm
Re: Bitwig 4.0 announced
Clips one after the others.
In Live you can set up a track as the "input" track, and route it to several armed audio tracks.
Then you can trigger the clip slots recording on the selected scene with a dedicated midi message per armed track, thanks to the "track launch" control (available only in MIDI mapping screen). I don't see any comparable feature in Bitwig. Is there any ?
In Live you can set up a track as the "input" track, and route it to several armed audio tracks.
Then you can trigger the clip slots recording on the selected scene with a dedicated midi message per armed track, thanks to the "track launch" control (available only in MIDI mapping screen). I don't see any comparable feature in Bitwig. Is there any ?
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1
Re: Bitwig 4.0 announced
So, you're really trying to convert your live setup to Bitwig?chapelier fou wrote: ↑Wed Jun 02, 2021 8:16 amClips one after the others.
In Live you can set up a track as the "input" track, and route it to several armed audio tracks.
Then you can trigger the clip slots recording on the selected scene with a dedicated midi message per armed track, thanks to the "track launch" control (available only in MIDI mapping screen). I don't see any comparable feature in Bitwig. Is there any ?
Ableton Forum Moderator
Re: Bitwig 4.0 announced
Somebody posted this on KVR, I was going to reply there, but since someone bumped this thread...:
https://github.com/bitwig/dawproject
LOL, they renamed Live's ALS format (with some plausible deniability changes, of course, like always) and open sourced it.
https://github.com/bitwig/dawproject
LOL, they renamed Live's ALS format (with some plausible deniability changes, of course, like always) and open sourced it.
♥♥♥
-
- Posts: 11421
- Joined: Wed Jun 23, 2004 9:30 pm
- Location: Seattle
Re: Bitwig 4.0 announced
This is a weird flex? Why would Bitwig use Ableton's format as a base for sharing projects between DAWs? that makes absolutely no sense, since Ableton Live, not Bitwig would be the most easily compatible with the format? It would make much more sense for it to be biased slightly towards Bitwig files, but that's not even the point of the whole project, the whole point is less issues not more.pottering wrote: ↑Sat Jun 05, 2021 9:29 pmSomebody posted this on KVR, I was going to reply there, but since someone bumped this thread...:
https://github.com/bitwig/dawproject
LOL, they renamed Live's ALS format (with some plausible deniability changes, of course, like always) and open sourced it.
I mean even if the format was closer in structure to Live, it wouldn't be some sort of hinderance to Ableton, if the project takes off, someone could export a project from Logic to Live with no issues, with no real benefit to Bitwig. The whole thing is close to ReWire or VST etc. in that sense than some sort of intellectual property issue like you're painting it out to be.
Re: Bitwig 4.0 announced
Why would Bitwig use another format instead of their format used by Bitwig itself?Machinesworking wrote: ↑Sun Jun 06, 2021 12:22 amThis is a weird flex? Why would Bitwig use Ableton's format as a base for sharing projects between DAWs? that makes absolutely no sense, since Ableton Live, not Bitwig would be the most easily compatible with the format? It would make much more sense for it to be biased slightly towards Bitwig files, but that's not even the point of the whole project, the whole point is less issues not more.pottering wrote: ↑Sat Jun 05, 2021 9:29 pmSomebody posted this on KVR, I was going to reply there, but since someone bumped this thread...:
https://github.com/bitwig/dawproject
LOL, they renamed Live's ALS format (with some plausible deniability changes, of course, like always) and open sourced it.
I mean even if the format was closer in structure to Live, it wouldn't be some sort of hinderance to Ableton, if the project takes off, someone could export a project from Logic to Live with no issues, with no real benefit to Bitwig. The whole thing is close to ReWire or VST etc. in that sense than some sort of intellectual property issue like you're painting it out to be.
My guess is it is the same reason Bitwig 4 doesn't actually save as or export ALS or FLP, it only imports those.
Same reason Logic doesn't rewire as device, and doesn't even receive MIDI sync (of course Logic won't export this .dawproject format either, it will at most import it).
♥♥♥
-
- Posts: 11421
- Joined: Wed Jun 23, 2004 9:30 pm
- Location: Seattle
Re: Bitwig 4.0 announced
Nothing you're saying is making any sense. One of the guys from Bitwig is attempting to do an open source type universal DAW format, it doesn't look like it's based on .als to me, and it's weird you would think that? It's also weird to think that exporting to other DAW specific formats is at all part of this, again, it's an attempt at a universal format. So the DAWs themselves will have to support importing or exporting to the format themselves, otherwise it won't work, not unlike rewire.pottering wrote: ↑Sun Jun 06, 2021 2:08 amWhy would Bitwig use another format instead of their format used by Bitwig itself?Machinesworking wrote: ↑Sun Jun 06, 2021 12:22 amThis is a weird flex? Why would Bitwig use Ableton's format as a base for sharing projects between DAWs? that makes absolutely no sense, since Ableton Live, not Bitwig would be the most easily compatible with the format? It would make much more sense for it to be biased slightly towards Bitwig files, but that's not even the point of the whole project, the whole point is less issues not more.pottering wrote: ↑Sat Jun 05, 2021 9:29 pmSomebody posted this on KVR, I was going to reply there, but since someone bumped this thread...:
https://github.com/bitwig/dawproject
LOL, they renamed Live's ALS format (with some plausible deniability changes, of course, like always) and open sourced it.
I mean even if the format was closer in structure to Live, it wouldn't be some sort of hinderance to Ableton, if the project takes off, someone could export a project from Logic to Live with no issues, with no real benefit to Bitwig. The whole thing is close to ReWire or VST etc. in that sense than some sort of intellectual property issue like you're painting it out to be.
My guess is it is the same reason Bitwig 4 doesn't actually save as or export ALS or FLP, it only imports those.
Same reason Logic doesn't rewire as device, and doesn't even receive MIDI sync (of course Logic won't export this .dawproject format either, it will at most import it).
You're reading all kinds of weird things into something that's supposed to be like VST, ReWire etc.
-
- Posts: 6021
- Joined: Mon May 15, 2006 12:15 pm
Re: Bitwig 4.0 announced
Only considering it. I have no Bitwig License for now. Trying to gather some info, but so far my setup seems unreplicable.[jur] wrote: ↑Sat Jun 05, 2021 6:47 pmSo, you're really trying to convert your live setup to Bitwig?chapelier fou wrote: ↑Wed Jun 02, 2021 8:16 amClips one after the others.
In Live you can set up a track as the "input" track, and route it to several armed audio tracks.
Then you can trigger the clip slots recording on the selected scene with a dedicated midi message per armed track, thanks to the "track launch" control (available only in MIDI mapping screen). I don't see any comparable feature in Bitwig. Is there any ?
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1
-
- Posts: 11421
- Joined: Wed Jun 23, 2004 9:30 pm
- Location: Seattle
Re: Bitwig 4.0 announced
here:
In reference to a developer from Bitwig doing a side project attempting to get a universal song transfer format started.
Re: Bitwig 4.0 announced
ALS is a gzipped XML file.
In fact, if you want to know how ALS works just read that "dawproject" page and change the words ".dawproject" to ".als" and "zip" to "gzip" (arguably gzip is zip already).
Or just use 7-zip in any Live Set and see how the XML works.
That also provides a REAL-LIFE example of how a XML file like "dawproject" would work with real plugins, real sample files, etc.
People that really want to push that "dawproject" thing gotta admit it is Live where people will find numerous actual examples of how to implement that "dawproject" thing in the real world, since Ableton already did it, years ago, with millions of users not even noticing it is a gzipped XML.
By the way, Live's ADG, ADV and ALC are also gzipped XML. In case Bitwig comes with "dawpreset" and "dawclips" too ("wow such a innovative company").
♥♥♥