Fender Mustang - Linux

Started by Elantric, February 01, 2012, 04:27:18 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.


Fender Mustang Linux support - a Linux Editor "Plug" for Fender Mustang DSP series products.

and its confirmed Fender Mustang DSP amps use a USB Class Compliant Audio interface - which means it will connect to an Ipad using the CCK

QuoteHi all,

this is my first post in this great community. Just wanted to share a nice experience I made with my Mustang II.

When I purchased the Mustang II, I did know it will work as audio input device on my Mac. The unit is class compliant, means it doesn't need any driver, just plug and play, the Mac will recognize it automatically. However I did not find any statements about compatibility with the Apple iPad. So I connected the Mustang via Apples USB Camera Connection Kit to the iPad (iOS 4.3.5). To my surprise the Mustang works without any problems. I planned to get me an Apogee JAM interface for the iPad, but as the Mustang does a great job I can save that money :D

I currently use it as guitar input for Mobile GarageBand. To get the best of both worlds, I downloaded a neutral preset for the Mustang from the FUSE preset sharing area, that does not change the original tone of the guitar. With this preset I can drive the built-in Guitar Amp instrument in GarageBand. When I want to record with one of the great Mustang presets, I create an Audio Recorder track and record onto that track.

The monitoring is done thru the iPad headphone output (same as you would do with the JAM). If you prefer to monitor thru the Mustang headphone output, you may want to connect the iPad output to the Mustang AUX input. I didn't try that so far, but it should work. After all the purpose of the AUX In is to feed playback tracks into the Mustang.

Fender you did a great job on the Mustang!


About a year ago, I tested my Fender Mustang GT200 amp USB audio connection with Ubuntu Studio v18.0.4, the audio-video-graphics flavour of the popular Ubuntu Linux OS distribution. Ubuntu Studio comes with a variety of audio software pre-installed: Audacity audio editor (including just about every plugin) and the Qtractor and Ardour DAWs. It also has the Linux Multimedia Music Studio (LMMS) pre-installed which is very similar to Fruity Loops.

I tried recording from the amp via USB into Audacity first. I got some wave forms but the audio was cutting in and out and badly distorted. I contacted Ubuntu Studio support via its Telegram chat app channel and with the help of some very obliging support volunteers, they quickly managed to sort out the problem, with me supplying info from my end to their questions. I later tested the amp in Qtractor and Ardour with positive results there too. So, the GT200 works well now in Ubuntu Studio. I have no reason to doubt that the GTX amps will work with it also.

Ubuntu Studio support has now migrated to the Matrix instant messaging/chat network. Element is the recommended app to connect to it on Android.

Ubuntu Studio OS uses a low latency kernel and the Jack Audio Connection Kit (JACK) sound server daemon to keep latency to an acceptable level. Unlike Windows DAWs, Linux does not need the low latency ASIO4All driver. Ubuntu Studio has undergone intensive development in the past few years. One important outcome is the development of Studio Controls which describes itself as follows:

QuoteStudio Controls is the easiest and best way to configure your Ubuntu Studio installation for real-time audio. Studio Controls has several key features that make it unique:

    Adjusts the CPU Governor for higher processing power as required
    Adds the user to the Audio group for real-time permissions if needed
    Gives control over the JACK Audio Connection Kit

    Bridges ALSA MIDI and PulseAudio to JACK if needed

    Allows for multiple, custom-named PulseAudio Bridges

    Adds USB Devices to JACK when they are plugged in

    Allows multiple audio devices to use JACK at once
    Persists your configuration between reboots
    Shows the status of JACK
    Settings persist between reboots, including JACK's running state

Ubuntu Studio's Studio Controls panel has made things a lot easier for those (e.g. refugees from Windows) who found dealing with Linux's various sound systems confusing and frustrating. But first a word of explanation:

QuoteAdvanced Linux Sound Architecture (ALSA) is a software framework and part of the Linux kernel that provides an application programming interface (API) for sound card device drivers. Some of the goals of the ALSA project at its inception were automatic configuration of sound-card hardware and graceful handling of multiple sound devices in a system. The sound servers PulseAudio and JACK (low-latency professional-grade audio editing and mixing) work on top of ALSA and implemented sound card device drivers. - Wikipedia

For a number of years it used to be the case that having two independent sound servers (PulseAudio and JACK) caused difficulties. For example, if you selected the low latency JACK audio server for recording in DAWs, you would subsequently discover that sound in your browser no longer worked because it relied on Linux's alternative PulseAudio server that could not run at the same time as JACK. So, you had to disable JACK in order to get sound back in your browser! Configuring the various hardware-software inputs and outputs for JACK could also be a challenge for some.

What Studio Controls did was to set up automatic sound bridges, including between JACK and PulseAudio, so that the conflict between them was eliminated. So JACK can now be permanently activated without losing sound in browsers. And it is all controlled from a single Studio Controls panel (see screenshot below)).

In addition this 'connected' version of Ubuntu Studio can now be installed as an optional add-on audio system to any other official flavour of Ubuntu (vanilla Ubuntu, Kubuntu, Lubuntu etc.).