Reaper won't initialize

[nanninga0]

I can't get reaper to initialize in Windows 10 when I try to start it. I tried starting it with and without holding the shift key. I tried uninstalling and reinstalling the program. It all started after I downloaded AISO4All (I'm not really sure what that is, but a forum said to download it, so I did). I'm clueless as to how to set up my MIDI drivers and I must have really screwed it up. In the upper right hand corner, the Reaper program says "audio device closed", whatever that means. How can I open an audio device if the program won't initialize and let me in? I don't even know how to open or close an audio device.

This is all very new to me. I've had Reaper for three days. I used to used Voyetra Record Producer until my computer crashed and I lost that program forever. So far, I have not been able to do a thing with Reaper.

What should I do?

[jrk]

When you say reaper won't initialise, what exactly do you mean? I gather the main window is displayed (at least enough to say "audio device closed"). Has the splash "screen" appeared and gone away again? Have you tried clicking up there where it says "audio device closed"?

Do check out the excellent user guide http://reaper.fm/userguide.php

[nanninga0]

All I get is that opening screen with a circle going around and around and then windows saying that it cannot open the program. When windows looks for a solution, it finds nothing and closes the program. At the top of the screen, it says "not responding"

[nanninga0]

This is a link to what the screen looks like when it freezes before initializing:

https://app.box.com/s/sqlmmgofxcupcfy9en9byuf4e4yddplj

[nanninga0]

I tried opening with cntrl-shift and that didn't work either. I cannot click on "audio device closed" because it will not let me click on anything (except the "X" in the corner to close the program). Instead of a curser, I have a little blue circle that just keeps revolving. When I close it, windows says the program is not responding.

[prezbass]

This could be most anything- let's start with some stats on your computer- CPU type, RAM, hard disk(s) and sizes, operating system, etc.

We'll figure this out.

[karbomusic]

Yea but it's hung, crashing or deadlocked. I'd first make a backup copy of, then delete reaper.ini and restart REAPER since the more benign start options are failing.

[nanninga0]

I have a Samsung laptop

Intel Core i3-3227u CPU @ 1.90 GHz
4.00 GB RAM (3.71 usable)
64-bit operating system, x64-based processor

Using Windows 10

85.8 gb free on hard drive

[nanninga0]

I have no idea how to copy or delete reaper.ini.

[nanninga0]

As a point of reference, I was able to open Reaper before I downloaded AISO4All. When I could open Reaper, the first thing I tried to do was open an rpp file I had created in Voyetra Record producer. Reaper said it couldn't parse the data, so it wouldn't open it. That is the full extent of my experience with Reaper.

[jrk]

reaper.ini might be in C:\Users\YOUR USER NAME\AppData\Roaming\REAPER

( \REAPERx64 maybe?)

Maybe try renaming reaper.ini (so you can get it back if you want to - Reaper will create a default ini file, I think) and try starting it again.

[xpander]

Originally Posted by nanninga0

When I could open Reaper, the first thing I tried to do was open an rpp file I had created in Voyetra Record producer. Reaper said it couldn't parse the data, so it wouldn't open it..

While the file extension is the same (.rpp), I don't think Voyetra and Reaper project files are compatible at all. I'd imagine you would first have to convert the Voyetra projects to some common format, maybe export them as wavs, and then load them into Reaper.

[nanninga0]

If Reaper cannot open these Voyetra rpp files, then I am screwed. I cannot convert them to wav or mp3 if I cannot open them. Voyetra Record Producer no longer exists, was never updated or supported beyond Windows XP and cannot be reloaded onto a machine because it requires approval from Voyetra, which no longer exists. So when my computer crashed last week, I lost Voyetra Record Producer forever. Does anyone know of a workaround?

Of course, that may be a moot issue if I cannot open Reaper anyway. This 60 day trial period is not going well at all.

[karbomusic]

Originally Posted by nanninga0

If Reaper cannot open these Voyetra rpp files, then I am screwed. I cannot convert them to wav or mp3 if I cannot open them. Voyetra Record Producer no longer exists, was never updated or supported beyond Windows XP and cannot be reloaded onto a machine because it requires approval from Voyetra, which no longer exists. So when my computer crashed last week, I lost Voyetra Record Producer forever. Does anyone know of a workaround?

Of course, that may be a moot issue if I cannot open Reaper anyway. This 60 day trial period is not going well at all.

I think there is a conflation here that because Voyetra used .RPP for it's projects (if that is the case), that this means Reaper, which also uses .RPP for it's project can magically work with them. This is not the case, they are two completely separate applications that just happen to use the same file extension. Any application gets to choose what it wants to use for it's own file extension(s), sometimes those collide but the only similarity is that name collision.

[jrk]

Originally Posted by nanninga0

This 60 day trial period is not going well at all.

In fairness, this isn't 100% a reaper issue - Of course reaper should handle being given the wrong kind of project file more gracefully than this. (If this is what's mucked things up, that is). But there's no real reason to expect reaper to open your old project, from some other program, just because the file extension is the same.

There's some folks out there on the interwebs claiming to have Voyetra Record producer and to have sucessfully activated it with some registry hack (since it's no longer possible to authorise it properly). Sounds dodgy to me, but you might look into that.

[nanninga0]

Originally Posted by jrk

reaper.ini might be in C:\Users\YOUR USER NAME\AppData\Roaming\REAPER

( \REAPERx64 maybe?)

Maybe try renaming reaper.ini (so you can get it back if you want to - Reaper will create a default ini file, I think) and try starting it again.

I went to the AppData\roaming\reaper and did not find any ini file.
I went to \reaperx64 and found no ini file
I did a search on my entire C drive and found no reaper.ini file

[karbomusic]

Originally Posted by nanninga0

I can't get reaper to initializeIt all started after I downloaded AISO4All (I'm not really sure what that is, but a forum said to download it, so I did). I'm clueless as to how to set up my MIDI drivers and I must have really screwed it up. In the upper right hand corner, the Reaper program says "audio device closed", whatever that means. How can I open an audio device if the program won't initialize and let me in? I don't even know how to open or close an audio device.

This is all very new to me. I've had Reaper for three days. I used to used Voyetra Record Producer until my computer crashed and I lost that program forever. So far, I have not been able to do a thing with Reaper.

What should I do?

Based on the bold parts and using REAPER in general, I'd download the REAPER manual and/or start here: https://www.reaper.fm/videos.php

Sit back, relax a little, and get some of the basics under your belt which will make life better, it just won't happen in 30 seconds so a tiny bit of patience will go a long way. I empathize with wanting to hit the ground running but me thinks a little prep work will really help.

[nanninga0]

Originally Posted by jrk

In fairness, this isn't 100% a reaper issue - Of course reaper should handle being given the wrong kind of project file more gracefully than this. (If this is what's mucked things up, that is). But there's no real reason to expect reaper to open your old project, from some other program, just because the file extension is the same.

There's some folks out there on the interwebs claiming to have Voyetra Record producer and to have sucessfully activated it with some registry hack (since it's no longer possible to authorise it properly). Sounds dodgy to me, but you might look into that.

Yes, I did that registry hack and the program worked just fine for years. But when I had to reset my windows after it crashed, the program was lost from my program files. You can only do the registry hack if the program was already successfully loaded in the past. If you try to reload the program, the hack doesn't work.

[jrk]

Originally Posted by nanninga0

I did a search on my entire C drive and found no reaper.ini file

You may need to tell windows to show hidden files (I know, but there you go) before you can see it?

Personally, I find windows search unhelpful often. Which is why I have grepwin. That'll find anything.
(If you don't mind waiting...)

[karbomusic]

Originally Posted by jrk

You may need to tell windows to show hidden files (I know, but there you go) before you can see it?

Personally, I find windows search unhelpful often. Which is why I have grepwin. That'll find anything.

There should be no reason to search if he can actually open Reaper.... Options > Show reaper resource path...

[jrk]

Originally Posted by karbomusic

There should be no reason to search if he can actually open Reaper.... Options > Show reaper resource path...

Ha. Yes, but the OP can't. That's where we came in.

[nanninga0]

Originally Posted by karbomusic

Based on the bold parts and using REAPER in general, I'd download the REAPER manual and/or start here: https://www.reaper.fm/videos.php

Sit back, relax a little, and get some of the basics under your belt which will make life better, it just won't happen in 30 seconds so a tiny bit of patience will go a long way. I empathize with wanting to hit the ground running but me thinks a little prep work will really help.

I downloaded the manual right after loading the program and can find nothing in it to tell me how to do anything if the program will not open other than saying to try opening while holding shift or holding cntrl-shift. I did what the manual said in this regard and still nothing.

I also watched about 4 introductory videos on youtube before opening the program. That's where I got the idea to download VISO4all.

I can patiently sit in front of a program which refuses to load all day, but that gets me nowhere. I appreciate the time you took to provide advice, but how do I prep for my current situation?

[nanninga0]

Originally Posted by jrk

You may need to tell windows to show hidden files (I know, but there you go) before you can see it?

Personally, I find windows search unhelpful often. Which is why I have grepwin. That'll find anything.
(If you don't mind waiting...)

I told windows to show hidden files and still could not find it.

[karbomusic]

Originally Posted by nanninga0

I downloaded the manual right after loading the program and can find nothing in it to tell me how to do anything if the program will not open other than saying to try opening while holding shift or holding cntrl-shift. I did what the manual said in this regard and still nothing.

I also watched about 4 introductory videos on youtube before opening the program. That's where I got the idea to download VISO4all.

I can patiently sit in front of a program which refuses to load all day, but that gets me nowhere. I appreciate the time you took to provide advice, but how do I prep for my current situation?

I'm not completely sure where you are stuck at the moment, apologies. Just to clear that up, can you actually open Reaper right now (by clicking the shortcut, not a project file)?

Once I'm clear, we'll get something rolling in some fashion - my guess is that if you can't open Reaper, there is a problem with ASIO4ALL or something where it initializes the driver (which occurs right when Reaper starts). If that is the case, we may want to find the ini and delete it.

Secondly, you can, just install a portable version to some folder of your choice, then work from that which will bypass any current issues with the current install (hopefully). To install portable, run the installer, check the Portable install checkbox, create/browse to the folder you want it to install to etc.

[jrk]

Originally Posted by nanninga0

but how do I prep for my current situation?

It's a real pain isn't it?
The troubleshooting FAQ is a good place to start. https://forum.cockos.com/showthread.php?t=23297

[karbomusic]

Originally Posted by nanninga0

I told windows to show hidden files and still could not find it.

It isn't a hidden file. If this is a regular install in "Program files", I don't think the OS indexes there for searches, generally that is a good thing. Assuming you installed 64 bit there is one place it is most likely to reside...


C:\Users\YOURUSERNAME\AppData\Roaming\REAPER <== this is likely the one you care about - check here first.


**** It is possible that your OS is configured (by default) to hide extensions aka .INI - if that is the case, and you find the path above, you may see a file that is just called REAPER in the folder because .ini at the isn't visible.

[nanninga0]

Thanks everyone. I finally got back into reaper.

[jrk]

Excellent - hope it works out.

[Littlemitch]

How did you do at the end ??