ReasonTalk.com

Ottostrom wrote: ↑

04 Nov 2017

Thank you so much Olivier! Will definitely do the same on my machine

Ostermilk wrote: ↑

04 Nov 2017

Yes it's a shame that users can't choose the locations of Soundbanks, RE's and additional content from the app itself, like you can set the 'Scratch Disk Folder' from Preferences/Advanced.

I've been making requests for this since 6.5 came out. I've also been making links and aliases through the OS since then with no ill effects and once they are setup you can forget about them fortunately. Mind you when I updated to Windows 10 Fall Creators Update the update process killed a couple of 'Junctions' I had setup so I had to re-instate them after that upgrade as well as add the new locations used by the additional content provided by R10.

The Hardlink Shell Extension app on Windows makes the process a cinch if you don't like entering the MkLink commands in a command prompt.

I like to keep my OS partition small as I image it regularly and it's a useful aid to that end and also if you just have a small but fast SSD that you want to keep uncluttered to keep these things off the OS drive.

So it's a bit of a shame we can't have user defined locations but once you get it sorted it's not a show stopper, but bear in mind you probably wouldn't get support if you ran into issues, so be confident with your OS before you start to change locations this way.

kitekrazy wrote: ↑

04 Nov 2017

Ostermilk wrote: ↑

04 Nov 2017

Yes it's a shame that users can't choose the locations of Soundbanks, RE's and additional content from the app itself, like you can set the 'Scratch Disk Folder' from Preferences/Advanced.

I've been making requests for this since 6.5 came out. I've also been making links and aliases through the OS since then with no ill effects and once they are setup you can forget about them fortunately. Mind you when I updated to Windows 10 Fall Creators Update the update process killed a couple of 'Junctions' I had setup so I had to re-instate them after that upgrade as well as add the new locations used by the additional content provided by R10.

The Hardlink Shell Extension app on Windows makes the process a cinch if you don't like entering the MkLink commands in a command prompt.

I like to keep my OS partition small as I image it regularly and it's a useful aid to that end and also if you just have a small but fast SSD that you want to keep uncluttered to keep these things off the OS drive.

So it's a bit of a shame we can't have user defined locations but once you get it sorted it's not a show stopper, but bear in mind you probably wouldn't get support if you ran into issues, so be confident with your OS before you start to change locations this way.

Reason is still in the dark ages on many things. So does R10 take up 10GB without Mklink?

Psuper wrote: ↑

04 Nov 2017

Holy crap are you SERIOUS? That's like "bad dev" 101 if you can't have your files where you want them from the default installation. Work-arounds shouldn't be needed.

Mine have been on my 3rd drive for years, maybe I initially set it up that way I don't recall. Regardless, that's just terribly shoddy dev work this day and age. I'm honestly shocked to read this.

Ostermilk wrote: ↑

04 Nov 2017

Psuper wrote: ↑

04 Nov 2017

Holy crap are you SERIOUS? That's like "bad dev" 101 if you can't have your files where you want them from the default installation. Work-arounds shouldn't be needed.

Mine have been on my 3rd drive for years, maybe I initially set it up that way I don't recall. Regardless, that's just terribly shoddy dev work this day and age. I'm honestly shocked to read this.

Was it you bigging up that crappy, unfinished grain based synth for $20 as a better alternative to Grain? In which case the definition of what you'd consider to be shoddy dev work is probably a bit different to mine.

Props ethos has always been to err on the side of simplicity so that folk can just fire up the program and start making music, so I'd suggest that it is more 'by design' than shoddy development. They are certainly aware of it because I've been banging on about it since RE's were introduced in 6.5 and I don't mean here, I mean directly via support as a feature suggestion.

Just because YOU have certain expectations it doesn't guarantee that everybody or even a majority share your views.

Having said all that I don't think allowing users to define content locations is over-complicating things for anyone that can actually double-click a program icon to launch it these days. I think if enough people politely and concisely raised this and other issues Reason has for them we'd be more likely to see better changes going forward, than we will by the almost automatic response that some have on this forum which is to state that the Propellerheads are 'dumb asses' at any given opportunity.

Honestly shocked? Really? Funny because as a I read your post it was no shock at all, in fact it seemed inevitable who the poster was.

Clear as Fog...

Psuper wrote: ↑

04 Nov 2017

Ostermilk wrote: ↑

04 Nov 2017

Was it you bigging up that crappy, unfinished grain based synth for $20 as a better alternative to Grain? In which case the definition of what you'd consider to be shoddy dev work is probably a bit different to mine.

Props ethos has always been to err on the side of simplicity so that folk can just fire up the program and start making music, so I'd suggest that it is more 'by design' than shoddy development. They are certainly aware of it because I've been banging on about it since RE's were introduced in 6.5 and I don't mean here, I mean directly via support as a feature suggestion.

Just because YOU have certain expectations it doesn't guarantee that everybody or even a majority share your views.

Having said all that I don't think allowing users to define content locations is over-complicating things for anyone that can actually double-click a program icon to launch it these days. I think if enough people politely and concisely raised this and other issues Reason has for them we'd be more likely to see better changes going forward, than we will by the almost automatic response that some have on this forum which is to state that the Propellerheads are 'dumb asses' at any given opportunity.

Honestly shocked? Really? Funny because as a I read your post it was no shock at all, in fact it seemed inevitable who the poster was.

Clear as Fog...

You don't have to agree with me, but you smell of fanboyism if you seriously don't understand that a simple install routine that almost all software has these days is ALL ABOUT simplicity - one place for your files is as simple as it gets.

And in the spectrum of DAWS where there are gigs of space being taking and used all the time... even more shoddy not to include it.

I give props where it's deserved, offer advice where I can, and am critical when necessary. All you just did was offer a lame apology of sorts for Propellerhead and attempt to smear me. As for you disliking me, I couldn't care less - it's obvious you have some 'thing' for my style.

Psuper wrote: ↑

05 Nov 2017

Oh I didn't miss the 'attaboy' while you were slandering me. If I make a statement, I've either done my research or been around the block long enough to be confident about my choice of words.

Regardless, when it comes to Propellerhead, little of our advice is productive, no matter the perceived flavor. Propellerhead does what they want in their own time and rarely if ever take a general consensus community feedback.

Olivier wrote: ↑

04 Nov 2017

Yes, this is in part because of how Microsoft wants files to be organized. R7 installed everything with the program. Nowadays though, programs have to be installed in a way that they are multi-user--account aware. When two people use the machine (i.e. both have their own user account), and one has a license for Reason v9, the other v10, then v9 licensee cannot access the v10 content because it is in the v10 licensee's directory structure.

But it can be solved. Personally I prefer to have not only the refills on another disk, but also the added content (klang, humana, etc) and the rack extensions.

How to move Refills, Rack Extensions and added content for Reason 10, on Windows" [Only checked by me on Windows 10]

Note that what i'm describing here is probably not supported by propellerhead. Do at your own risk.

I chose to move the directories holding the files to a new location and put symbolic links that point to the new locations (which are not stanadrd windows shortcuts) back in their place. This way it guaranteed that any new content that is written into that directory, is automatically placed on the new location

On windows 10 the locations are:

"%USERPROFILE%\music\Propellerhead Content" for the new R10 content. It contains both the optional devices and the optional refills..
"%USERPROFILE%\Appdata\Roaming\Propellerhead Software\Rackextensions" for your rack extensions.
"C:\ProgramData\Propellerhead Software\Soundbanks" for all the sound banks.

I have moved all these directories to a faster location. In my case "F:\Propellerhead Files"

I then made links using the mklink utility. This is a command line tool that is available with windows 10. To use it start the windows command prompt with administrator preferences.
In my case the commands to link everything back in place are:

mklink /D "c:\Users\Olivier\Music\Propellerhead Content" "f:\Propellerhead Files\Propellerhead Content"
mklink /D "c:\ProgramData\Propellerhead Software\Soundbanks" "f:\Propellerhead Files\Soundbanks"
mklink /D "c:\users\Olivier\AppData\Roaming\Propellerhead Software\RackExtensions" "f:\Propellerhead Files\RackExtensions"

The /D tells mklink to make so called "directory symbolic links".

I hope this helps.

If you prefer to not work with the command prompt, there are several windows shell extension you can install to work with symbolic links. For example this: http://schinagl.priv.at/nt/hardlinkshel ... nsion.html

Maybe someone wants to chime in how this is done on a mac ?

Grumbleweed wrote: ↑

22 Nov 2017

Olivier wrote: ↑

04 Nov 2017

Yes, this is in part because of how Microsoft wants files to be organized. R7 installed everything with the program. Nowadays though, programs have to be installed in a way that they are multi-user--account aware. When two people use the machine (i.e. both have their own user account), and one has a license for Reason v9, the other v10, then v9 licensee cannot access the v10 content because it is in the v10 licensee's directory structure.

But it can be solved. Personally I prefer to have not only the refills on another disk, but also the added content (klang, humana, etc) and the rack extensions.

How to move Refills, Rack Extensions and added content for Reason 10, on Windows" [Only checked by me on Windows 10]

Note that what i'm describing here is probably not supported by propellerhead. Do at your own risk.

I chose to move the directories holding the files to a new location and put symbolic links that point to the new locations (which are not stanadrd windows shortcuts) back in their place. This way it guaranteed that any new content that is written into that directory, is automatically placed on the new location

On windows 10 the locations are:

"%USERPROFILE%\music\Propellerhead Content" for the new R10 content. It contains both the optional devices and the optional refills..
"%USERPROFILE%\Appdata\Roaming\Propellerhead Software\Rackextensions" for your rack extensions.
"C:\ProgramData\Propellerhead Software\Soundbanks" for all the sound banks.

I have moved all these directories to a faster location. In my case "F:\Propellerhead Files"

I then made links using the mklink utility. This is a command line tool that is available with windows 10. To use it start the windows command prompt with administrator preferences.
In my case the commands to link everything back in place are:

mklink /D "c:\Users\Olivier\Music\Propellerhead Content" "f:\Propellerhead Files\Propellerhead Content"
mklink /D "c:\ProgramData\Propellerhead Software\Soundbanks" "f:\Propellerhead Files\Soundbanks"
mklink /D "c:\users\Olivier\AppData\Roaming\Propellerhead Software\RackExtensions" "f:\Propellerhead Files\RackExtensions"

The /D tells mklink to make so called "directory symbolic links".

I hope this helps.

If you prefer to not work with the command prompt, there are several windows shell extension you can install to work with symbolic links. For example this: http://schinagl.priv.at/nt/hardlinkshel ... nsion.html

Maybe someone wants to chime in how this is done on a mac ?

Sorry to dig this thread up but I've tried doing this and can create the link (after deleting the original content from the C drive) but when I open Reason it immediately stops with a pop up saying there is a Write Error and it goes no further. If I reverse everything Reason works fine but I'm left with a chuck of SSD memory eaten up by the extra content.

Any thoughts on why Reason wouldn't like this?

Grum.