Hawkeye

Administrators
  • Content count

    3,547
  • Joined

  • Last visited

Everything posted by Hawkeye

  1. LoopA Pro Metal Case

    From the album LoopA

    Revealing the brand new design plans for the new midiphy LoopA pro metal case, hope you enjoy! :) The final production version from Hallik Engineering might look slightly different, as this is just a photo simulation. Note, that you can easily install the available "caseless LoopA kit" into this case, when it is available, so you could already build and operate your LoopA now, and put it in the metal case in early 2020! Have happy holidays & enjoy creating! Peter  
  2. @Smithy, super cool and very nicely done! What was your total time to build it? 8-10 hours? Now awaiting your first official jam with it! :) Many greets! Peter  
  3. "P-Locks" for Midibox Seq 4 ?

    While the concept is differently named than on the Elektron sequencers, the parameter layers of the MIDIbox SEQ are very powerful and allow a "per-step" modification ("parameter locks") of different parameters. Basically, up to 16 such layers can be enabled per track/sequence, and of course you have 16 tracks/sequences that can run in parallel! Available parameter targets (layer names) are e.g. Note/Velcity/Gatelength/Chords/CC/PitchBender/Delay/Probability/Roll. In addition you get trigger layers for functions like Gate/Skip/Accent/Glide/Roll/Random Gate/Random Value/No Fx. With these features and a "high-res" sequence using many steps (e.g. 256 steps) and a high divider value (to play back steps quicker to retain the same short sequence runtime), you should be able to create almost anything that can be achieved with MIDI outputs, from drumrolls to filtersweeps, to... whatever you can imagine! :) Many greets and enjoy! Peter
  4. Congrats to the finished build, well done! :) I think you are right with the M3 nuts for the case interlocks, these should be low-profile nuts and we probably have packed normal-sized M3 nuts in the first kits. We'll contact all customers of the acrylic kit variant and (if required) send them eight replacement nuts! Other than that: hope the build went well for you and that you enjoy your new toy! :) Many greets, Peter
  5. Wohoo, congrats to the nearly completed build @Smithy! :) Also thanks for your photos! I just measured with the caliper and think there should be >2mm of clearance, if the 8-pin connector has been filed "flat" at the top: The OLED pins should be cut close to the PCB, that is very true: We are aware of space restrictions within the case, but wanted to create a really slim DIY device, so this is on purpose! :) Many greets and enjoy your new LoopA! Peter
  6. MIDI over Bluetooth with ESP32

    Very cool development, well done! While the girls in the house insist on automatically shutting down the WiFi network at bedtime "so they can sleep better" :), i can see why wireless connections would be cool, maybe also in a ProgrammA context :). Many greets, Peter
  7. midiphy Eurorack Expander Modules

    @sis.tm and @latigid on just had a look in the code to see what is really going on in seq_lfo.c - as a short conclusion, if a "note lfo" is used, the lfo value is rounded to an integer value between 1 and 127 to reflect a MIDI note - so even if this was put out via AOUT, that is probably not what you would want in a CV scenario (a more or less "stepless" continuous LFO waveform). Probably it would be best to ask TK. in the main SEQ V4 thread for a CV LFO expansion with non-note-steps, if possible, we'd also vote for that expansion, of course :)! Best regards and have a nice weekend! Peter
  8. @Phat, that sounds great! At some point in time, the LoopA software will probably get a CC track type, but it will never be as powerful as your dedicated CC Looper, that can just use the full STM32F4 memory for that single purpose :) Many greets, Peter
  9. midiphy SEQ v4+

    Very well done and thanks a lot for the nice report, @lp1977! Best regards, Peter  
  10. Strange behaviour?

    Hi Simon, first of all: that's one awesome datawheel knob! :) Yes, the strange behaviour without SD card is normal - the v4+ looks for the hardware configuration/layout file on SD card, from there normally the midiphy config is loaded - if it is not there, it will assume an "unmapped/standard SEQ", which does not match to the layout of buttons/shiftregisters, etc. Nothing can be damaged that way and all will revert back to normal, when you launch it with the SD card with the configuration file. The stability issue could be caused by unstable/insufficient +5V USB power. I had a very similar problem with my LoopA a few months back, switching to a better USB power supply or a high quality powerbank (for mobile use) solved it for me - could you try that out? Best regards, Peter
  11. Sammich UK PSU

    Here is a discussion with a similar question: so, from that thread, this here: http://www.buythis.co.uk/product/4927/genie-psu500-in-line-12v-dc-500ma-regulated-linear-power-supply might still work? You are probably fine with a high quality modern switching PSU as well, as long as the switching frequency is well above the audible range, especially as the SIDs are a bit noisy by themselves :).  Best regards, Peter
  12. Caseless LoopA available now! :)

    @sis.tm and @slo Thank you both very much! I am also glad it's finally out, it took too long, but there's the main job, the family and all the other distractions :) Many greets, Peter
  13. @Altitude as requested, we've now released the acrylic frontpanel plan as a SVG, as another customer wants to create a custom 3D printed case and asked for it. There is a 3mm "size indication" in the SVG, which can be used as a reference for scaling on your side. The plan is linked on the bottom of the "caseless" LoopA shop page: https://www.midiphy.com/en/shop-details/139/69 Direct link: https://www.midiphy.com/files/d14/LoopA%20Acrylic%20Case%20Frontpanel.svg Have fun and best regards! Peter    
  14. Thanks Bruno and Altitude! :) Altitude, will send you the acrylic case display cutout dimensions via PM or email shortly. Best regards and have a nice sunday! Peter
  15. Caseless LoopA available now! :)

    Thanks, ssp! All the credit for this picture goes to latigid on! :) Best regards, Peter
  16. Troubleshooting midiphy SEQ v4+

    Hi Adam, no problem to send you a spare LED, with all the "Murphy's Law" you encountered during the build! But, could you count if you don't have a spare already? For similar reasons (i.e. if one of the LEDs is defective from the start or is damaged during installation), we usually pack a total of 60pcs 2x3x4mm LEDs for a full kit, so there should be more than a single white 2x3x4mm LED left over as a spare. Have a good sunday and best regards, Peter  
  17. Acrylic LoopA available now! :)

    From the album LoopA

    Finally, after 4+ years of development! :) https://www.midiphy.com/en/shop-details/139/65/loopa-acrylic-case-essential-kit Hope you enjoy! Best regards, Peter
  18. And, it's finally release-day, sorry for all the delays and thanks to everyone who helped! The LoopA is now publicly available in two variants, a caseless/barebones variant, and an acrylic case variant: https://www.midiphy.com/en/shop-details/139/69/caseless-loopa-essential-kit https://www.midiphy.com/en/shop-details/139/65/loopa-acrylic-case-essential-kit Also, Adrian Hallik from Hallik Engineering is working on a new metal case, which should be available in early 2020. You can easily transplant the caseless LoopA to any case. Here is the full (2 hours +) video tutorial, all in all it should be a doable project and there are no IDC cables to build! :) And here are some impressions/photos of the kits and the final units - enjoy! :)   Firmware releases and user manual/handbook documentation updates will always be posted/linked in the first posting/on top of this thread! Have a great weekend and hope you enjoy the LoopA! Best regards, Peter
  19. Open source documentation for MIDIphy stuff?

    Probably it's best to keep the personal discussion in private via PM, no public fighting please. Will lock it for now, can be reopened if requested and if nonpersonal technical/legal discussion continues. Have a good weekend, it's a hobby, take it easy! :) Best regards, Peter
  20. Open source documentation for MIDIphy stuff?

    Please define "open" - anything that has been released in the recent decade or so, is based on TK.'s designs. This ecosystem, the MIDIbox hardware platform is fully documented, with free schematics and there is full source code available, everything is free for personal usecases. That's an awesome gift from TK. to the world! "Manufacturers" like Wilba/SmashTV, now sold via modularaddict.com or midiphy.com have just added a few bells and whistles to TK.'s ideas, like some fancy OLEDs or just added nice cases - but the base, the ecosystem is always the same, the modular, fully documented MIDIbox hardware platform. As "product development" takes time, effort and money, these manufacturers usually opt to protect their investment by not fully releasing e.g. CNC case plans or gerbers. These "products" are ok'ed by TK. for the reason, that a broader base of users can have access to the MIDIbox platform. Otherwise, creating everything from scratch will take time. E.g. i've built my first SEQ v4 completely from scratch in 2010, back then i had the time for it and it was an awesome experience (it's even documented somewhere in the forums with a photo tutorial, search for "ebony seq v4"). But not everyone wants to do that, or has the time for it. So, to answer your question: assume everything listed on ucapps.de is released under a "free for personal use license", everything sold commercially has to have been "ok'ed" by TK. before and those products do not automatically inherit full disclosure obligations of every file needed to create the product. If a "vendor" asks TK., if it is ok to release a MIDIbox-based product commercially, TK. will always ask for guaranteed customer support and probably look for a good track record in the forums of the respective creator over some years. Speaking for midiphy - in your own project, if you ever plan to use any unclear feature of our products, e.g. how the superflux LEDs are controlled, how the activity matrix is driven, or what is necessary for noiseless OLED operation, just ask the respective questions in the forums and i am sure you'll get technical and detailed answers. Best regards and have fun creating! Peter
  21. Open source documentation for MIDIphy stuff?

    @Corwin Probably all has been said now, there should be need to escalate things further, that is, if you, as the original poster are not out for an escalation? Of course, this is highly subjective, but as a personal sidenote, I don't see how "open source", "free for personal, non-commercial use" could be enhanced any further without adding pages of useless legal smallprint, that does not really add any more information? You're here to create a new personal project? Absolutely awesome! Welcome to the forums! If you want and have the time, please share your ideas, create a new thread for discussion with others. Feel free to use and enhance the available software in any way that is required for your project, it is all good. Have a good friday and a nice weekend! Peter
  22. Open source documentation for MIDIphy stuff?

    The software license is documented here: http://ucapps.de/mios.html Software Architecture Open-Source: yes(completely) License: Personal, non-commercial use only --- So, in short words, you can use MIOS for personal non-commercial projects at any time, you have full open source software access via github. If you are planning to sell anything (hardware or software), just ask TK. - it's not super complicated. Have a good day and best regards! Peter
  23. Open source documentation for MIDIphy stuff?

    What are you looking for exactly? The midiphy schematics are not publicly available, these are only handed out to customers, if required, which is similar to what Wilba's did when he was actively designing PCBs.  Usually, the schematics would be required to find and fix a build problem, but these problems are most often and more easily found and corrected by direct support, which is mostly done by latigid on. If i recall it correctly, there is not a single SEQ v4+ that was not completed due to a tech question. If you want to start scratch-building a new sequencer, really, ucapps.de has the best documentation out there, that you can think of. Best regards! Peter  
  24. It's all documented in here, including the proper hwcfg reference - Modularaddict sells the Wilba boards. Have fun with your new SEQ V4 and have a nice upcoming weekend! Peter
  25. Open source documentation for MIDIphy stuff?

    The source code is available on github: https://github.com/midibox/mios32 The schematics are available on ucapps.de and on wiki.midibox.org - this should get you going DIYing a CV sequencer from scratch. Have fun and have a nice upcoming weekend! Peter