| Page: 1 | Rating: Unrated [0] |
Reason 3 Issues
| Good [+1]Toggle ReplyLink» bob_ replied on Wed Apr 27, 2005 @ 8:49pm |
 Coolness: 102305 | Dear Reason 3 users!
You may have encountered a few glitches in using Reason 3.0. We at Propellerhead Software pride ourselves on shipping the highest quality software possible and are undertaking a thorough investigation of all bugs reported. Our intention is to fix all problems listed below and offer a high quality release. So please bear with us as we track down and squash all known bugs. In the meantime, we'd like to let you know about all significant issues we've found in Reason 3. We appreciate your patience and help in making Reason better than ever. Here is the list of confirmed bugs and issues: 1) Keyboard Control There is a problem when editing Keyboard Control mappings that can possibly lead the program to crash. For a detailed description of this problem and workarounds, go here. 2) Pattern Change Automation Reason 3.0 misinterprets pattern change automation when patterns don't start on the downbeats. This can be a problem when loading songs with pattern automation, created in version 2.5 or older. This problem does not occur if the length of the patterns conforms to the time signature (e.g. 16 or 32 step patterns in a 4/4 song) and the pattern changes happen on downbeats. 3) Triggering the RV7000 Gate The function that triggers the RV7000 Gate via MIDI doesn't work at all. 4) "Bad Format" when opening NN-XT patches or songs 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 of Dr.REX Preview 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) Replace mode recording 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. A temporary workaround is to instead create a second track for the device, record your changes on that track. Delete the notes you wanted to replace and move your new recorded notes into the first track. 7) Loud noise when playing back in Loop mode When playing back an NN-XT patch with Loop activated on the transport bar, the NN-XT can produce a loud transient noise at the loop end position, if there are notes very close to that position. This can happen when using Reason standalone or with ReWire. Users are advised to avoid high playback volume. 8) "Unknown Exception" on startup (Windows only) A few Reason and Reason Adapted users have got an "Unknown Exception" alert when trying to launch the program. This is because there are ReWire and/or REX dll files already installed on the computer, and these files have missing or corrupt version numbers. A temporary workaround is to search your system for "ReWire.dll" and "REX Shared Library.dll", delete all these files and then launch Reason 3 again. 9) "Internal Error" when opening a Reason song in ReWire mode (Windows only) When using Reason with a ReWire host and attempting to load songs or patches with a very large number of samples (e.g. Reason Drum Kits patches), some users have got an "Internal Error" alert. A temporary workaround that has been useful for some users is to read the samples from CD or DVD instead of the hard drive. In the case of RDK, this would mean removing the Reason Drum Kits refill from the hard disk and opening the songs or patches with the Reason Drum Kits DVD in the drive. 10) No hard drives shown in the Browser (Windows only) Under some circumstances, the browser in Reason 3.0 will not show hard drives under My Computer. 11) New files not shown in the Browser (Windows only) Some users have found that newly created files are not shown in the Reason 3.0 browser - you have to quit Reason and launch it again to see the new files. This only happens with hard drives using the FAT32 file system. 12) Wrong file dates and times shown in the Browser (Windows only) The Reason 3 browser shows all file dates using GMT time, instead of local time. 13) Automation of Combinator controls When you have automated a Combinator control (button or rotary) and play back the automation, there is a tiny delay before the Combinator passes on the information to the devices within it. Most often this cannot be noticed, but if you have assigned a Combinator button to a mute or a pattern switch on a pattern device, and automate this button, you may find that the mute or pattern change happens too late when you play back the automation. A temporary workaround is to automate the mute or pattern change directly on the combinated device rather than on the Combinator. 14) Pattern device Resolution can no longer be remoted The Resolution parameter on the Redrum and Matrix cannot be controlled remotely. 15) Hard to edit sequencer data during playback In Reason 2.5, "Follow Song" was temporarily disabled when you pressed the mouse button. This meant that you could move and edit notes and other sequencer data while the song was playing, with no restrictions. This feature doesn't work properly in 3.0 - you cannot e.g. drag a note outside the area currently shown in the sequencer, when you're playing back. 16) Performance problems Several performance and CPU usage issues have been found. We continue to investigate all issues, but we have confirmed a problem with scrolling as well as bugs in the MClass Equalizer, the DDL-1 delay and the Subtractor's noise generator, which could all cause occasional high loads on the CPU. 17) Program continues to draw or move data just after I release the mouse button (Mac only) The program is slow to react when the user releases the mouse button. 18) Remote issues For some users with M-Audio Radium keyboards, the Remote implementation doesn't work properly. It turns out there are two different Radium models, with different settings in factory preset 1 (just like Oxygen 8). Reason 3.0 only supports the latest model. There are also some minor Remote mapping errors. We would like to apologize for any inconvenience caused by these issues. We would also like to thank the users who have helped us find and identify these problems. Sincerely, Ludvig Carlson Reason product manager |
| Good [+1]Toggle ReplyLink» OoOLuShYsOoO replied on Wed Apr 27, 2005 @ 9:28pm |
 Coolness: 47290 | well, Im happy I havent upgraded from 2.5 yet then :P
*shrug* |
| Good [+1]Toggle ReplyLink» bob_ replied on Wed Apr 27, 2005 @ 9:41pm |
| Coolness: 102305 | i did and dude, sometimes it's so fuckin demanding on the cpu (imagine, i have only a 500mhz G4...)
i hope they will fix this problem soon.... but i still think it's good, the mastering tools sounds great |
| Good [+1]Toggle ReplyLink» Omni replied on Wed Apr 27, 2005 @ 10:12pm |
 Coolness: 87675 | It's still worth it to upgrade to 3.0. The mastering tools themselves make the whole thing worth it. |
| Good [+1]Toggle ReplyLink» OoOLuShYsOoO replied on Wed Apr 27, 2005 @ 10:37pm |
| Coolness: 47290 | hmm, I supposes I should try the upgrade on one of my computers to see if it would be for me. |
| Good [+1]Toggle ReplyLink» OoOLuShYsOoO replied on Wed Apr 27, 2005 @ 10:46pm |
| Coolness: 47290 | have either of you experienced any of these issues? |
| Good [+1]Toggle ReplyLink» PitaGore replied on Thu Apr 28, 2005 @ 10:30am |
 Coolness: 471905 | my compute can handle that much cpu ...
i just cant handle it myself up to now ..:lol |
| Good [+1]Toggle ReplyLink» Omni replied on Thu Apr 28, 2005 @ 10:55am |
| Coolness: 87675 | There's a few times where the CPU load got a little out of hand and I could not understand where that was coming from, but hitting STOP and PLAY again would solve the problem. Appart from this, it's been going well for me. |
| Good [+1]Toggle ReplyLink» nothingnopenope replied on Thu Apr 28, 2005 @ 12:54pm |
 Coolness: 201325 | yeah I've seen it spike from a few cpu bars to max for no apparent reason.
Reason 3 is worth trying out if you have a fast computer, if you don't have a fast computer then it is painful to use. |
| Good [+1]Toggle ReplyLink» Omni replied on Thu Apr 28, 2005 @ 12:57pm |
| Coolness: 87675 | My computer is pretty old-school by today's standards (I have a 733 mhz) and I still think Reason 3 is well worth the upgrade. |
| Good [+1]Toggle ReplyLink» nothingnopenope replied on Thu Apr 28, 2005 @ 12:59pm |
| Coolness: 201325 | g4 or pentium? I found it ran slow on a 733mhz g4. |
| Good [+1]Toggle ReplyLink» AlienZeD replied on Thu Apr 28, 2005 @ 1:32pm |
 Coolness: 509660 | I can't wait till I get my hands on you!!! (Reason 3.0) |
| Good [+1]Toggle ReplyLink» Omni replied on Thu Apr 28, 2005 @ 3:44pm |
| Coolness: 87675 | I have a P3 733... |
Reason 3 Issues
| Page: 1 |
[ Cumbre de Página ] |
Post A Reply |
You must be logged in to post a reply.
[ Cumbre de Página ] |
