Live 12 or Bitwig 5.1

[SLiC]

So never trust a statistic that you have not falsified yourself!

Studio One was to Cubase what Bitwig was to Live when it came out, same claims, rivalry, same arguments... For a decade I was Cubase + Live, then I went Studio One + Bitwig (got rid of Cubase but held on to Live as I had so many packs/MAX things). Ultimately everything goes full circle as I could see Cubase trying to be more like Studio One and Live trying top be more like Bitwig in many ways, that's why you need the 'disrupters', stops the big boys getting complacent.

[xbitz]

^^^ assembling a project in Studio One, then spicing it up with Bitwig, is a very tempting alternative (which is why I'm interested in the status of Studio One). It would be good if someone (like Image-Line) would start supporting the .dawproject format, similar to the .clap format, where another big name could also get involved

[SLiC]

^^^ assembling a project in Studio One, then spicing it up with Bitwig, is a very tempting alternative (which is why I'm interested in the status of Studio One). It would be good if someone (like Image-Line) would start supporting the .dawproject format, similar to the .clap format, where another big name could also get involved

I always go the other way around - song starters, loops, drums etc . in Bitwig and then assemble it in S1 for a more linear timeline type production and mixing/mastering. If I am adding guitar, vocals etc it is pretty much always in S1 due to the melodyne integration and neither Live or Bigwig have gone down the ARA route for some reason.

[xbitz]

well, the direction is a matter of taste (AFAIK S1 has dedicated mastering view so S1>Bitwig>S1 probably), what I'm looking at, and it would be good to have .clap support under S1, and the device list could be expanded at least with reverb https://www.bitwig.com/support/technica ... ements-62/

Built-in Devices
Generic EQ
Generic Compressor
Generic Gate
Generic Limiter

although the implementation of various reverbs already varies greatly under different DAWs, perhaps it's better if it only works at the third-party level.

so according to Google Bard

"Yes, the fact that the .dawproject file format allows projects to be moved between S1 and Bitwig, and thus allows Bitwig to perform tasks that it does not support (ARA), can speak in favor of Bitwig.

ARA is a technology that allows DAWs to communicate directly with plugins. This allows plugin manufacturers to provide features and performance for their plugins that would not be possible with traditional plugin interfaces.

Bitwig does not support ARA, so Bitwig users cannot access all the features of plugins that support ARA. However, using the .dawproject file format, Bitwig users can copy their project to S1, where they can access all the features of plugins that support ARA.

For example, if a Bitwig user wants to use an ARA-supported plugin that can apply correction to instruments, they will need to copy their project to S1 to access the plugin. In S1, the user can load the plugin and access all of its features, including ARA.

Using the .dawproject file format allows Bitwig users to take advantage of the benefits of ARA-supported plugins without switching to a different DAW. This is an important advantage that can speak in favor of Bitwig.

Overall, the .dawproject file format is a significant advancement for Bitwig. It allows Bitwig users to take advantage of the benefits of ARA-supported plugins without switching to a different DAW.

At last, something , if we also add the PreSonus Hub to the picture, it's possible to create a quite interesting hybrid workflow

[SLiC]

Google Bard just produces AI nonsense!

Using the .dawproject file format allows Bitwig users to take advantage of the benefits of ARA-supported plugins without switching to a different DAW.

Other than the fact that you have to buy and learn to use a different DAW to do that! I cant help but think adding ARA to Bitwig is the actual solution to the lack of audio pitch quantise!! You could switch to S1 as it has far more extensive audio and midi editing (including score) and better mixing and mastering as well...but on that basis you would be doing most of the production in S1!

[xbitz]

I saw that sentence, but it can easily be understood that due to the .dawproject format, a kind of fusion between S1 and Bitwig is happening.

[SLiC]

Yes, that was sort of my point- S1 has a lot of features that are a lot better than Bitwigs in the editing, mixing and mastering side, the ARA part would be the least of the reasons to switch over to another DAW in my opinion as it's less effort to use Melodyne as a 'plug in'. Also, if I was going to have a a lot of lot audio to edit and pitch correction to do I would have started have started in S1 as you have to own them both so...

IMO you can use Melodyne fairly easily with Bitwig (and even easier with Live if you select it as the sample editor) so I wouldn't swap DAWS just for that reason mid project.

[pdxindy]

I cant help but think adding ARA to Bitwig is the actual solution to the lack of audio pitch quantise!!

My desired solution is native pitch correction in Bitwig!

[SLiC]

I cant help but think adding ARA to Bitwig is the actual solution to the lack of audio pitch quantise!!

My desired solution is native pitch correction in Bitwig!

Maybe, depending how good it is and how lonmg it takes to come!- It's unlikely to be polyphonic or as good as Melodyne (and I already own Studio and know how to use it so probably stick with it) + ARA gives you other tools like vocal align etc. Reason and Cubase both have native, anything is better than nothing and native may tie in with modulation system etc for creative use, but I see no harm in having ARA as well, but like I said above, it isn't that much hassle using it as a VST for now, ARA just makes it that bit more integrated.

[pdxindy]

My desired solution is native pitch correction in Bitwig!

Maybe, depending how good it is and how lonmg it takes to come!- It's unlikely to be polyphonic or as good as Melodyne

I don't care if it is polyphonic... monophonic for vocals works perfect for me. If it was built-in, it would be better integrated, and knowing Bitwig, have some cool capabilities because of it.

[Trancit]

I think my short journey with Live will come to a quick end...

How can so many work with it???

I just created a song idea I really liked... I adjusted everything that it sounded perfect... CPU load was just 5-6%
I saved the song as... to the end of the saving process Live put out an error message and shut down...

I restarted Live again and let it recover the previous work...
What the heck... every Sylenth instance, every Shaperbox instance were initialized... many audio clips were missing and in the location I saved the project was just 1 consolidated audio file but no project file...
So I just lost at least the half of my song idea because of saving a live set...Thx very much Ableton!
Now I can try to recreate my idea in another more reliable DAW...

This has never happened in any other DAW... my system is completely stressless, no crashes at all and Sylenth and Shaperbox aren´t any indie no name plugins known for making trouble...

WTF!

[liquidsound]

^^^^^^You need to see a priest

[Trancit]

^^^^^^You need to see a priest

I really do have half a tear in my eye...

[SLiC]

I think my short journey with Live will come to a quick end...
How can so many work with it???

Maybe as many of us have never had (or even heard of) this problem? very weird- what version of Live and what OS?

[Trancit]

I think my short journey with Live will come to a quick end...
How can so many work with it???

Maybe as many of us have never had (or even heard of) this problem? very weird- what version of Live and what OS?

Hmmm... I saw many many videos long time users were claiming about constant crashes in Ableton so Idk if this really such a rare case... perhaps they are just used to lose much work... I am not. This was really the first time in my life...

This was Suite 11.3.13 on Windows 10...
Just a few Audio tracks with beat warp mode, Ableton native devices (non M4L) and the only VST´s Sylenth, Shaperbox, Voxengo SPAN+ and Psyscope Pro...
I used them in every project since years and none of them has ever caused any trouble in FL Studio, Reaper, Studio One and my limited experience in Bitwig...