Jump to content

StickyFeet

Knob Twiddlers
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About StickyFeet

  • Rank
    New Member

Previous Fields

  • Country
    Not Selected

Profile Information

  • Gender
    Male
  • Location
    Happy Gilmore's Happy Place
  • Interests
    Pugilism, Metallurgy, Astrophysics
  1. Thanks for the info, the synth I'm using doesn't support Midi CC pitch commands so that's no longer an option. Also, if I got a midi to CV gate, the only available input that can modulate pitch is the pulse width one and I don't think I'd achieve the desired results with that. So, I might end up just using the sequencer on the synth then running my soft synths with reaper. Luckily I've got 20 years of professional software engineering under my belt which had made a lot of this easier for me to pick up than anyone coming in blindly.
  2. Noob question, or not, regardless I'm still a Novice knob twiddler aspiring to become a Journeyman knob twiddler. I've always seemed to gravitate towards music that doesn't necessarily use 12 tone equal temperament and am discovering the limitations of attempting to write music that isn't 12 tone equal temperament with Midi. This has become even more evident with the purchase of an Analog synth last week. Using the synth, by itself, I have created some sequences and tuning that I'd love to be able to drive from Ableton so that I can either send additional notes to the oscillators on top of whatever it might be playing, or control it directly from the DAW. Many of the sequenced notes fall somewhere between the 12-ET scale so anything coming from Midi is just out of tune w/ how the hardware is tuned. I was wondering if anyone had any creative solutions. I've been brainstorming a bit, but I didn't want to commit to one without a little more research. So far the best ideas to have bubbled to the top are to create 2 (or more) seperate midi input sources but to insert CC pitch bend data, or start mucking around w/ Scala (which is probably just generating the aforementioned modulations to the midi data to achieve the same effect). I'll have to deep dive into the Midi spec to get a better picture of what's going on w/ the device interface. Ideas are greatly appreciated.
  3. An external clock and a CV / midi control module are in my future...
  4. It turns out I'm just incredibly impatient. I was using DirectX thinking the Moog was a video game, turns out it wasn't and Asio works much better. A lesson learned for sure...
  5. Hello, long time lurker, first time poster. While I've been listening to music for years a few months ago I took the plunge and started making it. Over the weekend I impulsively purchased Moog's new Subharmonicon synth and have fallen in love with it. However, I'm having some difficulties getting it synced up w/ my DAW for a variety of reasons. Bear with me, and I apologize in advance if I'm getting any of the terminology wrong but I was wondering if any of you have experienced an issue quite like this and have any solutions other than the ones that I have baked up... While I'm not certain, I would imagine the Subharmonicon's sequencer to be quite different in how it behaves to a global midi clock compared to other, more straight forward sequencers. The tempo knob on the device has a range of 20 BPM to 3000 BPM, but the actual tempo of whatever is being produced by it is based on ratios relative to the global time. For instance, if I have the tempo knob set to about half way (around 1500BPM) and set the first sequence to step at the lowest setting, the resulting pattern will play at something like 60 BPM (I didn't do the math, but you get the idea). The problem I'm having arises when syncing the device w/ my DAW using Midi. I'd like to keep the global midi clock time in the 100 - 200 range since Ableton (more likely my computer) likes to act up and fire off notes out of time once I go up into 300+ territory. I was wondering if anyone has a creative solution to somehow sending a multiple of the midi clock to the device such that if i set my midi clock to 120BPM, the device receive's a multiple of that. Otherwise anything it plays, is far too slow, unless I'm working in the upper bounds of the polyrhythm generators. A couple solutions: External clock device that might split the clock time into ratios (much like the device itself). A custom Max plugin that emulates said device above... Work w/ samples... :( Has anyone dealt w/ this type of issue before?
×
×
  • Create New...