60 karma · joined April 5, 2015
This is the mail I sent them in January. Still waiting for a response:
> (This is a pretty technical sales question)
> I wanted to know about the ECC compatibility of Asrock Rack X470D4U > In the specifications (https://www.asrockrack.com/general/productdetail.asp?Model=X...) it says the following:
> "*For Picasso Ridge and Raven Ridge CPUs, ECC is only supported with PRO CPUs."
> However, there is no such thing as "Picasso Ridge". There is however Pinnacle Ridge and Raven Ridge. Perhaps a mistake?
> So I was wondering what AMD CPUs had full ECC compatibility (so both detection and correction)
> Does the AMD Ryzen 5 1600 have full ECC support on that board, for example?
For example, a technique of masking distortion (or clipping, rather) is adding something with rich harmonic content (a trumpet for example) to parts that are expected to be hitting the wall and otherwise distorting / clipping.
Would trumpets be there otherwise? I don't know, but I'm sure producers are aware of the limitations of digital audio and as such adapt the music to it.
Might be unnecessary if deepfake technology is used.
#### Upload file to 0x0.st (The Null Pointer) - A filehosting service.
# Usage: nullpointer_upload <file>
nullpointer_upload () { curl -F "file=@$1" https://0x0.st ;}I wonder if the actual video conferences have been recorded. I'm very curious to see them.
Imagine offering an option to switch to only CC music. That would boost exposure of (usually) independent artists while at the same time clearing streamers from any copyright issues.
As an independent music producer myself, I for one would love the notion of my music being included in a game like this, even for free.
This reminds me of one of the first articles I've read about Linux and open source in general. It was about a CEO (and largest shareholder) of Medsphere Systems Corp, who open sourced their tech stack (I believe called OpenVista) and was promptly sued by his own company (!)
Unfortunately it seems that the sands of time have eroded the original content (which was apparently hosted on linux-watch.com, which now redirects to a VPS provider), but I've still managed to find something [0] [1] [2]
0: https://70.42.23.9/servers/a-medical-open-source-legal-hell-...
1: https://medicalconnectivity.com/2007/10/25/medsphere-settles...
2: https://www.informationweek.com/medsphere-settles-lawsuit-wi...
Wow. Any source for this?
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.
You can also look at Open Sound Control, as it was once intended as a replacement for MIDI.
Not only that, but it's not trivial to combine with DAWs because of jitter.
If that were so easy then I don't think much of these cheatsheets would exist.
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.
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.
https://old.reddit.com/r/MechanicalKeyboards/comments/9g0e24...
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.
> We offer part time courses for some of our tracks. Part-time course hours are Monday-Thursday 6 p.m. to 9 p.m., Saturday 9 a.m. to 12 noon Pacific.
Are these times also for EU students?