If I decide that Reason really can't be made friendly enough to run from within itself, I would put a copy of Reaper on the same Drive with Reason, and rewire it to Reaper. In XP, Reaper is very durable, and I would think if anything could survive Code Meter it would be Reaper. With ReaAccess running, Reaper looks just like Sonar 4,;nice horizontal tracks, time line controlled with right and left arrows, plus page up and down, hit r to record, couldn't be simpler, audio from Reason appears in Reaper, edits in Reaper, saved from Reaper, . And, if Code Meter screws up Reaper, just install another copy of Reaper on top of that one.
All your music and settings should be safely kept.I would think Sonar 8.5.3, the tempermental prima donna, would be the least likely to put up with co existing with Code Meter. After all these decades, even new X1 still is very jealous of a simple thing like even temporarily sharing a sound source with the screenreader, says, no thanks, I want it to be mine; mine; mine only, I'm closing now until I get my own.
Indigo L On 11/26/2011 6:20 AM, D!J!X! wrote:
That's a good option, but unless you are using 2 separate systems, it limits reason's usability, don't you think? I mean say you want to use it with sonar on a project, unless you've got the hardware going, it won't work on the same computer. That's the choice I would make though, if I decide to mess around with it again, probably install it on a spare computer with xp, and network it to my farm using midi over lan or just dedicating my oxygen to it for the time being, and using my delta1010 to send either a digital signal or a few analog lines to my pro40. I can then somewhat controll it from sonar (I might need a kvm switch to load patches and such, but no biggy). D!J!X! -----Original Message----- From: realmusicians-bounce@xxxxxxxxxxxxx [mailto:realmusicians-bounce@xxxxxxxxxxxxx] On Behalf Of Indigo Sent: Friday, November 25, 2011 11:18 PM To: realmusicians@xxxxxxxxxxxxx Subject: [realmusicians] Solving Reason's Code Meter Problem, maybe? I'm beginning to realize how serious a threat Code Meter could be to the health of computers with screenreaders, especially on Windows 7 64; with our fragile Wineyes 7.5x. I had a lockup on my brand new zingy fast machine, with very little on it except Reaper 64, Sonar X1 demo, and Reason 6. It froze so totally I had to shut down with the power button. It's back up, but I can tell it's way slower now, and was damaged by the crash. I had to restore back to the day I opened the box and set up the machine. It doesn't matter to me that the new machine seems slower now; I'm not going to keep the Windows 7 on it anyway, I'll do a clean install of XP Pro, but I now think even a single hard drive caddy, or docking station, is a good idea, and I want a hard drive with nothing but the screenreader and Reason 6 on it. I'll partition it, with another partition for data, and try to devise some way to isolate Winize somewhat from Reason 6 if such a thing is possible. There's obviously no way round that Code Meter, so I'll try to live with it, but on its own hard drive, so it doesn't harm Sonar, Reaper and other things. The developer's license I got from PropellerHeads was so I could look into Reaper 6, in hopes of accessing it for blind musicians. I have to tell the truth about what I learn about Reason 6, that running it might come with problems from Code Meter. I don't know yet, maybe Code Meter won't harm NVDA, Jaws or System Access, and maybe there are ways to make WindowEyes tolerate it as well. Reason 6 on XP, with WindowEyes 6.1 didn't freeze up, so maybe that's my solution, but I still want it on its own hard drive, just in case . Indigo L
