Copyright by SOMA Laboratory (This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.)
Privacy & Cookies Policy
This seems like an issue with your Drive potentiometer. Please write to [email protected] so we can resolve this for you.
I’m assuming this is only on one algorithm?
Can you post your knob settings and which algorithm you’re using please?
Some hum/feedback/bleed-through when touching the center pyramid (especially the top portion/delay lines) without patching anything into it is normal. Especially with the L and R delay lines.
You may have already tried this, but have you tried a different midi cable? They can get crimped/pins lose connection etc. Worth a try.
Hello,
Could you tell me more about what type of expansion box you’re making for the pulsar?
You can run the delay and reverb into each other using their corresponding pins (REV> to >DLY, or DLY> to >REV) OR you can run each channel of the pulsar out to whichever FX you want by using the OUT> pins in each channel. Hope this helps.
You SHOULD be able to do this using a TRRS to TS cable but I haven’t tried it myself.
Hello,
Send me an email at [email protected] and I can help you out with that.
I would recommend going to your closest band/orchestral instrument shop and telling them you’d like a cheap violin bow (to practice with). Make sure you get some resin for the bow also. Start with a cheap one (~$20) and see how you like it/experiment.
Is your pulsar still doing this after a power-cycle and with no patch cables connected (or MIDI)?
Its possible you need to lower the velocity of incoming MIDI notes/triggers sent to the pulsar, the velocity may be too high to notice/hear what you’re playing in manually.
This is normal behavior when the switches are set for LFO as the mod source for a channel…a small amount of modulation even with the MOD amount at 0. Make sure you don’t also have VIBRATO enabled.
I have had the Shaos lock up before, switching the length (63-16-217) has always brought it back though. Did you try that?
The pulsar buddy is great! 🙂
Hello,
What you describe is normal behavior for the pulsar as it doesn’t handle transport messages (start/stop). Once the pulsar receives clock via MIDI it will continue to play at the set tempo. There are a couple ways to make the clock start and stop on command.
A.) Use an analog pulse/clock that you can stop and run it to the pulsar clock input pin.
B.)Use a step sequencer with MIDI out, assign a pattern/sequence to one of the midi to cv pins on the pulsar (the 4 pins labeled KTR1,2,3,4 on the left of the pulsar) then run that pin to the clock input. (Try placing a step in every step of a 16/16 pattern etc then running to pulsar)
Using either of these methods you will need to hit the RST button in the clock divider array section to make sure the pulsar starts at the beginning of the pattern (if so desired).
