Mes précieux artefacts dans ma piaule à Balmora.
Uncategorized
1
Posts
1
Posters
0
Views
-
Mes précieux artefacts dans ma piaule à Balmora.
-
undefined oblomov@sociale.network shared this topic on
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@shinmera that's fine. all of the linux audio applications that will ever exist have already been written
-
@sixohsix @mcc I would be shocked if RtMidi has a solution for this that isn't sweeping it under the rug and hoping nobody notices. MIDI is the old half-abandoned mall inside your computer.
-
@sixohsix @mcc but ALSA insists that there is a "now", and that "now" is a thing that is real and exists, and has a clock and that clock moves forward in fixed increments, and never throttles, and so on. ALSA, despite also having this concept of batched time in its audio processing model i'm pretty sure, does not seem to believe that midi would ever be processed precisely, or need a be sieved in ~0.02 second chunks.
-
È nelle stazioni di Luciano Erba (Milano, 1922 – Milano, 2010)
È nelle stazioni ferroviarie
dove fili attraversano fili
tesi in alto tra pali e vetrate
è nelle grandi stazioni ferroviarie … https://cctm.website/luciano-erba-italia/#LucianoErba #stazione #poesia #cctmwebsite #anoipiaceleggere #leggere
-
@sixohsix @mcc not in a random userland thread at any rate. time is stretchy. now, the audio thread as it happens is a lot more precisely timed than regular threads, and you can say ah, I'm currently processing ticks N through N + 1024, where a tick is exactly 1/48000 sound card seconds.
-
@sixohsix @mcc this is probably fine in most cases since the events are expired as soon as they're created anyway. a midi packet is HOT HOT HOT and should be processed ASAP anyway. But WHERE is "now"? do you have a clock that if you sample it and then sample it again a second later will give you exactly a second of time between the two samples? no. you do not.
-
@sixohsix @mcc in theory you could build a sequencer that does the same thing as what alsalib does under the hood in the first scenario, but as far as I can tell you can't actually read a common reference point for a given event's time offset, so for all intensive porpoises you only have one time point for everything in both cases: "now".
-
@sixohsix @mcc option 2: you tell alsa you do not care about time stamps: alsa leaves the time stamps in messages as they were recorded if they have them. god help you if you have multiple MIDI streams feeding the same port, because they will either have "realtime stamps" which are time points relative to that the output queue that event was written to, or they will be in "ticks" which is the same thing except the duration is variable
