Jump to content

b.vigo

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by b.vigo

  1. Thank you guys for your replies; however, I got quite confused at certain points (I hope I'm not a nuisance). Let me take a look at them:

    The cores you're looking at is the PIC based ones. They have no USB as such. If you really want your builds to use 3 USB connections, then i think you should take a look at core32 module which has a USB connector.

    Is the core32 capable of handling analog inputs (pots)? I find encoders and LED rings harder to set up and configure, as well as the core 32. If not, I think I'm staying with the core8.

    And something else... is it possible to connect a core8-based controller (those with no usb port) to a pc using a Midi-to-usb converter (some kind of cable I found on stores and seem to be quite cheap), for both configuration and usage of the controller? - If this is true... I've been thinking of the following SOLUTION...

    2432.jpg

    (Power connections were ommited, obviously)

    If not, I'll immediately delete the image due to my excess of ignorance and stupidity.

    Because, you see... that gm5x5x5 interface (is it an...?) thing just made my brains explode.

    The bankstick is simply RAM.

    I got that clear now. For the project I have in mind... do I have a way to estimate how many of them will I need?

    No, you will most likely not miss an LTC.

    *phewh* ...believe me, I won't

    The app goes in the Core. The core is the CPU (so to say).. if you don't upload any app, then your buttons and knobs won't do anything. the app detects which control you're touching, and will send out MIDI data accordingly. It is like the OS of the box - remember that practically all the projects inhere uses the same Core module... the difference is in the app. The app also controls the LCD, menus and everything.

    This is by no means anything that should stop you :) it is just a file you send via MIDI from a piece of software that is very easy to use

    I understood the example. However, this is the thing I'm mostly scared of. I have no programming knowledge at all, and I wonder if there's a guide out there that could help me doing so. Are there any available pre-made apps on the internets that I could use and upload directly to my midiboxes?

    You should always go for the PIC that is mentioned in the build guides.

    Thy will be done, master.

    I hope you will enjoy it inhere, and maybe even get to see some pictures of your boxes in the forum gallery

    I'll definitely take my time to share the experience in the gallery. :thumbsup:

  2. Hello, people. Newbie here.

    I've been spending the last month doing a sketch for a project I have in mind (a Traktor Midi controller) and have been browsing forums and guides for info. The sketch is ready and I'm about to order the parts (PCB and components) and start building it. However, I still got some doubts I'd like to clear before buying anything.

    - What I have in mind is to build a set of 3 controllers (One for the 'A' deck, another for 'B', and the last one for the mixer, each one connected to an USB port) where each of them can work independently from each other. This would mean I'll have to use at least 3 independent cores (PIC based). Will my computer be able to recognize each of the controllers separatelly, and if so, how would it do so? What 'names' will it use for each one?

    - What is a 'Bankstick' and what is it useful for? I still can't figure that out!

    - Is it necessary to connect a LTC to the core? Will my Midibox be able to work without one? (I read at some part that configurations can be done while connected to a pc via the Editor, after installing MIOS -using SysEx- on a burned PIC, am I right?)

    - Will I necessarily have to use and upload apps to the chip? In what ways can apps help you when it comes to a midi controller?

    - I'm thinking of buying pre-burned chips (for the Core8) at SmashTV, and one thing I noticed at the Core8 Section is that you can choose between different chips (PIC18f452, PIC18f4620 and PIC18f4685, if I'm not wrong). Does this mean there will be different steps for each of these when trying to set up a controller? (The guide is explained for a PIC18f452 as far as I know, so in case this is true, I think I'll go for this one)

    Thanks for reading. I'm really willing to learn about this, so I would greatly appreciate help with any of the above questions. Oh, and sorry for my english, in case an error is found. It's not my native language (:

×
×
  • Create New...