Jump to content

nebula

Members
  • Posts

    943
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by nebula

  1. PIC Based core running MIOS8

    DINX4 with 32 buttons

    second DINX4, chained to 1st, with 16 buttons and 8 encoders

    DOUTX4 with 32 LEDs

    AINX4 with 32 pots

    DOGM26 lcd display

    Are there any obvious blunders in this design? I was unsure about the 8 encoders/16 buttons on one DINX4 arrangement, I guess this will require quite a bit of manipulation in software.

    No major manipulation is required. Encoders and buttons can share the same DIN ICs. The only rule is that encoders must be on one of the 4 primary input pairs on a DIN IC (so 0+1, 2+3, 4+5, or 6+7 - you can't do 1+2 for example). You'll get this when you configure your first app.

    Your parts list makes sense, but you should double-check the musings on these forums about DOG LCDs. I don't know how well they perform under MIOS8, and they don't work with all apps. You might be better off going with a "regular" HD44780-based LCD.

    I've been looking at encoders and pots on Alp's website, and to some extent they fit the bill for what I need. Does anyone know of any good suppliers in the UK, or a particularly good eBay seller?

    Try Farnell? Or maybe digi-key?

    In terms of acquiring the pcbs, would setting up a bulk order on this forum be my best bet, or should I see if I can get them manufactured locally?

    You'd be better served just ordering the boards from either of the two web shops that offer them for sale.

    Smash TV: http://avishowtech.com/mbhp

    Mike: http://www.mikes-elektronikseite.de/mshop_englisch/

    Either that or try making them yourself - it's not that hard, and single-sided layouts for all these boards exist.

  2. I'm far enough along on the prototype that I wanted to start testing. So, I plugged in the PIC, and things didn't quite work the way I expected. I forgot that, since I rearranged the shift registers, I had to reconfigure the firmware! Why am I telling you this? I already had SmashTV burn the first set of PIC chips, and they have the old firmware. That means that you'll have to update the firmware right away when you get things set up. I'll put this in the install docs. If I don't get to it before then, I'll modify the code on the plane Sunday.

    Sounds good to me! Don't forget to bring your partially completed PCB, spare components, tools, and consumables like solder and flux on your carry-on for testing and debugging. Airlines love that kind of stuff.

  3. The TR-808 doesn't have dynamic voices. There is a global accent and that's it.

    The TR-909 is different, in that its built-in sequencer offers two dynamic levels for most sounds, in addition to a global accent, plus it offers more dynamic control if controlled by MIDI.

    I have been casually trying to figure out the best way to do this for the 9090 as well. My 9090 boards are about halfway finished, and once they're done I plan to investigate this a little further. I also would like to have a MIDIbox sequencer controlling the 9090. I'm going to bet that the best way would be to use the DAC on the 9090 board (created with a resistor array).

    Unfortunately the MIDIbox 808 sequencer at this time AFAIK does not offer any way to program different dynamics for each note. So this will probably involve modifying the MIDIbox 808 firmware, or using MB SEQ (I don't want to do this).

    As for those who suggest that MIDI control of the 9090 is better, I have to agree with nuke that a standalone drum machine ultimately should not be subject to the timing limitations of MIDI when played from its own sequencer. It's not a big deal when only playing an individual part, but if you have a place where, say, 5 sounds occur at the same time, you will necessarily have an audible flam as the notes must be serialized with a best-case 1 ms gap between notes.

  4. And now, a word from the solder-technique nazi:

    When "reflowing" a solder joint, you should always either:

    (a) apply flux first, or

    (b) add a small amount of flux-cored solder to the joint.

    Flux is like the magic elixir of soldering. It removes contaminants and small amounts of oxidization on the metals to be joined, and carries it away. If your solder joint was poor in the first place, there is an good chance that it is due to insufficient heat, or because the flux in the solder did not reach the required surfaces. Oxidization occurs on metals like copper very quickly, so adding flux will greatly improve the likelihood that the solder will bond properly when re-heated. It also prevents the joint from becoming contaminated.

    Just sayin ... :)

  5. I was thinking this is a PC-side operation that requires coding up some software to round up the capabilities of this solution.

    Agreed ... there's no real advantage to doing this on the MIDIbox, since the samples are most likely to be PC-resident anyway.

  6. Now if we could only have a way to transfer our own PCM data across to the WS...

    Forgive my ignorance, but I don't completely understand why we can't do this. Would it be really difficult to reverse-engineer the PCM card data? Or is there some other reason I'm overlooking?

  7. Seppoman made a pcb for Not sure if the actual design is available somewhere though.

    Seppoman hasn't been seen in months, and the Eagle file does not seem to be available. If it was, I would get a couple made. I tried to PM him back in May; no response :cry:

  8. I remember being on the majordomo list as well - so we've known each other for longer than MIDIbox... :tongue:

    Yes, and we're also older than we'd probably like to admit.

    Maybe abuse an old Korg M3R? :angel:

    Aww cmon ... not if it still makes noise. I will admit I've been wrestling with the idea of hollowing out my old Anatek SMP-7 MIDI patchbay / Mac serial MIDI interface though.

    I agree from your rendering that there is not much room for an SD Card socket. Maybe I'm being a bit lazy, but I still have found no published layout for an SD card for MIDIbox that uses an actual socket I can buy. Everything I've seen documented so far is a hack.

  9. This is fantastic. I will be watching this closely... suddenly I feel a need to free up a rack space beneath my WS A/D. I never owned a SAM1, and I never even owned a PCM card. So I'll build this for sure. But may I suggest your final "shield" board include a footprint for a readily available SD Card socket?

    Many years ago (in the mid-1990s) I used to run the majordomo mailing list for the Wavestation. It was pretty cool seeing you scroll through old Ben Hall patches.

    Nice work!

  10. This in a weird way reminds me of "Smalltown Boy" by Bronski Beat ... must admit those SIDs sound sweet.

    I don't completely understand why you wouldn't use SIDs for those bass notes though ... I would think they could do it just perfectly.

    I really enjoy your videos!

  11. Any other (simple to implement) feature request?

    May I suggest my proposed modification be added to the official 1.2, so that shift + instrument encoder invokes "rotate"? ( )

    I'm even thinking about changing mine to be the other way around, so shift is required to select instruments!

  12. Logic Pro actually has an option to control a "RECORDING" light with MIDI messages (in the "control surfaces" settings)

    spreemusik's concerns are valid, but it could be configured with a "hang time" so it stays lit for a few minutes after the recording is stopped. I'd probably also add a toggle switch to force the light to stay on, regardless of the DAW's recording state.

  13. Like Rosch said, sammichSID's an easy project, and it is a complete kit (except for power supply).

    None of the projects on this site are available for commercial sale. That's one of the terms of using these designs.

    Occasionally you'll find one for sale, on eBay. These are not only unauthorized, but they are way overpriced!!

    If you really don't want to build one, you should consider MSSIAH, HardSid, or see if you can find a used SIDstation.

  14. I really don't want this to be perceived as a flame ... it's just my two cents:

    Arduino is about building robots, weather stations, LED decorations, and ... oh yeah, music stuff. I happen to like that MIDIbox is focused on MIDI and musical devices, in which the timing MIDI i/o or other musical communication is absolutely NEVER compromised, for any reason. I have complete trust in TK and everybody who develops for MIDIbox that this philosophy will always prevail in hardware and software designs, so we have an excellent and future-friendly platform for real-time, embedded musical applications.

    I fail to see the value Arduino could bring to MIDIbox, in the context of professional music production. It is always good to stay abreast what's going on in that other realm, but its technology, motivation and culture is precisely that: another realm!

    Here's an example: almost everybody in the MIDIbox community is an electronic musician of some sort. Can the same be said for Arduino?

    Regarding value in commercial: projects like "Beat707" are proof that cool music apps can be realized on Arduino, but to build it you have to pay somebody for it, and that person had nothing to do with the creation of the Arduino platform! MIDIbox-DMX is a great example of a non-musical MIDIbox project, and to build it all you have to do is download the schematics, documentation and firmware. (Optionally you can buy PCBs at bargain-basement prices.)

    It is the good will of great people that has made MIDIbox what it is, not financial gain.

    I think the LPC Expresso-based core will pave the way for more shield-like submodules however. The "core" PCB is really a bridge between the LPC and the classic MBHP modules. I envision complete projects as "shields" for the Expresso, and ribbon cable interconnects to other modules becoming less common.

×
×
  • Create New...