Thigh-
You are correct, my error. The boy over at Mff should have a field day with this error.
Bottom line, if yo notice the module under test in the vd was an m28. Also know that the three Plan B modules wth a micro P all use the same processor and te smae crystal, and they are all running at 24 mHz. SO this error doesn;t change anything, but if any of you fee; like helping out, a mention to this effect on the nfamous blog night clear up any confusion.
In regards to the tap clock syncing, we may have a software update coming that could potentially improve things in this regard and we will keep you abreast with updates. In the interim, there are two known workarounds, which I will add to the M28 page this week. here they are:
Form M28 user John Tejada:
Here was my workaround for syncing the tap clock.
i'm using my set up with a doepfer maq 16/3, although any sequencer with 2 channels or more should do.
first i send a phase lock to get the clock near what i need or just tap it in with manually.
next, i send a start signal to the tap clock by sending a gate signal at the down beat. then i use a 2nd channel of the maq to send a gate to the stop in just before the 2nd beat. the whole length of this sequence cycle is only a quarter of a bar (4 steps at 16th notes looping). so basically, step 1 sends a gate to start and step 4 sends a gate to stop.
as soon as it receives the stop it cycles to the beginning and it gets the start again. even though it stops, it doesn't stop long enough to give any audible pause for slower tap rhythms. the other bonus about this method for me is that i can tap in different times and get really creative and it will re-sync itself every quarter bar.
Workarund 2:
On a simular note, a second workaround can be had by simply running a square wave through an inverter to put it 90 degrees out of phase (a model 17 works well for this, as does the Boolean function of the M26:
Run the noninverted square wave into the phase lock input of the M28, and remove that signal as soon as the unit begins clocking that pace. It should be running on it's own now.
Now stop the M28 manually.
Run the noninverted sqware wave you just used to phase lock and insert that into the START INPUT. Take the inverted square wave (180 degree out of phase ) and put that into the STOP INPUT.
In that the M28 fires a quarter note out immediately upon starting, using this single waveform to start/stop the m28 should greatly improve the sync to the original input.
Now do the very same thing you did with the square wave test, but replace that with the midi note on or clock output from your sequencer. In short, use the midi signal as the start/stop controller instead of the square wave LFO.
Hope this helps,
- P
--- In PLAN_B_analog_blog@yahoogroups.com, "thighpaulsandraslingsby" <thighp@...> wrote:
Show quoted textHide quoted text
>
> I think the post was actually relating to the M28 Tap Clock. Although this a great module some people have some issues with the 'Phase Lock' drift. A couple of the more techie people have been attempting to help solve this so I think that is a valid music making concern.
>
> Thighp.
>
> www.thighpaulsandra.com
> www.aerielstudios.co.uk
>
>
> --- In PLAN_B_analog_blog@yahoogroups.com, Brad Hawkins <monkeyfinger@> wrote:
> >
> > seems to me that some people could just spend more time making music/noise than wasting time worrying about things like this
> >
>