|
Reason 3 (pg. 7)
|
View this Thread in Original format
| Massive84 |
| quote: | Originally posted by Airbase
Im a bit amused about the fact that you are judging on the new things of Reason 3 without even having it tried out. The Combinator does so much more than just layer sounds. First of all its an amazing time saver when you have patches you usually start out from. The neater things about the Combinator is however the rotary controls and the Button Switches, which you can connect to as many of your units in the rack as you want. you can make one rotary to turn the cutoff up on one unit, while it turns it backwards on another, while it adds reverb the more you turn, while you can have a EQ make the EQ-changes. You got unlimited posibilities to modify your Combinator patch with just one rotary, and then let me add that you have three more Rotarys. You can even have one rotary editing up to three different things in each unit of you like. You can make so spaced out things you wouldnt believe it.
And you probably wouldnt, as you refuse to try it out. |
I know all of that, friends did try the demo.
First i don't use the same sounds, so even if i make a mint soundscape with the combinator or a lush pad, i won't reuse it. Maybe you do, and thats where the combinator saves time.
All you said are indeed wonderful things, i wouldn't mind the combinator, i just don't feel Reason 3.0 should be a combinator only.
And am sure you agree on that.
Like i said i am dissapointed in Props, they took lots of time, to come up with minor changes and on top of that charging people allot of money.
Am not 100% judging since like you said, i didn't try it. Just saying i hoped for more in Reason 3.0.
If you like it , enjoy it then :) |
|
|
| MegaMan |
and i/we are enjoying it
thank you |
|
|
| cheesy |
I've been playing around with Reason 3.0 today and it's great! The best things I've found so far are the Combinator and the compatibility with my MIDI devices.
True the Combinator doesn't really allow new sounds, but it makes it much easier to create new instruments from multiple Reason components. It allows great flexibility in automating different parameters and mapping keys. I found it especially useful when using MIDI controllers.
And MIDI controllers, omg Reason 3 makes it so much easier to use them and has more powerful features like track groups. I have an Evolution MK449c keyboard and an Edirol UR-80 control surface (& audio interface). Out of the box Reason sets both of these up to work very well, especially all the obscure buttons on the UR-80.
For example the transport controls on the UR-80 work great automatically, and now track groups work too. Now I can easily control all 16 tracks of the mixer with the 8 faders by pressing the track group button to switch between sets of 8 (now only if I could control 2 full mixers since the UR-80 has 4 track groups :) )
The master keyboard and locking features are cool too. If you have more than one MIDI device you can set your main keyboard as the master keyboard, then either have the other devices "follow" the master keyboard or lock it to a specific Reason device. For example I can lock my UR-80 to my main Mixer to just control that mixer (plus transport controls, etc)
Since you no longer have to manually map the controls, theres an "Overide mapping" which replaces the old mapping. I think the way this works is it turns off whatever that control affected before and makes it only affect the overidden control. So say one of my rotary knobs adjusted the LFO speed by default, but I wanted it to control the filter cutoff, I could easily do that. It might even globally overide it so even when you switch devives it still controls what you selected.
Anyway, I'm rambling on, I just really like the new MIDI controller features. The browser is a little better too, as is the sequencer. I haven't had a chance to use the MClass devices yet but they look nice too.
Bottom line, if you have multiple MIDI controllers that are auto-configured by Reason 3.0 then you NEED to upgrade :) |
|
|
| DJFreaq |
| quote: | Originally posted by TonyZ
1) You have to turn off the soft clipping on the MClass limiter to see how much you're actually clipping by for the Mastering Suite, then reduce the volumes until you kiss the redline. Otherwise you get that ducking effect that totally s your sound up (which is probably why the n00bs are crying "bad sound quality!") |
Agreed. But I have been using compressors for a while now and know how to make them sound sexzy. It must be the computer or something else is being sketchy...
And yes of course I use an external mastering suite ;)
I am a real man after all. |
|
|
| Rob |
Anyone come across bugs in 3?
Propellerheads press release (on their site)
| quote: | Dear Reason 3 users!
As you may know, there are a few problems in Reason 3.0. At this point, the following issues have been confirmed as bugs:
1. There is a problem when editing Keyboard Control mappings that can possibly lead the program to crash. A detailed description of this problem and workarounds can be found here.
2. Reason 3.0 misinterprets pattern change automation that does not occur on downbeats, which means that the song doesn't play back as intended. This is mainly a problem when loading songs with pattern automation, created in version 2.5 or older. As long as you keep your pattern changes on downbeats, this problem does not occur.
3. The function that triggers the RV7000 Gate via MIDI simply doesn't work, in the sense that it doesn't do anything...
4. If an NN-XT patch references samples with names (or folder names) that include exotic characters, the patch may not load properly. This problem mainly occurs when loading patches that have either been created in Reason 2.5 or have been converted from another program. Patches in the sound bank or patches that don't include exotic characters in sample or folder names are not affected.
5. Remote Override mappings for the Dr.REX Preview button are lost when opening a song. The program works as before, but this particular Remote Override mapping has to be redone every time you open a document.
6. Recording in Replace mode plays back the notes being overwritten. We recommend that you do not use Replace mode recording until this has been fixed.
7. There are also some minor Remote mapping errors.
In addition to this we have received reports that under some circumstances the application requires more processing (CPU) power than in earlier versions. We are still investigating this issue.
In general we would like to apologize for any inconvenience the above issues may have caused - we are doing all we can to fix them. More information to follow when we have it.
Sincerely,
Ludvig Carlson
Reason product manager
|
Luckily the only one that I've had trouble with was 6. But I just delete notes and then record them so no biggy:o
2 = :nervous: |
|
|
| MegaMan |
yeh man, cant wait for this update patch
i am having trouble with that cpu stuff, and i have 128 meg video card, at the same time my friend uses 64 meg and he has no problem with it
if those problems can be fixed, reason will rule for once and for all |
|
|
| Sirocco |
| reason 3 is horrible. the high frequencies still have a grainy dithering and the mclass suite work as good as a bunch of mediocre freeware synthedit plugs. Jesus :( |
|
|
| Trancevision |
When Reason came out, it was something completly new and innovative.
But now, sound quality issues and non integration of vst support seems
to make it slowly an outdated production software.
I still love it when I am listening the thousands of rns I've created and I enjoy it as a tool for creating new ideas.
But somehow I feel disappointed about lots of things...
:(
I wonder if they will make a real quantum leap again in one of the next versions... Reason 3 isn't worth the money IMO.
Trancevision |
|
|
| aquila |
| quote: | Dear Reason 3 users!
As you may know, there are a few problems in Reason 3.0. At this point, the following issues have been confirmed as bugs:
1. There is a problem when editing Keyboard Control mappings that can possibly lead the program to crash. A detailed description of this problem and workarounds can be found here.
2. Reason 3.0 misinterprets pattern change automation that does not occur on downbeats, which means that the song doesn't play back as intended. This is mainly a problem when loading songs with pattern automation, created in version 2.5 or older. As long as you keep your pattern changes on downbeats, this problem does not occur.
3. The function that triggers the RV7000 Gate via MIDI simply doesn't work, in the sense that it doesn't do anything...
4. If an NN-XT patch references samples with names (or folder names) that include exotic characters, the patch may not load properly. This problem mainly occurs when loading patches that have either been created in Reason 2.5 or have been converted from another program. Patches in the sound bank or patches that don't include exotic characters in sample or folder names are not affected.
5. Remote Override mappings for the Dr.REX Preview button are lost when opening a song. The program works as before, but this particular Remote Override mapping has to be redone every time you open a document.
6. Recording in Replace mode plays back the notes being overwritten. We recommend that you do not use Replace mode recording until this has been fixed.
7. There are also some minor Remote mapping errors.
In addition to this we have received reports that under some circumstances the application requires more processing (CPU) power than in earlier versions. We are still investigating this issue.
In general we would like to apologize for any inconvenience the above issues may have caused - we are doing all we can to fix them. More information to follow when we have it.
Sincerely,
Ludvig Carlson
Reason product manager |
What great ing beta testing methods they must have used! |
|
|
| DJFreaq |
| quote: | Originally posted by Sirocco
reason 3 is horrible. the high frequencies still have a grainy dithering and the mclass suite work as good as a bunch of mediocre freeware synthedit plugs. Jesus :( |
word |
|
|
| MegaMan |
and one other thing i can barely stand, is people saying how ty it is, and not knowing how to use it properly.
if you really know what you're doing, you wont say like that about reason. |
|
|
|
|
