no render target file

[taizen]

Suddenly, whenever i try to render a track, or a project Reaper tells me:
error: no render target file
The target drive/path does not exist, is unavailable, or is in use.

To solve the problem i´ve already tried the following:

- erased the reaper ini file
- erased and reinstalled the reaper program file
- typed the default render path in the preferences
- rebuild the directory of my internal and external harddrive
- repaired permissions on both drives

without success.

I also opened my projects with the 64bit version of reaper - same error message.

I found posts in several forums on the internet about this issue. But no solution,
explanation, or work around.

I´m running reaper on a Powerbook 5,3 with Snow Leopard 10.6.8

[serr]

How on Earth did you hack 10.6.8 onto a PPC G4?

Or are you running 10.6.8 as a virtual machine?

Either way, that's really impressive but it's likely related to the issues.

[taizen]

Sorry. I made a mistake. It´s a macbook pro 5,3.

[serr]

Haha OK. You were about to get quizzed!


Can you save any file? Try saving a text file or something to test. This will verify that you haven't inadvertently denied yourself permission from the volume(s) in question.

Back to Reaper. Can you still record a track?

If the issue is Reaper crashing (not OSX permission related) I don't have any experience with this scenario. But you can at least rule out OSX and go from there.

[taizen]

Ouch. In terms of hacking or programing i´m quite an idiot.

Yes, i can save a text. Everything else works fine. Also, when i create a new project in reaper everything works as usual and i can render tracks again. The problem occurs only with existing projects.

[ned]

Check the directory path in the actual render window. I've found that it will always keep the last directory path rendered instead of setting to the default paths or the project directory. Messed me up a few times when looking for rendered stuff.

[taizen]

Thanks for the hint ned. I also messed it up several times and so checked it immediately. But everything is correct there.

[ned]

Strange. Has to be a path conflict somewhere as the problem doesn't affect new projects.

Maybe delete the plist file if you didn't already do that when you reinstalled reaper.

~/Library/Preferences/com.cockos.reaper.plist

Sometimes if a plist file is corrupted it can cause the associated application to do funky things.

Another place to check is in the 'Project Settings' window in reaper. The media tab has a place to input project specific paths that may conflict with other paths specified in the global preferences. Maybe a project path you specified that doesn't exist anymore.

Maybe double check that your account actually has read/write privileges to the directory you're trying to render to. Right click the folder in the finder and get info, bottom of info window. Should show your user name in left column and the read/write privileges in the right. This is just a long shot considering new projects can write to your render directory, but worth a check just to make sure.

[serr]

I don't see an obvious red herring. You've made Reaper write a new plist file and even its ini setup files. Ruled out any OSX issues (user or otherwise).

My experience is that Reaper in OSX is the tightest run ship in the DAW world. So I want to suggest there's maybe a plugin you use causing trouble. Or maybe you stumbled across a unique scenario that actually causes trouble.

At this point I would use the Protools corrupt session procedure.
Make a new session and import the tracks from your old session one by one until you find the one that breaks it.

[taizen]

Thanks ned & serr. I checked out all your suggestions. None brought a change. I guess
the only possible solution left is the PT corrupt session procedure (17 projects - bugger).