Ornament and Crime

[gretchen]

has anyone modded Sequins to clock itself internally? Looking at building a small system and it would be really nice to avoid needing an external clock / lfo.

[sakul]

No I hadn’t, thanks for the heads up!

[nurse_plissken]

gonna use my first post to chime in on the Quadraturia mode. I’m honestly considering getting (or building) another O_c for this mode alone(though I’m sure I’d use other apps too). CV over phase and shape is really cool, the XOR and AM options deliver some amazing shapes, and that combined with the predictive tap tempo and freeze makes for a REALLY sweet source of modulation, ranging from slow and smooth to almost chaotic, random stuff that are as related or unrelated as you want!

I really love it.

[naxuu]

Hemisphere 1.6 released:

The theme for Hemisphere Suite 1.6 is timing. Its centerpiece is the introduction of the Vector Oscillator, a waveform generator that allows you to create custom waveforms with up to twelve level/value segments, and then use those waveforms within applets as LFOs, envelope generators, and one-shot or cycling bi-polar modulators.

A full list of updates in 1.6 is here:

• Added Metronome applet, a master clock system that can run in the background to clock other applets, so that Hemisphere Suite sequencers (and other applets) no longer require an external clock. (https://github.com/Chysn/O_C-HemisphereSuite/wiki/Metronome)
• Tuner: Now allows Tuner to function in the right hemisphere when the screen is flipped.
• Added Vector Waveform Editor, a full app that allows you to build and audition Vector Waveforms. (https://github.com/Chysn/O_C-HemisphereSuite/wiki/Waveform-Editor)
• Added VectorLFO, a dual LFO applet that uses custom and preset Vector Waveforms. (https://github.com/Chysn/O_C-HemisphereSuite/wiki/VectorLFO)
• Added VectorEG, a dual uni-polar envelope generator applet that uses custom and preset Vector Waveforms. (https://github.com/Chysn/O_C-HemisphereSuite/wiki/VectorEG)
• Added VectorMod, a dual bi-polar modulator that uses custom and preset Vector Waveforms as either one-shot or cycling modulation sources. (https://github.com/Chysn/O_C-HemisphereSuite/wiki/VectorMod)
• Added VectMorph, a morph controller applet that uses custom and preset Vector Waveforms. (https://github.com/Chysn/O_C-HemisphereSuite/wiki/VectMorph)
• Added Boots 'n Cats (BootsNCat), a simple bass/snare drum synthesizer with stereo audio outputs. (https://github.com/Chysn/O_C-HemisphereSuite/wiki/BootsNCat)
• Added Setup/About app, which allows easy access to calibration and EEPROM reset functions, and checking the firmware version. (https://github.com/Chysn/O_C-HemisphereSuite/wiki/Setup)
• Removed bootup splash screen so that the module is immediately ready for use on power-up.
• Trending: Added dual operation , so it now accepts input on CV 1 and CV 2, and each operation and output is independent.
• Trending: Added change detection, which emits a trigger when a signal has changed.
• TrigSeq/TrigSeq16: Fixed issue that caused the first step to not play
• "A"SR: Fixed scale selection buffer overread crash

[Starthief]

VectMorph is extremely cool. The LFO as well, though I haven’t gotten along as well with the EG.

[naxuu]

What didn’t work about the EG for you? I haven’t installed Hemisphere yet (trying to!) but it’s seeming more and more indispensable with each release.

Re: Installing the Hemisphere firmware - I ran into technical problems last night trying to flash the Teensy. Teensy Loader wouldn’t recognize me pressing the Program Mode button on the Teensy on the back of the module. Tried the second method of building with the recommended older version of Arduino IDE, but it seemed to have trouble uploading the firmware and mentioned USB issues. Suggestions welcome here… (could it be as simple as swapping the cable out for a different one?)

[Starthief]

It seems like when selecting which vector waveform is used, the envelope gets reset to… the sustain stage maybe? And it sticks until you gate the envelope.

Also, all the vector stuff shares the same bank of data. The EG is the only unipolar source, and it scales/offsets the vector data so that the minimum value is zero instead of a negative voltage. The waveforms designed for bipolar use that end at 0 “in the middle” now end at some positive voltage, which is a bit counterintuitive at first.

Also: “pulse” LFO waveforms that transition directly from max at the very start to minimum at some point throughout the cycle, end on the maximum voltage in the EG, as if there’s an off-by-one error.

Locating the sustain stage arbitrarily can be confusing (maybe it needs to be indicated on the display somehow), and setting the envelope speeds in Hz is counterintuitive.

Common to all the Vector applets, they might have felt friendlier to use if they were single channel per applet rather than dual with two pages of settings – but having used a dual VectLFO + dual VectMorph in a patch, I do appreciate the utility.

[tylor]

I’ve been stuck with the same problem. I wondered if I was using budget USB cables intended for just charging or if my MacBook with USB-C is just unhappy. Would love to hear if you figure this out.

[naxuu]

Hm, if you’ve also got a Macbook with USB-C, then that could be our common issue. I’ll give it a try with an older Macbook and see what happens.

[coreyr]

I can confirm that usb cables can be at fault for failed recognition of the teensy. Another thing to look at is weather the usb power supply trace was cut on the teensy…

If the trace was cut it will protect from powering from both your case and over usb at the same time, but I believe it means you will have to provide power while programming.

I find it easy enough to leave the trace in tact and be sure to un plug it from your case whenever you program it. Unfortunately, if you are using the usb midi functionality of Hemispheres, you really need to cut that trace…

[louwrens]

It’s definitely not the USB C port on the Mac. Probably the cable or power trace like others have mentioned before.

Hemisphere suite is just getting better and better, can’t wait to try the new features in 1.6.

[okyeron]

FWIW: To test if the Teensy trace is cut or not

• with o_C disconnected from rack power, connect the Teesny to your computer over USB. If the screen on the o_C powers up then the trace is not cut

If your trace is cut, then you need to be sure to power the module from your rack when you attempt to flash the firmware (otherwise the Teensy won’t have power and won’t be recognized by the computer).

The trace in question provides the Teensy with 5v from the USB connector. When the trace is cut, the Teensy gets 5v via a voltage regulator on the o_C.

[Starthief]

The instructions I have for flashing firmware say to power the module from the rack before pushing the Teensy’s program button.

[b_w]

I was able to install a version (currently have 1.4c) a while ago, but when I went to install 1.6, I ran into this same issue. Screen lights up, but my computer doesn’t recognize it. I got in touch with chysn on the other forum, and suggested it was the cable, which i found to be untrue, then directed me to:

https://www.pjrc.com/teensy/troubleshoot.html

called “Teensy Not Recognized by Teensy Loader,” which outlines a procedure involving holding the reset button down while plugging in the USB cable.

To no avail. wondering what’s going on here. i would love to have 1.6.

[okyeron]

Question to ask chysn

• what version of the Arduino IDE and Teensyduino is he building the hex file against?

FWIW - I am able to load the Hemishperes firmware no problem with Teensy Loader 1.26 (I’ve got Teensyduino 1.41 with Arduino 1.8.5 - you can check versions in the Arduino about box)

EDIT: You can download previous teensyduino versions, but they’re kinda hidden:
https://www.pjrc.com/teensy/td_141/
https://www.pjrc.com/teensy/td_142/
https://www.pjrc.com/teensy/td_143/

[okyeron]

https://www.pjrc.com/teensy/troubleshoot.html

called “Teensy Not Recognized by Teensy Loader,” which outlines a procedure involving holding the reset button down while plugging in the USB cable.

NOTE here that the “plugging in USB cable” instruction would be “when turning on your modular rack power” in the context of the o_C

[coreyr]

This is only if you follow the OPTIONAL “cut the 5v trace” step in the O&C build guide or if someone else did so when they built it for you.

[tylor]

Yay got Hemispheres loaded!

It must have been the USB cable, the loader just worked, whew! My trace is cut, as the module didn’t power up with just USB. Kept the USB plugged in, hooked up the modular power, powered up, pressed the button on the Teensy, and ready to load

[naxuu]

It was the cable on my end as well. Yay for easy solutions! Happy hemisphering to all.

[b_w]

Ok, here’s where I’m at. I’m running (only) teensyloader on a pc. I drag over hemisphere 1.6A and it says the hex file is too large. this is before plugging in the O_c. When I plug in the O_c, nothing changes. Loader says it is still too large, although the O_c is running/powered. I’m am using a perfectly good usb. What now?

edit: resolved. ran the detect20mk hex file first so everything’s gravvvvy