moebius

Great work!! ;D I bet you had some fun time at the studio, I'm sure I'd have ;) Bye, Moebius

Yikes! What I mean that ground shouldn't be connected, and maybe even DIN connectors body shouldn't be in contact with input devices ground point. Opto is doing all the work here. (Sometimes ground loops arise even when devices are connected to grounded power supplies and to another device with another ground connection.. Like synths -> mixer) Bye, Moebius

I was thinking that something is sneaking from yamahas past your optoisolator. Midi input should be completely isolated from signals driving it. Is your MIDI input jack in contact with grounded MB case? Or middle pin grounded? Bye, Moebius

I guess that it is a grounding problem, maybe your Yamahas are supplying MBSID some interference signals, Ground loop?! Â ??? Bye, Moebius

Sorry, a little mixup.. I was assuming you are building 18F452 based mios compatible core. Â ::) Are you?! For 16F877 MB use firmware found from "OLD PIC16F Firmwares "-page. These you must "burn" on pic. For MIOS based version: Just wait for a release ;) Moebius

Hi Ryan. They use different MIOS application. After burning mios bootloader to PIC you can download mios over midi and  then suitable application. So, Yes you have to reprogram PIC, when switching to different application, but you can do it over midi. MB64Seq is still on beta level, so it's not offered for download. Bye, Moebius

Well, Just for the record: Alesis MMT-8 runs 8 multichannel polyphonic tracks at 96ppqn resolution with 80c31 (dating back from '82, remember 80's? ;) ) (clocked  @ 11MHz and uses 12 clock cycles for most instructions!), (27c256) 32kB EPROM for code and 2*52256 32kB SRAMs for sequences. I think that PIC 18F452 @ 40MHz easily outperforms that. But, wait: "supersequencer", with 16 MONOPHONIC tracks?! :o I really don't see any advances in that concept over, well 4*MBSeq.. maybe for the drums.. (with those upcoming drum triggers ;) ) Polyphonic tracks with "improved" ppqn resolution would be good aim?! And with that concept change it really needs much programming efford. This is nice. With performance oriented sequencer I'd like to see also has ways to manipulate sequence live: Maybe assinging arpeggiator to one track and "bouncing" it to another, live recording mutes ect. something resembling DJ:ing with sequences. Bye, Moebius p.s. multiple midi out is easy to construct with hex inverter and few resistors.

Damn! Reichelt isn't only one making mistakes: Of Course I got that Groove table wrong, but NOW it's fixed! So only every second 16th note gets shifted. Bye, Moebius

Sting (Just got back from "Funky Town", well, not really, got that one on 12")

Thorsten: Thanks to sil909 and AnalogueHeaven archives Grooves extracted! No midi file, but Here's the table, representing one beat and it's 16th note values shifted in relation to midi clock: [pre] Â Â Â Â Â Â Â 16ths: Â Â Â Â Â 1 Â Â Â 2 Â Â Â 3 Â Â Â 4 Â Â (1) none: Â Â 0 Â Â Â 0 Â Â Â 0 Â Â Â 0 Â Â (0) Shuffle1: 0 Â Â Â -1 Â Â Â 0 Â Â -1 Â Â (0) Shuffle2: 0Â Â Â -2 Â Â Â 0 Â Â -2 Â Â (0) Shuffle3: 0 Â Â Â -3 Â Â Â 0 Â Â -3 Â Â (0) Shuffle4: 0 Â Â Â -4 Â Â Â 0 Â Â -4 Â Â (0) Â [/pre] I think you can easily figure out what's going on.. Bye, Moebius oh, and link to the original posting: http://www.retrosynth.com/ah/search/lookit.cgi?-v9705.1068 /edit: Yet another ASCII fix, (Opera not functioning properly with YaBB) I hope I got IT ;)

Oh yes, I checked that package too.. Just thought that PortTalk could be easier to use, as there is 'bout complete C-example included. (Uses LTP1, but easily adapted to different I/O range) That "talk to a PCI abstraction layer".. well, I'm not sure, but I think this means using operating system, and so called memory mapped I/O.. (but these things are getting way out of my knowledge (as most of this) ;) ) But even as it's a PCI device, there is a possibility, that it can be used with port I/O. If you have that PCI card handy give it a try, with debug first-- Ok, checked it out, it's I/O mapped. Here's link for document explaining it's registers, in other words, what bytes to write and where in it's i/o space: http://www.measurementcomputing.com/registermaps/RegMapPCI-DIO24X.pdf /edit: more..

Too bad I sold TR-707 ages ago (bad sounds and no need for trigger output anymore).. Quick search on the net didn't reveal anybody willing to share their Shuffled patterns. SO: Has anybody got: TR-909, 7x7 or 626?! (Basically it's kind of a swing feel, notes between beats get shifted, by.. well, maybe we can get those midi files.) And thanks for your input on control surface.. I was afraid that it could be too far from your original analogue style sequencer idea. Thanks. Moebius

Oh, it IS there?! ;) You should try running it as argument for allowio.exe from PortTalk package like: allowio debug.exe /a (that /a grants rights to ANY i/o addresses, so be careful. You can also use exact i/o address as like 0x300 or something) Check the documentation!! Bye, Moebius

Looks great! Lot's of new functionality ;) You probably know these people with Roland fixation: Well, I'm one of those ;) So two suggestions: Groove button: I like the idea, but how about Roland TR-909, 7x7 style Shuffle levels?! It sure does make sequences Damn Funky! Is it difficult to implement some kind of selectable groove templates for that?! (And has anyone got a suitable TR, so timings for those shuffles could be extacted?!) Alternative sequencing control method, kind of like MC202: ASCII illustration: Non code:      12 note "keyboard" [-] [+] octave transpose        [][]  [][][]   [S] slide (tie)       [][][][][][][]  [<][>] [X] delete                step So, nothing fancy, just plain old step entry.. but that's how I like to work: very fast way of "scratchpad" sequencing and collecting ideas. Also updating (just pressing keyboard button) live while sequencer is playing could update that step. And this mini keyboard could also be used to transpose sequences live or for driving arpeggiator ;) Well, I might just be dreaming, Bye, Moebius /edit fixing ascii

Great!! ;D But problems ahead: WinNT/W2k/XP ->No DOS, no debug and if my memory serves me right: NT based Windows prohibits any "user space" programs directly accessing peripherals. But you can overcome this (and writing device driver ;) ) by using special I/O driver, check: http://www.beyondlogic.org/porttalk/porttalk.htm Just drop it in the system (reboot ;) ) and check the sample code (in C) for information. Then: Happy Coding ;)

You can use DOS debug command to try it out: In dos prompt type "debug": syntax is: -o [port address] [hex byte] I guess that those bytes are a hex presentation of 8 bit wide output, so with one write sets all output pins of that port: Just use binary, like 10011001 -> convert to hex: 99 like: -o 300 99 to quit debug use: -q In programming, it's just writing bytes to correct address. Bye, Moebius

Why aren't those .pdf/tiffs on midibox.org? Everything... anything? No updates, for a while, whatsoever.. Sorry, no dis -  but midibox.org could be a  download site for .mid files (as I got, for search results for "midibox", while a go), maybe some day it will, as nobody seems to care about it :( OK, Poeloq might need so help, but I don't: linking something, from somewhere: <a href:="http://somewhere">something</a> Did took me some minutes to figure out,  but shouldn't be that difficult to anyone writing any html.. Sorry, still no dis, -- but: Why ppl still ask for PCB images? Because they read FAQ? Bye, Moebius

King Crimson.. (Loved American Beauty ;) )

Maybe it was JUST the right time to find a bug ;) (Before all MB folks start worshipping false God, chanting TK, TK, TK..) Ok, just kidding, I hope I didn't offend anybody.. Bye, Moebius

Ok, It should be even possible to connect MIDIO128 direct to that breakout box, both use TTL levels. Both relay and TRIAC methods are okay normal lamps, I guess. What I meant with that "midi controlled dimming with AOUT", was that then standard 0-10v dimming equipment can be interfaced with midibox.. (It could be done with TRIACs, by means of pulsewidth modulating triacs triggering thus affecting its on time -> ac duty cycle.. but that is with extra programming efford.) Bye, Moebius

I hope that you only need on/off switching ;) MIDIO128 provides TTL level outputs, triggered by (for example) midi notes, this is propably ok, for midi side?! For interfacing to (I'm assuming) mains powered equipment there is an example, using relays. (Check MIDIO128 page) Proper relays are good for switching (and driving) heavily loaded ac lines. But as being a mechanical components, relays are kind of slow. Â Another way is using TRIACs. I'm not sure how much load TRIACs can handle. I found couple of links for reference: (AC switching with TRIAC from TTL) http://www.ee.washington.edu/circuit_archive/circuits/F_ASCII_Schem_PC.html (PIC 16C63 Midi controlled Light dimmer ;) ) http://www.mindspring.com/~jlittle/picstuff.html But Warning: HIGH VOLTAGE! You should really know what you are doing, even before thinking of project with high voltages present. :o --- But anyway, how is that particular computer Digital I/O board interfaced to control lighting? --- Bye, Moebius p.s. I think that midi controlled dimming will be available as soon as upcoming AOUT module is finished ;)

Propably not an easy way.. or readily available solution. But if you (or your company) has sample code for using the card I think it should be possible to program midi device driver for it. (More or less doin' ripping on public domain source code and providing some glue code) Bye, Moebius /edit ;) But why not using (just to be build) MIDIO128?!

identy

BACK ;) Search forum for the thread about samples.. Bye, Moebius

Great!! Thanks a lot! Bye, Samppa