Hi Devs
Reaper is already being used for some pretty big games in the industry now but with a few relatively tiny additions and the inclusion of PIPs as a big feature (which it really is!) it could become the "go to DAW" for games and linear media for quite a large majority.
I'm not saying it has all the post features of Nuendo (the DAW I came from) but enough to persuade most people to give reaper a try over Nuendo.
I already meet audio guys down here in the south of the UK and London that are working on big titles and using reaper so it's gaining a lot of traction there for sure but could gain more easily with some smallish additions.
The recent Wwise integration with Nuendo has got some of the reaper game guys to "come out the woodwork" and get excited about having these features in reaper
See the thread here if you want have a look at what's being said already.
http://forum.cockos.com/showthread.p...62#post1488962
I'm going to be working with a middleware audio dev soon on integrating reaper into it and will mention who when we have an idea of how much work it will be.
There maybe a few API requests from these sessions but I think reaper has quite a lot of it's back end open already right to allow hooking in things like opening audio files directly in the project they came from (based on the project's name being in the broadcast wav header?)
Things like that.
---------------------
Also, again.. please please, look at adding a few things to PIPs in reaper 5! They are massively useful to us game audio folk and linear media too (not to mention normal music too)
Below is a list of things that could help!
PIP things I'd like to see improved (in order of potential ease of implementation) would be:
-An option to have any new PIPS "take" the project settings from the master PIP they were created in. (this one would really help guys)
-An option to select a bunch of tracks/items and turn them into a PIP. (we can kind of do it but it's messy)
-a button on PIP items to temporarily "freeze"/commit a PIP to a physical disk file (instead of ram) so that you can load a big project without it having to load all the other PIPs first for the RAM renders.
-The other thing would be an option to "expand" a pip into a visible set of tracks and items into the same master project like cubase's folder system does now. OR, have PIPS come up in a secondary arrange page!
-The following bug just got brought to my attention too and severely limits the use of PIPs.
Currently, all imported projects always get turned into copies so there's no way to affect the original project once turned into a PIP. It always gets turned into a new copy (in the project directory) with the suffix "-imported".
Hope we can get that fixed as it would be very powerful for many uses in music and post production/sound design/games.