Jump to content

djsegler

Members
  • Posts

    37
  • Joined

  • Last visited

    Never

Everything posted by djsegler

  1. Would anyone be willing to post a basic block diagram of the hardware blocks to create a Mackie clone (or better yet, a Tascam US-2400 clone)? I'm still not sure how the multiplie cores get slaved together, how they are addressed, and what code to load into each of them. It would also be nice to have a tutorial on how to set up a core module in a step by step fashion for those of us just starting out. Browsing through the MBHP project section, I can find great documentation on how to build the stuff, but it's lacking a little in what to do with it after it's built! There are alot of code fragments, but not really any documentation on what to do with it from a high level. Ultimately, I would like to interface to Sonar 2.2, so if anyone has experience at that, it would be very helpful! Thanks!
  2. :D Does this only work on Sonar 3? I have Sonar 2.2 and have been a fan of the Midibox concept for almost 2 years now. I've been waiting for the Mackie emulation and now that it is here, I'm ready to dive in and make one! Would you be willing to offer some feedback on how well it works and I'm still confused on what modules I really need to build. Also, how many I would need to build if I want 25 motorized faders (24 for channels and 1 for a main bus). I really like the layout of the new Tascam US-2400 and I'd like to essentially make a clone of that. I 'm just still confused on what modules I would need for that, how many cores, how to interconnect them etc. There's alot of info on this site and I need some high level overview to bring it all together for me. Please help! Thanks!
  3. HAs anyone tried to copy the Mixed Logic M24 controller? I would like to create such a thing using this hardware if possible. -DJ
  4. Does the MF Module have the ability to support touch sensitive motor faders? I think this feature is important to allow for fine adjustments. -DJ
  5. I am trying to architect the various core modeules together to create something that has similar features as the MACKIE Baby HUI. I plan to have 16 motorized faders (touch sensitive), 1 motor fader for the master, 16 encoders, and a few buttons. Here are my questions: 1) I suppose I need a separate core for every 8 motor faders and every 16 encoders correct? Thus, for the example above, I would need 3 cores for the motorized faders and 1 core for the encoders. (And of course the 1 more for the main core that runs all of the midi, LCD, basic IO, etc). 2) Also, I mentioned touch sensitivity on the motorized faders - is that supported somehow in the MF core firmware? If not, what's required to do that? I hear that if motor faders are not touch sensitive, then it can be difficult to get them to release sometimes. 3) Is there another PIC part that has more IO to avoid having to use so many "cores"? There's room in the case, but that's alot of unecessary components! However, it sure beats spending $900 on a MACKIE Baby HUI!! Thanks.
  6. Do I really need the LCD display to achieve full functionality of any of the projects? Is it really only another form of visual feedback or do I need it for programming etc? If I build a unit that uses several cores, then I would have to have an LCD display for each core which doesn't make sense. I would rather do without the LCD unless I really have to have it. Please advise.
  7. So, let's say I want to build the motor fader project and download the firmware for it, but then decide I also want to add encoder knobs as well for the 16E project. What firmware gets used then? It appears that both projects require the core to operate, but if I load the MF firmware, then how do I get the features of the 16E? Does that mean I need to add a second core to function as the 16E? What about using an LCD panel, does it require yet another core?
  8. djsegler

    Doepfer

    Please keep me updated on your progress. I like building things and have used PICs before AND, the cost of buying a MACKIE controller or some other brand is too expensive as it does much more than what I need. This offers the exact solution for a much lower cost!! I am so thankful for this site and forum. :)
  9. djsegler

    Doepfer

    I agree - now that I have learned that multiple cores can be connected together. Do I understand correctly that I would need 1 core for every eight motorized functions? I would like to have 8 MFs, and 16 motorized knobs (2 for each of the eight fader channels). That way I can make a controller interface for Sonar that emulates the standard console view of 1 fader, 1 pan, and 1 effect send per channel. I like the motorized feature so that the knobs on the controller can be in sync and match the virtual knobs within Sonar. How does the MF firmware initialized to sync at the beginning? Does it automatically poll to obtain the set-up or do I need to send it automatically somehow?
  10. djsegler

    about LCD

    If you leave the LCD out, is it still possible to program the midi set-up parameters?
  11. Where do I find the firmware for the MF project? I would like connect two cores together to drive 16 motor faders if possible, but it is not clear to me what PIC code to use or where to get the code. Please help!
  12. djsegler

    Doepfer

    Is there any way to make a motorized version of this that retains all 16 faders?
×
×
  • Create New...