I am following the directions exactly, and the userIRs.rir file is where it is supposed to be, but REmatrix expects the file to be audio. It will only open wav, wave, aif or aiff. It does not see the .rir file because it doesn't expect that format.
 
 

That's actually the file the IRs are "stored" in after you import the .wav files.

There is no wav file to import.

Direct the import dialogue to C:\Cakewalk Content\NYC Showroom Impulse Responses.

That directory doesn't exist. Ah, wait a sec. I have that Cakewalk directory on an external drive. Now I see the imports.
 
Crazy that the directions given send me to C:\Users\Public\Documents\Overloud\REmatrix Solo

pencilartist
That directory doesn't exist. Ah, wait a sec. I have that Cakewalk directory on an external drive. Now I see the imports.
 
Crazy that the directions given send me to C:\Users\Public\Documents\Overloud\REmatrix Solo

That's the default location, it's not possible to anticipate all the custom places people put files. But you can use the info to search for where it is.

Just reading through the Braintree pdf file (page 4), there isn't a mention of the NYC Showroom directory in regard to importing, just the one I have noted here. Reading carefully, however, I see it's not telling you to import from there, but it's still the only one mentioned.

I just went through the same thing. It was only by luck that I remembered the "C:\Cakewalk Content" folder. It might have been mentioned in the command center when I downloaded everything (at about 300 baud over fiber), but it's not anywhere in any of the docs I found. There should be less mystery installing this kind of thing. Think of the non-technical musicians and Cake newbies...

It's all in the PDF about the Braintree update.

Ah. Thanks. That must be where I had seen it. Unfortunately, it's not in the PDF that pops up automatically after the command center completes the upgrade. That PDF just talks about how to work around the lack of preset management, after the new samples have been imported. It overshadowed my glimpse of the other PDF.
 
I still feel that any upgrade should be completed without much, if any, user intervention. I realize that takes more SW development, but one relatively small SW project can save thousands of individual user frustrations. Some of us are entangled in a wide variety of sophisticated tools, and it gets very hard to remember all the app-specific details.