Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pin connection issue on Windows #45

Open
lossius opened this Issue Jul 29, 2016 · 2 comments

Comments

Projects
None yet
1 participant
@lossius
Copy link

lossius commented Jul 29, 2016

Reported on the Reaper forum by ReaDave:

One thing I forgot to mention too is that there seems to be something odd going on with the pin connections in some of the plugins too. For instance, when I click the pin configuration tab on the 5 channel encoder, the plugin stops passing audio and I have to delete it and reinsert it to get it working again. This also happens with the Binaural decoder and some others too.
If I take it offline and back online it doesn't fix things. I have to remove and reinsert it.

This happens with all versions so far on my PC.

I've received similar reports on Facebook from other users as well, but I have not been able to reproduce (or maybe understand/see/hear) the issue myself so far.

I've asked ReaDave for further details.

@lossius lossius added the bug label Jul 29, 2016

@lossius lossius self-assigned this Jul 29, 2016

@lossius lossius modified the milestone: Version 1.0.0b10 Sep 8, 2016

@lossius

This comment has been minimized.

Copy link
Author

lossius commented Sep 8, 2016

witti reports on this as well in a private message, and provides additional info:

Cockos claimed to have it fixed, but plugins which are
reporting latency with pdc_delay and have more than two channels
still can crash reaper if you open the plugin-pin connector.
The problem is not the amount of channels the plugins are using in the code
but the declaration of in and out pins at the top of the code.
Commenting these in_pins and out_pins out fixes this issue for now...

So for your UHJ decoder for example it is:

//in_pin:W
//in_pin:X
//in_pin:Y
//in_pin:Z

//out_pin:L
//out_pin:R
@lossius

This comment has been minimized.

Copy link
Author

lossius commented Sep 12, 2016

The pin issue on Windows is believed to be caused by Reaper, not my plugins, and there are indications that it might be fixed in the upcoming Reaper 5.25 incremental release. For the time being, I'll wait and see, and I won't do any changes for my upcoming b10 release.

@lossius lossius removed this from the Version 1.0.0b10- maintenance milestone Sep 12, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.