Jim Hurley

That probably just uses the format: CHKDSK /f <drive> I use an administrative prompt: CHKDSK /f /r /b <drive> /f - fix simple errors /r - locate and relocate bad sectors in user files /b - find bad clusters in unused areas of the drive

It's a solid state GPT drive formatted NTFS.

Today I was running a CHKDSK on my D drive which is where I have all my music projects and paths in Cakewalk. While waiting for it to complete, I opened Cakewalk without thinking and it automatically created all these folders in my AppData folder on C because D was unmounted during the scan. Realizing my mistake I changed all the paths in preferences, reset my project folders, reset the default templates, etc. It took a while. Quite a while. Maybe a warning before making all these changes would be helpful? EDIT: I use in an admin shell the command: "CHKDSK /F /R /B D:" to find all disk errors in files and unused space. This unmounts D

How much time does it take to keep 4000 VST up-to-date? With only a thousand I seem to get updates several times a week. Mostly those these updates seem to be for Apple machines mostly.

If you only had one VST instrument and one VST effect what would they be? I am an experimenter, so it is somewhat easy: Reaktor would be my VST (and it could be used as an effect as well, but not here), Kore would be my effects instrument. That also cheats, because Kore can load anything. Without cheating, I would pick Falcon as instrument and Crusher-X as effect. Bidule and MSoundFactory could also appear as one of these alternates. These are all very general plug-ins.

I think the vast majority of mine are Melda and NI VSTs.

I retired in 1999, did a bunch of music, but now I just seem to collect VSTs! I do have some big plans to get back again soon, but other hobbies have taken over my time (like painting).

Nahimic, Sonic, and Avolute stuff are frequently installed with RealTek audio driver updates. I make a note to myself to eliminate these things and disable the services they start.

It also may be due to something that altered the environment path, perhaps. Not sure, though, but once, long ago, I saw adding one of the MS development tools increased the PATH by adding a lot of the development folders and that made a phenomenal slowdown to some scanning software tools. So if you made some changes that added folders to the PATH, maybe that will help narrow things down.

Installed OK

I have not heard back from the developers on this topic. I also find that marking regions seems to cause instant crashes very often. So I no longer use version 15. I will update it as new ones come out, but I find SF14 to be a superior product.

I think this happened to me once and I think it was due to a Broadcast Wave file having a timestamp embedded. The fix is to disable that.

I tend to read the manuals and release notes. I didn't find any release notes in the download, nor mention of this in the What's new sections (For SF 15 or 14)

Very interesting and something I had not known. I had seen these strings in the various viewer tools we talked about above and knew they could be altered somehow, but I never read about the hidden Internal preferences. I changed a few things for both SF 14 and 15 (It took some sets and resets and restarts to make everything consistent) and now I can get the behavior you saw in SF 14 and also SF 15. It seems that you must press Apply before OK to make them take. And system restarts seem to help. There are many ways to invoke SF and there are some differences that I have to resolve. You can invoke from a file type or shell command, etc. Thanks!!

The behavior I see is different. Both Sound Forge 14 and 15 behave the same in Windows file opening and in loading via Cakewalk tools menu. In both cases, new windows open when SF is invoked externally. It is only by loading a file inside SF14 or 15 via the open file menu that I can load the file into the current SF workspace. I can also load an external file into an SF workspace if I drag a file in Windows Explorer to the Sound Forge menu bar (but not dragging into the workspace which invokes Mix/Replace). I have Sound Forge Pro 14 64-bit build 130 and Sound Forge Pro 15 64-bit build 27. I don't know how to achieve the behavior you wish. I would like it to work like that also. Both have similar registry open shell command entries with a cryptic string passed.