Now this is a game changer - Bitwig, Presonus team up DAWProject
- KVRAF
- 25015 posts since 12 Jul, 2003 from West Caprazumia
Oh, and I can see both the Cakewalk and the Tracktion guys hopping on board rather soonish as well...
- KVRAF
- 25015 posts since 12 Jul, 2003 from West Caprazumia
With all your nay-saying and party-pooping I'd say the chances for that are rather abysmal....
-
- KVRian
- 762 posts since 26 Sep, 2007
Why should we keep guessing if you can't express yourself clearly and apparently don't care to be understood?
-
- KVRAF
- 35671 posts since 11 Apr, 2010 from Germany
Is that so hard to understand?chk071 wrote: Tue Sep 26, 2023 3:49 pm Cubase actually even has an API for their MIDI FX, but, it seems like it's very old, and hardly anyone ever made use of it (and it's also, obviously, limited to MIDI FX in Cubase): https://www.steinberg.net/de/developers/ (VST Module Architecture SDK)
You suggested another format. I don't need another format. That's the point. Either VST3 should support this, or Steinberg should develop an offspring which supports this, if they argue that VST is an audio plugin format, not a MIDI plugin format.
-
- KVRAF
- 6159 posts since 4 Dec, 2004
One benefit that may not be obvious: Unlike currently, Studio One 6 users will be able to open songs from versions 7 and up, using that format. Old versions from 6 up will be able to open new version song files using that format... which isn't currently possible and which has been a problem for some collaborating with people who haven't upgraded.
As relates to how many people need to move songs between DAW's, ask the developer of AATranslator who makes money serving those people.
P.S. I predict that AVID won't support it. I don't see them doing anything to make it easy to load PT songs in anything else.
As relates to how many people need to move songs between DAW's, ask the developer of AATranslator who makes money serving those people.
P.S. I predict that AVID won't support it. I don't see them doing anything to make it easy to load PT songs in anything else.
- KVRAF
- 26961 posts since 3 Feb, 2005 from in the wilds
He just hates any interesting development that isn't in his chosen software. That's why he's in this thread and the Studio One 6.5 announcement thread making disparaging comments.
-
- KVRist
- 302 posts since 25 Jun, 2005
You'll lose a lot of specific Studio One features doing that, but if they saved a copy of the DAWProject format for every normal save it would be a very handy option that would enable you to do that in future as a secondary option for sure.LawrenceF wrote: Tue Sep 26, 2023 4:27 pm One benefit that may not be obvious: Unlike currently, Studio One 6 users will be able to open songs from versions 7 and up, using that format. Old versions from 6 up will be able to open new version song files using that format... which isn't currently possible and which has been a problem for some collaborating with people who haven't upgraded.
- KVRAF
- 26961 posts since 3 Feb, 2005 from in the wilds
This collaboration with Presonus makes me think Studio One will support CLAP sometime in the near future.pikey wrote: Tue Sep 26, 2023 3:13 pm CLAP is an open format that allows plugins to generate and process MIDI and act as only a midi fx - https://u-he.com/community/clap/
Currently Reaper and Bitwig are the big(ish) DAWs onboard with the format, so time will tell whether it becomes a de facto format or not.
- KVRAF
- 26961 posts since 3 Feb, 2005 from in the wilds
But still much better than rendering everything to stemsskijumptoes wrote: Tue Sep 26, 2023 4:33 pmYou'll lose a lot of specific Studio One features doing that, but if they saved a copy of the DAWProject format for every normal save it would be a very handy option that would enable you to do that in future as a secondary option for sure.LawrenceF wrote: Tue Sep 26, 2023 4:27 pm One benefit that may not be obvious: Unlike currently, Studio One 6 users will be able to open songs from versions 7 and up, using that format. Old versions from 6 up will be able to open new version song files using that format... which isn't currently possible and which has been a problem for some collaborating with people who haven't upgraded.
-
- KVRAF
- 6159 posts since 4 Dec, 2004
In the stated use case you currently lose everything since you can't open the song file at all. The only current option is to stem and export midi.skijumptoes wrote: Tue Sep 26, 2023 4:33 pmYou'll lose a lot of specific Studio One features doing that..
-
- KVRian
- 851 posts since 24 Mar, 2021
This is very interesting! I hope other DAWs will join that project too, cause the more they are the useful this will be!
- KVRAF
- 11313 posts since 18 Aug, 2007 from NYC
this is great news and I’m hoping more support this.
And I’m very curious to see if Studio One will support Clap.
And I’m very curious to see if Studio One will support Clap.
- KVRAF
- 19818 posts since 16 Sep, 2001 from Las Vegas,USA
So let me see if I can understand why this is a game changer. The idea is to take a project created in DAW A and be able to load it in DAW B?
Other than being able to share projects between collaborators who own different DAWs what is the advantage?
Maybe DAW B has different built in instruments and FX or compositional tools or ? What am I missing?
Other than being able to share projects between collaborators who own different DAWs what is the advantage?
Maybe DAW B has different built in instruments and FX or compositional tools or ? What am I missing?
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
- KVRAF
- 13127 posts since 7 May, 2006 from Southern California
Woah that's really cool! Definitely hoping other DAWs adopt this. I work with other folks projects frequently, so anything that makes moving stems around will make my life easier.
- KVRAF
- 11313 posts since 18 Aug, 2007 from NYC
While I will never expect any release to impress everyone … you’re not missing anything.Teksonik wrote: Tue Sep 26, 2023 5:59 pm So let me see if I can understand why this is a game changer. The idea is to take a project created in DAW A and be able to load it in DAW B?
Other than being able to share projects between collaborators who own different DAWs what is the advantage?
Maybe DAW B has different built in instruments and FX or compositional tools or ? What am I missing?
I’ve done this many times (and it seems others here have too) with moving audio from video to a DAW, where things can be polished up and transferred back. If you have to do this, it’s great that it can be done especially when there are lots of edits.
Right now, if you and I want to collaborate on a project and we’re running different hosts, then we rely on rendering to audio before export, or wecan even include the midi files too.
But! Why this is better… I’m assuming that if you’re using a small time selection of a longer recording, I would have access to that longer recording and might be able to use part of it if something needs fixing, or to circle back and build continuity in a track.
Next is the ability to retain automation. I’m also assuming this is only helpful on a basic level (panning & gain changes), but damn that’s great not needing to contact someone to ask them to render without a volume change to fix something.
This just simplifies things (well, if you’re using BW & Studio One).
The whole different instruments things is not an issue for anyone collaborating, as you would still likely prefer to render to audio before sharing.
There’s also the benefit for those composing in one host, and moving to another to finish for any number of reasons. The whole process becomes easier.
To me, this satisfies one of the only reasons to be excited about a new product… if it either makes you better or helps you work faster. This would help someone work faster *if* they switch hosts or collaborate.