[video] Make windows fast enough for production (multi-part)

[kingozrecords]

This is a multipart series on making your windows 10/7 installation fast enough for production and even for live gigs.

So often it seems plausible that a computer could, but isn't it funny how something like a dongle, connectivity, services, automatic updates and a firewall, or antivirus could make that all but impossible?]

Myself, after installing and using the Private Win10 product; I went crazy for Windows 10 and you will too. That's because that not only is this product free, but it's not destructive.

It allows you to prevent the things that bog down windows 10, without being harmful and destructive as many other similar applications do. This is because Private Win10 allows you to turn all problem settings off with a switch and when you choose to - Also allows you to turn them back on!

This means that there's no worries when the next big windows 10 update happens and taking care of business is a piece of cake. However, I think it would be wise to say this: Turn off auto updates if you use this.

That should go without saying but really, you should always turn every setting back to the original every time you install a new update to be on the safe side.
https://github.com/DavidXanatos/priv10/releases

You're gonna go nuts when you try this, I mean you'll be running everything including your DAW like 20 to 40 to even 60% faster after following this video I've made for you.



I've seen hacked win10 installations and obviously, you have to reinstall everything, with this method you can make a production/live music performance pc for gigs without having to, Mint.

[kingozrecords]

Privazer is the second utility mentioned in this growing series that will have at least 8 videos. And what I want to maintain from the getgo is these things:

• If one software has almost everything, but a hampered utility with *less features, then we don't use the hampered utility.
• If a product is required to startup as a service or with Windows, we like don't want it (Private Win10 being the one exception).

Privazer provides the option to wipe free space, it also covers a few features that allow you to do what CCleaner was most popular for (while it was popular). These two things are primarily fixing registry issues and secondly wiping free space.

Wiping free space can also save CPU, because data isn't actually gone. You have to rewrite it many times until a system cannot register it as data. And what about SSD's they're more secure right? Wrong, they're even worse, in fact SSD specific File Allocation Tables like Exfat (the runner-up is NTFS) make it almost impossible to delete a file, even with NASA tricks to foil the CIA.

However, such a tool can be used unwisely, and I did the testing and made sure everything worked first to get this video together for you. Production PC's need every bit of power that they can get if you're going to be playing live, or even streaming. That's practically the same thing.

Therefore, if you're using software like iobit's system tools, don't use this, if you've installed Auslogics Boostspeed, I would not recommend you use this either, or CCleaner, or windows washer by webroot.

If you're not using a free space cleaner / registry cleaner however, than this one's for you. After this tut, tomorrow by the way; I'll be going over how to install the FREE version of Auslogic's Boost Speed 12 in such a way that will not cause problems.

[arkmabat]

Lame tip: if your version of Windows won't let you turn off updates, just fill up the boot drive so it has 4 gigs of space or less. Bam! Windows can't update.

[roman.i]

Quick tip for making the DAW faster, add the DAW process into Windows Defender exclusion list.
It makes the DAW to work much more smoother and faster, without this exclusion the Antivirus will check each audio sample you play in the DAW for real-time virus scan on every access.

[arkmabat]

I mean, I've nearly gotten a trojan from a pdf before. If you have any sketchy samples, it's worth scanning them all before using them, but this sounds like a good idea.

[kingozrecords]

I mean, I've nearly gotten a trojan from a pdf before. If you have any sketchy samples, it's worth scanning them all before using them, but this sounds like a good idea.

I remember when I was younger was I ever paranoid about viruses lol. And rightfully the old ones were so very potent. They'd wipe your pc in a heartbeat!

Quick tip for making the DAW faster, add the DAW process into Windows Defender exclusion list.
It makes the DAW to work much more smoother and faster, without this exclusion the Antivirus will check each audio sample you play in the DAW for real-time virus scan on every access.

Thanks! This is very helpful.

[Dasheesh]

does this actually work? i have been fighting windows for years on this ish. somehow they always sneak back in. somehow they even snuck code into my system that "fixes" updates, even when i turn them off at the service level. don't bother with the system settings (if you can even figure them out anymore), they mean nothing. it will bypass all your personal settings when ever it feels like it, and then resets them after it installs what ever crap micro$ wants to corrupt your machine with.

[legendCNCD]

Hot Tip: Disable updates completely with Sledgehammer and enable them when YOU want to update.

[Steve Bolivar]

You should post a link to these threads in the Computer Setup and System Configuration forum.

[whyterabbyt]

You should post a link to these threads in the Computer Setup and System Configuration forum.

No he shouldnt, he's talking complete bullshit half the time. Like this bollocks...

Wiping free space can also save CPU, because data isn't actually gone. You have to rewrite it many times until a system cannot register it as data. And what about SSD's they're more secure right? Wrong, they're even worse, in fact SSD specific File Allocation Tables like Exfat (the runner-up is NTFS) make it almost impossible to delete a file

[kingozrecords]

lol, it's totally true, exfat doesn't even truly delete anything. Instead of quoting people; spend that time on google and learn what there is to learn. I have no time for noobs and neither does anyone else. There's no nice way to say it. Noob.

[whyterabbyt]

lol, it's totally true

There's nothing SSD specific about exFAT or NTFS you dumb f**k.

I have no time for noobs and neither does anyone else. There's no nice way to say it. Noob.

Ive been a sysadmin since before you were nothing more than damaged spunk. Noob.

[whyterabbyt]

Wiping free space can also save CPU

comedy gold.

NASA tricks to foil the CIA.

brain-damaged comedy gold.

[whyterabbyt]

Transience: Originally a term deriven from the explanation of this "data" lost in the "buffer". "Oversampling" meant you were running the tape real hot. And of course that lead to the buffer spitting out random data.

Legacy comedy gold.

[kingozrecords]

ExFat deletes files by marking each file and directory entry with a symbol (0xe5 as the first byte), and also removing the pointer to the file entry so that the blocks are freed up. There is no second file table, so once it is done, it is not feasible to correct. AFAIK there is no other method to undelete a file with ExFat on linux.
reference: https://superuser.com/questions/1133007 ... isk-device

Though this superuser sounds eloquent, I'm reminded of another fact regarding the exfat file structure, and that is in regards to how exfat finds a file. You see, ntfs will mark the entry in the journal and there will be some erasure, but there is a compressed remanence (like hash to be fair). But that is surprising due to the fact that ntfs searches an index this way:

Directory file set
exFAT and the rest of the FAT family of file systems does not use indexes for file names, unlike NTFS which uses B-trees for file searching. When a file is accessed, the directory must be sequentially searched until a match is found. For file names shorter than 16 characters in length, one file name record is required but the entire file is represented by three 32-byte directory records. This is called a directory file set, and a 256 MB sub-directory can hold up to 2,796,202 file sets. (If files have longer names, this number will decrease but this is the maximum based on the minimum three-record file set.) To help improve the sequ*ential searching of the directories (including the root) a hash value of the file name is derived for each file and stored in the directory record. When searching for a file, the file name is first converted to upper case using the upcase table (file names are case insensitive) and then hashed using a proprietary patented algorithm into a 16-bit (2 byte) hash value. Each record in the directory is searched by comparing the hash value. When a match is found, the file names are compared to ensure that the proper file was located in case of hash collisions. This improves performance because only 2 bytes have to be compared for each file. This significantly reduces the CPU cycles because most file names are more than 2 characters (bytes) in size and virtually every comparison is performed on only 2 bytes at a time until the intended file is located.
https://en.wikipedia.org/wiki/ExFAT

So, ultimately - if files are stripped of directory related inheritance, in comparison to references often made to the journal:

File name lookup
exFAT employs a filename hash-based lookup phase to speed certain cases, which is described in US Patent 8321439,[32] Quick File Name Lookup Using Name Hash. Appendix A of the document contains details helpful in understanding the file system.
https://en.wikipedia.org/wiki/ExFAT

and yet, also references even within the file to file location are also culled:

• Removal of the physical . and .. directory entries that appear in subdirectories.
• exFAT no longer stores the short 8.3 filename references in directory structure and natively uses extended file names, whereas legacy FAT versions implement extended file names through the VFAT extension.

https://en.wikipedia.org/wiki/ExFAT

Then why is it omitted that the very nature of this file system is to search for files for their hash tag, rather than orientation by directory and also to rely less on directory structure as a whole. If this is true than deleted files are always being read, because the only device that suggests they are not there is the symbol "0xe5". And yet, in the case of either exfat or ntfs, a file must exist and respond in kind to suggest that it does not exist for it to be not there.

Hence deleted files are not actually deleted, and searching for deleted files in exfat is as simple as searching for files beginning with 0xe5. It really is the simplest thing.

in regards to tape

Transience: Originally a term deriven from the explanation of this "data" lost in the "buffer". "Oversampling" meant you were running the tape real hot. And of course that lead to the buffer spitting out random data.
Legacy comedy gold.

Losing transience was the initial "slip" overcome by the heads which were fed to the buffer at different speeds, this method was designed to overcome transience; ie: wow and flutter.

Tension transients suppression during acceleration and/or deceleration for storage tape drive
https://www.freepatentsonline.com/8681448.html

Like in the case of wow and flutter, in 8 track they were able to avoid there being a volatile transience by making the tape quite thick and due to the fact that the tension remained the same because it was a continuous circuit it ensured. The result is often referred as wow and flutter, but in the case of tape that ran freely without guides, like in the case of film there was less control. And heads acted as a way of preventing transience.

The harder and faster a tape was processed, resulted often in more heads being employed in the case of analog tape and those heads would add, correlate and truncate depending on a buffer. However, there was still an over-processing occurring as no one signal could be entirely omitted from the other, leading to the sound being pretty thick.

Even in data the same is true and patens are designed to avoid the phenomenon

In one embodiment, a system includes a controller configured to: determine a reference velocity at various intervals, receive or determine a secondary velocity based at least in part on a parameter associated with a drive mechanism motor, determine a value representative of a difference between the reference velocity and secondary velocity, adjust a speed of the motor of the drive mechanism for minimizing the difference between the reference velocity and secondary velocity, receive/determine a primary velocity based on reading information encoded on a magnetic tape, at a switching point, make the reference velocity about equal to the primary velocity, after the switching point, determine the reference velocity at various intervals, after the switching point, determine a value representative of a difference between the reference velocity and primary velocity, and adjust the speed of the motor of the drive mechanism for minimizing the difference between the reference velocity and primary velocity.
https://www.freepatentsonline.com/8681448.html

Unlike in the case of digital oversampling it was happening in real-time with no way to process faster than real-time which was why the effect of drive was unavoidable.

I don't think you should beware My quote, but maybe you'll find it a tedious adventure sorting things out after I explain things in greater depth. I live for research and I spend all of My time going over data and how to better process it. There's nothing I relish more than a good roast of ignorance.