DSP Robotics Support

I have tried 3 different ways since now discovering that a small control module is all of a sudden crashing Reaper-32 when closing the project.

This is the EVENT ERROR MESSAGE:

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 2/28/2015
Time: 8:03:20 PM
User: N/A
Computer: ------
Description:
Faulting application reaper.exe, version 4.7.5.0, faulting module mcf-ar v1.9.dll, version 0.0.0.0, fault address 0x00098e46.

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 37 2e 35 2e 30 20 4.7.5.0
0028: 69 6e 20 6d 63 66 2d 61 in mcf-a
0030: 72 20 76 31 2e 39 2e 64 r v1.9.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 30 fset 000
0050: 39 38 65 34 36 0d 0a 98e46..

I've not a clue what help this might be

I'm still on FS 3.0.4 on a WinXP-32 system.

Why the crashing has started is a mystery as this DID work [but I did this VST module back on v:3.0.2 I believe].
The current crashing is only when I close the Reaper project or quit Reaper all together. The VST module in question works exactly as programmed without a hitch ... 'cept the crash upon closing.

2nd note: I use this VST module within the chaining program Plogue BIDULE. I have the very latest version of it ... everything works ... minus the closing crash.

My question ... has something changed in the FS upgrade to 3.0.4 that could be the problem ?

I can post a screen shot & the schematic ... but basically:

This is a VST module that routes AUDIO between a MAIN output and a BYPASS output. Within BIDULE I have the routing set to allow 2 main stereo audio paths available [only one at a time]. Via a MIDI command [CC-30] sent on specific MIDI channel I can choose between the 2 pairs. The MAIN goes into another VST plugin that does audio processing, and the BYPASS choice skips around this plugin to continue passing audio through the rest of the chain.

Maybe someone can help identify the cause. Any info or data I can provide I'll be glad to.

I had this all working ... Mr NuBeat and STW were so kind to help design this ... and it use to work.

Thanks everyone. Because the crash is so consistent and happens only when closing the project, there must be some fundamental cause that I'm not finding in 3 different re-design attempts.

Again ... Thanks

OK ... just to keep this as simple/direct, here is a basic schematic that routes audio to 2 destinations based on the status of a switch:

This design uses the MULTIPLEX Prim as the base.

I have others that use RUBY for streaming, and another using GREEN ... each of these can do the job, some better than others .... but they all crash Reaper on close

Am I missing something so basic ??

Does having OUTPUTs not connected to anything cause a problem?

Still perplex what could have happened. I'm using REAPER v:4.75 [not the very latest I know] ... Now I wonder if this is a Reaper issue ?!??

Switching OUTPUTs is just a simple BOOLEAN toggle [basically]. How bad could I have messed this up

nada ?

Not even a bone

I would write to Malc/devs.

I recreated your multiplexer schematic and tried it with Reaper 4.55 (!). No issues. For convenience I attached the version I built for use in Reaper. I suspect it has nothing to do with Flowstone or Reaper, but bidule.

Hi tulamide,

Thanks for checking this out in Reaper.

I see you ran it in an earlier version [4.55]. The one I use [4.75] is not even the latest.

The switch you posted is just like one of the ones I used. I have several variations that use a 'ramping' feature to make the switch more gentle. They all worked previously.

Along the way, Reaper, BIDULE, and FS were all updated. Now to try and figure out which app is the culprit

Since I've read nothing of this issue directed to FS [although there are some which makes me hesitate to buy the upgrade from 3.0.4], either this is not a common use for others or FS is not the cause.

I've installed the latest BIDULE, but no improvement. Maybe Reaper having BIDULE issues ?? I don't know.

As I search/test fora solution, I'm looking to see if I can figure out how to do this switching using BIDULES built-in modules. So far that has not gone well

Again ... thanks for taking the time ... appreciate that !

just thinking ...

might the problem be due to the OPEN connection to the OUTPUT ? It's basically becomes an output with nothing there ... could these cause an issue ?

To test for something like this, could I tie in a 'default' value [like '0'] to the 2 open outputs ? How would this be done ?

Remember ... loading this all in ... the entire fx chain works. I can save off a session and reload ... still good. It crashes Reaper only when closing the session.

alright, I'm on my first sips of coffee ... so

Empty output = 0. But if you are not sure - put some -180dB noise to all outs. Since FS items like filters (3 months without flowstone and I'm starting to forget the names of descriptors...) don't like to process 0's, maybe the same happens on something connected after your plugin?

Option 2: instead of using multiplexers - you can create active ones using multipliers (thus - no recompiling within schematic).

OK ... I'll do some testing on the 1st option. Maybe this could mess up closing the app?

Option 2: instead of using multiplexers - you can create active ones using multipliers (thus - no recompiling within schematic).

This sounds very interesting ! particularly the 'no recompiling'].

Could you provide more info on what to use ?

Thanks tester