Jump to content

Pete Brown

Members
  • Posts

    20
  • Joined

  • Last visited

Posts posted by Pete Brown

  1. 18 hours ago, User 905133 said:

    Some Cakewalk users might be interested in this material on having unique serial numbers for USB devices.  Why do I mention this?  Well, because lots of Cakewalk users might be able to relate to this (and related) issues:

    So, maybe under MIDI 2.0 these kinds of issues will not happen.

    It only goes away if device manufacturers add unique serial numbers to their devices. All the operating systems have to work around this, and we'll continue to do so.

    MIDI 2.0 has in-protocol mechanisms to get device unique IDs, but if a device can do that, it likely would be able to have an iSerialNumber anyway. Also, those don't show up upon connection (we're not doing any in-protocol stuff right when we enumerate a device, or else Windows would take forever to start up) so they wouldn't change how Windows itself would see the device.

    • Like 1
  2. On 2/26/2021 at 10:00 AM, Jacques Boileau said:

    @Pete Brown I just went through your guide and it is excellent and thorough. Great stuff!

    One setting I haven't seen talked about in your guide, or I simply missed it, is the game mode. Since I do absolutely no gaming on my DAW's PC (I have a PS4 for gaming anyway), I turned that off. But I wonder if it has any real impact, negative or positive?

    I will put my vote in with @Craig Anderton comment: I use Edge exclusively on my DAW's PC. I did not see the benefit in installing a second browser and Edge has filled my browser need without a hitch. I started using Edge on my other, much older PC, where the fan would just run wild with Chrome opened. I was surprised how well it ran and never looked back. 

    Noel and I experimented with Game Mode a few years back, because it could be potentially useful for DAWs. Noel found that Cakewalk performed worse under Game Mode.

    This is consistent with what some other DAW companies have told me.

    Your mileage may vary, especially as core counts go up, so it's worth experimenting with. But for DAWs, optimizing for graphics FPS often comes at a cost for real-time audio. (This is also why gaming PCs aren't always the best base for DAW building)

    Pete

    • Thanks 1
  3. On 2/28/2021 at 4:52 PM, Jeremy Oakes said:

    Then why do we get so many posts that have so little to say other than disagree with the pros ( see the Noel  and Pete Brown posts) ? It becomes very tiring.

    J

    Not quite sure what you're saying there. I don't generally disagree with the pros. But the DAW builders I know and work with have very specific configurations of hardware and software that they support.  In at least one case, the PCs are locked down like appliances, and the customers are not allowed to install anything else on them other than plugins. The tweaks they do for that aren't necessarily ones that should be up on a general list.

    Pete

    • Like 1
  4. 1 hour ago, Craig Anderton said:

    In his guide, Pete sez...

    <<I beg forgiveness for the marketing-like blurb, but please do check [Edge] out.>>

    I know he can't shamelessly promote Edge without looking like a shill, so I will. Edge is fast and efficient, and improvements like Collections shows someone at Microsoft is thinking "hmm, I wonder what would actually help users."

    Thanks Craig

    I'll buy you a drink the next time we have an in-person NAMM or MIDI meeting.  :D 

    Pete

  5. 2 hours ago, Starship Krupa said:

    Controversial, to the point that I seldom recommend it unless people ask, but I disable Defender realtime scanning completely on all my systems. Excluding folders and processes from it as you suggest probably works as well. "Kids, do not try it at home" caveats apply.

    Background:

    I have my own anti-malware system in place I call "not clicking on random crap I get via email and on-demand scanning any executables I download." In the 40 years I have been using DOS and Windows, it's never failed me.

    Having been around that long in the industry, I'm also cantankerous about lowest common denominator precautions. In my IT career I never encountered malware that was as destructive and invasive than the malware solutions I encountered (slow startup, resource hogging, performance degradation, pop-up nags, etc.). I understand that as the user base for Windows has expanded (and to be fair, malware has gotten nastier) it may be considered essential to harden the protection to make it more fool-resistant. I'm a very persistent fool. 😁

    Regarding updates, I've found that the standard control in Home is fine for my amateur home studio.

    Got it.

    I don't agree with the decision to disable Defender, but I get where you're coming from.

    What you don't end up protected from, however, are drive-by malware installs that use browser exploits to install software on your PC, Mac, Phone, etc. The owners of the sites often don't even know that the malware distribution is happening there, because it comes through compromised ad networks, hacked sites, posted comments, etc. You can still manage a lot of that by being careful and aware, but some of these things can be tricky.

    I still use Defender, but I've also done a few other things in this house to help keep all the PCs safe (I have a 12yo and 15yo, each with their own PCs since they were 6, and my wife also has her own PC)

    • Ad-block. I felt guilty at first, but ad networks were a primary distributor of drive-by malware, so I gave up, That, and the ads that were pushing content all over the page were so distracting that I just couldn't function anymore.
    • Pi-Hole. I have a pi-hole for the house. Originally, I installed it so I could actually surf the web with my iPad Air. It was otherwise choking due to all the supplemental ad/tracking/scripting going on on pages. It really made a huge difference. I've unblocked the domains for xbox achievements, and some telemetry, but otherwise, it blocks a ton.
    • Before it was mandated, uninstalled and disabled Flash on all the PCs in the house. Way too many exploits
    • Way back, completely disabled Java on all browsers on all PCs. Hot mess of exploits that was. The only reason Java was on any of the PCs was (is) for Minecraft.

    Since then, there's only been one instance of malware in the house, from when my son was trying to download a Minecraft texture pack, and clicked the wrong download button (I hate those sites). He learned a valuable lesson that day, and no one has had problems since.

    There's a person on Gearslutz who PM'd me about malware they got. The vector there was their router, which has apparently been compromised. Again, didn't require any bad behavior on the part of the user, other than not making sure the router was up to date (and even then, not sure that would have stopped it).

    One thing I did recently enable is Windows Defender Controlled Folder Access. The first time you enable this, it's a bit of a pain as file access starts silently failing for some apps. But once you let them through, it's all good. Given the massive rise in ransomware, this seemed prudent. 

    Defender is pretty low-touch and low resource usage. Worth a try if you ever decide to give it another shot. :)

    Pete

    • Like 2
    • Thanks 3
  6. 10 minutes ago, Starship Krupa said:

    Excellent! It doesn't get more authoritative than this. I knew about excluding folders from Defender scanning (a tweak I figured out on my own, really good to disable it for your Cakewalk Projects folder and the VST3 and VST2 folders) but I didn't know that you could also exclude processes.

    One note:

    If you wish to mess with Group Policy settings (which are absent from Pete's guide) Group Policy Editor comes with Windows 10 Home, but the feature is not enabled by default. Fortunately, it's not difficult to enable it.

    I've done this, and it worked a treat (although at one point a Windows Update disabled it again so I had to re-enable it). I haven't tried the 3rd-party policy editor they recommend.

    FWIW the group policy editor is not actually supported on Windows 10 Home, but I figure anyone doing the above knows that. Also, be careful with DISM, as it's really easy to hose your drive with that. DISM does a lot of things, including provision an empty drive. It's the deployment image servicing tool. The way the batch file is written, that's not going to happen, but should anyone get curious about the tool, this is important to know.

    Which group policy settings would you apply to a DAW? I have some for controlling updates linked to from the post, but I haven't found any others that are essential, myself.

    Pete

    • Thanks 1
  7. The "prefer background processes" bit can actually hurt you. During the investigation for my tweak list, I looked this one up, because it comes up often.

    That setting is primarily for servers with background processes (think Database or web server) which need to be prioritized over the interactive applications. Normally, foreground apps get a boost to keep them responsive. Setting it to prefer background services puts foreground and background on a fairly equal footing, with some caveats.

    For DAW use, when using an ASIO driver setting it to "background services" :

    • If the driver is loaded by a process other than the DAW (like a service), and doesn't use MMCSS threads, this setting could potentially keep the audio driver from being starved by a faster interactive application.
    • If the driver is loaded in-process with the DAW, this will not have any positive effect because the audio driver is part of the foreground application process.
    • If the driver is loaded by another process (like a service), and DOES use MMCSS threads, this setting will not have any positive effect.

    In all cases, when you set this to prefer background processes, you are causing all those other services that folks put in tweak lists as "robbing" processor cycles, on an equal footing with your DAW app, causing them to potentially use more CPU than you may want.

    If you are using WASAPI, the calculus is a bit different because there are more moving parts.

    And, again, if the bit running in the background process is using MMCSS threads (many do now), this will not have any impact because those have a different scheduling algorithm applied.

    As I mention in my on tweak list, the key is to measure measure measure. And be sure to do so both before and after the change, and in isolation from other changes. In most scenarios, this setting is not going to help performance of the DAW. In some cases, it could make it perform worse.

    Pete

    • Thanks 4
  8. I tested in in Firefox as well. Maybe you're blocking something with an ad blocker, firewall, or DNS black hole?

    The blog site does check to see if you're signed into it when it first loads up, but it's not required unless you want to comment.

    If you go to just aka.ms without the rest of it, that's our page for managing short links. You have to have Microsoft employee credentials to log in there. Totally separate thing.

    Pete

  9. Hi All

    Noel let me know about this issue. (Thanks @Noel Borthwick )

    @Marcos Kleine which OS and version are you running? (If Windows 10, go to Settings->System->About to get that info).

    @Johnbee58 same Q for you. I'm curious to know why it works for you and not Marcos. Have you tried Noel's approach and found it to still work?

    Before I can get this in front of the team, I need to figure out if this is an issue that was always there vs. something new, so if anyone else can repro on older versions of Windows 10 and/or 8.x and/or 7, that would be incredibly helpful.

    To be frank, the GS wavetable synth isn't the best thing to use to make music with. It's in the OS mainly for compatibility, but the sounds are super dated and the latency is pretty high. Personally, I'd like to see it go away, but we have this thing about backwards compatibility. :)

    Pete

    • Like 1
  10. 4 hours ago, Jim Roseberry said:

    Hi Pete,

     

    The latest Win10 install discs are version 1903.

    Installing on socket 1151/Z390 based machines (numerous different motherboards), with all available patches (thru Windows Update procedure), high DPC Latency persists.  

    Installing from an older Win10 disc, there are no DPC Latency issues with v1803 or v1809.

    I've downloaded the KB4505903 fix from your link above... and will test to see if that resolves the issue.

    We appreciate your presence here on the forums!

    Hi Jim

    Stock 1903 has an issue with kernel code that causes high DPC latency on some PCs. The updates available for it should include the kernel patch we released last month, including KB4505903 (which I believe is in another roll-up with a different KB number).

    If you still have high DPC latency after that (and rebooting), please do a trace per the blog post above, and provide the link to me. Note that tools that measure DPC latency aren't always accurate -- the team needs to hear the glitch in the audio that is recorded as part of the trace.

    Finally, a common cause of DPC spikes is power settings: both the PC and the video card. There are LOTS of variables here, but with nvidia GPUs, make sure to set it to prefer maximum performance: (NVIDIA control panel -> Manage 3D settings -> Global Settings). Folks on other forums have found that that setting alone appears to have a big impact in DPC latency. It's not something I've measured, myself.

    Pete

     

  11. Noel ping me about this thread.

    We released a fix for the ntoskrnl 1903 very high DPC latency issue late last month. Not all of these things make it into announcement posts, so follow me on Twitter if you want info earlier.

    If after installing that (or the roll-up that contains it), you still get high latency spikes, it's likely something else. Best way to diagnose that is to take a glitch trace and make us aware of it by sending me a link to the Feedback Hub entry.

    Instructions are on Matthew's blog. Make sure you can hear the glitch when taking the log/trace. Sometimes we get traces with no audio, and that doesn't help. :)

    https://matthewvaneerde.wordpress.com/2016/09/26/report-problems-with-logs-and-suggest-features-with-the-feedback-hub/

    • Like 3
    • Thanks 3
  12. I've installed 18312 on my DAW PC.

    FWIW, I tried out the FLS Checker plugin, and it maxes out at 128. So DAWs all show 128 even after a ton of plugins have been added.

    46720193941_d4d431be21_o.png

    To confirm the slot increase, I wrote a small C++ console app. It's running under the debugger here, so a few slots are taken.

    Results

    32845424918_1bbaaca812_o.png

    Code

    31779028037_3325e17e86_o.png

  13. 51 minutes ago, Noel Borthwick said:

    That's pretty bad. I wonder if it's due to undo history or memory leaks. Did you try clearing your undo history @Pete Brown

    Thanks for the details, appreciated.

    I didn't dig into it at all. I also haven't tried it in Cakewalk. I've seen others report it, and I had it happen with me in another DAW.

    Pete

  14. 18 minutes ago, whistlekiller said:

    How about trying to limit what stuff you shove though a DAW. Some of the best music was created  with a minimum number of tracks and effects. 😀

    That's up to the individual.

    We just didn't think the OS should be making that decision for you.

    Pete

    • Like 2
    • Great Idea 1
  15. There are some real subtleties to this. I figured it would be good to post a clarification. 

    Most DAWs use between 20 and 40 FLS slots. Plugins typically use 1 to 45 slots themselves (with most using < 4).

    It's not about loading up 128 plugins, but loading up plugins that take up the remaining slots left after the DAW has its slots allocated. The VC runtime allocates a slot (the whole static linking thing), but code may allocate FLS slots for other, completely legitimate, reasons. Or the plugin may just have a whole lot of statically linked runtimes in its numerous sub components, using up slots and wasting memory by filling it with many copies of the same runtime code. You don't know which case it is unless you decompile the plugin code.

    Here are some numbers that folks put up in another forum (I have not personally confirmed them, but they look right):

    • Steinberg Padshop - 1
    • Spectrasonics Trilian - 1
    • Waves (Waveshell) 2
    • Waves Codex - 2
    • UAD -2
    • Roland TR 808-2
    • dbx160 - 2
    • Slate VMR - 2
    • FXpansion BFD3 - 2
    • Korg Arp Odyssey - 3
    • Steinberg Dark Planet - 3
    • BX20 - 4
    • ATR102 - 4
    • Kontakt -4
    • Maschine-4
    • SSL E Legacy - 4
    • API 2500 - 4
    • EMT 140/250 - 4
    • Fairchild 670 MKII - 4
    • LA-2A Grey - 4
    • Arturia Arp 2600 v3 - 6
    • Arturia Buchla - 6
    • Arturia DX7 - 6
    • Synclavier - 7
    • CMI - 8
    • Analogue Lab3 45

    I've also separately confirmed that iZotope Neutron uses 10 slots itself for the version I have (I'm a rev behind current, as I recall)

    So if the DAW uses, say, 30 slots, and you also have Analog Lab 3 loaded, and Neutron, you end up 85 of your 128 slots taken up. It's not at all hard to hit that limit this way. Note that freezing or disabling tracks doesn't change this count. It's about code loaded into the process. Also note that adding and removing a bunch of different plugins in a session can also use up slots, as it appears the slots don't always go back to the pool. Not sure why there, and I haven't looked into it.

    The limit is per-process, not machine-wide. Solutions that host plugins in a separate process get their own 128 slots.

    The limit itself goes back to Windows Vista, and hasn't changed since then. Folks using Windows 7 have confirmed that the slot count is the same as on Windows 10.

    The fix itself, if all goes well, will be in the 19H1 release of Windows 10, in the first half of this calendar year.

    Pete

    • Thanks 2
×
×
  • Create New...