I just installed my new audio expander on the meta module (v2.11) I checked the system menu telling me that “audio/cv expander connected”
Now that I am testing it for the first time I have to recognize that only the outputs work and only for audio, means Input 7-12 no function, Output 9-16 only audio, no CV.
Have I missed a point of configuration somewhere or might it be a broken one..?
The expander has no notion of audio or CV, it just sends out signals (DC-coupled). What are you seeing that tells you audio works but not CV? Feel free to share a patch file.
Doing the hardware test will rule out any patch issues. Go to Settings > System > Check Hardware.
Each of the output jacks 9-16 on the Audio Expander will have a different frequency sine wave, starting at 60Hz (jack 9) up to 7.6kHz (jack 16). Each sine wave should be about 17Vpp (roughly -8.5V to +8.5V)
If you patch a 1V/oct sequencer output (or any CV signal) into input jacks 7-12, the frequency of the sine wave on the corresponding output jack will change:
Input 7 modulates Output 9,
Input 8 modulates Output 10,
Input 9 modulates Output 11,
etc..
The inputs should be calibrated to 1V/oct so 1.00V will play a certain frequency and 2.00V will play one octave higher. If the calibration is off, you could do a re-calibration, but first just see if you’re getting signals.
You can can check against the internal (non-expander) audio ins and outs, they should be doing the same thing on the Check Hardware page, except the frequencies start at 40Hz.
Thank you for your detailed answer!!
I checked the expander with the following settings:
CV TEST
Inputs are routed to modulate a VCO, Outputs are sending LFOs.
An external LFO works on Inputs 1-6 of the MM but not on Inputs 7-12 on the expander.
Same with the outputs, an external VCO gets modulated by Outputs 1-8, nothing on Outputs 9-16.
AUDIO TEST
Inputs are routed to a scope, outputs are sending a sawtooth wave.
Same as above inputs 1-6 receive an external audio signal, no input on 7-12.
All Outputs are working perfect, everything fine on 1-16.
I will do the Hardware Check on the MM later this evening and tell you what has happened!
CV TEST.vcv (2.3 KB)
CV TEST.yml (11.9 KB)
AUDIO TEST.vcv (2.0 KB)
AUDIO TEST.yml (5.0 KB)
OK, thanks. Both those patches perform normally on my system. It’s odd that the audio test would generate output on the Outs for you, but not the CV test, since both generate a signal.
It could be a calibration issue: corrupted calibration values can cause the outputs and inputs to be scaled to the point that they’re essentially zero.
Also, it could be a cable issue, if it’s not securely attached. Or the unit could have a fault.
Try the hardware test when you get a chance. If that fails, then we’ll do a re-calibration (it’s fast and easy).
The good news are: it is working!!
I did the Hardware check and got signal on the outputs of my expander.
Then I checked the input voltages in “CV JACK CALIBRATION” and got input on jack 1-12.
Then I reloaded my CV TEST and AUDIO TEST patches and now they work perfect.
The bad news are: I absolutely don’t know what has happened!!
The problem was solved by just opening the hardware check..??
I hope whatever has happened will not “undo” one day (one day after guarantee…:))
The expander is working fine - problem kind of solved!
Again I would like to thank you spending your time on such a detailed answer - great support!
And thank you for developing this great instrument, can’t wait for the button expander…
OK, great! Hmm, I don’t know, maybe the cable is loose? Or could be some issue with multiple versions of the patch file, who knows… but glad it works
Hi,
Same problem as you. After “CV JACK CALIBRATION”, inputs give values in to work but not outputs…I will send it back to seller…
guy
Hallo
Today, after about two months of successful use, i encountered a problem with the In/Out expander.
I noticed that the inputs were no longer working in conjunction with the patch, meaning they weren’t triggering any modulation.
The audio expander was shown as installed in the meta settings, but it wasn’t functioning as expected.
Even after testing with various other patches, the problem persisted.
Powered the rack off and on again, and everything worked as it should.
It’s likely a firmware issue.
Friendly regards
1 Like
I’ve also had this problem and can’t really work out what’s causing it. The expander is always listed as installed but output just stops from the jacks and only a reboot can fix it. I’ve been trying to work out exactly how to reproduce it but no luck so far.
1 Like
I’ve had similar issues
1 Like
If anyone can replicate this issue with a specific patch and a specific set of circumstances, that could help narrow down the cause.
I have the patch on my 4ms card.
However, i can’t say or describe why the expander failed or when.
How can i send it to you?
You can copy the yml file to a phone or computer and send it as an email attachment to: 4ms@4mscompany.com but we are more likely to find the cause if you can provide more detail than just the patch.
Hi @danngreen
Same issue here. Almost impossible to reproduce. It happens sometimes during playback of any of patch. Video
Have to reboot. Than, it works again.
Cheers.
1 Like
It’s possible what’s happening is due to the cable between the MM and the Audio Expander. If it gets noise it can loose connection, and then the MM stops detecting whether the jacks are patched or not. Then it stops outputting or reading from the inputs because it thinks the jacks are not patched.
Inspect the cable is firmly attached on both sides, and make sure you’re using the cable we supplied with the module. Place the Audio Expander directly next to the MetaModule (no other modules in between). Also make sure when the modules are installed in your case, that the cable doesn’t run behind any other modules, or run close to any other modules or your power supply. Ideally the cable goes cleanly from MM to Expander without any folds, bends, or twists. It should not get close to any potential sources of noise (like, other modules).
I’m able to reliably cause this issue to happen by wiggling the cable a lot. The MM is supposed to recover from errors, but if it gets too many errors, it stops trying. I can play with that limit, and make it try harder to reconnect. But first see if you can solve it by making the cable’s path as clean as possible.
having the same issue here, meta aio is directly to the left of the module, it always shows as connected and I’ve done a factory reset on the system, tested the cable connections, fully updated… still nothing out of the outputs. keep waiting for an update to fix but this hasn’t worked since purchashing at buchla and friends. My meta’s been buggy since day one though so thought it was something to with that but looking above it appears to be a more common issue.
edit, tried moing it to the right side between the mm and buttons and same issue, no actual connections but shows as connected. also it’s creating some kind of very noticeable hum or grounding noise.
2nd edit, several hours of testing and fiddling later : ) so I’ve tried multiple combos, wifi/no wifi, buttons / no buttons… also all outside a case on supports. So having an absolutely clean path from the aio seems to increase the possibility that the aio outputs from 0 to working maybe 10% of bootups, I don’t see how that’s sort of open uncluttered scenario can play out in a case with the all the other expanders though. Just connecting the WiFi, buttons and aio already creates a rats nest behind the mm. Either way it’s still only working a small fraction of loads. When the aio is connected I’m also getting quite a bit of noise. Had issues with the mm booting at all with the button expander for about an hour but that seems magically resolved for now. Just to mention I’ve also tried with several patches just to be sure it wasn’t being caused by some random module. Resorted to just running a steady clock and gate out so I can quickly see if there’s signal or not.
1 Like
Definitely sounds like a hardware issue. Just replied to your PM to get it resolved.
Just a side note. I just installed the latest update after I couldn’t use my MetaI/O ext. with the previous version. It wasn’t outputting any voltages.
Since then, it’s working again.
Is it possible that under certain circumstances parts of the firmware could be damaged and that a simple reinstallation should fix everything?
@danngreen, I’m also having a problem with the I/O Expander but with a twist. I hadn’t used the expander for a while but yesterday I wanted to create a 6-voice MIDI to CV/gate interface to use my Sensel Morph with my SWN, so I made the patch below minus the waveforms. I was only getting the first four output pairs which are mapped to the MM, but not the pairs mapped to the expander. I removed the modules from the system I had them in to check the cables and put them in their own skiff, then ran the hardware check which worked. Tried the patch again and it still didn’t work for the expander.
I next looked at the MIDI mapping on the MM and saw “?” next to the last two pairs instead of assignments to the expander. When I clicked on one of them, the module froze and I had to power cycle. As a final test to see if any signal would connect to the expander I added waveforms and CV to the last four connections - they work but the MIDI connections still didn’t. I’ve included both the final VCV and YML files for you to look at.
MIDI_6-note_Poly_MM_w_waves.vcv (1.8 KB)
MIDI_6-note_Poly_w_waves.yml (2.4 KB)
(edit) Forgot to mention that I am on the latest firmware.
Hallo
Use a simple configuration with Befaco Rampage but can’t use the expander. Multiple switch on/off my META but not working all the outs in contrast to the meat outs.
Rampage.yml (5.2 KB)