Doktor Avalanche

Doktor Avalanche
The only big feature request I make is wildcard searches, so I can target the projects I want to look at, or even see all of them.
e.g. * or *.* or mysong*.cwp or my*.* etc...
 
....The rest is gravy.
 Thanks!

 

bapu
On the search page for VSTs case insensitive and wildcards?

In the project scope app (search tab).
Ta.

I know that's what you wanted. I should have that On the search page for VSTs case insensitive and wildcards? is what I would like.

We used to have a 3rd party app called SonarUtils. Unfortunately the gent who wrote the program didn't update it for x64 compatability and left off using Sonar so it never got updated.

One of its features was to add editor to the Utilities menu for the tool copy function whereby you can select an audio file/s or selection thereof, within Sonar, select the appropriate program shown in the tUtility menu and the selected audio is passed to the external program for editing and return to Sonar.

It requires a registry entry but many people find it difficult to implement but of course would love the function it provides

Any takers to reverse engineer SonarUtils and release for x64 or just create a tool that can create a registry entry by taking some simple inputs from a user.

Pity he didn't put it on codeplex.

mudgel
We used to have a 3rd party app called SonarUtils. Unfortunately the gent who wrote the program didn't update it for x64 compatability and left off using Sonar so it never got updated.

One of its features was to add editor to the Utilities menu for the tool copy function whereby you can select an audio file/s or selection thereof, within Sonar, select the appropriate program shown in the tUtility menu and the selected audio is passed to the external program for editing and return to Sonar.

It requires a registry entry but many people find it difficult to implement but of course would love the function it provides

Any takers to reverse engineer SonarUtils and release for x64 or just create a tool that can create a registry entry by taking some simple inputs from a user.

I remember that.  I think I still have old copies.  THAT was a handy tool.

I've updated ProjectScope one more time this week. I like the audio file preview feature so much, I'm calling it "Project Scope Producer Edition." Pretty snappy, no? Update notes are in the OP. Thank you everyone for your comments and suggestions. If any more features get added, I'm afraid it might require some....no, I can't say it....okay, I will say it...documentation (there, I said it).
 
Note on the file scanning. It supports the "standard" filename wildcards, so if you want all the Sonar files that begin with, say, Album 1, then use Album 1*. If you want all the project files that have Album 1 somewhere in the file name, then use *Album 1*

czyky
I've updated ProjectScope one more time this week. I like the audio file preview feature so much, I'm calling it "Project Scope Producer Edition." Pretty snappy, no? Update notes are in the OP. Thank you everyone for your comments and suggestions. If any more features get added, I'm afraid it might require some....no, I can't say it....okay, I will say it...documentation (there, I said it).
 
Note on the file scanning. It supports the "standard" filename wildcards, so if you want all the Sonar files that begin with, say, Album 1, then use Album 1*. If you want all the project files that have Album 1 somewhere in the file name, then use *Album 1*

I have to say, ProjectScope is really a helpful program, thank you highly for giving it the time and work for us!
 
I have years of project files that when created and named I had no idea what I was going to do, or who might wind up playing on it with me, or start and stops that may or may not have any data in the tracks.... or even no tracks at all.
 
I've spent the last couple of days cruising old archives and it saves tons of time.
You can click through from there without having the load time in Sonar, or the drag of windows explorer load-time, and open the chosen project directly from ProjectScope.
Fast!
 
Now I get to go play with the updated version.
 
Love It!
Thank you!

czyky
Note on the file scanning. It supports the "standard" filename wildcards, so if you want all the Sonar files that begin with, say, [style="line-height: 1.8;"]Album 1, then use [style="line-height: 1.8;"]Album 1*. If you want all the project files that have [style="line-height: 1.8;"]Album 1 somewhere in the file name, then use [style="line-height: 1.8;"]*Album 1*

Interesting, I tried exactly that and could not get it to work. Will it work for *         ? (everything, the question mark is a question mark and not a wildcard ).
I was also trying to find a way to list all projects. I'll try the latest and greatest version later. Thanks!

Sylent, I appoint you head of trade show demos!  Yes, That's what ProjectScope is for! (Among other uses.) I was realizing over the last few weeks that, hey, I've got more than ten years worth of projects, and sometimes locating one of the oldies (to steal from myself or to remix for client for a fee, heehee) took a lot of time and a lot of misses. When I started counting the number of projects I have amassed, well, like you (many of you) I said to myself, there has to be a better way to track down an old Sonar project. ProjectScope is my take on that better way.
 
Now that I (and you all) have a tool to scan CWP files, in hindsight I wish I had been better about leaving notes inside my projects, but you can bet I do leave notes in them now. Using KEYWORDS actually makes tonnes of sense now. I can put a few keywords in each project and then search on them whenever the need arises.
 
Just as I typed this, I realized a good enhancement will be to have a option for ProjectScope to run through all the Sonar projects and compile a list of all available keywords that I can then print or paste to a spreadsheet or whatever for future reference! Stay tuned.
 
Since ProjectScope now has AAFF (audition audio file feature--don't forget that acronym in your dog and pony speeches at the trade shows, Sylent!), I have started another standard procedure on each of my projects:

1. bounce a minute or so of the project to a new track,
2. name the track "preview" (this causes the audio clip to get a "preview" name as well)
3. then archive and hide the track. (I don't need to see the track generally, I only want it to generate a preview audio file.)

The bounced track's corresponding audio file shows up in the ProjectScope display when I peek at that project and I can audition what is in the project post haste (that's French for toot suite). On older projects, without the preview audio, I can make use of all those archived/frozen soft-synth tracks and audition those wav files to get an idea of the project anyway.
 
Auditioning a few seconds of the audio files is way faster than loading a project completely to hear what is in it, only to find it's not the droid, er, project that I was looking for.

Ha Ha... you got it! lol
 
And I agree, it's well worth taking a minute for notes and even a short preview when I start so many "header" projects hoping to get back to them one day "soon".
 
And ....., to query a directory of projects and get a dynamic list of all the tracks that "Jerome" played bass on!!
Jerome may not care.... but it sure can make my life less cloudy. lol
 
Thank you!
 
 

You get Jerome to play bass on your tracks?
 
Now, I'm jealous.