![]() ![]() And since it would just be some pre-sets that could be modified or discarded, there would be no loss of the flexibility and customizability that is unique to Reaper. This should not be that hard to do, and would really assist long-time PT users in transitioning to Reaper. What I and other commenters have wanted to see, is a set of pre-sets that, when implemented, make Reaper behave much like Pro Tools with pretty much the same set of commands. If all you want to do is finish a particular project, learning a whole new DAW that operates very differently is probably not on your “to do” list. If you are just trying to pick up Reaper and use it, this can be a liability–you need to spend time learning how to make it work for you, and not just a little time, it really is a major re-learning curve. I think a lot of this “why can’t Reaper work like Pro Tools” is due to the fact that Pro Tools has a set way of working, whereas Reaper is built to be very flexible–you often can find a number of different ways to do something.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |