Jump to content

Jim Hurley

Members
  • Content Count

    70
  • 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

39 Excellent

About Jim Hurley

  • Birthday 03/15/1952

Recent Profile Visitors

598 profile views
  1. Intel® Turbo Boost Max Technology 3.0 was introduced into Windows 10 recently, it is also called something like 'Favored Cores'. It can be read about here: https://www.intel.com/content/www/us/en/architecture-and-technology/turbo-boost/turbo-boost-max-technology.html I was wondering what might be the impact of that on Cakewalk and the selection of the thread scheduling models. For those who don't know, this is only available on certain models of Intel processors. It adds a driver to Windows and adds some firmware support to the chip's p-code to support thread movement to different cores without OS involvement. Supposedly it will help thermals and help prevent thermal limiting. Or that is how I read it. My naive thoughts are that moving a process from one core to another will wreak havoc to the cache memory. I ran some tests using a high load Reaktor ensemble running standalone outside a DAW and saw this: (R6-CPU-all-cores.png). Notice the spread in load across all cores. There is no evidence that any core is stressed. Probably that is due to the low sampling rate or averaging of Task Manager. Then I set affinity to use only Core 7: (Reaktor-set-affinity.png). And then I ran again and see Core 7 showing the load Reaktor reports: (Reaktor-using-only-one-core.png). I don't know if or how this could be disabled and it does make measuring and testing loads a bit tricky. Does anyone know more about this new feature and what it means for us in audio?
  2. I see a different policy page (Win 10 1903 {Version 10.0.18362.207}). It seems to say that policy is no longer supported. (yellow highlight).
  3. Here are some graphics - an icon and a track PNG Massive X.ico
  4. I have 'Hide related VST2 plugins' set, and I have MeldaProduction VST2 and VST3 plugins installed. Cakewalk 2019.03 shows both plugins in the plugin list. Is there something else needed to hide them?
  5. The external drive approach will work until it doesn't. Just like the MAC address approach. Some day Microsoft may change how external drives are handled and the licensing approach may break. I am not so opposed to licensing arrangements, what I don't like is that Waves tech support refused to admit that they have a bug and were willing to fix it. Probably it will be rare that people only have a single network interface. And that is WiFi. And that they enable random hardware MAC assignment. And that they buy Waves and use quick install. But it is quite common that Microsoft changes things with every patch Tuesday update, particularly with new security features. They might do something similar with Random MAC assignment and make removable drives address themselves uniquely upon install - or whatever.
  6. Not having used any Waves software before, I adopted the 'Easy Install' option. Or whatever it was called. Usually I perform a custom install and choose all my own settings, but I guess I'm getting tired of doing that. Besides, I heard so many people here talk about Waves. I saw there were other options, like using a USB stick, etc., but didn't want to keep another iLok-like device connected. I was surprised at the amount of stuff that got installed just to license a $29 Vocoder. Based on the last few days reparte with their support I am not impressed by their efforts to help or listen when given real advice. They don't seem to be aware that this MAC option even exists. I don't think they even believe what I wrote to help them figure this out - the advice they were giving was not very good debugging or troubleshooting practice. Looking into the Hardware randomization feature, I am not sure it is a good thing to use on a desktop computer. Originally, I just checked it off as a security thing and thought it might help avoid tracking issues. But I think this is only useful for smartphones in a public environment now that I've actually thought about what it means. Most tracking on my desktop would be via cookies or my IP address, not a MAC address. And my home router saves all MAC addresses in a table, so, by now, that table must be very full. So I cleared my home router's device list and turned this feature Off. I have a few other vocoders, so I won't miss this one. And I doubt I'll be buying any more such bargains. They have an 'all sales final' policy, but I spent so much time on this already, I just want to forget I even heard about Waves.
  7. Yes I am sure. Their Tech support told me: "Because Waves licenses are linked to the network adapters, it's best to temporarily enable the ethernet adapter just for the chance that Waves Central recognized your computer by it. If it did, and Waves Central will recognize the computer again, you'll be able to move the licenses back to the License Cloud and then disable the adapter. Once disabled, Waves Central will recognize your current adapter and you'll be able to activate the license again to it." They seemed to think that Waves had used my disabled Ethernet adapter as a MAC address and not my daily-changing WiFi MAC address. This setting is in Windows Settings under WiFi - Random Hardware Addresses. I verified this using 'ipconfig /all' on two consecutive days: ------------------------ Yesterday: Wireless LAN adapter Wi-Fi: Description . . . . . . . . . . . : Intel(R) Wireless-AC 9560 160MHz Physical Address. . . . . . . . . : 6E-D2-E3-26-72-30 Today: Wireless LAN adapter Wi-Fi: Description . . . . . . . . . . . : Intel(R) Wireless-AC 9560 160MHz Physical Address. . . . . . . . . : 9A-A1-6C-C7-AF-06 -----------------------------
  8. I bought the vocoder - Morphoder. But it doesn't work for me. The Waves Central licensing software uses a network MAC address to identify your computer. The only network MAC address I have is my motherboard WiFi and Windows is set up to assign random MAC addresses on WiFi. So I bought it, it worked the first time, but never again. I could not convince tech support that they have a bug.
  9. SF12 is very stable and the only program I have besides Cakewalk that can read and edit WAVE 64 files. Normal Wave files have a 32-bit size limit which makes very long wave files difficult to edit.
  10. Lots of great suggestions. Blue Cat's Chainer and similar things like Melda's MXXX and SoundToy's racks are great ways to combine a lot of your stuff into creative setups. If you have Reaktor, you could get MoleKular, which is a bit expensive, but it includes stuff made by Zynaptiq's Denis Goekdag from the older Kore Deep series.
  11. Like Lynn, I bought SF12 Suite a bit ago and had previous Sound Forge versions since its Sonic Foundry origins then through Sony and now Magix. I didn't think SF12 was all that much better than previous versions, but it was nice to get 64-bit support. If the upgrade were $50 or so, I'd buy it just to show support. I think I'll probably skip this one.
  12. There are a lot of things I like about Windows 10, But the Microsoft store and it's apps are not one of them. I just use it like I used Windows 7 - just the desktop, using Open-Shell to get back the old Start menu. The kernel is much more responsive. But the update process seems to be skyrocketing out of control, just about every recent update was a catastrophe for some people.
  13. This is getting de-railed due to semantics issues and the main idea is being missed by my bad title. The title is rhetorical, it isn't a real question. After a lot more research yesterday and today, it appears that after the April 2018 Windows update, some of the security settings got reset including the webcam and microphone. A lot of people have found this to be a problem, not just me. And the Windows Audio troubleshooter and any error messages one encounters are of no use at all in fixing the improper settings. It is just one of those things you have to know, or hope you got set properly at the start. What seems to be the new deal since then - being phrased in my own words - is this: Windows has two levels of security (or privacy may be a better word) for a microphone device. The first is to allow or not allow it to exist on the machine it is attached. This is somewhat like disabling it in Device Manager. If it is enabled, it will appear in the hardware and it can get drivers installed, etc. But it can't be utilized without the next level. The second level is to allow processes to be able to use the device. The settings say for this level state that Windows is always able to use it without setting this, but that is simply untrue and misleading for troubleshooting. You can use it without level 2 if you set it up via 'listening' but that seems to be a security hole or flaw. As I mentioned at the start of this thread, this was on my to-do list of bugs to track down for about the last 4 months. When I finally discovered the solution, it was rather startling to me how Microsoft set this up and the way they phrased the settings and hid it in Privacy Settings. For a time I it made me upset, as one often gets when troubleshooting, so I posted down here to get it out of my system, but I think it has backfired and I apologize for that. At any rate, my purpose is to help others who might have fallen down the same rabbit hole I did. If you are like me, when you install Windows you make a local account, turn off all the Windows monitoring stuff like Cortana, and let it do as little as possible for you. In so doing, you might set these things in a way that you don't intend unless you know the language.
×
×
  • Create New...