Reaper won't let me use a 3rd Party editor?

buckman · 12-08-2018, 03:19 PM

I don't know what I am doing wrong but Reaper will not let me open audio files in Sound Forge (my editor) at all?

I have added, and removed SF about 10 times, made sure of the path etc but still nothing??

I go into 'External Editor' and select the .exe for Sound Forge, and have double checked this and it sits within Reaper.

When i click on any audio file (nothing with a weird format) just a simple 16-bit wav file, and I 'open item in Editor' - every time Reaper says :

"One or more of the external editors could not be launched" ????

I know SF is working well, and is even an editor for my Acid Pro, and it works EVERY time in Acid?

What is happening with Reaper? Its the latest version

martifingers · 12-08-2018, 03:38 PM

Interesting. Just checked that my link to Audition still worked. It didn't! I reset the preference and still not working with the same error message as you.
I will do some more testing but maybe we are not alone!

emwhy · 12-08-2018, 04:24 PM

Try this...it should work but not 100% sure.

Under Preferences/Audio/Audio Settings makes sure Close audio device when stopped is checked (it's the first option). Your problem may be that it's trying to share a drive.

buckman · 12-09-2018, 03:17 AM

Quote:

Originally Posted by martifingers

Interesting. Just checked that my link to Audition still worked. It didn't! I reset the preference and still not working with the same error message as you.
I will do some more testing but maybe we are not alone!

This was one of the main reasons I use Reaper, although its an incredble DAW, I find I am constantly tweaking with it, or getting distracted with too many options, to the point that sadly, I now use Ableton and Acid Pro, as their simplicity (to me) is their strength. So for this editor feature to not work, is another annoyance.

Hopefully its just broken and will be fixed in v6.0?
Or even better v6.0 has an overhaul, and can edit with Area Selection like PT or another Audio Editor, so that we don't have to use any 3rd party

Quote:

Originally Posted by emwhy

Under Preferences/Audio/Audio Settings makes sure Close audio device when stopped is checked (it's the first option). Your problem may be that it's trying to share a drive.

Unfortunately this doesn't work, and have always had all my files 'offline' so that i can edit in a 3rd party app, so lets wait to see if there's a fix

EvilDragon · 12-09-2018, 03:26 AM

I think the right option isn't regarding the audio device, but Preferences->Media->[x] Set media items offline when application is not active.

buckman · 12-09-2018, 03:27 AM

Quote:

Originally Posted by EvilDragon

I think the right option isn't regarding the audio device, but Preferences->Media->[x] Set media items offline when application is not active.

Yes i've tried this also, EvilDragon, with no luck..

airon · 12-09-2018, 04:02 AM

That is weird. What version of Reaper are you using ? I’ll give my setup a test run when I’m back at my rig.

buckman · 12-09-2018, 04:03 AM

Quote:

Originally Posted by airon

That is weird. What version of Reaper are you using ? I’ll give my setup a test run when I’m back at my rig.

Latest REAPER 5.963, Windows 10

EvilDragon · 12-09-2018, 05:08 AM

Hm... it works just fine over here with Wavosaur...

Actually it didn't work at first, but then I noticed that the path to Wavosaur has changed (I forgot I'd moved it elsewhere). So I entered in the new path and then it worked

This is with the latest prerelease.

martifingers · 12-09-2018, 05:18 AM

Quote:

Originally Posted by emwhy

Try this...it should work but not 100% sure.

Under Preferences/Audio/Audio Settings makes sure Close audio device when stopped is checked (it's the first option). Your problem may be that it's trying to share a drive.

Thanks for this but already checked.

buckman · 12-09-2018, 06:17 AM

Quote:

Originally Posted by EvilDragon

Hm... it works just fine over here with Wavosaur...

Actually it didn't work at first, but then I noticed that the path to Wavosaur has changed (I forgot I'd moved it elsewhere). So I entered in the new path and then it worked

This is with the latest prerelease.

I deleted and re-added many times too, just incase the path was changed or corrupt, and it still doesn't work i'm afraid. Acid Pro uses the same path to SF and that works fine and is solid every time

EvilDragon · 12-09-2018, 12:02 PM

Wish I could confirm that but I don't own Sound Forge... Can you try with Wavosaur (it's free) and see if the same thing happens?

And a random question: did you set Reaper to run as administrator?

buckman · 12-09-2018, 12:11 PM

Quote:

Originally Posted by EvilDragon

Wish I could confirm that but I don't own Sound Forge... Can you try with Wavosaur (it's free) and see if the same thing happens?

And a random question: did you set Reaper to run as administrator?

Just tried now, and set Reaper to run as administrator (which it always was) and it seems it was turned off?

Turned it on again, and Sound Forge now seems to open?!

No idea why this was turned off in a Reaper update? So check this setting, as it seems to be this.. (weird)

karbomusic · 12-09-2018, 12:31 PM

It's a SoundForge issue FYI - It's very flaky about being able to run as the logged on user (the licensing check is poorly written IME) which means you may have configured it to run as admin which will absolutely cause this behavior - if you did something like suppress/disable UAC (that's bad too) you wouldn't know it SF was launching as admin. And you should never have to run reaper as admin, that's bad unless you have no other choice.

funkycornwall · 12-09-2018, 12:39 PM

I have soundforge 9 and iZotope RX7 as external editors in REAPER and they both work fine. I can edit any wave file in either editor and then when I exit the editor it asks if I want to save the edits. I click yes and then the edited file is now the new REAPER file.

karbomusic · 12-09-2018, 02:13 PM

I have SF 11. It's been flaky perms wise since the initial install. I don't feel like debugging and describing step by step right now but I know it's SF's issue in my setup.

martifingers · 12-09-2018, 05:07 PM

Yes. running Reaper as Administrator works here too.

Thanks everyone.

airon · 12-10-2018, 02:28 PM

Just RX6 here. Win7x64, Reaper latest dev version(video stuff) x64. That’s fine.

I’d try to install SF to an unrestricted location. What about keeping SF running before calling it as an external editor?

karbomusic · 12-10-2018, 02:35 PM

Quote:

Originally Posted by airon

I’d try to install SF to an unrestricted location. What about keeping SF running before calling it as an external editor?

Correct on both accounts and the fact it can't run reliably in a protected location is what makes it an SF issue. How to do this properly was in the Windows dev docs as far a back as 2001. If SF comes up without needing admin (which it occasionally will) just leave it open and it will work.

Bribedant · 01-19-2019, 07:55 PM

I'm looking for a solution to this too on Win 7 x64. Got latest Reaper and Audition CS5.5. "Open Items In Audition" gets Audition started but no wav file opens. "Open Item COPIES In Audition" works tho. Original files are locked somehow? Reaper runs in administrator mode. All Preferences tweaks as above tested. No luck.

Update: Well actually, it kind of works. Opening an item copy i Audition and save the copy. It shows up as a new Take below the original. I can work with this.