Sanderxpander

mudgel

Sanderxpander
Am I the only that finds this whole process ridiculously complicated for an end user? Why isn't there an "add Wave Editor" dialog or something that simply lets you point to a program and give the menu item a name? I'm pretty sure most DAWs work that way.

1. I don't know of any other daws that let you pass internal audio to an external editor and save it back.

2. As per Noel's post #12 in the following thread the feature is undocumented and unsupported.
3. There was a 3rd party utility that was called Sonar Utils, that used to do what you ask and more. Unfortunately it was never updated to work for Sonar x64 so we lost the feature. The gent that developed it left off using Sonar.

1. I know for a fact at least Ableton and Logic do this and simply let you browse for your preferred wave editor. Not sure about other DAWs but it seems a pretty common feature to me.
2. If undocumented and unsupported perhaps they need to take down this document
https://www.cakewalk.com/...e-to-SONARs-Tools-menu
from the support site. Seems pretty bad policy to me to direct users to hack their registry.
3. I know it's harsh but I don't think I should need to care about why they haven't developed this. It has been in this state for years. Whatever excuse they had has long since evaporated. I really hope this will be part of an oncoming update, it isn't exactly something complicated.

It seems from years past that programs like Sound Forge would automatically be available in Sonar's Tools Menu.

Whatever that process was developers are no longer doing it leaving us to have to do it manually. As Noël said, it predates his work at Sonar. Clearly we're talking about legacy code unfamiliar to the current development crew.

mcdonalk
I am still working the issue with Lynx, providing daily reports on observations that they request.

All the best, I hope you get it sorted.

Automatic would be great. But since they already know exactly which registry keys to create it should be pretty easy to create a simple "browse for editor" mini app that adds those keys. That has very little to do with legacy code.

I mean the current crew of developers who create programs like Sound Forge and that their code is legacy as they are no longer making their tools available in Sonar as they used to.

Read all of Noel's comments in that linked thread. That's what he said.

I don't really have a dog in this fight. I simply started in an effort to help folks put in the correct registry entries. And pointing to additional info supplied by Noel.
Perhaps you should put in a feature request.

I'm glad for all your efforts, they helped me, thanks!
I'm just somewhat peeved that they are necessary to begin with ;)
Sonar is simply lagging a bit behind the competition in this respect. It's ahead in others, so meh.

sound forge (pc version) hasn't changed for quite a few years now... i read the linked thread, noels comments, he doesn't say anything about "programs like Sound Forge and that their code is legacy as they are no longer making their tools available in Sonar as they used to" not even close...? but at least he shares the registry hacks needed to make external apps work (thanks noel!)

pwalpwal
sound forge (pc version) hasn't changed for quite a few years now... i read the linked thread, noels comments, he doesn't say anything about "programs like Sound Forge and that their code is legacy as they are no longer making their tools available in Sonar as they used to" not even close...? but at least he shares the registry hacks needed to make external apps work (thanks noel!)

I didn't quote Noël. I said "that" or "what" in connection with what Noël said. I was paraphrasing.
You need to read the linked thread entirely and you will see that Noël talked about code that existed before he was at Cakewalk and a time when Sound Forge automatically installed the link for the Tools Menu. I even remember when Sound Forge did that. Probably as long ago as SF 6 or 7.

2 of Noel's posts from that thread that form the basis of my comments.

Quote from post #16

Noël Borthwick IIRC it was to solve the converse problem. When I did plugin manager integration I needed it to be non modal and added a bunch of new items to the tool options like the parent window etc.
Some of the tools menu settings have been around a *long* time - since the pro audio days or earlier, and dates back before my time at Cakewalk.

Quote from post #17

Noël Borthwick
Dan, Its cool that it works now. Some tools require the current directory to be set.
You might want to post your reg settings for other users of RX. Also you could let Izotope know in case they want to self register this when RX installs. Sound Forge used to do this years ago.

If I understand you correctly, this was something SoundForge developers baked into their installation? So Sonar has basically never offered any easy adding of a wave editor through their own procedure?

Sanderxpander
If I understand you correctly, this was something SoundForge developers baked into their installation? So Sonar has basically never offered any easy adding of a wave editor through their own procedure?

I think more like Sonar provided the hook and when SF was registered as your default wave editor it automatically registered in the menu. That's only a vague memory though. Clearly the hook is in Sonar but I'm no computer guru so only have a very superficial understanding of what needs to happen from a programming perspective.

Yeah, it was a nice method. Sonar has the capability to read in the registry hook as long as it's there. It was basically something that people making editors would support, and they'd just appear in Sonar. But I think like anything non-standardised, support for it has waned over the years.
 
To be fair to Cakewalk, this dates back at least to 1996, and this kind of functionality didn't appear in other daws for years. Several still don't do anything like it.