moebius

Actually, it's not that straight forward.. I've got a C64C with 6851 R4. Bye, MOebius

Perhaps this is better answered by the IC-Prog homepage? http://www.ic-prog.com/ ;D JDM was originally designed to program 16C84 and later slightly modificated to support other devices. So, programming could be as easy as configuring IC-Prog and wiring the programming pins (and supply pins) of the PIC to the corresponding pins of the JDM... Bye, Moebius

Yes, it should work as long as devices share the same PSU ground.. And I'm not sure If that 1.2K pullup resistor in the midi input is actually needed if optocoupler is omitted?! Bye, MOebius

Looks sooo DIY, yet it's so Cool ;D I can spot (a bit modularized?) Simplesizer there, Formant Pro ADSR and MXR Distortion.. is that a moog 24dB ladder? I'm very keen to see what other people are DIYing ..Should SynthDIY'ers of the MB Forum unite somehow? Own little "tech corner" on the forum? Bye, Moebius

Hi, "No Can Do" - But for a cheapish DIY solution, go check: http://www.willem.org/ Bye, Moebius

My apologies, everyone - especially Twin-x. I'm sorry for my grumpy comments. I'm okay with the new server (as long as the database is up and runn.. arrgh.. note to myself: STOP you silly idiot!)! No hard feelings? Moebius p.s. I know, DDOSes are damn hard to defend against and usually do "damage" datacenter-wide as Border Routers to Internet central nodes are shared.

Cool ;D Hmm.. what gear do you actually control with the AOUT?!? And those VOTI encoders... can you post the specification to the Parts Archive section of the forum ::) Bye, Moebius

Hi, I'm here ;D If there's wrong information there it will be corrected.. ..But combining all the information about your SEQ2 - I'm wondering - what was the firmware that you uploaded? I mean - IF you used "main.*", then all the encoders, BUT the menu encoder are "DETENTED2", which is "DETENTED", I guess (?!) and this is Thorstens setup. Bye, Moebius

Err.. he said "microbuttons" (microswitches are mechanically a different thing altogether).. and if you search the Internet "tactile switch" is a correct term. That's the way: Switches are "normally open", and when pressed, the button shaft moves 1mm or less and makes a contact (and a "click" sound) No no no.. ;) I hope I'm expressing myself with my lousy english clearly enough.. and yeah, those buttons are way COOL.. too bad I have already chosen buttons for my sequencer.. Bye, Moebius

Hi, Uups, you saw that on uCapps.de-- Here's a link to forum posting where you can see it's construction more clearly: http://69.56.171.55/~midibox/forum/index.php?topic=2608.0 Those ARE "standard" tactile switches and separate leds mounted to board below the frontpanel with selfmade (DIY) transparent acrylic button "caps" ;) If you find switches with leds, you can use those as long as you take care that wiring is correct. Bye, Moebius

I'm hoping this is going to be a sticky topic ;) I'll edit this post or delete it, if it's not needed anymore - all this information is gathered from the forum, and shamelessly copied here - You're welcome to present it in a better form Bourns PEC11-series detented encoders (From SmashTV) Encoder mode: "DETENTED2" Pinout: (http://www.avishowtech.com/mbhp/images/encspecs17.gif) Note: the rightmost picture is "top down" (as seen from the top of the encoder looking down to the shaft) pin "A" goes to D1 pin "C" goes to Vs pin "B" goes to D0 (This means that, encoder C pin is "common". Encoder B pin goes to lower numbered DIN pin (of two pins assigned to that encoder) and encoder A pin to higher numbered DIN pin.) the detent can be removed ----- Thanks go to: mandingo: http://69.56.171.55/~midibox/forum/index.php?topic=3843.msg25094#msg25094 jdutcher: http://69.56.171.55/~midibox/forum/index.php?topic=3911.msg25766#msg25766 xcoulonx: http://69.56.171.55/~midibox/forum/index.php?topic=3299.msg23699#msg23699 Now - does anyone want to reveal the specs of the encoders from VOTI? What about different ALPS types? contributions more than welcome ;) /edit corrected link for moved page

Yes, It's also possible to burn MIOS and application code to the PIC along with the bootstrap loader - but this is totally unsupported (You'd have to find out the method by yourself - huh?) There are some good reasons for the current practice: Simplicity: With a PIC burned with a bootstrap loader, MIOS/application uploads/updates can be done over midi. With a MIDIbox, there's no reason to skip over getting midi (core) working, because you want midi working anyway. (And taking these things into account - there's no reason what so ever, to mess thing up by describing a redundant, more technical way of doing things) So - forget what I said ;) --- But what is the problem with your midibox? Describe? ?You have bootstrap loader in, but: A. Can't get it communicate over midi? (Can you see midibox sending the Sysex?) B. Midi seems to work, but MIOS upload fails (with a Mac)? Bye, Moebius

99%? 98%? 97%?...... Of course, I'm not complaining - let the merits of the new server speak for itself ;D http://dictionary.reference.com/search?q=functional Bye, Moebius p.s. What was that hosting company that offered 6 months free test drive? http://1and1.com was it?

Noo.. It's "only" a midi interface. ;D There are some USB audio circuits to be found on the internet - but those should really be considered as surface mount component soldering practice, with current audio interface prices.. I mean you'll probably end up losing money by building one yourself. Bye, Moebius

What did I post?!?? Have you seen this? Or havent't you? Is this something we have get used to?

"Connection Problems Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later."

-

Actually it matters - because this "feedback" situation is caused by MIDI-OX default port routings, that passes midi data from inputs to outputs. See MIDI-OX "view" menu and choose "Port Routings...". Disconnect the link between the midi ports connected to MIDIbox and the problem should be gone, even with MB merger enabled and both midi input and output connected to PC. Bye, Moebius p.s. There's also mention about this issue in "Code Upload via MIDI" page: http://www.ucapps.de/mios_bootstrap.html

Hi, My computer lost the ability to run MPLAB IDE (v 3.70) (and the most malware :)) as I manually removed IE from my 98SE system. Along the MPLAB install, there's MPASMWIN compiler which still runs.. I think it will run on W95 machines and requires no install by itself.. (so you could just copy it to another machine) I didn't see any real advantages using MPLAB.. well, it gathers all source files under "a project" and has Microchip assembler highlighting.. (and if you have a supported programmer, it will program the PIC for you) Still it's pretty bloated for a 47MB, or something, install. For now, I've settled using Programmers Notepad2 (http://www.pnotepad.org) but that's just an example.. I think that Jens' File Editor (http://home.t-online.de/home/Jens.Altmann/jfe_eng.htm) and EditPad Lite (http://www.editpadpro.com/editpadlite.html) are popular choices too?! There's no PIC assembler highlighting support for these that I know.. but at least PN2 supports creating your own "language schemes" for doing that.. and these also support calling external programs for compiling (and MPASMWIN can be called from the command line). BYe, Moebius

Why are you giving up your beloved 16F-core? It will work without ledrings - Yes, pots and encoders work at the same time.. IT IS APPLICATION code, that needs some adjustment.. as far as I remember, It has been done.. sorry.. can't find a link. I think it was based on Midibox64E with AINs enabled? Bye, Moebius

I didn't say that!

Hi, there - I'm sorry, I'm not HIGH.. :o :o ::) (nor anyone around this forum - What would happen If Tk was..) I think your ok. Your information is correct. Bye, Moebius

Hi, So, you're programming a 18F452? --You only have to program "MIOS bootstrap loader": http://www.ucapps.de/mios_bootstrap.html.. This can usually be done with a JDM...... (usually with some modifications) Then the MIOS and the application downloads are done by midi.. that's when you have your midi connections ready, right? ..If your just getting a new Pic from Smash.. then ask for the programmed one, with the ID 00.. I think? Bye, Moebius But ask again if this is too confusing.

Does anybody else see, what I see: http://69.56.171.55/~midibox/forum/index.php?topic=2718.0 Two similar posts by: "VILLADON" (posts: 1) and two replies from: "psytron" and a single reply from "DrBunsen" Hmm, Moebius

Hi, Actually those videos are kind of COOL ;) (And my comp even understands QT, unlike some recent M$ "standards"..) pay attention, boys and girls: The wheel seems to be a perfect example of an encoder. ;D "Shuttle" seems to output So-called "Grey code"-- BUT I'd still decode it as 8-positions (3-bits) (center+7 different degrees) and a direction bit. There's no MIOS modification needed to use this information. It just 4 buttons for MIOS! --- But WHAT should these center + 7 different reverse and 7 different forward positions output to midi? I have no clue, what kind of midi messages does Traktor support. (I didn't even see any controls that would benefit from this??) Then the midibox application code must be modified, so DIN entries for this shuttle control are decoded as different positions and appropriate midi messages are sent.. Bye, MOebius