[closed] Bitwig 1.2 doesn't start on El Captain after you closed it.

asked Oct 02 '15 at 17:05 by drishti (146)

—

Bitwig 1.2 doesn't start on El Captain after you closed it once. Only thing that helps is a reboot or to start it from the terminal.

I am also having this problem with 1.3. It is something to do with El Capitan. I am running Bitwig 1.3 on another computer that is still running Yosemite and no problems at all with 1.3. The thing is that Apple has already released their .1 update and no change in this situation. I have a feeling that the ball might be in Bitwig's court to get this corrected which is tough after the release of 1.2 and 1.3. I hope something happens soon because I have come to rely on Bitwig Studio as my central DAW and I am having to use Live right now :( It would help to get some feedback from Bitwig on this.

— (Oct 31 '15 at 10:20) gmg16

just tried in the latest OSX beta of El Capitan version 10.11.2 Beta (15C27e). Still same problem.

— (Nov 03 '15 at 21:18) gkillmaster

The problem solved in Bitwig 1.3.2.

— (Nov 20 '15 at 00:32) Petroff

The question has been closed for the following reason "The question is answered, right answer was accepted" by drishti Dec 06 '15 at 19:02

32 Answers:

oldest newest most voted

1234next page »

Problem is fixed in 1.3.5

link

answered Dec 06 '15 at 19:02 by drishti (146)

My temporary solution is running Bitwig from the Terminal.

Open Terminal (/Applications/Utilities/) and run the following command:

/Applications/Bitwig\ Studio.app/Contents/MacOS/BitwigStudio

It works without restart or Logout/Login.

link

answered Nov 01 '15 at 19:08 by Petroff (74)

Doesn't work for me, but "open -n Bitwig\ Studio.app" does.

— (Nov 16 '15 at 21:26) simon_n

Hi! Great! You fixed my bug! But I am not working with the same OS version, I just keep the OS 1.8.5… so, the new Bitwig Studio is not just unstable with the most recent version of OS. I reported the bug to the technical team, it is on the way… Best Regards

— (Nov 27 '15 at 05:10) kafaktor

They have something to work on, and it;s called Java... Do not bother with your config, Bitwig is using outdated routines just not signed by El Capitan. Someone focused a lot on the surface and less on the Captain i suppose

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=200m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=300m; support was removed Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: conn Nov 3 15:42:39 BitwigStudio[8960] <warning>: Backtrace (at 23818): Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 0 CoreGraphics Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 1 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 2 Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 3 Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 4 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 5 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 6 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 7 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 8 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 9 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 10 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 11 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 12 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 13 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 14 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 15 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 16 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 17 AppKit Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 18 Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 19 ??? Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 20 ??? Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 21 ??? Nov 3 15:42:39 BitwigStudio[8960] <warning>: void CGSUpdateManager::log() const: 22 ??? in 8.0 0x1d3c7 token 0xbffffffffff71e 0x00007fff9812b7c0 CGSDisableUpdateToken + 155 0x00007fff91c4131f disable_updates_sync_block_invoke_2 + 17 libdispatch.dylib 0x00007fff915013c3 _dispatch_client_callout + 8 libdispatch.dylib 0x00007fff915029aa _dispatch_barrier_sync_f_invoke + 74 0x00007fff91c411ed NSCGSDisableUpdates + 1162 0x00007fff91c40c6e NSCGSTransactionRunPreCommitActionsForOrder + 156 0x00007fff91c40bbf NSCGSTransactionRunPreCommitActions_ + 31 0x00007fff923e9596 -[_NSCGSTransaction synchronize] + 42 0x00007fff923e9709 NSCGSTransactionSynchronize + 76 0x00007fff921d58d1 -[NSSurface syncSurfaceWantsExtendedDynamicRange] + 150 0x00007fff91d13bb5 -[NSSurface _createSurface] + 677 0x00007fff91d13510 -[NSSurface setFrame:] + 785 0x00007fff91d12e1a -[NSSurface syncToViewUnconditionally] + 174 0x00007fff91d12ac8 -[NSSurface orderSurface:relativeTo:] + 101 0x00007fff91e06b66 NSOpenGLContextAttachOnScreenViewSurface + 183 0x00007fff9212d633 27-[NSOpenGLContext setView:]_block_invoke + 192 0x00007fff91c2ff05 NSPerformVisuallyAtomicChange + 147 0x00007fff91df392d -[NSOpenGLContext setView:] + 119 libcocoa-windowing-system.jnilib 0x000000012357ce59 Java_com_bitwig_mac_1windowing_1system_OpenGlRenderStrategy_copyToWindow + 329 0x000000010bfb3954 0x0 + 4495980884 0x000000010bfa5c4d 0x0 + 4495924301 0x000000010bfa5c4d 0x0 + 4495924301 0x000000010bfa5c4d 0x0 + 4495924301

link

answered Nov 03 '15 at 15:45 by Banshee700 (0)

the problem came with el capitan and the apple developer team has been notified. Also that the Sylenth 1 vst does not longer open the window. hopefully it will be fixed with next el capitan update :)

link

answered Oct 06 '15 at 22:42 by Jimmy (41)

Unfortunately, the latest update of El Capitan (10.11.1) does not fix the problem...

— (Oct 21 '15 at 22:38) Essdi

I just updated to El Capitan and I'm having the same Sylenth1 issue as well as the same issue with it not opening after it's been closed. I'm really hoping they fix the Sylenth issue because that's my main go-to synth that I use the most :(

— (Nov 02 '15 at 17:42) newman

Same here. No changes with 1.3 nor latest El Capitan update. Pls fix Bitwig.

Best work-around is user logout/login - faster than rebooting, and terminal doesn't work for me.

link

answered Oct 24 '15 at 19:54 by Dopplgngr (23)

—

edited Oct 24 '15 at 20:03

Same problem here. I don't know if the problem comes from the update of bitwig or osx because i did the update at the same time. Maybe it can be useful if we add our configuration...

Macbook pro 13 retina mid.2014 - 2.6 i5 - 16go RAM - OSX 10.11 - Audio interface : Steinberg UR22 - Bitwig 1.2 use in dual screen mode

link

answered Oct 04 '15 at 11:21 by Essdi (6)

i can confirm that. after completely removing the app, the preferencies and the folder in application support it worked for a short time. but after installing the first packages and opening and closing it a couple of times it stopped. just gives you an error sound when clicking the dock icon. starting it from the terminal doesnt work either. only after rebooting my macbook.

-edit-

opening bitwig with the terminal works when you add the "sudo" command

link

answered Oct 05 '15 at 11:32 by steampunkdnb (66)

—

edited Oct 05 '15 at 18:52

The problem remain with the 1.3 version... I am not a specialist with the terminal, what did you type ?

— (Oct 06 '15 at 22:22) Essdi

2	apparently it works only once, then you have to reboot again. open your terminal and type sudo open /Applications/Bitwig\ Studio.app — (Oct 06 '15 at 22:54) steampunkdnb

Thank you !

— (Oct 07 '15 at 21:29) Essdi

Clean install of El Capitan and Bitwig 1.2 displays this behavior. Seems like it will only launch once per user context, which is why you can get a second round by running it under sudo from terminal. Enhanced Java security?

link

answered Oct 07 '15 at 16:35 by JosiahMcGurty (11)

1	I have the same exact problem. It's very annoying. Only a log out and log back in, or a full restart lets you open Bitwig Studio again. It's just not possible to use it properly at all right now which is a shame. I hope this gets sorted quickly. — (Oct 15 '15 at 17:12) tntmp

Same problem here...

link

answered Oct 25 '15 at 18:06 by Banshee700 (0)

Same here on Bitwig 8-Track with MacBookPro Retina i7 2.6 GHz 16GB with OSX 10.11.1

link

answered Oct 26 '15 at 00:09 by Fleer (11)

1234next page »

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

learn more about Markdown

Tags:

bug ×17
osx ×14
1.2 ×11
elcapitan ×5

Asked: Oct 02 '15 at 17:05

Seen: 3,611 times

Last updated: Dec 07 '15 at 02:32

[closed] Bitwig 1.2 doesn't start on El Captain after you closed it.

The question has been closed for the following reason "The question is answered, right answer was accepted" by drishti Dec 06 '15 at 19:02

Follow this question

Related questions