DSP Robotics Support

Working along on my project ... things going well ... added in some new features ... things looking good ...

until ... I export as a VST, and load into REAPER .... which then crashes

From my crash log, I see this ...

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 2/22/2014
Time: 10:12:14 PM
User: N/A
Computer: xxxxxx
Description:
Faulting application reaper.exe, version 4.5.9.0, faulting module nvc-mammoth.dll, version 0.0.0.0, fault address 0x00359561.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 72 65 61 ure rea
0018: 70 65 72 2e 65 78 65 20 per.exe
0020: 34 2e 35 2e 39 2e 30 20 4.5.9.0
0028: 69 6e 20 6e 76 63 2d 6d in nvc-m
0030: 61 6d 6d 6f 74 68 2e 64 ammoth.d
0038: 6c 6c 20 30 2e 30 2e 30 ll 0.0.0
0040: 2e 30 20 61 74 20 6f 66 .0 at of
0048: 66 73 65 74 20 30 30 33 fset 003
0050: 35 39 35 36 31 0d 0a 59561..

does this mean anything to anyone ???

I don't even know where to start looking for the problem

Something else I notice ... this was a few days earlier when FlowStone crashed on loading my schematic:

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 2/20/2014
Time: 1:10:09 PM
User: N/A
Computer: xxx
Description:
Faulting application flowstone.exe, version 3.0.4.0, faulting module msvcr90-ruby191.dll, version 1.9.3.0, fault address 0x0005b5ea.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 66 6c 6f ure flo
0018: 77 73 74 6f 6e 65 2e 65 wstone.e
0020: 78 65 20 33 2e 30 2e 34 xe 3.0.4
0028: 2e 30 20 69 6e 20 6d 73 .0 in ms
0030: 76 63 72 39 30 2d 72 75 vcr90-ru
0038: 62 79 31 39 31 2e 64 6c by191.dl
0040: 6c 20 31 2e 39 2e 33 2e l 1.9.3.
0048: 30 20 61 74 20 6f 66 66 0 at off
0050: 73 65 74 20 30 30 30 35 set 0005
0058: 62 35 65 61 0d 0a b5ea..

again ... no idea what to do

Seems to be related with ruby files. My guess is. Either source ruby guts are damaged (thus exported files will also not work correctrly) or there is a conflict between some exports.

I would try to remove all ruby libs created by FS / FS apps, or I would try to reinstall the Flowstone (remove completely and install again). I would check the older iteration of the project (the one that worked) - if it still works, and this would give me the idea what has changed (and in what way ruby routines were involved; maybe some shared operations cause this). I would remove other FS plugins, to see whether reaper starts with this one only (or at least I would do some rescan on plugins, to clean the cache). At least a point to start with.

I noticed too, that my (standalone) apps have often "crash pattern". When I export the app, and start it in a new location - then first run (only first run) tends to crash it. Then it works fine. Also - when during loading I play with the main gui window and move it on the screen - it tends to crash from time to time. Hmm... Maybe somewhere a redraw limiter could help?

Hi tester,
This is the first time I'm crashing Reaper with a FS-VST. When I go back to an earlier version schematic, I am able to get a working version ... so ... something happened along the way.

I've tried to temp remove some of the updates I did [moving them outside of the main VST module], then re-export, but Reaper still crashes on the Re-Scan.

When I go back to the earlier version, Reaper scans it fine and it works .... so I guess I have to start there and slowly add in the updates and verify.

As to the FS crashes ... I have seen this too. When it happens, it is usually the first time ... the second time usually works

I DO notice that I'll see the 'reddish box' outline when first loading a schematic [like a RUBY overload] but that was usually brief.

Oh well .... got to track this down

Update news ...

Well ... went back to an earlier schematic version that DID compile and load as a VST ... and started the slow debug, modify process.

At first, it seemed that a small, un-used graphic being removed [cause it was no longer needed] would bring on the crash went I sent it to Reaper .... that was really strange [it was a RUBY graphic].

Well, that made no sense ... so I continued to re-add all the new features/mods that I had originally planned for. Each time I did a VST export and test in Reaper. Everything continued to work ... UNTIL ... my final little mod/feature.

This immediately brought the crashing back.

Looking closely into the module, I had a series of wireless Inputs and Outputs happening. They ALL worked correctly in FS ... but crashed Reaper. Disabling the wireless ... Reaper was happy.

hmmm .... I looked at the 'naming convention' I used in the wireless, and recall a TROG post that talked of this topic.

So .... I renamed the wireless OUTPUTS, and complimented their receiver with the same new name.

Export to REAPER .... big smiles No more crash on initial scan.... AND, the VST opened properly.

Well ... I'm happy that I got all the features in ... lost a day in the process ...

The disturbing part ...

Honestly ... try like heck to avoid crashing ... but, I would have thought FS would have complained I guess somethings can slip by.

Well ... I've learned a small lesson here. FIRST ... continue to do INCREMENTAL Numbered saves of a project !

Add to this .... much more export testing in the host during dev.

Anyway ... though I'm not absolutely certain the exact cause, it DOES appear to have been a naming conflict in the wireless connects that was culprit.

As an aside ... I did actually improve what my original design was to be ... so not a total loss by any means ... just a bit a nerve racking and the familiar anguish


off to play with the new VST toy ...

RJHollins wrote:Update news ...
Looking closely into the module, I had a series of wireless Inputs and Outputs happening. They ALL worked correctly in FS ... but crashed Reaper. Disabling the wireless ... Reaper was happy.

hmmm .... I looked at the 'naming convention' I used in the wireless, and recall a TROG post that talked of this topic.

So .... I renamed the wireless OUTPUTS, and complimented their receiver with the same new name.

Export to REAPER .... big smiles No more crash on initial scan.... AND, the VST opened properly.

Could you re-phrase what you mean?

Hi tester ...

not sure I could do a re-phase that would help

But as to the naming convention that TROG talked about .... I found the link:
http://www.dsprobotics.com/support/viewtopic.php?f=2&t=2257&p=10446#p10446

as with most of TROG's post ... something to study and learn from !

Of course ... this had specific reference to RUBY ... I THINK my issue was slightly different, as I was feeding values in and out of a module. Basically, I was controlling 2 buttons in 2 different locations, but they both interacted off each other. Might have been a type of feedback loop going on.... OR ... something got confused [beside me] with the wireless connects.

Once I went back in and changed the naming, things righted themselves. Things can get messy when a programming experiment becomes part of the works. Coming up with label, connector NAMES can sometimes be a challenge. I try to name them something meaningful ... but I think this time I got bit


BTW ... I sure hope the TROG is well ... it has been quite some time since he's posted.