Never be sure of this and if more people report something the importance raises. I reported some issues to them which got fixed in the latest update.dellboy wrote: ↑Mon Apr 29, 2024 9:39 amThe Bitwig conversion-export side seems to work fine. I exported and re-imported into Bitwig,and all was well. Its when you try to import the converted file into Studio One that it often does not work - very hit and miss. I see no point in reporting this to Presonus,as I am sure they must already know this.moss wrote: ↑Sun Apr 28, 2024 7:03 pmPlease report your issues to Bitwig and/or Presonus, so they can improve it.
Great to hear!dellboy wrote: ↑Sun Apr 28, 2024 6:58 pm So then tried the Moss Project Converter. This converts Bitwig Dawproject songs and can export to Reaper,and this works very well. It will even convert between Bitwigs clip view including scenes.
In Reaper,all the scenes are displayed along the top of the Reaper arrangement page and can be mouse clicked to play the clips in them. It succesfully loaded all the VSTs used in Bitwig seamlessly. Of course,if you use Bitwig instruments to compose your song then a suitable VST substitute will have to be loaded manually.
Latest News: Bitwig updates Bitwig Studio to 5.2
Studio One 6.5 DAWProject Integration
- KVRAF
- 4354 posts since 13 May, 2004
-
- KVRAF
- 2547 posts since 28 Mar, 2007
I take your point.
Further to trying your app with Studio One,I used your converter to import into Studio One,and this pretty much solved all of the problems I had experienced using the native Bitwig converter. Using your app in between Bitwig and Studio One allows for export of the clip view and scenes directly into Studio One much like it works in Reaper. All of the VSTs that I used in Bitwig loaded up correctly in Studio One. Good work
- KVRAF
- 4354 posts since 13 May, 2004
Didn't think of that! Great idea!dellboy wrote: ↑Mon Apr 29, 2024 11:04 amI take your point.
Further to trying your app with Studio One,I used your converter to import into Studio One,and this pretty much solved all of the problems I had experienced using the native Bitwig converter. Using your app in between Bitwig and Studio One allows for export of the clip view and scenes directly into Studio One much like it works in Reaper. All of the VSTs that I used in Bitwig loaded up correctly in Studio One. Good work
-
- KVRAF
- 2547 posts since 28 Mar, 2007
It gets better.moss wrote: ↑Mon Apr 29, 2024 11:37 amDidn't think of that! Great idea!dellboy wrote: ↑Mon Apr 29, 2024 11:04 amI take your point.
Further to trying your app with Studio One,I used your converter to import into Studio One,and this pretty much solved all of the problems I had experienced using the native Bitwig converter. Using your app in between Bitwig and Studio One allows for export of the clip view and scenes directly into Studio One much like it works in Reaper. All of the VSTs that I used in Bitwig loaded up correctly in Studio One. Good work
After importing into Studio One with your converter it is possible to create an arranger track and assign all the Bitwig scenes to intro-chorus-bridge etc,and either rearrange them in the inspector,or just click on them with mouse to trigger them. It takes a few seconds to re-create in Studio One what you previously had in the Bitwig clip launcher.(minus the ability to loop individual clips). I am sure you already knew this,being the creator,but I am just confirming that it works well.
-
- KVRer
- 2 posts since 28 Sep, 2023
Has anyone ever used the DAW project format between Bitwig and Presonus?
I started experimenting with it today. While the export process works, the import into Studio One did not yield the expected results.
In Studio One, the MIDI tracks function properly. However, for the sample tracks (samples triggered using the clip launcher function in Bitwig), the samples only appear once, essentially at the point where I first triggered them in Bitwig. All subsequent beats do not appear.
I am on 5.18 Bitwig and 6.6 Studio One
I started experimenting with it today. While the export process works, the import into Studio One did not yield the expected results.
In Studio One, the MIDI tracks function properly. However, for the sample tracks (samples triggered using the clip launcher function in Bitwig), the samples only appear once, essentially at the point where I first triggered them in Bitwig. All subsequent beats do not appear.
I am on 5.18 Bitwig and 6.6 Studio One
- KVRist
- 72 posts since 6 Mar, 2016
I think the ProjectConverter app by Mossgrabber gives you the best results:
https://www.mossgrabers.de/Software/Pro ... erter.html
But looping Bitwig clips seems not be included till now:
https://www.youtube.com/watch?v=hLLhZivbNDI
P.S.: I tried to convert some Bitwig and Reaper projects with it on macOS 14.5 but got only crashes when I hit the convert button.
https://www.mossgrabers.de/Software/Pro ... erter.html
But looping Bitwig clips seems not be included till now:
https://www.youtube.com/watch?v=hLLhZivbNDI
P.S.: I tried to convert some Bitwig and Reaper projects with it on macOS 14.5 but got only crashes when I hit the convert button.
My offers as studioBischof at Knobcloud: https://knobcloud.com/user-profile/22920
- KVRist
- 72 posts since 6 Mar, 2016
The new version works (again). Thanks, Moss
So you can export Bitwig clips into scene markers in the Studio One arrangement or just record the clips to arrangement in Bitwig before export.
On the sample question: I tried to get the Bitwig Sampler to export via dawproject into a Studio One SampleOne for a Bitwig kick sample, but had no luck. SampleOne doesn't show up. I used Bitwig 5.19 and S1 6.6.
So you can export Bitwig clips into scene markers in the Studio One arrangement or just record the clips to arrangement in Bitwig before export.
On the sample question: I tried to get the Bitwig Sampler to export via dawproject into a Studio One SampleOne for a Bitwig kick sample, but had no luck. SampleOne doesn't show up. I used Bitwig 5.19 and S1 6.6.
My offers as studioBischof at Knobcloud: https://knobcloud.com/user-profile/22920
- KVRAF
- 4354 posts since 13 May, 2004
A generic sampler instrument does currently not exist in the specification but would be interesting to be added. Especially, since both Bitwig and Studio One support the multisample format. And that is also the workaround you can apply. Export a multisample file from the Bitwig Sampler which can then be loaded in to the Studio One sampler.Bjørnson wrote: ↑Sun May 26, 2024 8:05 pm The new version works (again). Thanks, Moss
So you can export Bitwig clips into scene markers in the Studio One arrangement or just record the clips to arrangement in Bitwig before export.
On the sample question: I tried to get the Bitwig Sampler to export via dawproject into a Studio One SampleOne for a Bitwig kick sample, but had no luck. SampleOne doesn't show up. I used Bitwig 5.19 and S1 6.6.