Not really played enough with it, but it works with VoiceOver out of the box. I reckon you get better plugins with tools or Logic though and Reaper doesn't have loads of instruments like the other 2 but I did do some work in it and if you have some plugins that you like that are in VST format, I've got Waves Ren Max bundle, that will help. As I say though, not played with it for about a year.
On 5/30/15, Poppa Bear <[email protected]> wrote: > On reaper are any additional programs needed to run it, or is it compatible > out of the box with Voice Over? > > > > From: [email protected] [mailto:[email protected]] On Behalf > Of TheOreoMonster > Sent: Saturday, May 30, 2015 10:37 AM > To: [email protected] > Subject: Re: accessibility comparison chart > > > > I think what would be more useful is a table with the list of things and a > link to steps to accomplish those tasks in each DAW. This will give anyone > the ability to judge for themselves which workflow works better. But owing > to what Scott said, a simple yes no table would be a pain for anyone to > undertake, can you imagine documenting steps for doing each things in each > DAW. Also i think blog pretty much sums up my thought on the current scene > as it relates to access and DAW. > https://reaperaccess.com/current-accessible-daws-for-blind-audio-recording-engineers/ > > > > > > > > On May 30, 2015, at 10:24 AM, Gary Readfern-Gray > <[email protected]> wrote: > > > > Ok, cards on the table, In my opinion Pro Tools is so far ahead in the > accessibility stakes, it's not even funny. So, why have I switched to > Logic from PT? > > Truth be known , I like them both, I think Logic's workflow is cool, > and just fits my style better like for example being able to work with > regions with VoiceOver, which you can't do with PT . And I like > Logic's virtual drummer, that's way cool. and a bunch of other things. > > But Anyway, it's not just about the accessibility. I have a little > sight which helps me in a few cases in both Logic and P T. It's also > about things like price. Not everyone can affords tools or for that > matter Logic. > > So, after all that waffle what am I saying here? Different strokes for > different folks and I for one, think it would be helpful to have a doc > showing what's accessible in each DAW and what isn't, not necessarily > a comparison between the two. > > For example, sends are not yet accessible in Logic, but wait, track > stacks offer much of the functionality of sends and they are > accessible. > > Just my take on things. > > On 5/30/15, Scott Chesworth <[email protected]> wrote: > > > > With both sides of this fence being a work in progress though, > everyone's opinion of accessibility is a subjective thing, so I'm not > sure a Yes and No answers type table would be accepted as accurate > across the board. For most people who're actually using either of > these options to get stuff done, about the best definition of > accessible in the land of the DAW is "I can get stuff done using it". > A lot of the workarounds and workflows that the Logic folks are using > would likely leave a lot of the PT users shaking their head, and that > goes both ways. See, I'm already giving away my biased opinion by > putting the options in that order in the last sentence lol. > > Not saying it's a bad idea as such, just that I think it'd be a > difficult thing to compose and I don't envy the poor sucker who takes > on the task. :) > > On 5/30/15, Jean-Philippe Rykiel <[email protected]> wrote: > > > > Yep, blame it on my French English. > JP > > http://www.jprykiel.com > http://soundcloud.com/ryksounet > http://twitter.com/ryksounet > http://facebook.com/jeanphilipperykiel > > Le 30/05/2015 11:19, Christopher-Mark Gilland a écrit : > > > > First off, I think this would honestly render much better as a table > than it would as a chart. > > Chris. > > ----- Original Message ----- From: "Jean-Philippe Rykiel" > <[email protected]> > To: <[email protected]>; <[email protected]> > Sent: Saturday, May 30, 2015 5:13 AM > Subject: accessibility comparison chart > > > > > > Hi all. > excuse me for posting to both lists, It is something I never do, but > you will obviously understand why. > I wonder, For users who have a hard time choosing between ProTools > and logic, if It would be possible to set up an accessibility > comparison chart between both Daws, including categories like MIDI, > editing, effects, synths and so on. > Of course, the hard part is that it would have to be updated as > Applications evolve. > Of course 2, everyone knows that they are not real competitors as > ProTools became a Must have for compatibility with pro studios, and > Logic didn't, but this might not be a choice criteria for all, and so > I think this comparison remains valuable. > It is something I would have gladly done, but I'm using neither of > them for the moment, happy with sonar, but knowing I will have to > change some day. > What do you say? > Best, > JPR > > -- > > http://www.jprykiel.com > http://soundcloud.com/ryksounet > http://twitter.com/ryksounet > http://facebook.com/jeanphilipperykiel > > -- > You received this message because you are subscribed to the Google > Groups "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, > send an email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
