Previous versions of Starling VIA

Plugins & Modules
1

Since the current version of Starling VIA will not load without crashing is it possible to get a previous version of this plugin? It was working fine until the latest update. I do not have a dev environment setup so I am hoping someone can help me. I have a lot of patches using this plugin so…

2

Not sure I understand. It was last updated in the library 4 months ago, which was the first release for Rack v2. So which version are you looking for? FWIW they load fine on my Mac, no crashing.

3

I have some crashes with the Starling modules,
but they load here on Win 11 and VCV 2.1.2

@shofb did you send a bug report to Starling?

4

Are your crashes with OSC3? If so, both that have been found have been reported.

1 Like
5

My mistake I just assumed (I know what that word means) that there was an update since everything was working until a couple of weeks ago when crashes started. Here are 2 log traces both of which point to VIA Meta being the cause. One of one of my patches while the other is a sample.

I posted a bug report on what I thought was their Github site but Andrew closed it and sent me to the VCV Rack support where I posted a bug report. Don’t know why he didn’t want it posted as an issue on their GitHub site. Anyway I sent them an email but have not heard anything from anybody until you guys.

From the example load…

[16.154 info src/engine/Engine.cpp:1395 fromJson] Creating module Starling Via META [16.155 info src/engine/Module.cpp:173 fromJson] Patch created with Starling_Via v0.6.2, currently using v2.0.0. [16.569 fatal adapters/standalone.cpp:48 fatalSignalHandler] Fatal signal 11. Stack trace: 31: 0x0 30: 0x0 29: _C_specific_handler 0x7ff9f73e7f60 28: _chkstk 0x7ff9f8052240 27: RtlRaiseException 0x7ff9f8001070 26: KiUserExceptionDispatcher 0x7ff9f8050e60 25: strlen 0x7ff9f741d2c0

From my patch

[46.650 info src/engine/Engine.cpp:1395 fromJson] Creating module Starling Via META [47.074 fatal adapters/standalone.cpp:48 fatalSignalHandler] Fatal signal 11. Stack trace: 31: 0x0 30: 0x0 29: _C_specific_handler 0x7ff9f73e7f60 28: _chkstk 0x7ff9f8052240 27: RtlRaiseException 0x7ff9f8001070 26: KiUserExceptionDispatcher 0x7ff9f8050e60

6

From the error message I can see that your problem happens when loading an old patch, made with Startling VIA version 0.6.2 which is ancient. It would be nice of course if all patches, no matter how old, could be loaded without problems in newer versions of Rack, but that is far from always the case.

If you make a fresh patch from scratch, with the current version 2.0.0 of Starling VIA modules, does that crash as well? Otherwise, if it’s only crashes with those old versions of starling I’m pretty sure the resolution will be “forget about it”.

7

Loading older patches with the v2 modules should, generally, be OK as I fixed that issue in May

and the build was added to the library in June.

1 Like
8

I would try to edit the patch,
that it tries to load the V2.0.0 Starling Via module.