#41

I built 4 ornament and crimes just to use the hemispheres!
I think its a great work you have done :slight_smile:

#42

Sorry, didn’t mean to sound like I expected you to do it, because I think you already did a lot.

That MIDI/CV interface sounds really interesting. In some near future I want to try to code some kind of musical virtual machine for hemispheres. Quantized CV inputs could be treated as opcodes when programming the machine and CV outputs could be configured to output registers/memory locations or could be written to directly.
For example you could write something like
ATO1 ;; set output1 to send value of register A
LDCV1 ;; load input1 to its own register
LDCV2 ;; load input2
ADDXY ;; sum input1 register and input2 register and put the value on register A
So basically a teletype but on a lower assembler level.
It would probably be 100% impractical but I wonder what could be done with such „general” cv processing virtual machine.

1 Like
#43

In some near future I want to try to code some kind of musical virtual machine for hemispheres. Quantized CV inputs could be treated as opcodes when programming the machine and CV outputs could be configured to output registers/memory locations or could be written to directly.

Woah, that sounds cool!

#44

I’ve recently been eyeing off Klavis Caltrans as a productivity booster with my analog oscillators. Is it feasible the o_C/Hemisphere could calibrate per output in the same kind of fashion?

#45

Hello everyone, I dunno if this bug has already been brought up but I have a weird glitch while using Clock divider/multiplier. It’s very bad when powered up for few minutes, then gets progressively better and disappear completely once it’s “warm”.
The problem is the value of the multiplication/division keeps resetting to the initial value of 1, even when you turn the knob, it won’t scroll between divisions but keep going back to 1. I 've written in a group on facebook and at least other 2 people have the same behaviour. Suggestions?

#46

I have a weird glitch while using Clock divider/multiplier. It’s very bad when powered up for few minutes, then gets progressively better and disappear completely once it’s “warm”.

Clock Divider has two ways to set the divisor/multiplier value: the panel and incoming CV. The Ornament and Crime hardware has no way of detecting the presence of a jack in its CV inputs, so I had to look for non-zero CV values. Since there’s always a bit of noise in the ADC, I can’t just compare the input to 0V; I instead look for values outside of a certain range, or “software detent.”

When your module is cold, it’s reading values outside of this detent range (0V plus or minus about .042 volts), making Clock Divider think that you’re trying to set a divisor of 1 via CV. Since incoming CV takes priority over panel control, it seems like you can’t make changes.

If you’re already sure that calibration is good, the easy solution seems to be to make sure that your module has warmed up. If you need to use the module immediately, try feeding it an offset with Shades or similar.

2 Likes
#47

I’ve recently been eyeing off Klavis Caltrans as a productivity booster with my analog oscillators. Is it feasible the o_C/Hemisphere could calibrate per output in the same kind of fashion?

Ornament and Crime does something like this via References. I removed References in Hemisphere Suite because I didn’t need that functionality, and wanted the flash memory for other things.

However, Hemisphere Suite still observes the References auto-calibration data. So if you auto-calibrate to your oscillators using References, and then install Hemisphere Suite, it’ll adjust for your oscillators.

Note that this might make Hemisphere Suite behave inconsistently between hemispheres. Since Hemisphere Suite focuses more on modulation, while Ornament and Crime focuses on pitch, this sort of output calibration doesn’t fit comfortably into the design philosophy.

1 Like
#48

very interesting! thanks for pointing out and dansimco for asking.

I can easily justify caltrans as a dedicated module because I missed that feature ever since ditching silent way (call me lazy. but calibrating is a pita with some oscillators, and my system has been polyphonic since day one. also great to tune anything that oscillates: filters, maths…).

I enjoy your wonderful work with hemisphere in a small single (stable) oscillator setup. But good to know this would be in there and hackable.

#49

Hi. I’m struggling to understand how scale duet works. I haven’t found any way to patch it so that notes or scales cycle. No matter what, I see no movement on screen and don’t get any output. All other modes appear to be working correctly.

Are there any known issues with the current firmware?

#50

Scale Duet is different from the other Hemisphere Suite quantizers in that it only quantizes when clocked. In other words, it doesn’t quantize continuously. So make sure to provide a trigger to Digital 1. Here’s a simple patch:

  • Maths channel 1 output to CV 1, then set that Maths channel to cycle
  • Maths channel 4 EOC output to Digital 1, then set that Maths channel to cycle
  • Out A/C to an oscillator’s V/Oct input
  • Oscillator to whatever

Scale Duet lets you choose which notes are in the quantized output by moving around the keyboard and turning the notes on and off, an idea stolen from Intellijel’s µScale II quantizer. There are two such scales, and a logic signal to Digital 2 is used to select between them.

3 Likes
#51

Thanks! I’ll try your patch idea.

#52

I suppose that patch worked, but I don’t see any animation on the screen display when using scale duet. All other modes have some visual indication that something is happening. With SD the little cursor under the piano keys never moves ( I expected this to advance with each step to indicate the note being played) and the scale shown on the screen doesn’t switch from one to two.

Is all of that normal behavior?

#53

Yep, that’s normal behavior. The display is used only for editing the scales.

2 Likes
#54

Happy Solstice! I’m pleased to announce the release of Hemisphere Suite 1.8. This release adds an internal clock to Hemisphere, adds interface and Buchla voltage level support for the Northern Light Modular 2OC, and a few other modulation points and enhancements.

Hex files and release notes are here: https://github.com/Chysn/O_C-HemisphereSuite/releases/tag/HSv1.8

16 Likes
#55

Congrats on the release!

Can this release be used with ornament and crime 4 robots (1u intellijel) by pkum audio.

Thanks!

#56

Very cool - the shift register additions seem like something I would use for sure. The gated slew defeat is also nice and it never hurts to have another couple more offset/attenuators. Also, more scales!

#57

Can this release be used with ornament and crime 4 robots (1u intellijel) by pkum audio.

The Variable Output Range requires some additional code, which is in the ocplus branch, and that’s still at 1.7. I’ll have to merge the 1.8 code into this branch. I also need to add some calibration parameters to go up to 10V, which I haven’t yet been able to do without the module crashing :slight_smile:

I’m not sure what happens if you simply load Hemisphere Suite 1.8 into a 4 Robots. Obviously you won’t have access to the range-setting button press (long-hold the Up control button), and the calibration might be iffy. But I’m not really sure what else might be wrong. Maybe it’ll work just fine!

2 Likes
#58

@chysn (or anyone else),
Do I need to cut the power trace on my teensy if I’m going to use hemispheres for midi over usb? I can’t remember if that is needed and can’t seem to find mention of it…

1 Like
#59

I’d say yes. If the teensy is getting power from the module (ie your rack power) then you want to Not use power from the usb Jack (just data)

2 Likes
#60

I’d always cut it on any O_C build

2 Likes