How to connect two computers to one 5.1 audio system?

Question

Audio

On one computer, the motherboard has three standard connectors that can be reassigned to 5.1 sound.
The second computer has not been assembled yet, now I'm choosing a motherboard with the ability to install two video cards (accordingly, the possibility of installing pci audio is no longer available).
Question: how to organize the simultaneous output of sound from these computers to a 5.1 audio system?
I considered this option - from the first computer, connect three audio connectors to three audio connectors of the second computer (reassign them to "input" accordingly), and connect the audio system through the remaining three audio connectors ("output"). That is, use the software audio mixer of the second computer. But here, firstly, you still need to find such a motherboard with six audio connectors, and secondly, will it be possible to reassign these connectors in this way? Basically, more or less normal motherboards have only 5 audio jacks and 1 spdif (not suitable for us). Will it be possible to remap one of the front audio jacks?
What if you buy an external usb audio card, will it make the task easier? Although, of course, you don’t want to buy too much.
So far I have looked at this motherboard: ASRock Z170 Extreme4
Unfortunately, all motherboards with six audio jacks that I have found are generally low budget and do not meet the rest of my requirements (good power (>= 8 phases), proper SLI operation, usb 3.1). Please tell me if such a motherboard exists.
The most ideal option is an external stand-alone audio mixer, but I don’t even know how to look for one and are there such ones within 5,000 rubles?
Here is a picture to illustrate

Answer 1

How to connect two computers to one 5.1 audio system?

What for? How is this shit supposed to work?
As soon as you formulate the task, it will become clear how to implement it.
If you need to listen to classics from one computer at the same time, and rock from the second, and all this should sound from one set of speakers, you make or buy a mixer with resistors.
. Adjustments are not needed - just 3 10K resistors soldered by a star.

Answer 2

PC1 makes a shared folder. PC2 also plays its own files from the PC1 shared folder.

Answer 3

Do I understand correctly that in order to store files, they need to be divided into folders,

Not right.
In order for files to be uploaded and uploaded safely, it is not necessary to segment them (split into folders).
The problems that you may have heard about are only related to obtaining a complete list of files in a directory. Yes, it is long and slow, but it does not affect the speed of reading a particular file in any way.
And on combat servers, using storage in the local file system is completely nonsense. There is no such problem in principle.
Segmentation can be done for, let's say, beauty. Or to make it clear who owns a particular file. But its practical utility is questionable. There is no harm, however :)
Again wrong.
First, never, NEVER trust user input. Save the downloaded file - generate a name yourself. And the original name is not forbidden to save in another place. If you need to allow the user to save the file under the original name, this is done in several lines.
Secondly, your segmentation is too aggressive. If we imagine that a username can only consist of lowercase Latin letters and numbers (total alphabet 26+10=36 characters), then such a storage can accommodate 36 ^ (1 + 2 + 3 + 4 + 5) = 36^15 = 2.21 * 10^23 files without repetition. What if the username is shorter than 5 characters? What if it's renamed?
Remember "first"? Since we need to come up with a file name ourselves, why not use either UUID and generate a unique (with high certainty) value of the form 28c5a6d8-f7b5-440f-aeaa-150e4fd0bebcand then segment it? For example, two segments of two characters each date cool links of the form 28/c5/28c5a6d8-f7b5-440f-aeaa-150e4fd0bebcand the ability to place 65 thousand files so that they are one at a time in the directory :)
There is also an option to use not UUID, but calculate the checksum of the file and take it as a name. The practical value of such a hash, however, also tends to zero :)
If we are talking about Junga, then she does it herself, this is a regular function of the repository.

Answer 4

If a user can have many files, then there will be an ass, which means you need to create subfolders for files.
If there are many users, then there will be an ass, which means you need to sort users into subfolders.

Answer 5

It doesn't matter if you don't intend to navigate directories using mc or something like that.

Answer 6

Don't shoot yourself in the foot - listen to Sergey and use standard practices:
use a fast hash algorithm to generate the filename - avoid problems with duplicates, encodings and invalid characters in the name;
scatter files into subfolders based on the first 2-3 characters of the hash, and not by belonging to the user, then you will have 2 levels of nesting with your head;
store the user-file connection in the database, at the same time the initial name can be saved if necessary;
if the files are small (for example, avatars), then consider storing directly in the database.