Arturia JP-8 V crashed GP5 twice tonight

Plugins
1

Before i start, i know I’ll get loads of posts about it being rock solid. It has been for me until tonight.
Im on a MacBook Pro M1 and everything is up to date (other than JP-8 V ironically, that was one update behind the current one).
I was using the knobs and sliders on my Keystep MKII, in Arturia mode, nothing else in the Rackspace other than a Midi in and my interface.
This has never happened to me before. With any Arturia pluggins, but im now very nervious.

If someone can guide me as to how to find and upload the crash log im happy to do this. If anyone has any idea what i can look at as to why this happened please let me know.

2

Not sure if this is the current procedure: GP crashing when using "open recent" - #4 by keyman

1 Like
3

Thanks. I followed that and there was nothing showing.

EDIT: I think I did it wrong, I’ll have another look tonight. I looked just as I was leaving for work.
Is it ok to cut and paste it here or should I upload it as a zip file?

4

Please attach the zip file. Thank you.

5

Nope. There is nothing there. I had a look on my Mac mini at work and i can see a couple of crash reports from other programs, so looked in the same place on my MBP which has GP on it but the list is empty.

6

Can you search for *.ips files (in the Finder)?

Alternatively, try to crash the Arturia plugins again and copy the report here.

The report will show the culprit.

7

Thanks for that.

Here are two of the cash reports. Strangely they are both now showing in the Console.

Archive.zip (62.2 KB)

8

Crash is definitely in the Jup-8 as can be seen from this crash report. Please report to Arturia

Thread 0 Crashed:: HotFudge Dispatch queue: com.apple.main-thread
0   Jup-8 V4                      	       0x428428e70 0x427c34000 + 8343152
1   Jup-8 V4                      	       0x428417954 0x427c34000 + 8272212
2   Jup-8 V4                      	       0x428416eec 0x427c34000 + 8269548
3   Jup-8 V4                      	       0x42819e964 0x427c34000 + 5679460
4   Jup-8 V4                      	       0x42895f698 0x427c34000 + 13809304
5   Jup-8 V4                      	       0x42884f648 0x427c34000 + 12695112
6   Jup-8 V4                      	       0x42884f3e0 0x427c34000 + 12694496
7   CoreFoundation                	       0x183e654d8 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
8   CoreFoundation                	       0x183e6546c __CFRunLoopDoSource0 + 176
9   CoreFoundation                	       0x183e651dc __CFRunLoopDoSources0 + 244
10  CoreFoundation                	       0x183e63dc8 __CFRunLoopRun + 828
11  CoreFoundation                	       0x183e63434 CFRunLoopRunSpecific + 608
12  HIToolbox                     	       0x18e60d19c RunCurrentEventLoopInMode + 292
13  HIToolbox                     	       0x18e60cfd8 ReceiveNextEventCommon + 648
14  HIToolbox                     	       0x18e60cd30 _BlockUntilNextEventMatchingListInModeWithFilter + 76
15  AppKit                        	       0x1876c2cc8 _DPSNextEvent + 660
16  AppKit                        	       0x187eb94d0 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700
17  AppKit                        	       0x1876b5ffc -[NSApplication run] + 476
18  GigPerformer5                 	       0x1052f8e60 0x104c60000 + 6917728
19  dyld                          	       0x1839fb154 start + 2476

111
9

Yeah, thats what i said in my first post.
Only happened when i was turning knobs on my controller. I guess i shouldn’t do that again.

10

Well, that should NOT crash the plugin — I assume you can turn knobs on other plugins without problem.

You should report this issue to Arturia

11

I don’t normally use real time control on my sounds liek this This was just a manual filter sweep. Didnt happen all the time, but im nor going to risk it. I normally use Zenology for that sound and don’t have any issues, but i thought id try JP-8 as i found a more suitable tone.

There are no issues using the Plugin as stand alone so im not getting in to blame ping pong. Arturia will say if its not doing it in stand alone its not their software etc. I’ll go back to using Zenology Pro if i have to.

Im not aksing for help here, just wanted to flag this up for reference.

12

Standalone and plugin are 2 different piece of software.
Why not help Arturia to improve their software in sending them the crash report.
In the past they have been very responsive when they got a crash report.

13

Sigh - there’s no ping pong - we don’t play the blame game – if it was our fault, we would immediately own and address it - but it’s clear from the stack trace that it’s an Arturia issue.

We have a VERY good relationship with Arturia, they have our host for Q/A so if you let them know about this issue, they will look into it, possibly contacting us if ncessary.

14

Nonsense. That’s like arguing that if their plugin works in their standalone mode (which is basically just a very trivial plugin host, by the way) then if it breaks in any DAW it must be the DAW’s fault.

15

Ive got a workaround. Thats good enough for me for now. I don’t have the time or inclination to fault find this, especially when my knowledge of Macs is still very basic and i don’t wan to change anything as everything else is working.

In no way am i suggesting its GP thats at fault, but ive been palmed off with other software companies in the past and ended up giving up as each company said to contact the other.

Feel free to bring this up with Arturia if you want. If it happens again I’ll email them but for now im not bothering.

I have contracted them about a Minifuse1 not behaving itself and got told it’s normal, and yet its never happened to any of the other interfaces ive been using.

16

I have been told EXACTLY this in the past. you might not do it, but others do.

17

So on which location did you find them?

I’d like if you reported this to Arturia. I bet they would take care of this quickly.

If they don’t respond (which is unlikely) I’ll contact them. Is that OK?

21

Ive had a response back from Arturia.

I told you it was a waste of time. not going to help at all.

This is what I got back.

"Thank you for reaching out and sorry for the inconvenience

We developed our instruments to be used with the following Platform specifications:

Windows

  • Win 10+ (64bit)
  • 4 GB RAM
  • 4 cores CPU, 3.4 GHz (4.0 GHz Turbo-boost)
  • 32GB free hard disk space
  • OpenGL 2.0 compatible GPU
  • ARM processors not supported on Windows

Apple

  • Mac OS 10.13+
  • 4 GB RAM
  • 4 cores CPU, 3.4 GHz (4.0 GHz Turbo-boost) or Apple Silicon CPU
  • 32GB free hard disk space
  • OpenGL 2.0 compatible GPU

===>>> For more information about the compatible DAWs, I invite you to take a look at the following link:

I’m really sorry, but there isn’t official compatibility with GigPerformer 5 and unfortunately, we cannot guarantee that our softwares will function smoothly in that environment.

Thank you so much for your understanding.

Let me know if you need more assistance."

22

No, trust me, it was not a waste of time.

5 Likes
23

@Dave_bass5

Dave, Arturia wants to know the exact version number of the plugin that crashed.

Thanks
D