Jump to content

HUROLURA

Programmer
  • Posts

    156
  • Joined

  • Last visited

Everything posted by HUROLURA

  1. I am working under win XP (both for dev PC and internet access PC). Is the command the same ? Where should I type it ? I usually try to dedicate a PC to each task to prevent messing up one thing working while working on something else. For that reason I also have a Creamware/SonicCore Scope SDK dedicated PC. Besides, the Internet access PC is the familly one. Thanks for the upload access but this would take some time before I would have something to upload. Just starting MIOS32 programming now. I first have to setup my "dev PC/Mios32 board" couple. The dev PC is a Win XP Asus EEEPC 900. I also intend to use it for installing the soundart Chameleon SDK. The Mios32 board is almost finished.
  2. Just wanted to know how you achieve simply this process (any special tool) rather than downloading files one by one ... 2nd question would be how to offer modified source code to the Midibox community
  3. From www.soselectronic.com: - EADOGXL160W-7 would cost 26 € excl VAT for a 69x43 mm viewing area (160x104 pixels). - RGB EALED78x64-RGB would cost 30.4 € (!!!) excl VAT whereas EALED78x64-A amber only model would cost 8.25 € excl VAT An OLED 28x35 mm (much smaller) 176x220 pixels display with serial control would cost around 39 € excl VAT. A T6963C controlled simple 132x39 mm (240x64 pixels) display would cost 41.8 € excl VAT I do not think we could control a true TFT display as this would require much more RAM ...
  4. Has finished assembling his 1st Core32

  5. Regarding the display: I downloaded the DOGXL160-7 160 x 104 simulator which is usefull. I think the RGB backlight could be great to improve user interface by color coding the differents parameter (8 colors availables). Alternatively, this could also be achieved with a true mini TFT color display ...
  6. Ok, I spend some time this week end to get through the different synths I would like to be able to control with this Midibox. The general setup would be: - 1 set of control elements for "classic" audio flow OSC/MIX/FILTER/AMP/PAN + 1 simple display to show the parameter change - 1 set of control elements for managing the mod matrix (probably with a display both to show the routing and to control it) - this second set should be also used for seq management
  7. Hum, two Core32 ? What other project do you have in mind ?
  8. OK, I started building up my Core32 while still thinking about the best way to organize a simple and efficient user interface that fits my needs ...
  9. HUROLURA

    HUROLURA 1st MIDIBOX

    Core32 based Midibox
  10. From the album: HUROLURA 1st MIDIBOX

    Next step would be to install MIOS 32 ...
  11. From the album: HUROLURA 1st MIDIBOX

    So finally I started building my very first Midibox board: a Core 32. It is alive !!!
  12. Received my package. Will see what I can get working out of it. Most of the trouble regarding other set of pieces seems to come from bad pcb (ground short circuit).
  13. From what I understand, there is 3 leds inputs on the backligth to control each of the color leds ...
  14. I do not understand the full color backlight ? Does that mean you can control the color of the backlight ?
  15. I am more used to handle T6963C controller based displays hich can connect to the Core32 LCD connectors. I am not sure the I2C or SPI access can be more efficient than the parallel access provided on the LCD connectors. But I will check it out ...
  16. This one would be the most flexible as it could be re-arranged for any use. But I do not feel this would be the most user friendly. I would miss some extra knob. I thought about using the same kind of display but beside a more synth structured "classic" Midibox.
  17. Do you also have a MIDIBOX + ASX project ? Maybe we can discuss about it ...
  18. From the first look I had to Midibox64 source code I just noticed it was PIC assembly language !!! One more good reason to use CORE32. Any mod would be easier ...
  19. Cool So now I have to startup assembling mine ... Here we go !!!
  20. OK, so as Philetaylor, this one is not a real MIDIBOXed device (so far). The only DIY part are the wood panel. But the MIDIBOX I think I would like to build would probably integrate some features to control ASB invisible features (knobs for FX control and realtime control through pitch bend, modwheel, velocity and aftertouch). So the chalenge for me is first to imagine a way to provide access to multiple external synth including ASBs, ASX/Plugiator, NOAH Ex, Chameleon, and maybe a few Waldorf gear. I must admit it is a rather ambitious project but that's mine. The second step would be to build it up !!!
  21. Regarding the Midibox 64 upgrade to the Core32, maybe we can work together on it at first, share it with other members here and then customize it to our specific needs. I just had a look at the USB_Midi_2x2 which could be a good starting point.
  22. OK I just spent the last 15 minutes to finish my first MIOS32 MIDIBOX to house an ASX synth board. As you advice, I took one picture of it. Here it is: I thought I should call it the ApFool 01 This is just a preliminary version and I think I could improve it further. Maybe it is a bit in advance on its time. What do you think about it ?
  23. The first idea is what I would like but more than one CORE would be neceassary and ... I do not have the room for such thing !!! The second idea I had is more or less a kind of MIDIBOX 64. So Mios8 should be enough. As already mentionned I only have a MIOS32 board. And my idea would also be to design something I could you use also with over synth by selecting a different mapping (CreamWare NOAH, Waldorf MicroQ, Soundart Chameleon Australis ...). So maybe some more memory would be more flexible. And I could still add a small steseq goodie afterward.
×
×
  • Create New...