For those who care in this project: is MIT an acceptable license for code?

Two things!

One, infrequent reminder that we use Matrix for communications as much as possible. Join us here: matrix.to/#/!fBIVVMfUdQBKyZrfp !

Two, the Code of Conduct has been updated. Please remember to read it and keep it in mind while working with this project and the creatures in it!

Two things!

One, infrequent reminder that we use Matrix for communications as much as possible. Join us here: matrix.to/#/!fBIVVMfUdQBKyZrfp !

Two, the Code of Conduct has been updated. Please remember to read it and keep it in mind while working with this project and the creatures in it!

Drawings for most of the I/O modules are scanned. Need to do some digital editing before uploading them. They'll be on the wiki; I will post here once they're up.

Show thread

... I need to scan in all those module drawings I did the other day.

So this project has, to this point, been primarily one woman with input from several friends and a few others.

I would like to change that. I've compiled a (possibly incomplete, possibly too complete) list of all the specialties that this project needs.

Phase 1:
-Electrical Engineer who is versed in mains power, DC power, and conversion between them
-Network Protocols Engineer, specifically one versed in AES67
-Physical Network Engineer
-Someone versed in microcontrollers, I2C, and I2S with TDM
-Firmware Engineer
-A-D/D-A Hardware Engineer
-Analog and Digital Audio Engineer
-Engineer versed in time systems: GPS, NTP, Word Clocks, etc

Phase 2:
-Database Designer and Engineer
-GUI and Frontend Software Designer and Engineer
-Backend Software Engineer
-PCB Designer
-CAD Engineer with experience doing PCBs

Phase 3:
-Someone who knows how to work with motors
-Metal Fabricator and Welder
-Mobile Software Engineer for phones and tablets
-Processor Engineer e.g. CPUs, GPUs

... it's a daunting list, particularly with the understanding that this is an open source project, both software and hardware, and these are some pretty specialized skills. At the moment, I don't have the money reserves to pay people for this or it'd be easier.

But I also believe that we can pull something like this off in a spectacular upset of the current proprietary nonsense that is so much of the audio industry. Our community deserves a better system.

Please boost. I need y'all's help to make this work.

So this project has, to this point, been primarily one woman with input from several friends and a few others.

I would like to change that. I've compiled a (possibly incomplete, possibly too complete) list of all the specialties that this project needs.

Phase 1:
-Electrical Engineer who is versed in mains power, DC power, and conversion between them
-Network Protocols Engineer, specifically one versed in AES67
-Physical Network Engineer
-Someone versed in microcontrollers, I2C, and I2S with TDM
-Firmware Engineer
-A-D/D-A Hardware Engineer
-Analog and Digital Audio Engineer
-Engineer versed in time systems: GPS, NTP, Word Clocks, etc

Phase 2:
-Database Designer and Engineer
-GUI and Frontend Software Designer and Engineer
-Backend Software Engineer
-PCB Designer
-CAD Engineer with experience doing PCBs

Phase 3:
-Someone who knows how to work with motors
-Metal Fabricator and Welder
-Mobile Software Engineer for phones and tablets
-Processor Engineer e.g. CPUs, GPUs

... it's a daunting list, particularly with the understanding that this is an open source project, both software and hardware, and these are some pretty specialized skills. At the moment, I don't have the money reserves to pay people for this or it'd be easier.

But I also believe that we can pull something like this off in a spectacular upset of the current proprietary nonsense that is so much of the audio industry. Our community deserves a better system.

Please boost. I need y'all's help to make this work.

Hi, Fedi.

I need your help. This project is based around the fundamental ideal of driving audio over a layer 3 IP network, *open source*. No Dante, no AES50, none of that. Open source only. To that end, I have run across Ravenna and AES67 as the only serious contenders, and I have Questions that need answers from people who understand the underlying protocol and possible implementations.

So, one... are there any other *serious* options for a/v-over-IP that i have missed (AVB doesn't count)?

Two, can anyone put me in touch with somebody who actually understands AES67/Ravenna in more than a passing way?

Please boost this and help me find answers.

Thank you.

I spent some time tonight doing work on the project. Roughed out (almost all) the I/O modules' analog signal flow, power, and a start at I2C. This now leads to the point of using ADCs and DACs.

My research skills are somewhat failing me. I am not sure at this point how to get a digital signal from an ADC to a processor point, particularly over ethernet. This is my current snag. The signal has to travel over a distance before it hits a non-preamp processor, either a computer or a dedicated card.

So how do we take the signal from multiple ADCs, get them *to* the ethernet line, through it, and to the processor? Ethernet should just be what it always is: packets. Large MTU packets probably but still packets.
So is the ADC just a stream of binary or what??

Help!

Very minor update

Spent some time this afternoon drawing up a diagram that roughly outlines the system at bare bones, but also somewhat indicates data flow within the system.

wiki.osstudio.glitchiest.town

Good news! A signal from an input to a direct output works!
imagine that.

now for the more complicated part: getting a signal in through an ADC then processing it Enough to get it back out to a DAC and the output wire

how the

Some finagling has happened!
The Matrix community is now hosted at: matrix.to/#/+osstudio:glitchie and links to each channel are in there.
Wiki has had some minor updates, and i'm working on a proper website for the project.

i have also obtained a couple more chips for basic building! Things are happening, just... very slowly.

Whee!

OpenSourceStudio update 

So, it's been a bit since i've talked about OSStudio, for which i apologize to everyone who followed me specifically for updates on that. Note on that bit in a moment.

i didn't realize just how much there was going to be to the basic electronics behind this project, so i've been spending some time learning. Been obtaining parts slowly, and schooling myself on electronics basics. i think i do have some idea of what the next steps are now that i've covered some of the knowledge gap.

The next step is specifically to work on getting audio into and out of an analog system -- probably starting with a line source. Once we have working line in and out, next step will likely be microphone in and out, and then hi-z sources (e.g. electronic guitars). When we have analog audio fashioned into something usable, then converting to digital and getting it into computers in the next step. There will be some coding at that point... which is probably the next knowledge gap!

And onto the bit i mentioned near the beginning. i'm working on setting up a new Fedi account specifically for the project, where i intend on posting further updates. i will likely make a reply to this post with the account name, once it has content on it.

Hopefully talk to y'all again soon!

#OpenSourceStudio #DIY #AudioEngineering #OSStudio

Hey all.
i have updated the Vision for the OpenSourceStudio project here: osstudio.wiki.klisglitch.space

i spent most of today trying to review our options when it comes to the Ethernet backbone. Have decided that AVB isn't the only contender. osstudio.wiki.klisglitch.space

We're making progress, and having great conversations in our Matrix chats. You can find our community here: matrix.to/#/+osstudio:matrix.k We look forward to talking with you!

#AudioEngineering #OpenSourceStudio #DIY #OSStudio

So. Today, i received a package of fasteners that i ordered last week. Getting them allowed me to finally put together the 1U rack section. i got the necessary screws to fit the nuts i got with the 3U rack, and they fit perfectly. The only issue with this shipment: the square nuts i got are just a little oversized, and don't fit in the rails. Grah!
But: for now, i can lay out some parts of the modules, on both 1U tiles and the 3U parts.
And a power strip can hold the rack upright! Progress?

So, where that puts me: need to obtain LCDs, LEDs, and buttons, for module layout.
For starting electronics: some actual ESD parts, breadboard, the aforementioned parts from layout, ADC, DAC, the parts to make a preamp, a few DC to DC power converters, um... crap. Some other parts? Guess it's time to make a real list... At least i already have a microcontroller, i think. Although i may have fucked it up, at which point, another hits the list...

#AudioEngineering #OpenSourceStudio #DIY

And with this, i can start laying out Module fronts! ... well, sorta! Still need to get my hands on some displays...

Got 3U rails in the other day, 1U rails and the 1U rack ears are in the mail. Attached the 3U to the 12U rack rails today!

#AudioEngineering #OpenSource #OpenSourceHardware #DIY #OpenSourceStudio

... i started having thoughts a while back, in a particularly annoyed moment, about the proprietary nature of so much of the audio/music industry. As an audio engineer, this is a particularly true sentiment, as so *incredibly* much of the gear my fellow engineers and i use is entirely proprietary -- both in the software and hardware departments. From how our soundboards are not-entirely-but-close-enough-to black boxes, to how the new digital age has brought so many new proprietary "standards" -- Dante, AES50, etc. There are actually open/non-proprietary standards out there for audio and video transmission over networks, and for sound control. There is no seriously good reason why we should throw hundreds of thousands of dollars at single pieces of equipment.

With this in mind, i started a new project: OpenSourceStudio. The goal of the project is to create open hardware versions of the tools we use on a daily basis in our work, and to allow for a far more modular studio. So far, i have a... start, in the form of a wiki. While this project is still early stages, i believe it has great potential to make our lives better and our work easier.

The wiki: osstudio.wiki.klisglitch.space (Registration is closed, and edit access can be requested through the Matrix community.)
Matrix community: +osstudio:matrix.klisglitch.space

i look forward to working with those of you who see potential in this project! And please, spread the word! Thank you!

#AudioEngineering #OpenSourceStudio #OSStudio