Edzel Yago

I do. I just forget my password most of the time.

I do. I just forget my password most of the time.

I do. I just forget my password most of the time.

I do. I just forget my password most of the time.

I do. I just forget my password most of the time.

Don't know about a 'build guide' but we're looking at doing something for a DAW. =D So far it sounds simple enough. Just the question of DPC latency based on parts that doesn't seem like it can be answered until after it's built and tested.

Don't know about a 'build guide' but we're looking at doing something for a DAW. =D So far it sounds simple enough. Just the question of DPC latency based on parts that doesn't seem like it can be answered until after it's built and tested.

Shouldn't matter as long as it's storage SSD is a little faster tho

some do, others still use usb 2.0
like this apollo twin
https://www.bhphotovideo.com/c/product/1511708-REG/universal_audio_apltwxd_apollo_twin_x_duo.html?sts=pi&pim=Y
 

Mostly a post-build thing. But there may be some USB controllers, Ethernet controllers, etc that can cause latency. So you'll have to look at user forums for the specific software(s) you intend to use. So you may end up having to buy something like a different motherboard that originally planned for.
 
Yes. But I will personally never use HDD's unless I really have to. But if it's a cost saving measure, it will be fine.
 
Some MIDI interfaces do. But USB 2.0 has a faster transfer rate than the MIDI standard. So it's kinda pointless to spend money on those kinds of interfaces UNLESS you need a lot of MIDI in/out.

I'll try and answer all your questions at once so here goes, 

Latency
1, Latency in ASIO workloads is heavily CPU dependent so single core performance is important (if you're using a modern CPU it should be fine) and if producing music/audio using plugins this workload can be multithreaded so clock speed and core count are important from a latency standpoint as well as the audio interface you choose to use (different manufacturers use different drivers that allow for differing amounts of latency). The reason latency is CPU dependent is that ASIO buffer size (and by proxy latency) can only be reduced so much before you start getting artifacting in the audio signal, I mean random starting and stopping, popping, ugly stuff that you basically don't want BUT the faster your CPU is the lower you can reduce this buffer size before the artifacts start. The more plugins you use the more likely you are to exceed your buffer and start artifacting again at which point you have to increase the buffer size (latency). I usually run at about a 512 buffer size at 44.1khz on my Ryzen 5 1600 just because I use a lot of taxing plugins and any lower buffer (or higher sample rate) and I create artifacts, the 512 buffer gets me about 16ms input latency and 12ms output latency.

RAM/Storage
2, I produce easily with 16GB of RAM but if you'll be multitracking (recording lots of channels at once) or using large plugins disk speed is much more important so SSDs are a must. Personally I use HDDs for my massive plugins but the loading time for some large (70GB+) KONTAKT libraries can be very painful so if you've got the chance use SSDs for plugins but in reality they should do fine off a HDD.

Gear
3, Take a look at the guide in my signature, it runs through the basic components of a studio setup as well as explanations on what each bit does and the best mics/interfaces at given price points. On top of the info there about interfaces it's important to remember a couple of extra things for production, the first being that knowledge on how to set up mics is more important than the mics you use and the second is that there's no shame in using plugins for instruments if you don't have access to the real thing. If you'll be using plugins you will want a MIDI control surface whether that be a keyboard, launchpad or otherwise is up to you but they will make it far easier for you to play around with ideas and record them. Many interfaces are thunderbolt but they're usually either large format interface designed for pro studios with lots of channels or interfaces designed to be expandable with multiple interfaces coming together to form a conglomerate device (yes you can do this natively on MAC with any interface but it requires manufacturer support in Windows). Thunderbolt interfaces are also much more expensive but price point is up to you. Other connection options to be aware of are Dante (ethernet) and ADAT (optical), each serve a purpose but for your situation as far as I can tell USB and Thunderbolt will be the two main considerations.

Software
4, Program of choice is important, there are tonnes of different DAW softwares and some work better than others for some people, spend the time finding the one that is right for you but for starters I always recommend Reaper, it's one of the best quality DAW softwares out there and it's free! (sort of). It has all the features of ProTools without the dumb stuff that makes ProTools annoying to use like lack of VST support and constant crashing.

If you have any questions about specific pieces of gear, plugins or software I'd be more than happy to answer any questions you have 

Thanks for the input, guys! Much appreciated!!
 
So will latency be a post-build thing rather than a pre-build consideration?
 
Would VSTs be fine to be on say an HDD with projects being on the SSD?
 
Do many music/audio peripherals use thunderbolt?

Thanks for the input, guys! Much appreciated!!
 
So will latency be a post-build thing rather than a pre-build consideration?
 
Would VSTs be fine to be on say an HDD with projects being on the SSD?
 
Do many music/audio peripherals use thunderbolt?

More actual RAM to load in your VST's (16gb personal minimum). LOTS of storage as some VST's can be 20-50gbs or more each. Some are even hundreds of gigabytes each (but they're usually packages with lots of stuff in them). I don't know about other software, but Ableton Live doesn't really benefit much from a beefy GPU. As for CPU, higher core clocks are usually better than more cores. An SSD is a must if you wanna get anywhere in your project. Sound card doesn't really matter too much. You just gotta make sure you use the right ASIO drivers. As for peripherals, that's all really up to the individual. Me personally, I just use an old keyboard (piano) as a MIDI controller. But some people like to have different kinds of controllers for different kinds of instruments. Mostly it's all USB. An XLR interface if you're gonna do vocals or live recording an acoustic instrument. But if you're doing a live setup, rather than for recording, the standard 3.5mm output really should suffice (at least it did for us). I ran into an issue though on my personal system with latency and USB 3, WIFI, and even Ethernet drivers. Those all had to be disabled in order to correct the latency issues. But then again, the system I built was much older (AMD FX series CPU). Use something like Latencymon to monitor what causes your latency. You'll also have to fiddle with your ASIO drivers a bit to get that latency down as much as possible. Beyond that, that's all I really ran into myself.

I do a lot of music production and mixing
about 16gb more if you are using a ton of effects
only thing extra is a xlr interface and a midi keyboard
usb is only thing I can think of
not really because sounds is routed thought the xlr interface

DEMOCRACY RIGHT MEOW!
 
THIS SHIRT IS NOW AVAILABLE!!
 
https://www.districtlines.com/83006-Holy-Cat-Balls-T-Shirt/Linus-Tech-Tips
 
 
Okay, so here's "Holy Balls" with cats because people like cats and balls... Or was it that cats like balls? Or cat balls...? I can't remember what the instructions were and I got stuck in a cat.  :huh:
 

 
I played around with the placement and sizes of balls and junk; let me know if any of these strike your fancy.
 
The cat has been fixed.
 

 

HDR videos on the regular won't be for a while. I'm waiting on hardware to actually get things going on Windows machines. I learned and did the things on our Mac Pro with an Apple XDR and a PA32UCX.
 
HDRX and HDR is not the same and as far as I know, HDRX shouldn't be used to try to make HDR. I'm still testing scenarios indoors and outdoor to start making our workflow with HDR in mind.

Tyler looks like my kind of people. The kind of people who know you apply 3 light coats and spend vast sums of money on miniatures you may never use for games that are getting constantly cancelled because nerds can never agree on a time to play board games with one another. 
 
Also the kind of dude who absolutely takes a minimum of 3 board games on every road trip.
 
 

Tinnitus. It helps drown it out. Too many loud noises in my younger years.

Tinnitus. It helps drown it out. Too many loud noises in my younger years.

I REALLY wanted to do more mice but it was a matter of restricted time. We had rented the camera for the shoot with Gav (day 1) and had to return it the next day. We said we'd return it by 3 (have it leave the office at 1). Which meant we had to do the spoken bit, do the tests, some analysis to make sure things were good, then finish the tests within a few hours AND ingest the footage (which is painfully slow).
 
=P NEXT time though!

Time. Flight in was a bit delayed and he had to leave the next morning. We squeezed another video in the next morning/afternoon as well (without Gavin) while we had the camera though.

I REALLY wanted to do more mice but it was a matter of restricted time. We had rented the camera for the shoot with Gav (day 1) and had to return it the next day. We said we'd return it by 3 (have it leave the office at 1). Which meant we had to do the spoken bit, do the tests, some analysis to make sure things were good, then finish the tests within a few hours AND ingest the footage (which is painfully slow).
 
=P NEXT time though!

Time. Flight in was a bit delayed and he had to leave the next morning. We squeezed another video in the next morning/afternoon as well (without Gavin) while we had the camera though.

No denying that your 240Hz shot was insanity, would be hard-pressed to try that in 60Hz.