ilmenator
-
Posts
2,304 -
Joined
-
Last visited
-
Days Won
37
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by ilmenator
-
-
2 minutes ago, Antichambre said:
I you don't want to use any Andy's Boards then you can go from scratch, with the pinout of J8/9 and a blank Config file, no?
Sure, that is always an option. However, having two different config files doesn't really make sense with the underlying functionality being exactly the same. But then, that approach also leaves a lot of freedom for changes, so that could possibly be a good solution as well.
52 minutes ago, latigid on said:It's not a priority at the moment, sorry.
I don't think you'd need to be afraid of schematics in the public - on the contrary, it would probably help you a lot once you have to do troubleshooting and support on your customers' builds. This community has been awesome in the past when it came to solving build problems. However, I do respect your priorities.
I'm looking forward to seeing the v4+ taking off!
-
13 minutes ago, latigid on said:
I'll probably put the matrix schem up at some point. For now, I'm happy to supply it to those who have purchased the PCBs (just Peter, Adrian H, TK. and lazy beta testers :P ) or to those who need troubleshooting advice.
That's not so nice, what a pity. So I'd need to buy a PCB from you in order to receive the schematics, although I don't even want to use your board?
-
Peter, nice work! Also good to see a mini-TPD, albeit this seems to have only a single color?
Are the UI schematics publicly available or do we need to reverse-engineer them based on the v4+ config file? I'm thinking about my own homebrew version using Marquardt switches, I don't like those christmas tree ones you are using :-).
Best, ilmenator
-
Ok, then what you have is the v2 version already. Here are some measurements, but don't get overly excited about the three decimal places, as the cursor's and the board's raster did not match exactly when I measured...
-
Is this for the v1 or the v2 BLM16x4 board? I think I moved some components around in the transition from v1 to v2 to make room for the added traces necessary to accommodate three different types of switches/buttons at the same time...
-
On 25.8.2018 at 5:21 PM, latigid on said:
16x8 LED matrix works well!
You've got the ON / OFF phases of the LEDs reversed!
-
Very nicely done, thank you!
If you want, you could add the build file to the TPD Wiki page - but only if you want, no obligation whatsoever - I just like the idea!
Best, ilmenator
edit: or, I could also do that, if you don't mind?
-
Just now, Antichambre said:
You will get the same problem with the switches, isn't it? Then...
Yes, and that's already bad enough, so why open it up for even more dust to enter?
-
18 hours ago, Hawkeye said:
Regarding the encoder knobs: we will probably suggest to Adrian to counter-sink them "into the frontpanel", i.e. have bigger cutouts, like another famous sequencer out there :).
I'd rather not "countersink" them - I always feel better without dust getting inside the enclosure.
-
Great that you've figured it out (and that you report here!)
-
Where are you located?
-
Check the repository, there is a MIDIbox solution for this from which you can take some code inspiration!
-
Congratulations, the unit is looking very nice indeed!
-
@tedysuwarnady I hate being the guy, but you are seriously misbehaving. You are continuously ignoring all the suggestions you get. This is tragic because answering them would help to determine what is wrong with your unit. It seems like you don't even care about help.
Also, please stop asking for schematics and board files in every other of your posts.
-
- 64 input ports and 64 output ports, scalable
- 8 mergers, freely configurable
- a panic button
- zero latency for the router
- configuration via software interface ("setup")
- handling via a dedicated hardware interface (remote control) that can be placed anywhere, e.g. on the mixing desk (like a Lexicon LARC)
- ports can be given a name, and these names are displayed in the user interface
- setups can be stored and recalled via MIDI, and there is a program change table like in some older Yamaha synths
- activity display showing in-, out- and merger activity
- modular approach, so that I don't have to pay for all the IOs when I only need 32 because I'm Hawkeye
- distributed, as in "I have a number of racks with equipment, and these are located all around my studio, but I want to keep my MIDI cables short with only one 'multicore' going to the central matrix from each rack"
- obviously DIY, but preferably there is someone who has done all the hard work, and PCBs are made available
- affordable
The v2 of this will feature all of the above
.
-
Sure, drop me a PM for details.
Best from Köln, ilmenator
-
1
-
-
We have had problems reported here on the forum when using 3,3V based MIDI gear trying to send data to certain 5V operating MIDI receivers. Maybe that is a path for further inquiry?
-
There weren't a lot of projects on the 16F88, so I assume you are refering to the MIDI merger project? This is located here.
-
Thanks for your update!
-
Very nice as always - thumbs up!
-
That would be much appreciated by everyone around here - thanks!
-
That's absolutely true, it is not always a good idea to go for the "best"/"biggest" tool :-).
-
Thanks for the good work! I'll put a link in the wiki pointing to this thread.
-
Drop me a PM.
ilmenator
-
1
-
midiphy SEQ v4+
in MIDIbox SEQ
Posted · Edited by ilmenator
I'm aware of that already, but that is a reverse-engineering process that I'd rather not spend my time on.
If the schematic was clean enough to create the board file with, then that is clean enough. I understand the term "priority" a little differently, but hey... It's good to see progress with our beloved SEQ!