LinuxMusicians

How exactly did you do it? For Ubuntu 18.04, this should work (provided you have source repositories enabled): BLUEZ_ORIG=bluez_5.48.orig.tar.xz BLUEZ_UBUNTU=bluez_5.48-0ubuntu3.2.debian.tar.xz BLUEZ_PATH=bluez-5.48 sudo apt-get build-dep bluez --yes sudo apt-get install build-essential libasound2-...

Took a while, but I finally got myself a Yamaha MD-BT01, and while it doesn't work out of the box in Ubuntu 18.04, all that is required to get it working is to recompile bluez with --enable-midi.

I'm trying to get my old copy of Jam Origin's MIDI Guitar working with LinVST. I'm able to use its internal synths just fine, but when enabled, MIDI out doesn't produce any output. Does LinVST support VST MIDI out at all, and if not, how feasible an addition would it be?

To the people running 1.2.9: have you also tried recording multichannel audio for extended periods of time (as in, not only testing it for a few minutes)? On page three, Musinux explicitly mentions having experienced these issues on many firmware versions including 1.2.9+479. I haven't tried that pa...

I got a suggestion to try "v1.2.4+201 (Release Date 2015-12-01)" and a reminder that MOTU doesn't officially support Linux which is about what I expected. I've now tried that version, and the results are the same as with v1.2.8+378 that I tested in July: everything seems to work fine unti...

In the pro audio driver readme, they say that 48 is a good starting point. I think my ultralite defaulted to 64. Have you tried increasing the safety offset? I've tried setting the host safety offset to both extremes and to various values in between them, with no perceivable difference. This with t...

Has anyone successfully used any wireless MIDI transceiver such as the Yamaha MD-BT01 or the Quicco mi.1 in Linux? I have a device I'd like to occasionally sysex, but I'd like to avoid unnecessary cabling if possible.

Woah, sounds promising! What are the changes exactly?

Drumfix wrote:If that's the case i would recommend to prevent the driver from changing the sample rate and pitch

I've tried this to no avail. The same glitch occurs even after disabling sample rate and pitch changing.

How can I tell when that patch gets merged into the kernel? I'm not familliar with how Linux kernel releases are managed, but the patch in question: https://github.com/tiwai/sound/commit/58cabe8715f20b7fb33431bb1f2c5bd7a438b11b is currently in Takashi Iwai's "for-next" branch, which I ass...

Thanks for the workaround! It indeed fixes the fonts. Everything looks nice and crisp now.

Earlier this week I did some minor kernel hacking, including backporting the aforementioned patch by Adam Goode to my current kernel (Ubuntu's 4.15.0-29-generic*) and creating quirk entries to get rid of the "clock source 1 is not valid" messages. None fixed the bitcrushing issue. It's a s...

When trying out the latest beta on Ubuntu 18.04 on a hidpi display with UI scaling set to 200%, the fonts are very blurry. A cropped screenshot of About REAPER -> Changelog: https://0x63.org/reaper-fonts-linux/fonts-reaper.png The same text copied to LibreOffice Writer using the same font and colour...

Unfortunately, I can now confirm that while downgrading the firmware to 1.2.8 did solve the problem I was initially having with the current firmware revision, it didn't fix all glitch issues for me. While working on a project today, recording and playback worked normally for a good while, but eventu...

I also just happened to come across this interesting ALSA patch notification from two days ago: https://www.spinics.net/lists/alsa-devel/msg80348.html If the audio device is externally clocked and set to a rate that does not match the external clock, the clock will never be valid and we cannot set t...