Jump to content

Jim Hurley

Members
  • Content Count

    107
  • Joined

  • Last visited

  • Days Won

    1

Jim Hurley last won the day on March 1 2019

Jim Hurley had the most liked content!

Community Reputation

53 Excellent

About Jim Hurley

  • Birthday 03/15/1952

Recent Profile Visitors

778 profile views
  1. 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.
  2. 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)
  3. 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!!
  4. 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.
  5. The same thing will happen if you open a sample from Windows File Explorer, each sample gets its own editor. That's how Cakewalk keeps track of which sample you are working on -- it is by window. In that SF window you can open another sample from the audio data folder of your project, and it will open in the SF Workspace.
  6. Yes, the UFS file is a file system much like Acronis TIB. It would be nice to be able to unpack them and replace samples, scripts, etc.
  7. I used to have an Event ASP 6 for a long time. Dome tweeter. I liked it a lot, but I eventually added a subwoofer. Last year I got an Adam A8X. Ribbon. It has far better bass and high end, but I think it really needs a midrange driver to be perfect. Still I like it a lot better and the high end is excellent. It definitely does not need a subwoofer. I can feel the air from the ports 10 feet away. I like having a power switch on the front. It is easy to adjust the curves. My ears are not so good anymore (I wonder why?), so take that into account. I would not call them harsh at all. It does require a few days of break-in, maybe longer. I fed it pink noise for a week with both speakers out-of-phase facing one another.
  8. I have been thinking about this a bit, and the better tool is Sysinternals Process Explorer. It will show strings in the image of a file as well as in memory and allow search for strings. For example, here is the memory image string search for 'tutor' showing an intriguing entry:
  9. Yes, these have appeared here and there in root folders at various times. I've seen them in other folders, too. It is related to the VST scan, I think. I think they have always been empty, but my memory is faulty these days... I have my TEMP system environment folder set to C:\Temp and the temporary file folder in Sound Forge prefs set to D:\Temp and I've seen them in C and D root drive as well as C:\Program Files\Sound Forge. These past few days I've spent many hours rummaging through Procmon logs of Sound Forge startup and tutorial processing so I am getting accustomed to it more. I attempted to figure out when this started - I know it happened in SF 12, 14 and 15. I have the SF 11 installer as well as many earlier ones, maybe back to the Sonic Foundry days (I never through anything out, drives are cheaper than my time), which is the last version when SF was owned by Sony. I tried to install that, but it required an installation of early DOTNET installations to proceed, so I quit at that point. Very Off Topic. It is interesting to follow the history of these types of tools. I bought Cool Edit 95 and Sonic Foundry Sound Forge when they were introduced. I liked Cool Edit more and purchased a 'LifeTime license' from Syntrillium. A short time later, maybe in CooEdit 2000 or so, Syntrillium sold Cool Edit to Adobe and it became Audition. I guess that was the end of life, because my license no longer worked. Sonic Foundry was sold to Sony and now Magix. Spectral Layers was owned by Magix, but now Steinberg. Confusing. And if you want to get support you have to upgrade and switch to the new owner.
  10. By the way, I checked this behavior in Sound Forge 14 and 15 in multiple machines and in Sound Forge 12 on my laptop. They all do the same thing. Kevin's Kludge outlined above works well enough for me. My posting on Magix probably will go nowhere.
  11. I don't see that sort of scan display. Mine looks like this:
  12. Sysinternals is full of useful debug aids. One thing I like to use for string search is PEStudio. It is an older 32-bit app and it sometimes crashes on big files, but it has so many useful features related to security and privacy. For example. if I want to see what Protein(*).dll does:
  13. I think that scan is just looking for new and changed plug-ins. I think the 'grovel' is when each plug-in is queried of all it 'can dos' and stuff like that. Usually that makes lots of system calls, registry changes, etc. There will always need to be a new/changed scan, but not the initial 'grovel' type. This is my assumption, I have no direct knowledge.
  14. Here's my take on the title. I made this about 9 years ago.
  15. For the last several releases, Sound Forge has opened with an optional tutorial window. You can disable the view of that, but you can't disable the creation at startup of the tutorials, as far as I can see. What happens behind the scenes is that 'sftutor.dll' in the install folder opens the install file 'forge.tut' which is basically a 7-zip archive of a web page. Then sftutor extracts that and then opens a 'show me' function that uses internet explorer to do the tutorial which can highlight parts of Sound Forge as it proceeds. This tutorial is deleted when you close Sound Forge. At least with my settings that happens, Even though my temp file is set to 'D:\Temp' in Sound Forge, the tutorials will be build in 'C:\Temp', or whatever the environment TEMP variable is pointing to. I have tried to disable this in several ways. The first was by using Sysinternal Suite 'Procmon' tool to examine the system calls during this time. I did not see any obvious Registry calls that might bypass these steps. Next I tried renaming 'forge.tut'. That will generate a startup error, but if you ignore it, it may work, as Sound Forge appears to open OK. But I don't like that. Next I tried to delete sftutor.dll but that throws an installation error. I used to have a 'dummy.dll' lying around for this purpose - rename it to sftutor.dll and nothing will happen. But I have not used that in years and I can't find it anymore. So I gave up and just let it be. The tutorial comprises 297 Files in 8 Folders, so it isn't insignificant. Has anyone else been bothered by this enough to do something about it? My post at Magix forum: https://www.magix.info/us/forum/sound-forge-pro-15-builds-tutorials-can-this-be-disabled--1270691/
×
×
  • Create New...