Page MenuHomePhabricator

Crash when using FX action
Closed, ResolvedPublic

Description

Hi,

Until now i was running 0.1.3(51) of mixing station on Windows 10 and i just updated to latest version, to maybe incorporate thing like app-link to my setup.
But it crash really a lot.

Basically my setup is a bunch of midi controller that control the software with inbetween Max4live for the midi link and a lot of extensive midi feature (that alow me to have motirized faders control volume, and with a push switch to GEQ or having LED Knob switch from EQ to send, to resume give the midi setup and tactile screen a console behaviour custom to my need).

With previous version, even with this "heavy" midi processing it was very stable, but now, well, absolutely not.

As long as there is no active interaction between max4live and mixing station nothing crash (even the regular "midi actualisation" that mixing station does is okay).

But when i start to actively turn knobs, switch pages or try using app-link, it crash within 3 min, sometimes in an instant.
This is the error that i got.

Mixing station has crashed.

jave.lang.NullPointerExeption

at codeBlob.cg.d.d(sourceFile:81)
at codeBlob.ky.c.d(sourceFile:225)
at codeBlob.cl.a.d(sourceFile:83)
at codeBlob.mx.g.f(sourceFile:50)
at codeBlob.mx.g.c(sourceFile:577)
at codeBlob.cf.b.b(sourceFile:429)
at codeBlob.cf.b.a(sourceFile:330)
at codeBlob.ch.a.a(sourceFile:52)
at codeBlob.ch.d.run(sourceFile:170)
at javae.base/java.lang.Thread.run(Unkown Source)

For now i will revert back to 0.1.3(51) as a obviously need stability for my work (even tho i have a tablet also running mixing station as a backup in case there is any trouble with the computer).
But i will love to use the latest version with the new features later on !

Platform: Windows
Variant: XM32
Version: 1.1.1(154)

Event Timeline

Your previous version was very old. The crashes could be a result of a corrupt midi mapping file since crash is happening in the FX action.
Usually it's best to update more regularly.

I'll take a look at the details tomorrow, maybe it's really an app issue then I can fix it tomorrow

{{userId:1}}

Hi,

Yes i do have a rules, if i don't update if i don't have time to fix my overall system afterward.
Perhaps i should just update more often with probably just little fixes to do.

Annyway,
i did install from fresh the new version on backup computer, and toying around this afternoon and it seems to work juste fine (with just the "old" midi mapping file).
So maybe if was just a case that indeed update from quit an old version did something wrong.

{{userId:3520}}

For now, there is just one thing that does not work as intended (applink), i did use a completely new app setting to try it out.

-> if i create a button for an open view (let say Channel PEQ) and use the applink option so it open on the tablet, it won't work.
I have to first use it once with normal setting, so it open on the PC, then go back to the button config, select the app-link option and now it work as intended and open it on the tablet.
(if i save this, close the app, open it again, and try to us the button it is not working)

-> if i create a midi command link to a controller button for an open view and select app-link, it just crash right away as i exit midi config.

ps: toying around with app-link and channel processing window got me thinking, i will open a new ticket to give you my point of view on how to integrate this in the most flexible way (imo).

{{userId:3520}}

AnonymousTaskBot mentioned this in v1.4.3.
AnonymousTaskBot mentioned this in v1.1.2.
AnonymousTaskBot mentioned this in v1.2.2.
AnonymousTaskBot mentioned this in v1.2.2.
AnonymousTaskBot mentioned this in v1.2.2.
AnonymousTaskBot mentioned this in v1.2.2.
AnonymousTaskBot mentioned this in v1.2.2.
AnonymousTaskBot mentioned this in v1.2.2.
david renamed this task from Repeted crash after updating to last version (probably midi related) to Crash when using FX action.Mar 26 2021, 11:37 AM