Reason 8.2 Update is Available!

[buddard]

I think it would make the most sense to only zoom horizontally on the pinch gesture, since (I believe) it would be the most common operation by far... Zooming both axes simultaneously would probably be the most annoying behaviour possible.

(That's another gripe I have with the Cmd + scroll option, by the way: The slightest vertical movement will immediately affect the vertical zoom as well. It would probably benefit from some kind of heuristics to prevent "collateral zooming", like restricting the zoom direction to the "dominant" direction of the scroll gesture.)

[Eagleizer]

I saw the mention of "Revert" for the browser and thought "hurray, hurray, hurray!". But now I think I have read somewhere that it "reloads" the patch used before browsing, rather than actually just going back to its previous state. Can anyone confirm/deny please?

The reason it matters to me is that I quite often tweak patches quite a bit after loading them and so "reloading" the patch wouldn't take me back to where I was before browsing :/

It can work exactly as you describe if you understand HOW it works and you approach it like the "old" version.

If you browse and tweak WHILE browsing (not possible to do in previous versions), it will not work as expected, which is logical IMO because the idea of Revert is to take you back to the "pre-browsing" state.

But if you browse, then leave browse mode to tweak a patch, then when you begin browsing again, revert will return you to your tweaked patch (not the stored "preset" you started with).

This is exactly what you want, you just have to "tell" it when you want to keep the patch by ending your browse session. This worked automatically in the old version, fwiw because you had was no other option!

Reverting, BTW, takes you OUT of browse mode, so you'll have to "browse" again to re-activate the feature. Again this is how it used to work, except the browser is not now "modal" which causes the confusion IMO. But it was pretty easy to learn the new workflow for me.

Remember that Revert takes you back to the state of the instrument when you ENTERED browse mode, not the preset stored on disk - sometimes these are the same thing, like if you created a device loaded with a factory patch, then loaded a second patch, then hit revert you would be returned to the factory patch. But not because it's the one on disk but because it was the one LOADED into the device when you began browsing. 

I probably could have stated this more clearly - hope this helps!

Never thought I`ll say this, but you are wrong Giles. Tincture
probably read my post which is the correct description of how Revert
works: 

http://www.reasontalk.com/post/show_sin ... stcount=12

Feel free to try for yourself: 

- Create an instrument
- Move mix fader to get out of browse focus
- Make 5 tweaks to the patch (Let`s call them Tweak 1-5)
- Click the instrument`s browse button
- Load 5 patches (one by one)
- Click Revert

The patch, with your latest tweak setting (Tweak 5), is loaded. 

When you now hit Ctrl+Z, you are not going back to Tweak 4,
but you start to go back through the patches you previewed. 

So, if you want to go back to Tweak 4, you can save 1 operation
(Revert) by using Ctrl+Z right away, instead of Revert first.


Example. When you do the following: 

1 Thor Init patch (no browser focus)
2 Adjust Master Volume 
3 Change Mode
4 Load: Epic Poly 
5 Load: Gangsta Lead 3
6 Revert 

- your history (for Undo) now looks like this, with a copy of Thor`s 
latest state before browsing; first:

(Numbers representing Undo 1, 2, 3 times and so on.)

0 Change Mode (copy of your original state, before browsing, without the undo`s)
1 Load: Gangsta Lead 3
2 Load: Epic Poly
3 Change Mode (Original)
4 Adjust Master Volume
5 Thor Init patch

-----

Same example for R7:

1 Thor Init patch 
2 Adjust Master Volume 
3 Change Mode 
4 Load: Epic Poly 
5 Load: Gangsta Lead 3
6 Cancel 

- your history (for Undo) now looks like this, with Thor`s 
latest state before browsing; first:

(Numbers representing Undo 1, 2, 3 times and so on.)

0 Change Mode (Original)
1 Adjust Master Volume
2 Thor Init patch

-----

I`d prefer that Revert actually "went trough" the Undo`s until it
found the last state before browsing, but that`s not how it works.

Hope this was clear enough  


Cheers

[selig]

I saw the mention of "Revert" for the browser and thought "hurray, hurray, hurray!". But now I think I have read somewhere that it "reloads" the patch used before browsing, rather than actually just going back to its previous state. Can anyone confirm/deny please?

The reason it matters to me is that I quite often tweak patches quite a bit after loading them and so "reloading" the patch wouldn't take me back to where I was before browsing :/

It can work exactly as you describe if you understand HOW it works and you approach it like the "old" version.

If you browse and tweak WHILE browsing (not possible to do in previous versions), it will not work as expected, which is logical IMO because the idea of Revert is to take you back to the "pre-browsing" state.

But if you browse, then leave browse mode to tweak a patch, then when you begin browsing again, revert will return you to your tweaked patch (not the stored "preset" you started with).

This is exactly what you want, you just have to "tell" it when you want to keep the patch by ending your browse session. This worked automatically in the old version, fwiw because you had was no other option!

Reverting, BTW, takes you OUT of browse mode, so you'll have to "browse" again to re-activate the feature. Again this is how it used to work, except the browser is not now "modal" which causes the confusion IMO. But it was pretty easy to learn the new workflow for me.

Remember that Revert takes you back to the state of the instrument when you ENTERED browse mode, not the preset stored on disk - sometimes these are the same thing, like if you created a device loaded with a factory patch, then loaded a second patch, then hit revert you would be returned to the factory patch. But not because it's the one on disk but because it was the one LOADED into the device when you began browsing. 

I probably could have stated this more clearly - hope this helps!

Never thought I`ll say this, but you are wrong Giles. Tincture
probably read my post which is the

correct

description of how Revert
works: 

http://www.reasontalk.com/post/show_sin ... stcount=12

Feel free to try for yourself: 

- Create an instrument
- Move mix fader to get out of browse focus
- Make 5 tweaks to the patch (Let`s call them Tweak 1-5)
- Click the instrument`s browse button
- Load 5 patches (one by one)
- Click Revert

The patch, with your latest tweak setting (Tweak 5), is

loaded

. 

When you now hit Ctrl+Z, you are

not

going back to Tweak 4,
but you start to go back through the patches you previewed. 

So, if you want to go back to Tweak 4, you can save 1 operation
(Revert) by using Ctrl+Z right away, instead of Revert first.


Example. When you do the following: 

1 Thor Init patch

(

no browser focus

)

2 Adjust Master Volume 
3

Change Mode

4 Load: Epic Poly 
5 Load: Gangsta Lead 3
6 Revert 

- your history (for Undo) now looks like this, with a

copy

of Thor`s 
latest state before browsing; first:

(Numbers representing Undo 1, 2, 3 times and so on.)

0

Change Mode (

copy of your original state, before browsing, without the undo`s

)

1 Load: Gangsta Lead 3
2 Load: Epic Poly
3

Change Mode (

Original

)

4 Adjust Master Volume
5 Thor Init patch

-----

Same example for R7:

1 Thor Init patch 
2 Adjust Master Volume 
3 

Change Mode

 
4 Load: Epic Poly 
5 Load: Gangsta Lead 3
6

Cancel 

- your history (for Undo) now looks like this, with Thor`s 
latest state before browsing; first:

(Numbers representing Undo 1, 2, 3 times and so on.)

0

 

Change Mode (

Original

)

1 Adjust Master Volume
2 Thor Init patch

-----

I`d prefer that Revert actually "went trough" the Undo`s until it
found the last state before browsing, but that`s not how it works.

Hope this was clear enough  


Cheers

I think we are talking about two different things, as I don't dispute anything you've written above!

Every thing I described in my post was something I actually DID in Reason as I wrote that text (how I always work). So if you do exactly what I describe you'll find out it works exactly as I described!

Plus, I wrote a LOT of things in my post - are you saying each and every line I wrote is wrong, or if not which ones are you saying is wrong?

[Eagleizer]

I saw the mention of "Revert" for the browser and thought "hurray, hurray, hurray!". But now I think I have read somewhere that it "reloads" the patch used before browsing, rather than actually just going back to its previous state. Can anyone confirm/deny please?

The reason it matters to me is that I quite often tweak patches quite a bit after loading them and so "reloading" the patch wouldn't take me back to where I was before browsing :/

It can work exactly as you describe if you understand HOW it works and you approach it like the "old" version.

If you browse and tweak WHILE browsing (not possible to do in previous versions), it will not work as expected, which is logical IMO because the idea of Revert is to take you back to the "pre-browsing" state.

But if you browse, then leave browse mode to tweak a patch, then when you begin browsing again, revert will return you to your tweaked patch (not the stored "preset" you started with).

This is exactly what you want, you just have to "tell" it when you want to keep the patch by ending your browse session. This worked automatically in the old version, fwiw because you had was no other option!

Reverting, BTW, takes you OUT of browse mode, so you'll have to "browse" again to re-activate the feature.

Again this is how it used to work, except the browser is not now "modal" which causes the confusion IMO.

But it was pretty easy to learn the new workflow for me.

Remember that Revert takes you back to the state of the instrument when you ENTERED browse mode, not the preset stored on disk - sometimes these are the same thing, like if you created a device loaded with a factory patch, then loaded a second patch, then hit revert you would be returned to the factory patch. But not because it's the one on disk but because it was the one LOADED into the device when you began browsing. 

I probably could have stated this more clearly - hope this helps!

Never thought I`ll say this, but you are wrong Giles. Tincture
probably read my post which is the

correct

description of how Revert
works: 

http://www.reasontalk.com/post/show_sin ... stcount=12

Feel free to try for yourself: 

- Create an instrument
- Move mix fader to get out of browse focus
- Make 5 tweaks to the patch (Let`s call them Tweak 1-5)
- Click the instrument`s browse button
- Load 5 patches (one by one)
- Click Revert

The patch, with your latest tweak setting (Tweak 5), is

loaded

. 

When you now hit Ctrl+Z, you are

not

going back to Tweak 4,
but you start to go back through the patches you previewed. 

So, if you want to go back to Tweak 4, you can save 1 operation
(Revert) by using Ctrl+Z right away, instead of Revert first.


Example. When you do the following: 

1 Thor Init patch

(

no browser focus

)

2 Adjust Master Volume 
3

Change Mode

4 Load: Epic Poly 
5 Load: Gangsta Lead 3
6 Revert 

- your history (for Undo) now looks like this, with a

copy

of Thor`s 
latest state before browsing; first:

(Numbers representing Undo 1, 2, 3 times and so on.)

0

Change Mode (

copy of your original state, before browsing, without the undo`s

)

1 Load: Gangsta Lead 3
2 Load: Epic Poly
3

Change Mode (

Original

)

4 Adjust Master Volume
5 Thor Init patch

-----

Same example for R7:

1 Thor Init patch 
2 Adjust Master Volume 
3 

Change Mode

 
4 Load: Epic Poly 
5 Load: Gangsta Lead 3
6

Cancel 

- your history (for Undo) now looks like this, with Thor`s 
latest state before browsing; first:

(Numbers representing Undo 1, 2, 3 times and so on.)

0

 

Change Mode (

Original

)

1 Adjust Master Volume
2 Thor Init patch

-----

I`d prefer that Revert actually "went trough" the Undo`s until it
found the last state before browsing, but that`s not how it works.

Hope this was clear enough  


Cheers

I think we are talking about two different things, as I don't dispute anything you've written above!

Every thing I described in my post was something I actually DID in Reason as I wrote that text (how I always work). So if you do exactly what I describe you'll find out it works exactly as I described!

Plus, I wrote a LOT of things in my post - are you saying each and every line I wrote is wrong, or if not which ones are you saying is wrong?

 

Sorry about that! I spent so long time testing and writing that I
forgot to highlight what I disagreed on in your post I also see 
how Tincture may have misunderstood my post, which is why I
probably read your post in a different way than you meant.

Tincture wrote:
"But now I think I have read somewhere that it "reloads" the patch used before browsing, rather than actually just going back to its previous state. Can anyone confirm/deny please?"

You wrote: 
"Again this is how it used to work, except the browser is not now "modal" which causes the confusion IMO.

and: 

"Remember that Revert takes you back to the state of the instrument when you ENTERED browse mode"

I my book, back to the same state means "as if nothing ever
happened" (like in R7), and back isn`t entirely correct either, 
as you are still going forward in the history of Undo. This is
what I thought Tincture was asking about. And if it wasn`t,
I apologize for that too.  

Anyway, sorry for the misunderstanding. At least it should now
be clear to everybody how this works


Cheers

[jfrichards]

I saw the mention of "Revert" for the browser and thought "hurray, hurray, hurray!". But now I think I have read somewhere that it "reloads" the patch used before browsing, rather than actually just going back to its previous state. Can anyone confirm/deny please?

The reason it matters to me is that I quite often tweak patches quite a bit after loading them and so "reloading" the patch wouldn't take me back to where I was before browsing :/

It can work exactly as you describe if you understand HOW it works and you approach it like the "old" version.

If you browse and tweak WHILE browsing (not possible to do in previous versions), it will not work as expected, which is logical IMO because the idea of Revert is to take you back to the "pre-browsing" state.

But if you browse, then leave browse mode to tweak a patch, then when you begin browsing again, revert will return you to your tweaked patch (not the stored "preset" you started with).

This is exactly what you want, you just have to "tell" it when you want to keep the patch by ending your browse session. This worked automatically in the old version, fwiw because you had was no other option!

Reverting, BTW, takes you OUT of browse mode, so you'll have to "browse" again to re-activate the feature.

Again this is how it used to work, except the browser is not now "modal" which causes the confusion IMO.

But it was pretty easy to learn the new workflow for me.

Remember that Revert takes you back to the state of the instrument when you ENTERED browse mode, not the preset stored on disk - sometimes these are the same thing, like if you created a device loaded with a factory patch, then loaded a second patch, then hit revert you would be returned to the factory patch. But not because it's the one on disk but because it was the one LOADED into the device when you began browsing. 

I probably could have stated this more clearly - hope this helps!

Never thought I`ll say this, but you are wrong Giles. Tincture
probably read my post which is the

correct

description of how Revert
works: 

http://www.reasontalk.com/post/show_sin ... stcount=12

Feel free to try for yourself: 

- Create an instrument
- Move mix fader to get out of browse focus
- Make 5 tweaks to the patch (Let`s call them Tweak 1-5)
- Click the instrument`s browse button
- Load 5 patches (one by one)
- Click Revert

The patch, with your latest tweak setting (Tweak 5), is

loaded

. 

When you now hit Ctrl+Z, you are

not

going back to Tweak 4,
but you start to go back through the patches you previewed. 

So, if you want to go back to Tweak 4, you can save 1 operation
(Revert) by using Ctrl+Z right away, instead of Revert first.


Example. When you do the following: 

1 Thor Init patch

(

no browser focus

)

2 Adjust Master Volume 
3

Change Mode

4 Load: Epic Poly 
5 Load: Gangsta Lead 3
6 Revert 

- your history (for Undo) now looks like this, with a

copy

of Thor`s 
latest state before browsing; first:

(Numbers representing Undo 1, 2, 3 times and so on.)

0

Change Mode (

copy of your original state, before browsing, without the undo`s

)

1 Load: Gangsta Lead 3
2 Load: Epic Poly
3

Change Mode (

Original

)

4 Adjust Master Volume
5 Thor Init patch

-----

Same example for R7:

1 Thor Init patch 
2 Adjust Master Volume 
3 

Change Mode

 
4 Load: Epic Poly 
5 Load: Gangsta Lead 3
6

Cancel 

- your history (for Undo) now looks like this, with Thor`s 
latest state before browsing; first:

(Numbers representing Undo 1, 2, 3 times and so on.)

0

 

Change Mode (

Original

)

1 Adjust Master Volume
2 Thor Init patch

-----

I`d prefer that Revert actually "went trough" the Undo`s until it
found the last state before browsing, but that`s not how it works.

Hope this was clear enough  


Cheers

I think we are talking about two different things, as I don't dispute anything you've written above!

Every thing I described in my post was something I actually DID in Reason as I wrote that text (how I always work). So if you do exactly what I describe you'll find out it works exactly as I described!

Plus, I wrote a LOT of things in my post - are you saying each and every line I wrote is wrong, or if not which ones are you saying is wrong?

 

Sorry about that! I spent so long time testing and writing that I
forgot to highlight what I disagreed on in your post I also see 
how Tincture may have misunderstood my post, which is why I
probably read your post in a different way than you meant.

Tincture wrote:
"But now I think I have read somewhere that it "reloads" the patch used before browsing, rather than actually just going back to its previous state. Can anyone confirm/deny please?"

You wrote: 
"Again

this is how it used to work

, except the browser is not now "modal" which causes the confusion IMO.

and: 

"Remember that Revert takes you

back to the state

of the instrument when you ENTERED browse mode"

I my book,

back to the same state

 means "as if nothing ever
happened" (like in R7), and back isn`t entirely correct either, 
as you are still going forward in the history of Undo. This is
what I thought Tincture was asking about. And if it wasn`t,
I apologize for that too.  

Anyway, sorry for the misunderstanding. At least it should now
be clear to everybody how this works


Cheers

Sorry

it's

not

clear

to

me.

If

you

could

just

explain

it

a

bit

more,

vertically

that

is,

I

think

I'll

get

it.

[trimph1]

I saw the mention of "Revert" for the browser and thought "hurray, hurray, hurray!". But now I think I have read somewhere that it "reloads" the patch used before browsing, rather than actually just going back to its previous state. Can anyone confirm/deny please?

The reason it matters to me is that I quite often tweak patches quite a bit after loading them and so "reloading" the patch wouldn't take me back to where I was before browsing :/

It can work exactly as you describe if you understand HOW it works and you approach it like the "old" version.

If you browse and tweak WHILE browsing (not possible to do in previous versions), it will not work as expected, which is logical IMO because the idea of Revert is to take you back to the "pre-browsing" state.

But if you browse, then leave browse mode to tweak a patch, then when you begin browsing again, revert will return you to your tweaked patch (not the stored "preset" you started with).

This is exactly what you want, you just have to "tell" it when you want to keep the patch by ending your browse session. This worked automatically in the old version, fwiw because you had was no other option!

Reverting, BTW, takes you OUT of browse mode, so you'll have to "browse" again to re-activate the feature.

Again this is how it used to work, except the browser is not now "modal" which causes the confusion IMO.

But it was pretty easy to learn the new workflow for me.

Remember that Revert takes you back to the state of the instrument when you ENTERED browse mode, not the preset stored on disk - sometimes these are the same thing, like if you created a device loaded with a factory patch, then loaded a second patch, then hit revert you would be returned to the factory patch. But not because it's the one on disk but because it was the one LOADED into the device when you began browsing. 

I probably could have stated this more clearly - hope this helps!

Never thought I`ll say this, but you are wrong Giles. Tincture
probably read my post which is the

correct

description of how Revert
works: 

http://www.reasontalk.com/post/show_sin ... stcount=12

Feel free to try for yourself: 

- Create an instrument
- Move mix fader to get out of browse focus
- Make 5 tweaks to the patch (Let`s call them Tweak 1-5)
- Click the instrument`s browse button
- Load 5 patches (one by one)
- Click Revert

The patch, with your latest tweak setting (Tweak 5), is

loaded

. 

When you now hit Ctrl+Z, you are

not

going back to Tweak 4,
but you start to go back through the patches you previewed. 

So, if you want to go back to Tweak 4, you can save 1 operation
(Revert) by using Ctrl+Z right away, instead of Revert first.


Example. When you do the following: 

1 Thor Init patch

(

no browser focus

)

2 Adjust Master Volume 
3

Change Mode

4 Load: Epic Poly 
5 Load: Gangsta Lead 3
6 Revert 

- your history (for Undo) now looks like this, with a

copy

of Thor`s 
latest state before browsing; first:

(Numbers representing Undo 1, 2, 3 times and so on.)

0

Change Mode (

copy of your original state, before browsing, without the undo`s

)

1 Load: Gangsta Lead 3
2 Load: Epic Poly
3

Change Mode (

Original

)

4 Adjust Master Volume
5 Thor Init patch

-----

Same example for R7:

1 Thor Init patch 
2 Adjust Master Volume 
3 

Change Mode

 
4 Load: Epic Poly 
5 Load: Gangsta Lead 3
6

Cancel 

- your history (for Undo) now looks like this, with Thor`s 
latest state before browsing; first:

(Numbers representing Undo 1, 2, 3 times and so on.)

0

 

Change Mode (

Original

)

1 Adjust Master Volume
2 Thor Init patch

-----

I`d prefer that Revert actually "went trough" the Undo`s until it
found the last state before browsing, but that`s not how it works.

Hope this was clear enough  


Cheers

I think we are talking about two different things, as I don't dispute anything you've written above!

Every thing I described in my post was something I actually DID in Reason as I wrote that text (how I always work). So if you do exactly what I describe you'll find out it works exactly as I described!

Plus, I wrote a LOT of things in my post - are you saying each and every line I wrote is wrong, or if not which ones are you saying is wrong?

 

Sorry about that! I spent so long time testing and writing that I
forgot to highlight what I disagreed on in your post I also see 
how Tincture may have misunderstood my post, which is why I
probably read your post in a different way than you meant.

Tincture wrote:
"But now I think I have read somewhere that it "reloads" the patch used before browsing, rather than actually just going back to its previous state. Can anyone confirm/deny please?"

You wrote: 
"Again

this is how it used to work

, except the browser is not now "modal" which causes the confusion IMO.

and: 

"Remember that Revert takes you

back to the state

of the instrument when you ENTERED browse mode"

I my book,

back to the same state

 means "as if nothing ever
happened" (like in R7), and back isn`t entirely correct either, 
as you are still going forward in the history of Undo. This is
what I thought Tincture was asking about. And if it wasn`t,
I apologize for that too.  

Anyway, sorry for the misunderstanding. At least it should now
be clear to everybody how this works


Cheers

Sorry

it's

not

clear

to

me.

If

you

could

just

explain

it

a

bit

more,

vertically

that

is,

I

think

I'll

get

it.

Building a quote pyramid what?

[selig]

Sorry about that! I spent so long time testing and writing that I
forgot to highlight what I disagreed on in your post I also see 
how Tincture may have misunderstood my post, which is why I
probably read your post in a different way than you meant.

Tincture wrote:
"But now I think I have read somewhere that it "reloads" the patch used before browsing, rather than actually just going back to its previous state. Can anyone confirm/deny please?"

You wrote: 
"Again this is how it used to work, except the browser is not now "modal" which causes the confusion IMO.

and: 

"Remember that Revert takes you back to the state of the instrument when you ENTERED browse mode"

I my book, back to the same state means "as if nothing ever
happened" (like in R7), and back isn`t entirely correct either, 
as you are still going forward in the history of Undo. This is
what I thought Tincture was asking about. And if it wasn`t,
I apologize for that too.  

Anyway, sorry for the misunderstanding. At least it should now
be clear to everybody how this works


Cheers

Not sure exactly what you're saying, but indeed I was correct: revert takes you back "as if nothing ever happened, like in R7". During beta testing this was clarified by the Props that this is the goal, and I'm simply repeating it here. You are not "going forward" in the history of undos" (and I don't even know how that's possible!) - you are going BACK to the undo buffer that was loaded when you began browsing. 

It doesn't reload the "patch" because there doesn't have to be a "patch" - it reloads the SETTINGS. A "Patch" is something you save on disc. Even if you have not saved a "patch", Revert still works. But if you loaded a patch then edited it, then entered browse mode, revert takes you back to YOUR EDITS at the time you entered browse mode - just like it did with R7.

Here's a simplified example of how it works, so everyone is clear. 

When you first enter browse mode, the current SETTINGS are put in a SEPARATE and new undo buffer.
Then you browse, and when you hit the REVERT button, the new undo buffer is used to return the device to the original state at the time you began browsing. This is pretty much how it worked in R7, except there was only one UNDO buffer. Now there's two! 

In BOTH cases during browsing, new patches are loaded into the device for "auditioning". In both cases an undo buffer can be used to return the device to the original "pre browsing" state. The main difference now is that the browsing "window" can remain open even when not actually in browse "mode" (why it's not a "modal" system), in the old version (R7) the browser is only visible during browse mode. 

So indeed, "Revert" takes you back "as if nothing happened". I outlined this in the post you quoted, and it works 'as advertised' (like R7) as far as my testing shows.
Sorry for any confusion.

[miscend]

I saw the mention of "Revert" for the browser and thought "hurray, hurray, hurray!". But now I think I have read somewhere that it "reloads" the patch used before browsing, rather than actually just going back to its previous state. Can anyone confirm/deny please?

The reason it matters to me is that I quite often tweak patches quite a bit after loading them and so "reloading" the patch wouldn't take me back to where I was before browsing :/

It can work exactly as you describe if you understand HOW it works and you approach it like the "old" version.

If you browse and tweak WHILE browsing (not possible to do in previous versions), it will not work as expected, which is logical IMO because the idea of Revert is to take you back to the "pre-browsing" state.

But if you browse, then leave browse mode to tweak a patch, then when you begin browsing again, revert will return you to your tweaked patch (not the stored "preset" you started with).

This is exactly what you want, you just have to "tell" it when you want to keep the patch by ending your browse session. This worked automatically in the old version, fwiw because you had was no other option!

Reverting, BTW, takes you OUT of browse mode, so you'll have to "browse" again to re-activate the feature. Again this is how it used to work, except the browser is not now "modal" which causes the confusion IMO. But it was pretty easy to learn the new workflow for me.

Remember that Revert takes you back to the state of the instrument when you ENTERED browse mode, not the preset stored on disk - sometimes these are the same thing, like if you created a device loaded with a factory patch, then loaded a second patch, then hit revert you would be returned to the factory patch. But not because it's the one on disk but because it was the one LOADED into the device when you began browsing. 

I probably could have stated this more clearly - hope this helps!

Never thought I`ll say this, but you are wrong Giles. Tincture
probably read my post which is the

correct

description of how Revert
works: 

http://www.reasontalk.com/post/show_sin ... stcount=12

Feel free to try for yourself: 

- Create an instrument
- Move mix fader to get out of browse focus
- Make 5 tweaks to the patch (Let`s call them Tweak 1-5)
- Click the instrument`s browse button
- Load 5 patches (one by one)
- Click Revert

The patch, with your latest tweak setting (Tweak 5), is

loaded

. 

When you now hit Ctrl+Z, you are

not

going back to Tweak 4,
but you start to go back through the patches you previewed. 

So, if you want to go back to Tweak 4, you can save 1 operation
(Revert) by using Ctrl+Z right away, instead of Revert first.


Example. When you do the following: 

1 Thor Init patch

(

no browser focus

)

2 Adjust Master Volume 
3

Change Mode

4 Load: Epic Poly 
5 Load: Gangsta Lead 3
6 Revert 

- your history (for Undo) now looks like this, with a

copy

of Thor`s 
latest state before browsing; first:

(Numbers representing Undo 1, 2, 3 times and so on.)

0

Change Mode (

copy of your original state, before browsing, without the undo`s

)

1 Load: Gangsta Lead 3
2 Load: Epic Poly
3

Change Mode (

Original

)

4 Adjust Master Volume
5 Thor Init patch

-----

Same example for R7:

1 Thor Init patch 
2 Adjust Master Volume 
3 

Change Mode

 
4 Load: Epic Poly 
5 Load: Gangsta Lead 3
6

Cancel 

- your history (for Undo) now looks like this, with Thor`s 
latest state before browsing; first:

(Numbers representing Undo 1, 2, 3 times and so on.)

0

 

Change Mode (

Original

)

1 Adjust Master Volume
2 Thor Init patch

-----

I`d prefer that Revert actually "went trough" the Undo`s until it
found the last state before browsing, but that`s not how it works.

Hope this was clear enough  


Cheers

Is that meant to be problem? Seems pretty straightforward you can either use revert or undo.

[ClassickHitz]

Joy joy, new colors and it only took 15 years to add.

Wheeew whoooo finally Redrum properly working intuitively with other midi controllers other than Nektar. What a novel concept!! 

Is Propellerhead now telling me I no longer have to move my FSB/Okester to a separate folder to update? Wow, I really appreciate the elimination of this headache. It was only annoying as hell from version 6, 6.5, 7, 7.1, 8, 8.1 to 8.2

I can't say thank you enough. 

What next? Putting back all the transport data bar information on the left side again. 

Please stop as I can hardly contain my excitement. 

[-008']

Joy joy, new colors and it only took 15 years to add.

Wheeew whoooo finally Redrum properly working intuitively with other midi controllers other than Nektar. What a novel concept!! 

Is Propellerhead now telling me I no longer have to move my FSB/Okester to a separate folder to update? Wow, I really appreciate the elimination of this headache. It was only annoying as hell from version 6, 6.5, 7, 7.1, 8, 8.1 to 8.2

I can't say thank you enough. 

What next? Putting back all the transport data bar information on the left side again. 

Please stop as I can hardly contain my excitement. 

I don't think anyone is saying you should be jumping up and down peeing your pants over a .Point release.

However, the fact that this one is a point release which kind of promises: more point releases, faster and more often... that is at least something positive, IMO. Still nothing to trip over tho!

The future (for any software) might be no "wow!" updates at all if you really think about it...

[gak]

I can't keep up with the mostly quoted/quoted/quoted posts

Can anyone elaborate on this? Seems straight forward but many hosts I've used have had focus issues (even when allegedly fixing them) so I'm wondering if anyone has actually noticed a diff.

• Keyboard focus is now returned to the sequencer after the user makes settings in the Transport panel.

[phasys]

Amusing how a moderator (Hi Selig!) uses those extensive quotes and doesn't clean up the posts.

[gak]

Amusing how a moderator (Hi Selig!) uses those extensive quotes and doesn't clean up the posts.

http://www.reasontalk.com/post/changes- ... 1286761157

[selig]

Amusing how a moderator (Hi Selig!) uses those extensive quotes and doesn't clean up the posts.

You KNOW I do it only to irritate you, cause I know you so well!

And BTW, I'm no longer a mod so I can't clean up anyone else's posts.

[Lunesis]

Sorry, it's just a crappy side effect of this forum's coding. I've asked them about fixing it to include only one quote per message but they seem to be willfully dragging their feet.

[ClassickHitz]

Joy joy, new colors and it only took 15 years to add.

Wheeew whoooo finally Redrum properly working intuitively with other midi controllers other than Nektar. What a novel concept!! 

Is Propellerhead now telling me I no longer have to move my FSB/Okester to a separate folder to update? Wow, I really appreciate the elimination of this headache. It was only annoying as hell from version 6, 6.5, 7, 7.1, 8, 8.1 to 8.2

I can't say thank you enough. 

What next? Putting back all the transport data bar information on the left side again. 

Please stop as I can hardly contain my excitement. 

I don't think anyone is saying you should be jumping up and down peeing your pants over a .Point release. However, the fact that this one is a point release which kind of promises: more point releases, faster and more often... that is at least something positive, IMO. Still nothing to trip over tho! The future (for any software) might be no "wow!" updates at all if you really think about it...

I'm sorry but I just don't agree at all. Nothing about this being a point release suggest in any way that more point releases are coming any faster than in the past. This isn't Reason's first point release by the way...I seem to remember 2.5, 6.5 and 7.1

As for the future for any software...most would agree that the recent Logic Pro 10.1 software upgrade is pretty freakin' awesome with a plethora of wow factors.

Did I mention it was free!

https://www.apple.com/logic-pro/

I think the only DAW that needs to catch up on it's wow factor is Reason. Admittedly I'm patiently waiting but currently still not impressed. I'll stick with version 7.1 for now with no regrets. 

[-008']

I'm sorry but I just don't agree at all. Nothing about this being a point release suggest in any way that more point releases are coming any faster than in the past. This isn't Reason's first point release by the way...I seem to remember 2.5, 6.5 and 7.1

As for the future for any software...most would agree that the recent Logic Pro 10.1 software upgrade is pretty freakin' awesome with a plethora of wow factors.

Did I mention it was free!

https://www.apple.com/logic-pro/

I think the only DAW that needs to catch up on it's wow factor is Reason. Admittedly I'm patiently waiting but currently still not impressed. I'll stick with version 7.1 for now with no regrets. 

Really? Nothing about this update suggests that there will be more updates? Literally everything about this update suggests more updates! Lol

•There is an auto-update system built in to reason and its interface now.

•Updates take mere minutes at one-tenth the size.

•This is .2 after 8 dropped how long ago...?

Reason 3, 4, 5 had complaints that used to sit there between whole entire versions and not be addressed ....and now we have something like "Revert Browse" being implemented in just a quick point release or two after the new browser. Proving that, despite what you say, they can fix stuff faster, and likely will. Besides, It's good for business.

Different people like different things. For ex: Logic or bitwig or ableton doesn't wow me at all. Fl studio lost its wow factor like 12 years ago and I stopped using it.... And I've demoed all again, repeatedly throughout the years. Different stuff clicks for different folk.

[EnochLight]

I'm sorry but I just don't agree at all. Nothing about this being a point release suggest in any way that more point releases are coming any faster than in the past. 

And yet, we've seen 5 different Reason updates over the course of the past year:

Reason 7.1 - released 4/2014
Reason 7.1.1 - released 5/2014
Reason 8 - released 9/2014
Reason 8.1 - released 12/2014
Reason 8.2 - released 4/2015

I've said this before and I'll say it again - on top of everything else (read: RE's, the RE SDK, IDT, their limited mobile apps) we've seen more Reason updates occur than any other time in their history.  I mean seriously man - this is FIVE UPDATES IN THE PAST 12 MONTHS!

I'm not sure why this is so difficult to grasp for some.   :s0959:

I think the only DAW that needs to catch up on it's wow factor is Reason. Admittedly I'm patiently waiting but currently still not impressed. I'll stick with version 7.1 for now with no regrets. 

Reason has always been playing "catch up", and it's only become more pronounced since it officially became a DAW once Record & 6.0 dropped.  You act as if Logic gained the features that it currently has overnight.  And it's free?  Wow - that's novel!  Oh wait, no it's not - every update I listed above has been free with the exception of 8.  

But that's cool, stay on 7.1 if it fits your needs and gets you to where you need to be.  7.1 truly was a fantastic version of Reason, and you can do SDK 2.0 RE's with it and stuff so... there's that.  That browser though... ugh.. how do even manage?

[gak]

Think of it this way: You could be using studio one and waiting for updates  

[trimph1]

Think of it this way: You could be using studio one and waiting for updates  

Now now...don't you be picking on Studio One like that..... :s0238:

[gak]

It's my other host. I'm just saying that if you really want to be underwhelmed by updates, that one is seriously update deficient. 

[EnochLight]

LOL!!! Yeah, when I bought Studio One, there was honestly a brief pause where I had to commit to knowing I might never see a feature-packed update occur ever. But it does get periodic maintenance updates. I've gotten at least 2 since I bought it last year. You haven't?

[trimph1]

Sorry, it's just a crappy side effect of this forum's coding. I've asked them about fixing it to include only one quote per message but they seem to be willfully dragging their feet.

From what I have seen, most forums seem to have a limit of around 3-5 nested quotes. So it may be an issue with limiting further...

On one forum I was on, that being CW's Sonar forum, the formatting was so bad that after 7 nested quotes you got the words coming out single letter down the line...

[BarbaraC]

I've read through this entire blessed thread, knowing that the good, the bad, and the ugly would likely be mentioned, but I was also looking for something that would convince me to upgrade from version 7. I like the new browser (as long as it can be hidden--can it?) and I like the proliferation of colors because I'm always in need of colors with which the lines contrast (bad contrast on light green, for instance), but these two things aren't worth $129 to me because of the kind of music I create, which relies heavily on old-fashioned instruments. Really, there must be a bunch of stuff I'm missing. My inner child wants to upgrade, but the very annoying grownup says to stop being so childish.

[jfrichards]

...there must be a bunch of stuff I'm missing...

If you're on the fence, I would suggest seeing what 8.3 and 8.4 bring to the table (I would guess 2 to 4 months ETA).  I loved it right away, but that's because I use drag and drop of samples into audio tracks and kong, and dragging of rex loops into audio tracks, kong, and octorex a lot, and hunting and dragging patches, and I've come to love the Softube Amp, which rivals and complements Verimilion.  Yes you can hide the browser with F3.  The colors are very cool but not necessary.  It's nice to have the option of staying on 7 which is a killer program.

Discover is more or less a huge evolving refill of 45 second samples.  You can download any of the 500 new daily clips into Reason and use them however you want.  Not useful for traditional composition, that's for sure.  And certainly nowhere near the professional uses of Soundcloud, Bandcamp, Dropbox, etc.  There is some really good stuff on Discover though.

There are a bunch of little improvements with 8, but none that warrant $129.

Maybe the biggest improvement is the new update methodology, which means we will see many X.x updates from now on and it will only take 4 worry-free minutes.