DSP Robotics Support

Ehm...

And you can move it into code (less cables) or asm (optimization?), and hop if needed.

Someone told me to use Selectors instead of Multiplexers to switch stuff off, so that's what I do.

But now that you mention multiplying by 0... that could very well fix the bug I have currently with poly streams switched off via selectors. So thanks for that.

tester wrote:Ehm...

And you can move it into code (less cables) or asm (optimization?), and hop if needed.

OK ... I see this [kinda] ... never did anything like that. But I hooked it up the way I thought it should be [using the first, top example], and indeed, it switches between the 2 outputs. very cool.

I'm going to implement this within my project and test how it works in the 'real world'.

Will report back.

Thanks Tester.

Back from testing the 'tester' design.

First, let me say, this is an interesting concept ... one I'd not seen or used before. Implementing this into my project file was quite simple. [which is always welcomed].

I was able to test the operation within FS by feeding a WAVPlayer input and routing the outputs to 2 different monitor systems [the 'MAIN' and the 'ByPass' for the test]. It worked great as I could manually toggle to either system with a BOOLEAN.

I then wired this routine into the logic section of my project, and then exported as VST.

In Reaper, I called up my test FXChain which has a MIDI Controller [VST] and BIDULE [housing several VST's with additional support modules like MIDI CH filter and this special routing module.

Again ... everything worked ! The BYPASS was a hard change as I have no ramping feature that I would put in [wanted to keep this as straight forward, simple as possible]. Everything worked.

When came time to CLOSE the audio project. Hmmm ... Reaper got busy. The harddrive began lots of activity [like I've seen before - not in a good way] ... and after a bit of time ... REaper just disappears [crash] to the desktop. No error message showed up ... just straight to the desktop

Basically ... this is the problem every design I've tried has resulted in.

I can save the project, and it will load up correctly and work just fine. It's the closing of the project that brings the crash.

I'm stumped

I'm trying to think of a way I could test this ONLY using Reaper's FX chain [leave BIDULE out of it], as I try to narrow down who has the problem

perplexed.

RJHollins wrote:I'm trying to think of a way I could test this ONLY using Reaper's FX chain [leave BIDULE out of it], as I try to narrow down who has the problem

I already told you, the problem is bidule. As I said I already tested using only Reaper, the audio was routed to the correct channels when switching bypass on and off, and Reaper didn't crash. I also used an older version than yours, to show you that it has nothing to do with your Reaper version being to old. I also used exactly your chematic to show you that it isn't a Flowstone issue either. All you needed to do was inform the developers of bidule of the issue. Instead you worked hours and hours just to get to the same results, I told you 18 hours ago

If you still don't head over to the bidule forum, you will never solve this.

Do you have/use BIDULE ??

Like I said, there were 3 pieces of software that have been changed/updated, so it adds to the troubleshooting task to figure out ... and NONE of this software is bug-free.

In particular ... the FIRST culprit I look at is ANY plugin I make with FS


Now that I'm registered at the Plogue forum, I'll post this particular issue there ... see what results from that.

Considering what BIDULE is, there are some extreme templates built that use multiple VST's that easily 'talk' on 16 INs and OUTs. One of the OUTPUT modules handles 64 outputs As I read through the forum, I have yet to see anyone mention a similar issue that I have with a 2-in, 4-OUT circuit. That's not to say there is not a bug somewhere, but MY little 'simple' routing switch can take down REAPER

Anyway ... I was fortunate to get some BIDULE help, and have modified a piece that is native to BIDULE to handle the switching via [CC-30]. It works, and most importantly, does NOT crash.

Still, I'm a bit disappointed to not use my FS module to do this particular function. I kept the MIDI FILTER VST that is FS made [works].

These are mainly personal tools I use for my Mastering job. Maybe the BIDULE guys will find something ... but for now, I've a full working chain ... got to be happy about that

I'll post back any reply.

Thanks for helping Guys ! Additionally ... I did get to see/learn about a different routing technique [tester] ... so it is all good.

Glad you got it working!

Regarding troubleshooting: I understand that you were insecure. But, let me show you what I saw from your descriptions and my additional tests:

1) A plugin made with Fowstone works. No crash.
2) A plugin made with Flowstone and Reaper started. Works. Reaper closed. No crash.
3) A plugin made with Flowstone, Reaper and bidule started. Works. Reaper closed. CRASH.
4) A plugin made with Flowstone and Reaper started. Works. Reaper closed. No crash.
5) Dozens of plugins, Reaper and Reason via Rewire started. Reaper closed. No crash

Don't you see any significance there?

Thanks !

Full report and LOGS have been sent to Plogue.

I had time to test an identical setup, but using the METAPlugin chainer from DDMF.

Works ... without any issue or crashing. I actually forgot I bought this plug

will report back.