asked Mar 01 at 18:09 by KAZNakamura (11)

Hi, After upgrading to Bitwig 2.3 beta 4 until 2.3 official release, always my Bitwig Studio crashes when launching. Too short time to send crash report. Nothing I can do.

Is there any way to have workaround?

Thanks in advance.

This is the Q&A system for usability questions, for technical issues please contact our support team!

link

answered Mar 01 at 18:10 by dom ♦♦ (2.0k)

Hi,

same problems here also with 2.3.1 on MacPro 2010 with High Sierra 10.13.2.

Also not able to send a crash report.

:-(

link

answered Mar 03 at 10:40 by kraimor (21)

Some VST and VST3 plugins are responsible for my crashes. (I´ve identified the responsible plugin in the logfile and copied it away in another folder. Then started bitwig again and read the new logfile. Same process again and again and again...)

BUT I´ve still a crash.

Something is wrong with the audio engine...

See following logfile:

[2018-03-04 13:20:28 float-main-app info] Starting application version 2.3.1 revision 8fb00fe8ddb9d9f90d05496d669135f7bdcc48aa [2018-03-04 13:20:28 float-main-app info] Starting with arguments [2018-03-04 13:20:33 duration-monitor info] FloatMainApplication.initializeDeviceLibrary() took 18 ms [2018-03-04 13:20:33 duration-monitor info] FloatMainApplication.initCoreContentFileSystem() took 0 ms [2018-03-04 13:20:33 duration-monitor info] FileTypeResourceLocator.populateWithAllFileTypes() browser/unknown_file.svg took 4 ms [2018-03-04 13:20:33 duration-monitor info] MediaManagerNotificationWidgets.register() took 0 ms [2018-03-04 13:20:33 duration-monitor info] LibraryMetadataReaders.init() took 89 ms [2018-03-04 13:20:33 duration-monitor info] LibraryProject.init() took 23 ms [2018-03-04 13:20:33 duration-monitor info] FloatMainAPplication.openChecksumCache() took 100 ms [2018-03-04 13:20:33 duration-monitor info] FloatMainApplication.determineDocumentsToRecoverAfterCrash() took 4 ms [2018-03-04 13:20:33 duration-monitor info] FloatMainApplication.registerDefaultLabelProviders() took 4 ms [2018-03-04 13:20:33 duration-monitor info] FloatMainApplication.initProfiles() took 19 ms [2018-03-04 13:20:33 duration-monitor info] FloatMainApplication.loadConfigFile() took 0 ms [2018-03-04 13:20:33 duration-monitor info] FloatMainApplication.loadPreferences() took 95 ms [2018-03-04 13:20:33 duration-monitor info] FloatMainApplication.initializePackageManager() took 12 ms [2018-03-04 13:20:34 duration-monitor info] FloatMainApplication.initSingleInstanceApplication() took 826 ms [2018-03-04 13:20:34 duration-monitor info] SingleInstanceGUIApplication.init() took 834 ms [2018-03-04 13:20:34 duration-monitor info] FloatMainApplication.init() took 853 ms [2018-03-04 13:20:34 notifications warning] No Audio Device selected: You need to choose an Audio Device before using Bitwig Studio [2018-03-04 13:20:38 float-document-master error] Error launching or running engine for project New 1: Engine Audio Device not properly configured [2018-03-04 13:20:38 float-engine-communication info] Engine process successfully started [2018-03-04 13:20:38 notifications warning] No Packages Installed: We recommend to install at least the Essentials Collection [2018-03-04 13:20:39 base-control-surface warning] Could not register Jython interpretter: org.python.jsr223.PyScriptEngineFactory [2018-03-04 13:20:39 base-control-surface warning] Could not register JRuby interpretter: org.jruby.embed.jsr223.JRubyEngineFactory [2018-03-04 13:20:39 float-document-master error] Error launching or running engine for project New 1: Engine Audio Device not properly configured [2018-03-04 13:20:39 float-main-app fatal] Application crashing in subsystem GUI Event Thread: com.bitwig.graphics.cairo.CairoException: input string not valid UTF-8 at com.bitwig.graphics.cairo.CairoGraphicsOutput.setScaledFont(Native Method) at com.bitwig.graphics.cairo.CairoGraphicsOutput.Piy(SourceFile:823) at bKc.ruM(SourceFile:541) at bKc.tgh(SourceFile:516) at bFY.kA2(SourceFile:3303) at bFY.Piy(SourceFile:1240) at com.bitwig.flt.app.eCu.Piy(SourceFile:1763) at bFY.Ulk(SourceFile:1198) at bFY.ObF(SourceFile:1152) at com.bitwig.flt.app.HAN.ObF(SourceFile:1741) at bFY.UIf(SourceFile:886) at com.bitwig.flt.app.BitwigStudioMain.main(SourceFile:185)

My audio interface is a RME Fireface UFX. I´ve also tried to turn off the Fireface and started bitwig again. Same problem

link

answered Mar 04 at 13:33 by kraimor (21)

edited Mar 04 at 13:35

Hi,

I also checked the crash log and found responsible(?) plug-in, deleted it away and still have a crash. I checked the crash report again and another new suspicious plug-in. Yeah, endless!

After deleting some plug-ins, now I gave up and waiting for answer from BW tech team.

Thanks for your information, any way.


iMac (Late 2013) macOS Sierra 10.12.6 2.9 GHz Intel Core i5 16 GB 1600 MHz DDR3

Audio I/F Persons FIRESTUDIO mobile

MIDI I/F novation LAUNCHKEY 25

link

answered Mar 04 at 13:59 by ejammer (11)

edited Mar 04 at 15:11

Following plugins are responsible for my crashes: Brainworx Megasingle Brainworx Shredspread Brainworx Solo Brainworx Stereomaker Brainworx Tuner Noveltech Character Orchestral Companion Strings_64 Orchestral Companion Strings SPL Transient Designer Plus

If you look in my logfile above I´ve identified some interesting:

Application crashing in subsystem GUI Event Thread: com.bitwig.graphics.cairo.CairoException: input string not valid UTF-8

13:20:39 float-main-app fatal] Application crashing in subsystem GUI Event Thread: com.bitwig.graphics.cairo.CairoException: input string not valid UTF-8 at com.bitwig.graphics.cairo.CairoGraphicsOutput.setScaledFont(Native Method) at com.bitwig.graphics.cairo.CairoGraphicsOutput.Piy(SourceFile:823) at bKc.ruM(SourceFile:541) at bKc.tgh(SourceFile:516) at bFY.kA2(SourceFile:3303) at bFY.Piy(SourceFile:1240) at com.bitwig.flt.app.eCu.Piy(SourceFile:1763) at bFY.Ulk(SourceFile:1198) at bFY.ObF(SourceFile:1152) at com.bitwig.flt.app.HAN.ObF(SourceFile:1741) at bFY.UIf(SourceFile:886) at com.bitwig.flt.app.BitwigStudioMain.main(SourceFile:185)

link

answered Mar 04 at 14:03 by kraimor (21)

I have the same problem (UTF8) on my Macbook Pro (10.12.6)

link

answered Mar 04 at 14:45 by kraimor (21)

Try 2.3.2 RC 1 they released a few days ago. It LAUNCH!

I will, though, use 2.2.3 until they release final 2.3.2.

link

answered Mar 11 at 09:32 by ejammer (11)

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×30
×3

Asked: Mar 01 at 18:09

Seen: 714 times

Last updated: Mar 11 at 09:32