Joined: May 26, 2007 Posts: 421 Location: England
Audio files: 3
Posted: Thu May 12, 2011 3:25 pm Post subject:
Hi all.
Can't get the camera to talk to the computer properly, so have recorded a quick audio demo. In this example, The M2C is being used to gate an audio signal via a VCA.
The stage 2 divider toggles are being switched in and out live while the beat is running. A daughter board to allow gate control of the toggle action would seem a logical first add-on I reckon....
It's a rough demo, and simple, but gives an idea of how easy it is to set up rhythms and patterns with the toggles.
More later (when I can get the video done, which looks like it may be a while.....)
cheers,
Dave
M2C DEMO 1.mp3
Description:
Filesize:
2.96 MB
Duration:
2:09
Viewed:
1616 Time(s)
_________________ "Everything in moderation, including moderation"
absolutely orsm and exactly what i hoped it would be like
I think the sync daughter board i have been working on should be able to sync fonik's PWM master clock to this which would be outstanding
I will need to make some output multiples i think
Joined: May 26, 2007 Posts: 421 Location: England
Audio files: 3
Posted: Fri May 13, 2011 4:01 am Post subject:
Hi guys.
Mathias is the boss where PC boards are concerned. I think we need to get around 30 or more pre-orders to make it viable, and get the price down to something reasonable. I reckon we have around 10 or so folks who want one so far.....
cheers,
Dave _________________ "Everything in moderation, including moderation"
Yes, yes, yes!
I'm up for one of those board for sure!!!
Aaaagh, so many great designs to build already and now another belter...
Top stuff guys, a great collaboration indeed it seems.
definitely up for one however
dave just to bring up the question
would 2 or more of these be usefull really in the context of a single modular even a really large modular ?
I was thinking to have a form of buffered multi's on the output to increase the number of outputs to what i would need,
is there an additional benefit to multiple modules that i haven't figured out yet ?
I will need a reasonably good arguement in favour, so i can justify the expense to my wife
2 would be good to divide the rate differently for different devices. You can put me down for 2 now that I think of it. I might only build one right away, but I'm sure I will need the second in the future as I create more lunetta type devices and sequencers.
now there is some momentum here?
i think we will have to start a list... _________________
cheers,
matthias
____________
Big Boss at fonitronik
Tech Buddy at Random*Source
2 would be good to divide the rate differently for different devices
hmm yes i think i can see how that may be preferable to just using other dividers afterward though i can see i will do that also anyway
dave would a midi thru be reasonably easy to implement for chaining a few of these together ? no biggy i do have quite a few spare midi outs on my interface rack still.
mathias i may go to 4 of these possibly now. will need to recheck the budget first though
dave would a midi thru be reasonably easy to implement for chaining a few of these together ? no biggy i do have quite a few spare midi outs on my interface rack still.
a decent MIDI thru circuitry needs another IC, and the board is rather large already.
Dave already said something about another reason for MIDI thru off: MIDI clocks are woven in the MIDI data stream. So you don't want to use MIDI clock data and other MIDI data on the same output.
For distributing a MIDI clock to multiple instruments a simple multiple would do, i bet. _________________
cheers,
matthias
____________
Big Boss at fonitronik
Tech Buddy at Random*Source
MIDI clocks are woven in the MIDI data stream. So you don't want to use MIDI clock data and other MIDI data on the same output
yes i just reread that post
i was thinking more along the lines of having one dedicated midi out from my interface rack just for midi clocks rather than say having to use up 4 outputs if i were to build 4 of these modules
Quote:
a decent MIDI thru circuitry needs another IC, and the board is rather large already
was thinking i could do a small add on board . as long as the midi clock data can be accessed . I think dave suggests later on all midi data is available on headers so it shouldn't be a problem just wanted a conformation that it includes the clock data
Quote:
For distributing a MIDI clock to multiple instruments a simple multiple would do, i bet
that would be great but not sure if it would be all that simple.
midi can be horribly finicky especially on longer cable runs
Erhm,
MIDI is based on a current loop, so you would need to buffer this rather than just split it. The spec of MIDI is also very particular about grounding and to avoid earth loops and hum, hence being an opto isolated current loop.
I'm sure it wouldn't be too tricky to come up with a little distribution circuit if you wanted to send the same clock to several boards, maybe it could be after the MIDI decode, like a master/slave scenario?
Erhm,
MIDI is based on a current loop, so you would need to buffer this rather than just split it. The spec of MIDI is also very particular about grounding and to avoid earth loops and hum, hence being an opto isolated current loop.
you are correct, ben. nevertheless a simple split works. you do not want to distribute it this way to several instruments over long distances though, right? _________________
cheers,
matthias
____________
Big Boss at fonitronik
Tech Buddy at Random*Source
Joined: May 26, 2007 Posts: 421 Location: England
Audio files: 3
Posted: Fri May 20, 2011 4:59 am Post subject:
Hi guys.
If you wanted to distribute MIDI CLOCKS to more than one M2C, a 1-in 4-out MIDI thru box would be the easiest way. That way, The MIDI input only gets buffered and re-sent once.
Diablojoy - the best reason for having more than one M2C, would be that you have one in the rack to clock things with, and another on the test bench for developing new widgets with. Once you have got another set of dividers for instance, you can add them to the rack M2C as an expander module and keep experimenting..... Unplugging it each time an idea comes along would be a pain
As far as outputs go, there is a header on the PCB that carries;
24PPQN CLK
START
STOP
CONTINUE
ACTIVE SENSING - and a couple of others. It can be used without affecting the basic operation of the board. The signals are all fast positive-going +5V signals, and are unbuffered. A CMOS out put has a large fan-out, so could drive quite a few more IC's directly, but as you suggested, it might be a good idea to buffer the signals. A 74HC244 or 74HC245, or their regular CMOS equivalents would probably be good for this.
The good folks on the [sdiy] list pointed me towards some info on DIN-SYNC. It seems a small amount of extra logic would be needed - a 4013 flip-flop or 4027 could perhaps be used to generate the RUN/STOP gates that DIN-SYNC needs.
If Matthias is up for it, should we go ahead with a PCB run?
BTW - Matthias - I'll order one too for the test bench to make new devices with - lots of ideas already
cheers,
Dave _________________ "Everything in moderation, including moderation"
I would suggest another output, along with start/stop/etc, if it's possible to add:
System Message: Song Position Pointer = 0
0xF2 xD1 xD2
If D1 = 0x00 and D2 = 0x00, then the song pointer is set to the beginning. This is VERY useful in synchronizing multiple sequencers DURING PLAYBACK. Most Seq. ignore the START command once playback has begun. (START is also interpreted to reset the song pointer). This can then be used to reset sequencers, LFOs, OSCs, etc in the analog realm.
Maybe you can recognize Song Pos Pointer, and toggle Start again?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum