my guess is that the expansion card, like the built in port, only uses a TRRS jack, meaning there are two conductors for audio output from the laptop, but only a single conductor for audio input to the laptop, meaning that you will only be able to get the mono input you are seeing without switching to a usb-c source.
Note: I do not have the audio expansion card, so this is just a guess. messaging support is the best way to get the official answer to this question.
I tried everything listed in the installation guide, without success. A screenshot of the PulseAudio Configuation tab shown the problem. In the profile dropdown menu for the audio expansion card with the 3,5-mm-plug connected only the options “Analog Stereo-Ausgabe” (Analog Stereo Output), “Digital Stereo (IEC958)-Ausgabe” (Digital Stereo (IEC958) Output), and “Aus” (Off) show up. No Option for “Analog Stereo Input” is shown, although according to the marketplace entry Audio-In should be supported. Definitely no idea.
Update: With a usual 4-pole headset connected, the dropdown menu offers the following possibilities. I conclude, that using the input function requires a 4-pole connector and only supports mono audio.
This is not what I expected and for what I paid 20 € for the expansion card + 30 € (!) for the shipment.
It seems I have to buy a usual audio-USB-grabber instead.
My comment here has more information in the specific context of the internal audio on the FW13:
I vaguely recall that a number of years ago, some Macs had switchable 3.5mm audio ports, such that, I think, you could set the interface, for example, to have TRS stereo input and no output, and set line-in vs mic-in; these also had optical input/output on the same port; at the time Apple was still trying to cater to creative fields and a featureful audio interface was a selling point. But a feature like this would require specific support from the chipset (switching between input and output on the same line). At least with the internal FW13 interface, that support isn’t there.
In general, my understanding is that the 3.5mm expansion card is not really significantly better than the internal audio interface of the FW13, at least in terms of features. I don’t see any indication that it would be arranged differently, as its primary motivation is to have a 3.5mm port on the FW16.
It is a bit disappointing in this regard, and there would be room for a more featureful audio expansion card, but the one Framework offers isn’t.
Can we get a confirmation from Framework that the new audio expansion card is mono input only? Could you find out @Matt_Hartley? I had also assumed it was a 3.5mm trs stereo input, but luckily I haven’t purchased yet.
The product page description reads:
The Audio Expansion Card contains a 3.5mm headphone jack, which supports audio input and output. This Expansion Card provides increased dynamic range and improved signal to noise ratio in comparison to the Framework Laptop 13 built-in audio jack.
I think it would be really helpful to update that description to make clear the output is stereo and input is mono - if that’s the case. Product descriptions shouldn’t really allow any room for assumptions either way. Technical specifications would stop any further confusion or disappointment and the hassle of increased support and return requests.
Edit: Also I think it’s worth pointing out that this expansion card isn’t being sold as 16" laptop specific. Increased dynamic range and lower signal to noise ratio is an improvement over the 13" laptops soldered audio output and for some people that’s a reason to buy.
Why assume the output is stereo? That’s not in the specs either.
Like I said in my post, there are no specifications in the description at all. And no specifications allows for assumptions to be made both ways. You expected the input was mono, I expected it was stereo - it’s a coin toss.
Adding tech specs to the marketplace product page removes any possibility of a customer making assumptions and ensures they make an informed decision before purchase.
I agree to fyoosh that precise specifications in the marketplace are recommended.
Besides that: Already before ordering the framebook itself I asked whether the built-in jack was also for stereo input, and this was confirmed. Finding out it did not work led me to discuss this issue with the support, without final result.
So I had the idea the expansion card was also created to tackle this issue, and I read the description in the marketplace the same way as fyoosh does.
I think the proper solution would be to offer an audio expansion card with all those features a desktop pc has: TRS line in, line out and mic in.
What is particularly frustrating about this is that, unlike manufacturers who simply don’t give precise specs, Framework often does, to the point of individual chips, but puts them in blog posts, in employee forum responses, and in files on Github, while the Marketplace often gives little or no specific information. I’m certainly not criticizing the disclosure of the information elsewhere, but it seems like it would be more organized to put it in the Marketplace too. I feel like some parts of Framework’s target purchasers would find the information quite useful, and many others, even if it wasn’t useful to them, would appreciate it being there.
That’s very disappointing. I think the problem here, as I discussed in the other thread, is that the chipset does support stereo input generally (ie, it has more than one ADC), and there is stereo input from the internal microphone, but the wiring and switching mechanism to enable stereo input from the 3.5mm jack is not there. Support should understand the difference between these two things.
I would argue that Github is one of the best places for some information, like the exact chips used or maybe even very precise specs. There is such a thing as information overload for many people. As Framework’s sales expand, more and more regular consumers are buying. We are seeing this happen. People with much less technical knowledge are showing up with questions or just asking if Framework would be good for them as a basic user who’s not tech-savvy. Even very detailed specs, that are useful to you and me, can cause overload for basic users.
Those that truly need very precise specs, that most do not, should be accustomed to doing some research. So they should be able to find much of what they need. I’ll admit, it would be good if Framework could work toward having more available in a single place. Tho, the one time that I pointed out some information on this forum was not present on their Github, Nrp himself responded and had it fixed in a couple of days. And I didn’t raise the issue in the best, most appropriate place. Which would have been on their github. Framework does more than almost any other company I can think of. And we should remember, they are currently still a small, fairly new company. So I feel like, at this point in time, we can do a little research if we really need some minute detail.
But for the 3.5mm Audio expansion card I do think they should note on the item page that it’s a standard jack as found on the majority of laptops, maybe with a link leading to details.
Yeh I agree. I definitely haven’t meant to imply the product listing needs details about which chipset is used etc.
Just the basic specifications for an audio output and input expansion card, which is: whether the 3.5mm output and input jack is stereo and mono respectively. It’s information that can only be helpful to a potential customer.
The rest of the marketplace product descriptions seem absolutely fine. The storage expansion cards include read and write speeds, the USB-C includes power specs and the HDMI card includes the supported resolution and refresh rate.