Hm, so if Studio A has 5 of Socket 1, you want 5 Socket 1 records, and if Studio B has 10 of Socket 1, you'd want another 10 Socket 1 records, for 15 total?
If not, I'd recommend just using automations for this if you can. Let's say you have a single select field called "# of Socket 1" in the table that contains your list of photo studios. You could create an automation that would create a set number of records based on the value in that field via conditional logic
E.g. if you select "3" in the field "# of Socket 1", your automation would create 3 records in the "Sockets" table and link it to the triggering record
The major issue with this approach is the fact that you can only have 25 actions within each automation, and so if you wanted to accommodate, say, 12 of each socket type, you would need to build 4 automations for that socket type alone
I've found another solution but it's really a burden.
The idea is to have another table, called ELECTRICITY, which has as fields: studios (linked to the studio table), socket type (linked to the socket type table) and a number of sockets. I then add a rollup from the STUDIO table on an "Electricity" field that gathers the information from the specific ELECTRICITY table.
But I cannot properly format the return as I want. There is just a simple concatenate(values) possibility. Airtable is really falsely a sophisticated tool and among everything certainly NOT a database like the official marketing statement mentions.