R13 (.1) Browser woes

[dakta]

Haha well I do suspect I am on the spectrum (in fact getting tested for it) so I am naturally worried about change

thing is this has upturned my own workflow with very little benefit, I normally assure myself with forced changes there is some greater good aspect, but this seems like a lot of stress for what exactly, in fact i'm in a worse place than before because I'm not actually enjoying it as much. It's definitely added some 'chore' aspect to the thought of 'hey I fancy dabbling in music for a bit' which means I now do it less because, well, headache and hassle.

I also don't want to diminish the views of people who find the new system better, but for me it's been a big back step and result in a net loss of what I enjoyed about reason overall.

[chimp_spanner]

Haha well I do suspect I am on the spectrum (in fact getting tested for it) so I am naturally worried about change

thing is this has upturned my own workflow with very little benefit, I normally assure myself with forced changes there is some greater good aspect, but this seems like a lot of stress for what exactly, in fact i'm in a worse place than before because I'm not actually enjoying it as much. It's definitely added some 'chore' aspect to the thought of 'hey I fancy dabbling in music for a bit' which means I now do it less because, well, headache and hassle.

I also don't want to diminish the views of people who find the new system better, but for me it's been a big back step and result in a net loss of what I enjoyed about reason overall.

I don't know many musicians who aren't I'm having my own little journey of self discovery at 40, pushing 41, suspecting that I probably have some kind of ADHD going on. Only became way more pronounced now that I'm living fully on my own for the first time in my life. So I get it! Still, change is a constant. And I don't think RS (or any company) can afford to stand still. I'd love to be able to help somehow if you're having that rough of a time. I think I get from your post where the friction is, and I've seen similar comments elsewhere so I'll try and incorporate that into a video. Hopefully this week!

[PhillipOrdonez]

Maybe you missed it but the solution to your issue is to click on the browse button on the desired device you want to explore, click the orange button on the left which contains all the patches for that device, and search away just like you did before, except now patches load when clicking them so all you need is to click on one, then using the arrows on your keyboard you can browse and preview each like a boss. You can fold the tags and all that so it’s out of the way and you can focus on your patch names just like it was before.

Any other gripe that needs squashing?

[dakta]

I haven't missed it, I'm airing that i don't like it. I can do this. (And will do this). You haven't fixed the gripe about it being a window blocking my view of devices as I browse, so if you could get started there as opposed to being sarcastic that'd be some positive movement.

[dakta]

Haha well I do suspect I am on the spectrum (in fact getting tested for it) so I am naturally worried about change

thing is this has upturned my own workflow with very little benefit, I normally assure myself with forced changes there is some greater good aspect, but this seems like a lot of stress for what exactly, in fact i'm in a worse place than before because I'm not actually enjoying it as much. It's definitely added some 'chore' aspect to the thought of 'hey I fancy dabbling in music for a bit' which means I now do it less because, well, headache and hassle.

I also don't want to diminish the views of people who find the new system better, but for me it's been a big back step and result in a net loss of what I enjoyed about reason overall.

I don't know many musicians who aren't I'm having my own little journey of self discovery at 40, pushing 41, suspecting that I probably have some kind of ADHD going on. Only became way more pronounced now that I'm living fully on my own for the first time in my life. So I get it! Still, change is a constant. And I don't think RS (or any company) can afford to stand still. I'd love to be able to help somehow if you're having that rough of a time. I think I get from your post where the friction is, and I've seen similar comments elsewhere so I'll try and incorporate that into a video. Hopefully this week!

Thank you for a sensible reply

[selig]

I haven't missed it, I'm airing that i don't like it. I can do this. (And will do this). You haven't fixed the gripe about it being a window blocking my view of devices as I browse, so if you could get started there as opposed to being sarcastic that'd be some positive movement.

I don’t know if anyone here is able to fix things the way you want them to be fixed, but in the spirit of starting the new year on a positive note I’ll be happy to give it a shot for you.

I don’t need to see devices in the rack when browsing for patches, but if I did I would resize the browser window so it only took up a fraction of the screen. Or maybe better yet, detach the Rack View so the browser isn’t anywhere near it and can’t block ANY of it. We all have different ways of working, but I can’t personally imagine any workflow where I’d want the browser open for extended periods of time. I tend to focus on one task at a time, fwiw, and as such have yet to find this browsers location or positional limitations to even come onto my radar, let alone cause any change in my workflow. Still, I know not everyone works the same way I do so I’m not judging, just trying to help.

That said, if you’re really wanting/expecting someone to fix it for you I would not count on any of the members of the forum (that are not also RS employees) to do so. Make your voice heard where it counts.

[dakta]

TBH you have nerly touched on one of my interim solutions but I can't implement it yet due to physical space and that's to literally get a second screen so I can have a bit of a tidy workspace with a dedicated and familiar workflow/environment (environment might be the more accurate word). It wont solve the floatingness of the window but will mean there's a space out of the way for it

I have fed back to RS, and tbh my response wasn't so much an expectation for anyone here to fix my gripes, more a response to the challenge of if I've any more - which I do

[PhillipOrdonez]

I haven't missed it, I'm airing that i don't like it. I can do this. (And will do this). You haven't fixed the gripe about it being a window blocking my view of devices as I browse, so if you could get started there as opposed to being sarcastic that'd be some positive movement.

How is your screen resolution and how do you have your workspace set up so that the browser will block the rack? That just doesn’t happen to me in standalone. It does happen in the rrp but that’s not an issue either because you keep the browser closed at all times when not browsing anything. Why would I want to lose screen real estate on a thing I’m not using? The browser is meant to be closed.

No intentional sarcasm from me, bro

[PhillipOrdonez]

TBH you have nerly touched on one of my interim solutions but I can't implement it yet due to physical space and that's to literally get a second screen so I can have a bit of a tidy workspace with a dedicated and familiar workflow/environment (environment might be the more accurate word). It wont solve the floatingness of the window but will mean there's a space out of the way for it

I have fed back to RS, and tbh my response wasn't so much an expectation for anyone here to fix my gripes, more a response to the challenge of if I've any more - which I do

Beware that a secondary screen won’t work for you because the browser is locked to the screen you’re in. Say you have the rack on one screen, if you call up the browser, it’ll stay on that rack window and won’t be able to be moved to another screen

[joeyluck]

I am a user that likes to leave the Browser open when I'm browsing patches and it's in the way 🫤 I'm a laptop user.

I like to use the arrow keys to scroll through patches. I also like to see the device for which I'm browsing patches so I can play with parameters while I browse patches... For instance, I might think I like a patch, but I need to disable the built-in reverb, and now I need to close the Browser just to do that. I think I like another patch, but I don't like how the filter is responding, so let me see how it sounds if I dial back the filter env mod, gotta close the Browser to do that...

I have the Browser at its smallest size and it still blocks everything. I've made requests for being able to make the Browser smaller, as well as a simple compact mode that would make the Browser the size of the Device Palette.

I can see different approaches to browsing/searching. If I want to search for something, not knowing exactly what I'm looking for using tags and whatnot, then using the Browser larger makes sense to me. If I have navigated to a folder and want to simply scroll through patches, I no longer need a large Browser.

I don't use the RRP often, but it feels unusable to me without a dockable browser, so I can't imagine how those users are working with it currently.

[dakta]

TBH you have nerly touched on one of my interim solutions but I can't implement it yet due to physical space and that's to literally get a second screen so I can have a bit of a tidy workspace with a dedicated and familiar workflow/environment (environment might be the more accurate word). It wont solve the floatingness of the window but will mean there's a space out of the way for it

I have fed back to RS, and tbh my response wasn't so much an expectation for anyone here to fix my gripes, more a response to the challenge of if I've any more - which I do

Beware that a secondary screen won’t work for you because the browser is locked to the screen you’re in. Say you have the rack on one screen, if you call up the browser, it’ll stay on that rack window and won’t be able to be moved to another screen

Hmmm I didn't think of that, thats a bummer!

[selig]

TBH you have nerly touched on one of my interim solutions but I can't implement it yet due to physical space and that's to literally get a second screen so I can have a bit of a tidy workspace with a dedicated and familiar workflow/environment (environment might be the more accurate word). It wont solve the floatingness of the window but will mean there's a space out of the way for it

I have fed back to RS, and tbh my response wasn't so much an expectation for anyone here to fix my gripes, more a response to the challenge of if I've any more - which I do

Beware that a secondary screen won’t work for you because the browser is locked to the screen you’re in. Say you have the rack on one screen, if you call up the browser, it’ll stay on that rack window and won’t be able to be moved to another screen

I’m not having an issue here. I use the Sequencer to select the instrument, hit browse, and the browser is locked to the main screen while the Rack View fills the second screen unobstructed. Double click on the Sequencer track and the Rack View auto scrolls to that instrument without taking focus away from the Sequencer window.

If for some reason you DO open the Browser in Rack View, just click again in Seq View to close it (or vice versa)! Also, it will remember the size and position in each view, so you could have it BIG in one view and little in another.

Bottom line, select instruments and click on the BROWSER button located in the Sequencer View, problem solved.

[PhillipOrdonez]

Beware that a secondary screen won’t work for you because the browser is locked to the screen you’re in. Say you have the rack on one screen, if you call up the browser, it’ll stay on that rack window and won’t be able to be moved to another screen

I’m not having an issue here. I use the Sequencer to select the instrument, hit browse, and the browser is locked to the main screen while the Rack View fills the second screen unobstructed. Double click on the Sequencer track and the Rack View auto scrolls to that instrument without taking focus away from the Sequencer window.

If for some reason you DO open the Browser in Rack View, just click again in Seq View to close it (or vice versa)! Also, it will remember the size and position in each view, so you could have it BIG in one view and little in another.

Bottom line, select instruments and click on the BROWSER button located in the Sequencer View, problem solved.

That’s a good point. Selig! That would work for Dakta!

[dakta]

Once i move rooms and can fit a second screen I'll certainly give it a whirl, it'll probably take some getting used to anyway but I do think it'd make more sense to have the rack on one side and the sequencer/other things on the other. Not sure how other people play but when I'm scrolling through sounds I like to tweak things like filters and see if it fits, so constantly moving the browser to one side (or having in on top in the first place) is more than a bit annoying. I do sometimes just use the up-down button on the device but if you want to change folder with the inbuilt you could do it quite easily without popping up.

It's not a deal breaker for using reason but it's just far more clunky IMO

[joeyluck]

Not sure how other people play but when I'm scrolling through sounds I like to tweak things like filters and see if it fits, so constantly moving the browser to one side (or having in on top in the first place) is more than a bit annoying.

This is exactly what I mentioned above

[selig]

Not sure how other people play but when I'm scrolling through sounds I like to tweak things like filters and see if it fits, so constantly moving the browser to one side (or having in on top in the first place) is more than a bit annoying.

This is exactly what I mentioned above

This is where I’d map a physical controller to the filter while scrolling patches. That way you don’t have keep grabbing the mouse, you can stay at your keyboard and play (assuming your controller has additional assignable hardware controls). You could almost close your eyes and just play, with the right setup!

[joeyluck]

This is exactly what I mentioned above

This is where I’d map a physical controller to the filter while scrolling patches. That way you don’t have keep grabbing the mouse, you can stay at your keyboard and play (assuming your controller has additional assignable hardware controls). You could almost close your eyes and just play, with the right setup!

Yeah I have that capability and I do that from time to time, but I also like to see the list to see what is previous and next.

[Mataya]

Great, you can start with me.

So, I've downloaded autosub synth RE, fired up Reason 13, loaded autosub, pressed patch browsing icon on the synth and instead of seeing patches for this synth I have to wait 10min for browser to finish scanning the "All locations" folder. And this happens every time I load Reason. I've reinstalled Reason, deleted cache and stuff mentioned here and still the same problem.
So for those non browser hoes here, do you have the same problem and just not finding it to be a problem (which I just would not believe) or is there a way to have browser work like in earlier versions? Also, Redrum browse a sample from a first slot, find it in one of my folders with drum shots, close browser, browse from a slot 2 on a redrum, the browser goes to "All locations" ...need to got trough all the folders again.
Thanks for suggestions. Sorry for being a hoe.

M

[dakta]

well make sure you're sure about name calling Patrick because some of us have constantly given you an income stream, I don't think even the love of sounds would overcome being branded by the developer for having a valid criticism and using (gasp) a forum with a specific titled thread to discuss it.

And on that note - the critique I think is valid, I didn't like the negativity towards R13 when it was announced because BETA aside nobody could actually see what was coming and I thought the negative anticipation was a bit annoying - so I get it - but this side of release we do actually know what we don't like or what is proving hard to live with.

It's not like we are chronic reason haters, outside the browser style change I remain as much a reason enthusiast as anyone. But, this has (for me - this is the caveat ) not been a positive step or experience. And there may be workarounds, but even then before it was fine without workarounds or an altered flow. For me.

[chimp_spanner]

Great, you can start with me.

So, I've downloaded autosub synth RE, fired up Reason 13, loaded autosub, pressed patch browsing icon on the synth and instead of seeing patches for this synth I have to wait 10min for browser to finish scanning the "All locations" folder. And this happens every time I load Reason. I've reinstalled Reason, deleted cache and stuff mentioned here and still the same problem.
So for those non browser hoes here, do you have the same problem and just not finding it to be a problem (which I just would not believe) or is there a way to have browser work like in earlier versions? Also, Redrum browse a sample from a first slot, find it in one of my folders with drum shots, close browser, browse from a slot 2 on a redrum, the browser goes to "All locations" ...need to got trough all the folders again.
Thanks for suggestions. Sorry for being a hoe.

M

Yeah you definitely shouldn't have to wait that long - I would file a bug report! I know this was a widespread issue early on for some users but it's not been for me for a few versions now and they probably assumed it to be fixed in 13.1. You're not the only person I've seen with it though so do report!

On your second point, every sample slot in ReDrum is basically its own instrument, and can recall a different search state (filters, tags, location). The way to do what you want is to just open the browser with CMD+F / F9 (or hit browse on any slot to call up the browser), go to where the samples are that you want, then you can just click and drag them into each slot without closing the browser or losing your place. Even though you're only working from one browser 'session' any filters or tags you apply will be remembered per-slot. As will locations. So for example if in the first slot you drag in from Drum Supply, and in the second your Splice folder, the next time you open either folder you'll be taken straight to those locations.

Like I said earlier I think this is a messaging thing. I had fully intended to cover all of this in a video last night but...I started watching Silo instead. Next thing you know, bam. 10 episodes down. And I wonder why I feel like death this morning...

[PhillipOrdonez]

Great, you can start with me.

So, I've downloaded autosub synth RE, fired up Reason 13, loaded autosub, pressed patch browsing icon on the synth and instead of seeing patches for this synth I have to wait 10min for browser to finish scanning the "All locations" folder. And this happens every time I load Reason. I've reinstalled Reason, deleted cache and stuff mentioned here and still the same problem.
So for those non browser hoes here, do you have the same problem and just not finding it to be a problem (which I just would not believe) or is there a way to have browser work like in earlier versions? Also, Redrum browse a sample from a first slot, find it in one of my folders with drum shots, close browser, browse from a slot 2 on a redrum, the browser goes to "All locations" ...need to got trough all the folders again.
Thanks for suggestions. Sorry for being a hoe.

M

Yeah you definitely shouldn't have to wait that long - I would file a bug report! I know this was a widespread issue early on for some users but it's not been for me for a few versions now and they probably assumed it to be fixed in 13.1. You're not the only person I've seen with it though so do report!

On your second point, every sample slot in ReDrum is basically its own instrument, and can recall a different search state (filters, tags, location). The way to do what you want is to just open the browser with CMD+F / F9 (or hit browse on any slot to call up the browser), go to where the samples are that you want, then you can just click and drag them into each slot without closing the browser or losing your place. Even though you're only working from one browser 'session' any filters or tags you apply will be remembered per-slot. As will locations. So for example if in the first slot you drag in from Drum Supply, and in the second your Splice folder, the next time you open either folder you'll be taken straight to those locations.

Like I said earlier I think this is a messaging thing. I had fully intended to cover all of this in a video last night but...I started watching Silo instead. Next thing you know, bam. 10 episodes down. And I wonder why I feel like death this morning...

Time to hit the record button already! Chop chop

[Mataya]

Thanks Chimp ...

a bit clearer now, but I actually had some other issues with the browser, I just forgot at which point they appeared, because I've switched to FL studio for a while. Can't really handle reason searching it self over and over. They fixed some stuff in 13.1, I'm pretty sure they'll fix some more stuff people point out.

Watched a few of your videos and they are very good. Wish you more time for working on some more. Had the same problem with "From". 3 seasons of pure frustrations.

tx again
M

[chimp_spanner]

Thanks Chimp ...

a bit clearer now, but I actually had some other issues with the browser, I just forgot at which point they appeared, because I've switched to FL studio for a while. Can't really handle reason searching it self over and over. They fixed some stuff in 13.1, I'm pretty sure they'll fix some more stuff people point out.

Watched a few of your videos and they are very good. Wish you more time for working on some more. Had the same problem with "From". 3 seasons of pure frustrations.

tx again
M

No worries! And thanks for checking them out - I will endeavour to do more! I think I'll always have a lot of love for Reason. Even when it frustrates the hell out of me, it's still great at certain things that I just find so much harder in other DAWs. I just think it has a lot of unrealised potential and while I'm sure there'll always be things to chip away at, hopefully we can put the browser behind us soon and move on to other things.

[joeyluck]

Great, you can start with me.

So, I've downloaded autosub synth RE, fired up Reason 13, loaded autosub, pressed patch browsing icon on the synth and instead of seeing patches for this synth I have to wait 10min for browser to finish scanning the "All locations" folder. And this happens every time I load Reason. I've reinstalled Reason, deleted cache and stuff mentioned here and still the same problem.

You should report this. I have this issue after I install anything new and I have a report that's being investigated. I can't browse patches for newly installed REs for several minutes. After indexing has completed though, I don't have this issue again unless it's for something newly installed.

[selig]

This is where I’d map a physical controller to the filter while scrolling patches. That way you don’t have keep grabbing the mouse, you can stay at your keyboard and play (assuming your controller has additional assignable hardware controls). You could almost close your eyes and just play, with the right setup!

Yeah I have that capability and I do that from time to time, but I also like to see the list to see what is previous and next.

What do you mean “the list”? My suggestion is specifically so you can keep the browser (list?) visible and still grab the filter (or any parameter) while browsing, which I thought was the goal?

The alternative is what we’re trying to avoid (I think), which is closing the Browser so you can find the filter graphic on screen with the mouse so you can then adjust it as you play (which requires you to keep the filter knob in view). At which point you can no longer see “the list”, correct?

Thinking I might be confused about this, I tested it with my Novation SL MkIII and it works flawlessly, and there are already knobs assigned to the filter (and many more) so I don’t even need to create anything - just use the up/down arrows to browse while seeing the full list, and tweak away as you play - which all seem to be such a better way to implement this workflow than any alternatives IMO regardless of screen size (even if the browser wasn’t an issue this approach would still make more sense to me).

Or have I misunderstood something important here?