[–] 2 points 1 month ago (4 children)

It doesn't have a volume control because it's designed to go into a head unit, or I think you mentioned you had a mixer? That's fine too. It outputs at a standard level, but if you hacked a pair of earphones on to the output with special adapters, it'd be much too loud.

  • source
  • parent
  • context
  • [–] [S] 1 point 1 month ago (5 children)

    Thanks! 😊 I cleaned the surfaces with isopropyl alcohol to make it really shine. The play/output controls aren't too amazing, basically just "play", a Dolby noise canceling effect, some EQ and no volume control. But! The recording/input controls seem amazing! Volume control, panning and hi cut/boost. 😁

  • source
  • parent
  • context
  • [–] 2 points 1 month ago* (last edited 1 month ago)

    The OS will normally buffer writes in RAM when an application does a write, then when it has a bunch, do them all at once, so it'll do a big chunk of one, then the other.

    Also for some unusual filesystems, like, say it's a log-structured filesystem, the actual data may just be more-or-less written forward for both of them.

  • source
  • Modern storage systems and protocols have device performance and longevity in mind, too.

    A lot of really smart people have thought long and hard about the problems and limitations of the components that computers run on and how they communicate, and the longevity of the components is a testament to that collective effort.

  • source
  • parent
  • context
  • [–] 3 points 1 month ago (1 child)

    There will be limitations throughout your network; LAN speed, write speed on B, write speed on C, etc. these factors may slow down the reads on A such that it is never reading at full speed no matter what.

    If you took a simpler example, say old SATA disk A being read the. Getting written to NVME disk B and C on the same machine, you are much more likely to start hitting HDD caps on the reading device, where delays from seeking may occur. Even then, your OS should be providing some level of "smoothing". It could be either reading whole files or large blocks of data from the HDD at any one time, such that it will try to make the most of a read at a location while not bottlenecking the sending of data to both write devices. Not to mention that rsync may also be smart enough to cache data between the two outputs such that two readys don't need to happen.

    With all that said.... Does it matter? Not really. The OS will try it's best to get data out of A as fast as possible. The network will try to get data distributed in the same way. Disk A may be working hard and may do some jumps and read/writes, but it won't intentionally break itself.

  • source
  • [–] [S] 1 point 1 month ago

    Really quick update incase anyone every sees this issue themselves years down the road, it’s been days and so far no problems as it strangely still seems to be working fine. πŸ€” Leaving me obviously beyond perplexed as to what this call is… πŸ˜΅β€πŸ’« Here are the number of calls in 24 hours, which isn’t terrible…

  • source
  • parent
  • context
  • view more: β€Ή prev next β€Ί