|
o_C
Mar 17, 2022 20:02:09 GMT
Post by funbun on Mar 17, 2022 20:02:09 GMT
I'm trying to use o_C, but not having much success. Okay, I'm trying to use Quantermain as a quantizer. It simply isn't reading any of the CV inputs. I selected input 1 at the CV source for output A, but I'm not getting anything. The oscillator doesn't change notes or anything. I'd tried a simple triangle LFO and my SEQ16 as the CV to be quantised, but I'm getting nothing.
Do I have to calibrate the module at all? Am I missing anything?
|
|
|
Post by funbun on Mar 17, 2022 20:10:03 GMT
I think I got it! You gotta have a trigger source and cv source plugged into to each channel. Whew! This is going to be a deep module. It'll be well worth it though. I hope to have a pair of these running, one with the standard and one with hemisphere.
|
|
|
o_C
Mar 17, 2022 22:43:25 GMT
via mobile
funbun likes this
Post by tIB on Mar 17, 2022 22:43:25 GMT
Oh nice, wasn't aware these were out there yet.
|
|
|
o_C
Mar 17, 2022 22:53:42 GMT
tgergo likes this
Post by funbun on Mar 17, 2022 22:53:42 GMT
Yeah, I literally got mine in the mail today. I didn't realize Quantermain had four Turing machines! My goodness! That's like buying four rbss modules. Given that the o_C has dual sequencers, I could easily replace my three SEQ16s and SEQ8 with a couple of these things. Save a whole lot of space in the rack.
|
|
|
o_C
Mar 17, 2022 23:30:59 GMT
via mobile
funbun likes this
Post by tIB on Mar 17, 2022 23:30:59 GMT
Yeah, I literally got mine in the mail today. I didn't realize Quantermain had four Turing machines! My goodness! That's like buying four rbss modules. Given that the o_C has dual sequencers, I could easily replace my three SEQ16s and SEQ8 with a couple of these things. Save a whole lot of space in the rack. That's pretty much where I'm at with it - goodbye quantiser and lfos...
|
|
|
o_C
Mar 17, 2022 23:33:37 GMT
funbun likes this
Post by dizzeesatchel on Mar 17, 2022 23:33:37 GMT
Nice to hear these are out there - hope that means the ‘in production’ email will be hitting my inbox soon!
|
|
|
o_C
Mar 18, 2022 6:01:25 GMT
via mobile
funbun likes this
Post by lukylutte on Mar 18, 2022 6:01:25 GMT
Nice if they start shipping 👍. Definitely think waiting for mine! Only took one but might take more to put in each case...
|
|
|
Post by robertlanger on Mar 18, 2022 8:16:03 GMT
I think I got it! You gotta have a trigger source and cv source plugged into to each channel. Whew! This is going to be a deep module. It'll be well worth it though. I hope to have a pair of these running, one with the standard and one with hemisphere. Great to hear you like it! Indeed, this thing is extremely deep... We are just producing a new batch, a small hint: The Teensy processor boards that these module use got a bit difficult to obtain and if yes, for an increased price (the "usual" chip crisis 🤷🏼♂️); therefore we will have to increase the module price by a small amount (around 5 EUR) soon...
|
|
|
o_C
Mar 25, 2022 5:48:18 GMT
funbun likes this
Post by azybcxw on Mar 25, 2022 5:48:18 GMT
I received my o_C with hemisphere today. Is the following behaviour to be expected? ( i'm using the scope-applet from hemisphere to measure the voltages; and a multimeter ) - The Outputs are fine, but the Input-Range is only ~3.3V ( on all 4 cv-inputs ) - when i connect ground to any cv-input, it's voltage drops by 0.8 volt ( i would have expected no input = no voltage; but no input is 0.8v ) - when i received it, with nothing connected to an input, the voltage was about 4.1 volt ( going to 3.3 when connected to ground and up to 6.6 with a voltage ) - within the 3.3v-range, the scaling is fine ( 1v added to the input adds 1v to the reading; at the end of the range, the voltage gets clamped ) I tried calibrating, that removed the initial 4.1V offset. But it didn't help with the 3.3V-range, nor with the 0.8V-offset when nothing is connected. I attached an image from the adc-debug-screen. On eurorack o_c, i would expect a value of around 2730 on the right column; is this different with the aemodular-version? Attachments:
|
|
|
o_C
Mar 30, 2022 13:57:37 GMT
Post by funbun on Mar 30, 2022 13:57:37 GMT
Tell me if I'm wrong, but the Teensy micro-controller is only 3.3v.
|
|
|
o_C
Mar 30, 2022 15:56:04 GMT
funbun likes this
Post by azybcxw on Mar 30, 2022 15:56:04 GMT
The teensy has 3.3V, that is right. But i would have expected the 5V of ae to be scaled down to 3.3V, not clamped. ( and by calibration, o_c would scale it up again to 5V in the software ) My o_c-Outputs are 0-5V, only the inputs are not.
It's fine if that's the expected behaviour ( some hemisphere-applets won't work though ), i'm just not sure it is.
|
|
|
o_C
Mar 31, 2022 15:08:54 GMT
pol likes this
Post by robertlanger on Mar 31, 2022 15:08:54 GMT
I received my o_C with hemisphere today. Is the following behaviour to be expected? ( i'm using the scope-applet from hemisphere to measure the voltages; and a multimeter ) - The Outputs are fine, but the Input-Range is only ~3.3V ( on all 4 cv-inputs ) - when i connect ground to any cv-input, it's voltage drops by 0.8 volt ( i would have expected no input = no voltage; but no input is 0.8v ) - when i received it, with nothing connected to an input, the voltage was about 4.1 volt ( going to 3.3 when connected to ground and up to 6.6 with a voltage ) - within the 3.3v-range, the scaling is fine ( 1v added to the input adds 1v to the reading; at the end of the range, the voltage gets clamped ) I tried calibrating, that removed the initial 4.1V offset. But it didn't help with the 3.3V-range, nor with the 0.8V-offset when nothing is connected. I attached an image from the adc-debug-screen. On eurorack o_c, i would expect a value of around 2730 on the right column; is this different with the aemodular-version? - The voltage drop from open inputs to grounded is by design; it has to do with the "virtual ground" that is necessary in a single-supply system like AE plus the non-availability of switching sockets. If this is an issue, we could add a modification maybe. - "up to 6.6 with a voltage" is astonishing; no voltage should be higher than 5V in AE. Did you measured this at the output with a multimeter? - At the moment I cannot explain the 3.3V clamp for the inputs; I will check this in depth next week and give an update. In general, The AE O&C should behave like the Eurorack version, but with the limitation of "no negative voltages" and "output voltages limited to 5V (theoretically; practically it should be 4.5 volts). As background info: The firmware is 100% identical with the eurorack one; for this was important to avoid modifications every time the firmware gets updates.
|
|
|
o_C
Mar 31, 2022 17:24:18 GMT
Post by azybcxw on Mar 31, 2022 17:24:18 GMT
- I measured the inputs, not the outputs ( ... i used the outputs to measure the inputs; but the outputs are fine as far as i can tell ) - The 6.6volt is just o_c's interpretation / calibration. I'm reading this from the scope of o_c-hemisphere. - The real input voltage comes from o_c (hemisphere -> voltage-applet), ae ( 4attmix dc ) or mordax data and is 0-5V. ( triple checked with ae-meter, a multimeter and mordax data ) - My o_c came calibrated to 4.1V when no Input was connected ( the range being 3.3V when grounded, up to 6.6V when receiving 3.3v or more ). - all 4 cv-inputs behave the same; 1V = 1V ( with offset from calibration ), so tracking seems fine until it's getting clamped I tried calibrating the inputs ( only the adc-pages ). First to 0V when grounded. Then to 2.5V when no input is connected. No matter which calibration. The voltage drop between no-input and ground is always 0.8v ( that's fine by me ), and it will always clamp when input is more than 3.3V. ( by intuition: it feels like the voltage drop should be 2.5V, it would definitely add up to 5V if it were. So maybe that's what is wrong? ) I also checked the debug-display which shows raw-input-values. ( the one in my picture; you get there by keeping the right encoder pressed and tapping the left encoder 3 times; should work on both firmwares ) It shows the same behavior ( voltages above 3.3V don't change the value that is displayed ). Judging from the o_c troubleshooting-page ("some or all of the CV inputs aren’t working correctly") i would ask: could my lm4040 or mpc6004 be broken? But i don't know what to look for.
|
|
|
o_C
Apr 2, 2022 10:32:06 GMT
funbun likes this
Post by 101 on Apr 2, 2022 10:32:06 GMT
I've ordered an o_C (original firmware). Very excited. The generative and modulation possibilities look mind boggling.
|
|
|
o_C
Apr 5, 2022 18:06:32 GMT
funbun likes this
Post by robertlanger on Apr 5, 2022 18:06:32 GMT
- I measured the inputs, not the outputs ( ... i used the outputs to measure the inputs; but the outputs are fine as far as i can tell ) - The 6.6volt is just o_c's interpretation / calibration. I'm reading this from the scope of o_c-hemisphere. - The real input voltage comes from o_c (hemisphere -> voltage-applet), ae ( 4attmix dc ) or mordax data and is 0-5V. ( triple checked with ae-meter, a multimeter and mordax data ) - My o_c came calibrated to 4.1V when no Input was connected ( the range being 3.3V when grounded, up to 6.6V when receiving 3.3v or more ). - all 4 cv-inputs behave the same; 1V = 1V ( with offset from calibration ), so tracking seems fine until it's getting clamped I tried calibrating the inputs ( only the adc-pages ). First to 0V when grounded. Then to 2.5V when no input is connected. No matter which calibration. The voltage drop between no-input and ground is always 0.8v ( that's fine by me ), and it will always clamp when input is more than 3.3V. ( by intuition: it feels like the voltage drop should be 2.5V, it would definitely add up to 5V if it were. So maybe that's what is wrong? ) I also checked the debug-display which shows raw-input-values. ( the one in my picture; you get there by keeping the right encoder pressed and tapping the left encoder 3 times; should work on both firmwares ) It shows the same behavior ( voltages above 3.3V don't change the value that is displayed ). Judging from the o_c troubleshooting-page ("some or all of the CV inputs aren’t working correctly") i would ask: could my lm4040 or mpc6004 be broken? But i don't know what to look for. Now I investigated the clip issue of 3.3 volts at the inputs; seems I could identify the cause. Can be fixed with an additional resistor - would you dare to solder a bit? Just PM me about the details.
|
|
|
o_C
Apr 5, 2022 22:41:28 GMT
funbun likes this
Post by dizzeesatchel on Apr 5, 2022 22:41:28 GMT
I don't have my o_C yet and don't fully understand the problem either but i don't mind a bit of soldering and would be interested to know more, if possible
|
|
|
Post by 101 on Apr 6, 2022 8:24:13 GMT
Please solder mine up before it's sent out
|
|
|
o_C
Apr 6, 2022 8:46:09 GMT
funbun likes this
Post by pt3r on Apr 6, 2022 8:46:09 GMT
Please solder mine up before it's sent out
|
|
|
o_C
Apr 6, 2022 13:41:57 GMT
via mobile
nols and jota like this
Post by lukylutte on Apr 6, 2022 13:41:57 GMT
Mine just went to the post. So I guess it's too late 😂. However, since I totally don't understand why and how it's an issue or why even looking into this,it's totally fine.
|
|
|
Post by pt3r on Apr 6, 2022 14:07:46 GMT
Mine just went to the post. So I guess it's too late 😂. However, since I totally don't understand why and how it's an issue or why even looking into this,it's totally fine. This is a bit like the pitch issue with the OG firmware for CIRRUS which was no issue for me until someone else noticed it.
|
|
|
o_C
Apr 6, 2022 15:05:29 GMT
via mobile
pt3r and jota like this
Post by lukylutte on Apr 6, 2022 15:05:29 GMT
Same 😂
|
|
|
o_C
Apr 10, 2022 20:41:53 GMT
Post by dizzeesatchel on Apr 10, 2022 20:41:53 GMT
I don’t understand a lot of what’s going on with this module yet but it did seem worth recalibrating the CV inputs? I ran through the calibration instructions and where the CV inputs were supposed to read 0 with nothing connected it was showing more like 1700 - adjusted this down and it does seem like the input is more ‘centred’ at least when sampling CV into Copiermaschine …but also i wasn’t sure if this offset was something to do with adapting to AE voltages. Also at least for me the left encoder scrolled in the opposite direction but this is very easily fixed in settings
|
|
|
o_C
Apr 20, 2022 13:19:46 GMT
Post by funbun on Apr 20, 2022 13:19:46 GMT
How do you hook up the voltmeter?
|
|
|
o_C
Apr 20, 2022 20:09:12 GMT
funbun likes this
Post by dizzeesatchel on Apr 20, 2022 20:09:12 GMT
I didn’t actually use a multimeter - don’t have one - it’s only needed for calibrating the DAC according to the guide so i just skipped that. Would be interesting if someone with an appropriate meter ran through the whole calibration and could clarify whether it’s actually necessary or not
|
|
|
o_C
Aug 18, 2022 21:59:24 GMT
funbun likes this
Post by davesworld22 on Aug 18, 2022 21:59:24 GMT
Hi - I am having issues. Any chance there is a schematics to look at with voltage test points on it for the o_C? Is it the same as the schematic in GitHub?
Thanks in advance, David
08/20/22:2 Anyone? Bueller, Bueller?
I am trying to hook up a guitar through Zoia, mixing the guitar and o+C before the Zoia. The attractiveness of this o_C product is the voltages used to power and the octaves available. Except, I am having issue and want to check the schematic for this open sourced product.
08/21/22: Well, I decided to void the warranty and open up the module from the front panel. Sitting in the upper right near some smb resistors and capacitors was a small solder splash. Easy to remove, but since I applied power, not sure if this may have affected the circuitry. Right now, I am fighting the dare to reapply power and try again. Would love to take a peek at that schematic to see the area the splash was in and find out if I may have a problem.
08/24/22: The non-responsive response to my inquiry on this issue is puzzling. I cannot recommend this product, or any other AE Modular products as support is lacking. I will inform the seller of the issue I found and seek a refund.
|
|