-
Posts
2,516 -
Joined
-
Last visited
-
Days Won
147
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by latigid on
-
-
I'm not confident I can work it out from the vague description; it's not your fault. MIDI is a current loop and the cables are passive. Normally resistors would be a good idea if you don't know what's what, but in this case they might hinder the operation by limiting the current. If you don't mind taking a risk or two, try the orientation you describe and swap it around if there's no joy. For a MIDI in, normally the 0v (ground) pin is not connected at the port. So you may wish to leave the sleeve of the TRS plug disconnected. Leave the pin two of the DIN connector connected to shield the cable.
You're free to use a male DIN or even cut an old MIDI cable apart to avoid using a female adapter plug.
Best of luck, YMMV etc.
-
I don't like the idea of combining MIDI in and out on one 1/4" jack. It's just another variation on the standard that will confuse. TRS 3.5mm jack with individual signals is bad enough :).
What feature do you wish to use? I.e using the MIDI in of the Strymon? Or sending the MIDI out from the Strymon?
-
Cool development!
If you like, I still have some of the USB PCBs around (maybe res-SD too). All wCores come with the USB attached; there's no current plan to sell them separately.
-
The matrix works fine :). The software is not yet optimised to work with the "inverted" sink driver.
-
-
You could try. First connect the MIDI out to MIDI in (loopback test).
http://www.ucapps.de/howto_debug_midi.html
-
Hi, welcome
Yes, MIOS Studio should be used to upload hex files for your SID app. First, the MIOS Bootloader should be burned onto the PIC.
http://ucapps.de/mios_studio.html
http://ucapps.de/mios_bootstrap_newbies.html
Find a list of suitable interfaces here:
http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_whitelistTypically avoid those on the blacklist, including a lot of cheap USB-DIN plugs.
-
16x8 LED matrix works well!
- 1
-
There's only one micro port on the DISCO board :). If you don't have a "special" USB OTG cable, connect pin PA10 to 0v (ground).
On the wCore, this is accomplished with a USBA port and a dedicated switch to enable host/slave.
-
5 hours ago, Antichambre said:
I'm waiting for new UI PCB before checkout... I suppose the ENC plates don't change, I've got v1.0?
Enc plates I think are unchanged since v1.0. Perhaps some diodes were moved around to lessen the chance of accidental shorts.
le mec is now at v1.3. Basically unchanged but some differences (mostly to do with minimising ghosting).
-
As far as painted keycaps go: it could work. I spent weeks emailing trying to get painted caps, but they would have been fully painted and much more expensive. So the idea with model train paint could be cool!
Personally I love the look of blank illuminated keys:
-
We could still label the Matias switches e.g. between the Matias rows. As you mentioned, the "GP" labels are printed on screen anyway. The selection row does change its function, and not all functions are 1-16, e.g. for selections regarding tracks, the group terminology (GxTy) is still used. Personally I quite like the "clean" look without extra labels.
Regarding brightness, Peter has gone for a fairly bright incarnation. If it was too much, you could easily increase the RJ values to limit the current. Personally I don't find the brightness too bad with 49R9s in my build.
There are two further options that might help. First, we are ordering a set of relegendable switchcaps. These won't be available for some time, but could be a type of upgrade. The cost will be more than the default DSA clear (which by the way have some diffusion on the top of the cap), as each cap comprises two parts. Then all Matias switches could be independently labeled.
Second, you can choose the colours of the step LEDs. Notice on TK.'s demo that positions 1/5/9/13 use a different step colour to the rest. This might help to differentiate them.
Best,
Andy -
Did you check the soldering/flux residue around the pins that control the display?
-
It could be a dud display injecting bad vibes onto the SPI, it could be a defective chip or flux residue.
-
-
As you noticed, you can't extend ribbon cables this way as you end up "mirroring" the connection. Better would be to use a male IDC such as this:
-
I didn't want to spoil it!
-
Not enough UARTs for 8 MIDIO. You can expand with I2C (up to 8 output ports, perhaps inputs as well but normally only ins are used).
-
There will be Mouser BOMs available but they're still being finalised. Don't worry, Mouser ships very quickly!
-
Nice idea! How do you plan on attaching the assembly to the panel? Still screws through the acrylic? Or can you weld the spacer to the panel and use a tapping screw thread?
-
Hehe, yes you should! I've got a set of blue/green LEDs if you want some.
For the 16x4, can you test the parts rather in stages? I.e. see if you can connect the SEQ to the Rx/Tx and check it works, then add the 16x4 then add the TPD. This should be doable by loading _NG and using set debug on in the MIOS Studio terminal.
-
As far as I can see, the split wiring is only necessary if you use separate DIN/DOUT modules. As you send/receive the full SRIO it should work with the J2_SI jumper installed and simple IDC10s.
-
It's really a great little box! We'll order another set of prototype PCBs in the next day or two, then after the SEQ is all sorted we can think about getting the LoopA to a ready state.
- 1
-
On 7/28/2018 at 11:56 AM, Antichambre said:
Genial! It will help a lot!
More than the Seq parts which are used here, this video contains a lot of tips and tricks! Great!Also, thanks for the initial feedback on the v1.0 wCore boards. The breakaway option and microMatch headers were incorporated!
Effect pedal, MIDI on a Jack.[SOLVED]
in Design Concepts
Posted
I'd say as these are built for guitarists rather than MIDI nerds, it's more than likely that there's sufficient protection built in. If the signals are around the wrong way it will not work but probably will not harm the unit.