Notifications
Clear all

Reason Rack Plugin


Kendall W Cochran III
(@pbeprod)
Member
Joined: 1 year ago
Posts: 229
Topic starter  

@getdunne

Wondered if you have or use Reason. Do you have the Reason Rack plugin? I've got the Suite 11 which comes with it. Most of the time I have issues with Unify trying to open or even add the plugin as an Instrument in a layer. Usually it just sits there til I have to force it shut.


Quote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@pbeprod

I have Reason Suite, and I have used the Reason Rack plug-in in Unify in instrument, audio-effect, and MIDI-effect slots. It's worked fine for me so far, on both PC and Mac, but I confess I haven't had time to dig into it super deeply.

Can you give an example of a case where you try loading the Rack plug-in and it doesn't work?


ReplyQuote
Kendall W Cochran III
(@pbeprod)
Member
Joined: 1 year ago
Posts: 229
Topic starter  

@getdunne

Never mind. It's worked fine the last 7 times when I've loaded the patch. I've shut Unify, then opened again and the patch has loaded fine. It seems like in my life, if I want something to work all I need to do is request assistance, from then on I can never get it to duplicate the issue. 😳 Thanks!!!

The patch I was using with the problem had 5 instances of the Reason Plugin.


ReplyQuote
Kendall W Cochran III
(@pbeprod)
Member
Joined: 1 year ago
Posts: 229
Topic starter  

@getdunne

Well it froze again. I'm thinking the main issue is when I'm switching between a patch that has Omnisphere instances to the ones that have Reason plugin in them. I then have to close Unify down and reopen for me be able to open the patch.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@pbeprod

If you can send me a recipe to reproduce the issue, I can troubleshoot. Otherwise, I'm sorry you're having grief, but I can't help.


ReplyQuote
Kendall W Cochran III
(@pbeprod)
Member
Joined: 1 year ago
Posts: 229
Topic starter  

@getdunne

When I get done with the current work week I’ll construct an install of the few patches that cause the problems. That way you can drag and drop. All the patches layers contain either Reason standard library, Johns Omnisphere patches, or Unify’s standard libraries. So you should be compatible with these patches.


getdunne liked
ReplyQuote
Kendall W Cochran III
(@pbeprod)
Member
Joined: 1 year ago
Posts: 229
Topic starter  

@getdunne

Thought I'd send a note. Today's first day off, so catching up on things. I also created a patch that was near maxing out the CPU in UNIFY on my PC, played it the whole day. Then when I tried later it wouldn't play it at all. So I reduced latency so it would. Honestly, until today I had never thought of Latency in that way before. Attached a picture of what Unify did when I opened one of the patches with Reason Plug-in in it. Using the latest Beta. Edit. It wasn't the latest Beta. it was 106 guess I am behind. But I tried it in 115 and still froze. Side note I'm going from the huge patch to the Reason patch.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@pbeprod

Am I correct that you're reporting two separate issues here: something about CPU and latency, and some kind of freeze in Reason?

I'm not sure exactly what you mean by "I reduced latency". Please explain.

I'll try the Reason plug-in in Unify on my PC here.


ReplyQuote
Kendall W Cochran III
(@pbeprod)
Member
Joined: 1 year ago
Posts: 229
Topic starter  

@getdunne

No, the latency thing was just a mention. The patch has like 8 layers some with 8 or nine layers in them. I had just never though of increasing latency so a patch could reduce CPU load so it would play. Went from 256 to 512. The main purpose was the Reason thing.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@pbeprod

Ah, thanks for clarifying. What you're actually adjusting there is "buffer size", which affects latency but isn't quite the same technically. (I know, it's a hair-splitting distinction.)

Is the Reason lock-up repeatable? Does it happen with every patch featuring Reason as a plug-in, or just some?


mj_prod liked
ReplyQuote
Kendall W Cochran III
(@pbeprod)
Member
Joined: 1 year ago
Posts: 229
Topic starter  

@getdunne

ive been trying for a while to find any duplicating issues. But they’ll open every time after closing then reopening.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@pbeprod

Frustrating! Thanks for your perseverance.


ReplyQuote
Kendall W Cochran III
(@pbeprod)
Member
Joined: 1 year ago
Posts: 229
Topic starter  

@getdunne

Hey I was messing with Unify tonight before going to bed and had my standard wait and hold when trying to open a patch with Reason in it. I found this and thought maybe this might narrow something down. I found it in the task manager and noticed it saying something about "Wait Chains" thought I send it to you. It was saying something about threads in Unify that Windows was having to wait on giving the "Not responding" on both Reason and Unify. Included a screen shot of the window. Hopefully this might provide some clues to the issue I'm having with this in Windows in the Standalone Unify.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@pbeprod

Interesting. I didn't know about the Windows wait-chain traversal capabilities before.

This suggests that Reason and Unify are getting stuck in a deadlock condition, where each is waiting for the other. I have a hunch this might be similar to issues we used to have with Spectrasonics' plug-ins. I'll try to contact Reason Studios for help with this.

As always, many thanks, Kendall!


ReplyQuote
Kendall W Cochran III
(@pbeprod)
Member
Joined: 1 year ago
Posts: 229
Topic starter  

@getdunne

The "reason" I was asking was based on this.

Posted by: @getdunne

@pbeprod

Interesting. I didn't know about the Windows wait-chain traversal capabilities before.

This suggests that Reason and Unify are getting stuck in a deadlock condition, where each is waiting for the other. I have a hunch this might be similar to issues we used to have with Spectrasonics' plug-ins. I'll try to contact Reason Studios for help with this.

As always, many thanks, Kendall!

If not that's fine too.


ReplyQuote
Share: