R4.01, portable install does not put itself in <dir>\REAPER...!

I just did the portable install of v.4.01. I did it the same as always, clicked "Portable install", clicked "Browse" and selected the dir for my portable Reaper installation. to my surprise v.4.01 did not install in the REAPER dir under my selected dir, but directly in the selected dir. Now that I check setup dialog, I see that the REAPER folder is indeed not added to the install path, as it has always been since R4alpha1. This gotta be fixed! EDIT: OK, looking at the changelog, it's gotta be this (I'm on W7x64) Code:

As far as I can gather, my portable install installed as it always has. :confused:

Myself I (and some others IIRC) several times was tricked by Reaper's installer adding the REAPER directory when I directed it to a directory I wanted to install into. If I direct the installer to a directory I called "Reaper pre" I always had to remember to delete the REAPER subfolder it proposed. That's now gone? I like.

I prefer the opposite: the installer should not add a reaper subfolder by default, I fell at least a couple of times when upgrading a portable to discover that I pointed to my reaper folder and the install went in a "reaper" subfolder instead of the exact folder I chose. I have multiple portable installs, like "Reaper_win7", "Reaper_x64" and so, so I don't want a "reaper" subfolder to be automatically appended each time. - Mario

The improvement is that people were often not expecting that it adds that \REAPER bit and were prone to end up with \Program Files\REAPER4\REAPER\YIKES\REAPER when they pointed to the REAPER4 folder instead of its root folder, which is indeed a bit ambiguous and the interpretation that you should point it to the actual folder you want to install it in or did install it in sounds more reasonable to me. Also, if you renamed the folder like above, you had to make sure you change the proposed folder name after selecting the root folder, which is not needed anymore. The bad thing is that the "unexpected" part was now handed over to you right away, not sure if anyone at Cockos expected that. Sorry for the mess. On the bright side, it creates a mess in the root folder, which is relatively easy to identify/add to selection/delete.

Yeah, I'll survive with it... but it sure surprised the pants off of me when Reaper started up claiming that I had not selected an audio interface, and then wanted me to enter my registration key :)

Thank you for the clarification Ollie. I was wondering if it was the desired behavior but it makes sense now.

I got caught with this too but I went ahead, took the chance and directed to the "REAPER" subfolder and everything worked fine.:) I agree, I think this is the way it should work.