Coma

Ok, yo te ayudo no tengo problema. Tenés algún archivo setup ya modificado que quieras compilar? Si no decime cuántos led rings, encoders y pots tenés y cómo están conectados y te lo compilo. Si ya tenés un setup armado es más fácil porque evitamos errores. Pero si se te complicó con eso, lo vemos.

The attachment which gives me an error is "DIN - DOUT Schematic & Board.rar". The remaining works just fine. I'll wait for those updated versions anyway, really thank you!

Sure, here's a link: http://line6.com/community/servlet/JiveServlet/download/1229-2gearbox%20midi%20cc.pdf Attached too in case link brakes. The product I own is Gearbox. gearbox midi cc.pdf I have done some testing with MIDI with this software, I have some understanding of how it works that maybe isn't shown in the manual, please do ask for any question. I'm still defining how I want the interface to be, I'll post that and the test application I put together in C. I managed to send specific midi CC I need but couldn't think or find of a way to make bars displays, only could do text and numbers. Anyone can give me a hint where can I find some functions or examples in C to do them? Thank you!

Primero, felicitaciones por haber llegado a este punto, no te falta mucho parece. ¿Probaste recompilar el código fuente de Midibox64e? Si te fijás en el paquete midibox64e_v2_2c se incluye un archivo llamado setup_midibox16e.asm ó setup_midibox64e.asm Abris ese archivo con un editor de texto común y podés configurar cuántos cuántos DINs, tenés y demás. Luego tienes que compilarlo, para eso hay un muy buen tutorial en la wiki donde te explican qué herramientas necesitás y cómo instalarlas. http://www.midibox.org/dokuwiki/doku.php?id=windows_toolchain_quickstart Con esa configuración me parece que podés cubrir las tareas que describiste. No hace falta programar nada nuevo, solamente setear el midibox64 al hardware específico que tenés. Por ejemplo, cada cual puede ubicar los botones de MENU donde le convenga y luego en ese mismo archivo configurar cual es cual en el siguiente fragmento de código (lineas 120-125 de setup_midibox16e.asm): ; DIN pin numbers of menu buttons #if DEFAULT_ENC_DATAWHEEL == 0 #define DEFAULT_DIN_MENU_EXEC 7 ; menu exec button assigned to DIN pin #7 #define DEFAULT_DIN_MENU_RIGHT 6 ; menu right button assigned to DIN pin #6 #define DEFAULT_DIN_MENU_LEFT 5 ; menu left button assigned to DIN pin #5 #define DEFAULT_DIN_MENU_SNAPSHOT 4 ; menu snapshot button assigned to DIN pin #4 Por ejemplo si tu navegación derecha e izquierda querés que sean los botones 0 y 1 tenés que remplazar 6 por 0 y 5 por 1. Si ya tenés bien definido que querés pero no querés ó no podés instalar las herramientas necesarias, adjunta el código de tu setup_midibox16e.asm que quieras compilar, yo te lo compilo y te paso el HEX, pero te recomiendo poder hacerlo vos mismo ya que es muy útil para probar cambios que quieras hacer.

I'll try to make a simple example to describe what I need. Let's say I have 2 types of effect which may have up to three models. TYPE: Stomp MODELS: Synth Harmony, Synth Lead, AutoWha TYPE: Delay MODELS: Multi-Head, Sweep Echo, Digital And each model has it's own set of parameters: STOMP EFFECT MODEL P1 P2 P3 P4 Synth Harmony Inter Filter Wave Mix Synth Lead Wave Filter Decay Mix Auto Wah Sens Q DELAY EFFECT MODEL P1 P2 P3 P4 Multi-Head Fdbk Mix Heads Flutter Sweep Echo Fdbk Mix Speed Depth Digital Fdbk Mix Bass Treble Let's say I have 5 encoders. My idea is to have 2 buttons for group change, 1 encoder to control effect model and 4 encoders to control parameters. Labels of parameters should change when I change models. Banks, groups, patches, I don't know how to organize it and program it properly. Any suggestions/hints? Thank you and sorry for doubleposting and lack of clarity (non-english native speaker). update 11-18: I'm starting to check C app developmet stuff on the wiki and it seems it might be a lot easier to code a custom app in C than modify/hardcode asm source of MB64e. Until someone may give me a thought or two about this I'll try to build a custom app to do what I need. update 11-19: with C tutorials and samples I managed to make a little app to switch which CC# a single pot sends. I guess I'll build up from there. Found some interesting topics about scaling (didn't know the term until now). Still don't know how will I manage presets and I don't know PIC's limitations regarding memory usage and stuff. Seems like I may work things out myself but some thoughts and ideas are welcome!

Hi, I want to build a controller for my guitar amp simulator of choice, which is Line6's software. I bought a couple of kits from SmashTV(core, din, dout, ain), soldered and tested with pots, buttons, lcd and leds, so far so good. I'm awaiting for the encoders, which I had to bought abroad because couldn't find them here. The main concept is to use 8 encoders to controll the different parameters of each effect (no effect has more than 8 parameters). What I couldn't get right is which method to use to change what effect will be the encoders controlling. I understood there are groups, banks and patches, but couldn't make up my mind on which method would be better. I have 8 sets of parameters I would like to control, and I would like to save several presets of those (and maybe playlists for the near future) How should I proceed? Thank you for your support.

Retomando un poco la idea, nadie más en Argentina quiere mandar a hacerse PCBs? Mayer hace tiradas con un mínimo de 10 unidades nada más? Serían $80 del "master" y después $12 x 10 placas. $200 las 10 placas. $20 cada placa. Igual quiero confirmar si esos números están actualizados, me voy acomunicar con ellos pronto y posteo.

I can't seem to find the Eagle schematics. Were they lost in the forum update or removed by some other reason? Or I'm too dumb and just can't see them? Thanks!

I don't know why I couldn't complete that sentence. Last night I assembled my first core from a KIT from Avishowtech and it worked perfectly. Now I'll make a little controller for Cubase to test things out a little and then I'll go for the FCB controller modification thingy. One GREAT workaround would be to find a FCB with non working electronics and working mechanics because striping a perfectly working unit does seems wrong. Hard to find one of those FCBs around here but I'll try. I would like to know how hard/expensive would it be to make a custom firmware for the fcb1010, can someone point out any forum where I could find people that can give me some directions about EPROM programming?

Well, I mind the led stuff showing correct effects on/off state. For unconsistent led behaviour the FCB is pretty programable as it is, with the UnO firmware. I dropped a mail at the guys that make Gordius asking them for the firmware but they can't release it or sell it by itself. I'm more than thankful with them for releasing the UnO firmware which is just awesome. I'm walking on even thinner ice considering I didn't even successfully assembled a single core module! But is nice to get a perspective of the specifics of what can be done with midibox and how hard would it be. Ripping the electronics out of the FCB crossed my mind, but it is

Hi, yeah, I've noticed it is written for PIC18F4620. Thanks for the heads up. I don't want to run before I know how to walk, so I'll get a core with DINs and AINs running and then try to work this out. I'm also interested in making a MIDI interface to use as a controller for line 6 VST. Something similar to Axe-FX but running on a PC and with Line6's software instead of Axe-FX's. So first thing first I guess. edit: I've just discovered something (rather important) in Little Giant Manual. So there's a special firmware to enslave the FCB1010 to the Little Giant and I would need another firmware to make a pedal/midibox work with the FCB1010 properly. Does anybody have any experience programming firmware such as this? Where should I start? I have some programming experience but none with assembler nor firmware stuff.

Yo me prendo con 2 core, 2 din, 2 ain y 2 douts. Habría que llegar a 10 ó a 20 de c/u?

Eduy2kk, buenísima data! Sería genial juntarnos algunos y encargarse una tirada grande de cores por lo menos. Lamentablemente no creo que lleguemos nunca a ser los suficientes acá en Argentina. Pero bueno, acá está el espacio para juntarse. alogic, no se si estamos hablando de lo mismo. En ucapps está este modelo de placa. Y en el online store podés comprar este. ¿Se puede trabajar con este gif último y armar esa placa bifaz? Yo deduzco que sí, pero al no querer complicarme demasiado prefieor encargarlo y dejar la manufactura de pcb para más adelante.

Hola! Yo estuve viendo para hacerlas por mi cuenta ó mandarlas a hacer y decidí encargarlas a en http://avishowtech.com/ El costo de envio es de aproximadamente 30 u$s hasta 8 libras. En esas 8 libras entran 1 kit core, 1 kit din, 1 kit ain y 1 pcb ain y 2 pcb din. Uno de los problemas que me hicieron decidirme por encargarlo es que la calidad del pcb es muy superior a lo que podría hacer por mi cuenta y probablemente aún superior que lo que puedo conseguir que me hagan acá. Ah y me pareció que la versión que hacen en avishowtech es la 4º y solo conseguí esquemas de la 3º. ¿Cuál querés encargar vos? Sin embargo me interesa apoyar la propuesta y algun módulo LTC. Si posteás algunos costos te confirmo. Yo estoy en buenos aires, capital. Saludos!

That's exactly what I'm talking about. Thank you very much! I¡ll try to build one as soon as I get the parts. edit: I see there's pretty much programming involved to get it working as needed. I think it would be better to make myself a simple core+ain+din midibox first to familiarize with MIOS and all that stuff and then see how far can I get with the pedalbox. I'll oder the parts asap.