> Heck, a decade and a half ago there were claims that governments could narrow a search for an audio file upload based on the deviation from 60hz on the power line noise - in an audio recording.
I think it was referring to Electrical network frequency analysis, which is to find the time that the recording was made. It compares small changes in mains hum frequency to historic records of the changes. I am not sure how it is in the US, but the UK grid has a single frequency over the network so it wouldn't work for finding the location.
The propagation of waves is very fast, but wouldn't distance from multiple large sources or sinks fluctuate the frequency just slightly based on distance?
I long for the day I can build a Mini-ITX laptop. I think it's doable considering you don't go for a dedicated GPU, but alas... the documentation on that is not abundant and I do not have the necessary CAD knowledge yet.
There are no issues with using MIDI in a DAW because of jitter: jitter is a problem of device drivers, hardware and badly implemented MIDI handling inside the DAW. It works remarkably well.
AFAIK it's only capable of 14 bit resolutions for things like modwheel. CC can only have 128 values, right?
Also, isn't it safe to say that by the nature of USB MIDI interfaces, they are not well suited for MIDI operation? As in: Since USB drivers buffer messages, it causes jitter. Is that correct? Are there USB MIDI interfaces / drivers that don't have these issues otherwise?
Added to that: MIDI is mostly used for interfacing with external hardware, and as such you're dependent on the external hardware's MIDI implementation, which isn't always superb to say the least unfortunately.
No, there are many parameters with 14 bit resolution. Precisely how many depends on exactly how you interpret the MIDI specification.On the order of 64, plus or minus depending.
Sure, USB interfaces might be problematic but it's very dependent on the precise hardware. My MOTU Ultralite AVB is basically unusable because of jitter; my MidiSport 2x2 (also USB) is extremely usable and has extremely low jitter. So you cannot make blanket statements about it being caused by using USB for MIDI.
I've been fantasizing a little about a new modular format, or at least a new category of synth controllers, taking advantage of the higher resolution of MIDI 2.0 for some modulation signals. I could be wrong, but I thought MIDI 2.0 was supposed to potentially be faster/more timing accurate too.
I'm not overtly familiar with MIDI 2.0, but from what I've heard it does fix most of the issues of the old MIDI. However, if you transport your messages over DIN ports, all bets are off.
You can also look at Open Sound Control, as it was once intended as a replacement for MIDI.
OSC has never, ever been even remotely close to being a replacement for MIDI.
Every MIDI message (well, almost every MIDI message) has a defined semantic associated with it. The receiver of the message might choose to reinterpret that, but the default semantic is still defined by the standard.
There is not a single standard OSC message. The only thing that is standardized in OSC is the format of a message. Both the receiver and sender have to agree to a specific set of messages, with a specific set of semantics.
Trivial example: you want a MIDI-driven synth to start playing middle C. You send it a MIDI NoteOn event with the note number 60. There is no equivalent for this with OSC, not even close. You must know precisely what messages the synth will accept and which ones will mean "start playing middle C".
OSC is cool but it isn't and almost certainly will never be a replacement for MIDI.
The cheat sheets exist because people aren’t learning regex. You don’t need to learn every flavor of regex, just the one or small number you need to know. And once you know the basics, the differences are very minor.
The basic regex is easy, infact an English word is a regex! A dot matches a single character. Star multiple of the previous character. Just that is useful for a lot of cases!
Perhaps adding a "Prerequisites" chapter might further help in getting the intended audience across?
I associate "from the bottom up" approach with something being explained by starting from the very basics and aimed towards someone completely unfamiliar with the subject.
I don't think anything comes even remotely close to the level of productivity and rapid experimentation / prototyping these DAWs can bring to the table.
It's not quite the same thing, but VCV Rack is making incredible and rapid progress into becoming a fully fledged DAW. I find myself using Ableton less and less and Rack more and more. Check it out!
Yes, I'm aware of VCV Rack and it is an amazing open source project. I use Bitwig Studio though, and having The Grid there (which is Bitwig's own modular environment, introduced in v3) is just too convenient to use another one next to it.
Notice how the author had looked up how to do his example in Stack Overflow.
I found that foraging through different man pages looking for a specific thing to do only once is just very time consuming. Luckily looking up information on places like Stack Exchange or even different blogs and forums (which I usually land on after using a search engine) is much more efficient.
Yes, the information contained might not be completely up-to-date or accurate, but at least it sets you up on the right path to search further.
If Mozilla is able to setup Firefox as a turn-key noob-friendly solution for a more secure and private web experience, then I can definitely see this as a sustainable business model.
For that however, many things (which are far from trivial) have to be done. Among other things:
1. Focus on security. That means among other things:
1a: Reducing core code complexity (for example, removing Pocket and integrating it only as an opt-in extension)
1b: More audits
1c: More Rust (and Servo by that extension)
2. Focus on integrating more privacy-enhancing features, such as:
2a: Reducing the effectiveness of browser fingerprinting
2b: Integrating more features from Tor-Browser into vanilla Firefox. Would be even better if they integrated Tor out of the box too.
In fact, Firefox should perhaps aim at 0 difference between TBB and vanilla Firefox.
2c: Reducing reliance on (user-hostile) search engines. Perhaps integrate DuckDuckGo as default search engine in the future?
3. Focus on marketing campaign which includes super noob-friendly (video) tutorials. I'm thinking something in the Kurzgesagt style.
Not sure if this is the right place to shed some light on my issue, but my repo is in the process of being deleted for over a month now [0]
Basically I made some mistakes in that repo and didn't know how to rectify them, so I decided to delete it and then make it again. However the deletion process got stuck it seems.
Wow. Any source for this?