Hey all. While testing out the Bitwig 4.0 beta5 I've run into a bug where exporting audio silently fails and I'm wondering if anyone else in the community has had similar issues.
If I keep an eye on `/tmp/bitwig-emmet/` I can see that a temporary .WAV bounce track is created. But, about half way through the exporting process Bitwig logs some FFmpeg errors and the bounce track is cleaned up without producing the desired output files. It seems like bouncing the tracks down to a single track is working fine, but converting between formats is not.
Here's a log of stdout while exporting: https://pastebin.com/raw/JHCHZmTL
I've tried a variety of different export options, including exporting just a single format (like wav) and exporting all the available formats (wav, flac, opus, vorbis, mp3). I've also tried various bit depths/rates and sample rates, but exporting fails 100% of the time.
My workstation is a bit on the unusual side, since I'm running Fedora 34 Linux with the PipeWire audio server, so it could very well be a problem that's unique to my own set up. I reached out to Bitwig support and they were nice enough to file the report despite my distro not being officially supported, but they were not able to confirm the bug on their Ubuntu set up.
So is it just me or has anyone else been having issues exporting with 4.0?
Bitwig 4.0 Beta: Issue with audio export?
-
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
Yes, this is a pretty commonly reported bug, although I think it was fixed in beta4 (I might be wrong, though):EmmetPDX wrote: Tue Jun 29, 2021 9:34 pmHey all. While testing out the Bitwig 4.0 beta5 I've run into a bug where exporting audio silently fails and I'm wondering if anyone else in the community has had similar issues.
If I keep an eye on `/tmp/bitwig-emmet/` I can see that a temporary .WAV bounce track is created. But, about half way through the exporting process Bitwig logs some FFmpeg errors and the bounce track is cleaned up without producing the desired output files. It seems like bouncing the tracks down to a single track is working fine, but converting between formats is not.
https://downloads-eu.bitwig.com/beta/4. ... eta-5.html
-
- KVRAF
- 4874 posts since 13 May, 2004
Send it to the Bitwig Beta mail.EmmetPDX wrote: Tue Jun 29, 2021 9:34 pm Hey all. While testing out the Bitwig 4.0 beta5 I've run into a bug where exporting audio silently fails and I'm wondering if anyone else in the community has had similar issues.
If I keep an eye on `/tmp/bitwig-emmet/` I can see that a temporary .WAV bounce track is created. But, about half way through the exporting process Bitwig logs some FFmpeg errors and the bounce track is cleaned up without producing the desired output files. It seems like bouncing the tracks down to a single track is working fine, but converting between formats is not.
Here's a log of stdout while exporting: https://pastebin.com/raw/JHCHZmTL
I've tried a variety of different export options, including exporting just a single format (like wav) and exporting all the available formats (wav, flac, opus, vorbis, mp3). I've also tried various bit depths/rates and sample rates, but exporting fails 100% of the time.
My workstation is a bit on the unusual side, since I'm running Fedora 34 Linux with the PipeWire audio server, so it could very well be a problem that's unique to my own set up. I reached out to Bitwig support and they were nice enough to file the report despite my distro not being officially supported, but they were not able to confirm the bug on their Ubuntu set up.
So is it just me or has anyone else been having issues exporting with 4.0?
-
- KVRer
- Topic Starter
- 29 posts since 15 Mar, 2018
Hmm... I'm already on beta5.antic604 wrote: Wed Jun 30, 2021 5:57 am Yes, this is a pretty commonly reported bug, although I think it was fixed in beta4 (I might be wrong, though):
https://downloads-eu.bitwig.com/beta/4. ... eta-5.html
Good to know it's not totally unique to my system, though.
Ok, will do.moss wrote: Send it to the Bitwig Beta mail.
-
- KVRer
- 1 posts since 24 Jul, 2021
Im gunna keep this short because im about to throw everything in my studio out my 4th storey window.
I just encountered this bug and overcame the many many many hurdles it presented me to get my track to export.
Im on Bitwig 4.0.1 and its not yet fixed.
Like op said it silently fails and the file is on the computer (recently added list) but does not actually exist.
The other thing is that the project itself is workable but it just wont export.
Even if you save as it still fails.
My workaround was as follows.
1- if you have sends and returns bounce them with all processing so you can have them as tracks. (Unfortunately Bitwigs routing capabilities are limited)
2 - Then open a brand new project and copy and paste everything back to a new file.
3 - try to export and cross fingers.
One if the most annoying problems i faced was that my tracks would ve randomly greyed out and i would have to re copy and paste them from the OG file.
I just encountered this bug and overcame the many many many hurdles it presented me to get my track to export.
Im on Bitwig 4.0.1 and its not yet fixed.
Like op said it silently fails and the file is on the computer (recently added list) but does not actually exist.
The other thing is that the project itself is workable but it just wont export.
Even if you save as it still fails.
My workaround was as follows.
1- if you have sends and returns bounce them with all processing so you can have them as tracks. (Unfortunately Bitwigs routing capabilities are limited)
2 - Then open a brand new project and copy and paste everything back to a new file.
3 - try to export and cross fingers.
One if the most annoying problems i faced was that my tracks would ve randomly greyed out and i would have to re copy and paste them from the OG file.