Hawkeye

Administrators
  • Content count

    3,387
  • Joined

  • Last visited

Community Reputation

58 Excellent

2 Followers

About Hawkeye

  • Rank
    MIDIbox Guru
  • Birthday 01/15/1976

Contact Methods

  • Website URL http://www.youtube.com/user/Maelstroem3

Profile Information

  • Gender Male
  • Location Germany, Munich

Recent Profile Visitors

9,325 profile views
  1. midiphy SEQ v4+

    @studio nebula maybe for your peace of mind :) - before we launched the v4+, i tested my first batch of LeMEC boards for a full week, 7x24 hours using only 10R resistors all around! No single LED failed :). The 1/8th duty cycle probably made that happen - and at fairly quick duty cycle rates we probably are looking at average current rather than peak current, if we have a good heat sinking solution, which is given for those superfluxes. The average current would only something like 60mA divided by eight when you use a 47R for red. Nevertheless Andy since then has given me the title equivalent of "mad LED slayer" or such, could not decipher the word he used, hehe :). Note also that brightness did not increase much more when going down from 22R to 10R, the LED is just saturated and the long cycle-off time and the big internal superflux heatsink material will probably keep it from burning up. I doubt that you can kill it with a 47R even with disabling the matrix. But i think you will be really safe with 100R resistors all around, but i would not worry too much, in doubt the superfluxes can be easily replaced, as they are accessible from the backside. But never had to do it yet. Have a great new week start! Many greets, Peter
  2. Yes, agreed, a power supply issue might explain it (also back then for my old V4) - @Rio: do you have access to a scope and could monitor the 3V/5V supply lines during unit startup? This might also explain why problems don't happen with low-speed cards, as the transfer speeds or card response speeds might be limited and not pushing the system that much? Many greets, Peter
  3. In the case of my old V4, it was almost certainly questionworthy wiring of the SD card attached to a too long ribbon wire - and general noise introduced by VFDs, long wires and no buffering anywhere :). I don't think the schems have changed dramatically, but Thorsten or Andy may know more. Many greets, Peter  
  4. @Rio just as a confirmation, i sometimes had this problem, too on my old SEQ V4 (not the new v4+) and it occured just at power up time. Once the startup was successful and the SD card could be read, it did not happen again during runtime. I suspect the SD card cable might have been a bit too long, or maybe it was caused an unstable power supply. After upgrading to the new v4+ (with the shorter cable within the case) i never experienced this problem again - and i am using the same physical SD card as before, unchanged since 2010 or so :). Best regards! Peter
  5. MidiBox SID Sound design tips

    @Smithy also, your MBSID drum demo still beats all of my youtube videos regarding views! :) Bad friend! :) Hehe! Many greets, Peter
  6. midiphy Eurorack Expander Modules

    @TK. thanks a lot for your quick answer! We're discussing it! Many greets, Peter
  7. midiphy Eurorack Expander Modules

    @TK. if you have time, would it be possible to define a requirements list of UI features (OLED real estate required, encoders, switches, 3.5mm eurorack input and output ports) that you would like to see in a new dedicated future MBCV module? :) We were lately discussing/planning a new STM32F4 based digital oscillator eurorack module which may have quite similar UI requirements - that way we might get away with a single set of PCBs that could satisfy two usecases! :). 50mm max depth is a given. Many greets and best regards! Peter  
  8. midiphy Eurorack Expander Modules

    @lukas412 awesome! Hope you will have lots of fun buildling and using your new modules! Best regards! Peter
  9. midiphy Eurorack Expander Modules

    @lukas412 recently TK. came over for a visit, for a long walk and also to grab his new set of these modules! :) We performed a tracking test in conjunction with a purely digital oscillator on a MIDI controlled synth and could not really hear any problem at all over many octaves. That is, if you perform good calibration, which is explained in the video tutorial in chapter 64, here: https://www.youtube.com/watch?v=dD8VeSuTKWI&t=5561s Have fun and many greets! Peter
  10. seqv4 problem

    Hi Vincent, hope you are doing fine! Have you checked the switches themselves? (Just use a multimeter and see if you get 0R resistance if the switch is depressed). Some of the switches used in the Wilba V4 UI just failed after a while, my old V4 also suffers from this problem and has a lot of dead switches - i've currently retired it in the basement storage room! :) As you asked, the step switches are "in between" an input channel, the step LEDs, a diode, and an output channel creating the matrix, so no direct connection to ground - see attached schem region that shows the step switches 5&6 (center bottom). Many greets and good luck! Peter  
  11. Troubleshooting midiphy SEQ v4+

    @knochenfabrikcould you recheck/reflow the SMT IC soldering? DACs and opamps? Don't know if it is in the problematic output circuit, but the upper left pin of the transmute8 IC4 in the pictures looks like a bit bigger than necessary solder blob. Also, sharp high-res photos with good lighting would help! Thanks a lot and i am sure you'll get the last channel up and running finally! For me it's back to video tutorial cutting... Many greets and good luck! Peter
  12. Troubleshooting midiphy SEQ v4+

    @niles unfortunately, not all MIDI USB OTG gear seems to talk well to each other. For example my (older) AKAI MPD24 works perfectly via USB with the SEQ, but my newer, small-keys midiplus x4 mini keyboard (which looks a bit like the keystep) does not yet work. It think there might be a software/communications handshake issue with some newer USB MIDI gear - which has the advantage, that it might be fixed at some point in time, if someone has the time to look into it. Best regards, Peter
  13. New eurorack modules in the house! :)

    Thanks, man! Working on the corresponding video build tutorial now, which will cover everything (including set-up and calibration). These modules should also work fine with your SEQ v4, if you have a line driver (transmitter) board with a DB25 output connector installed. Have fun and many greets! Peter
  14. Troubleshooting midiphy SEQ v4+

    Please also note, that we decided to sell the boards early due to demand, but now have an extensive video tutorial on them coming up shortly, it will cover: * assembly * cable building & wiring within your eurorack, * setting up the modules in the v4+ (configuration file and menu) and * fine-calibrating the CV outputs individually over 10 voltage-steps of the eurorack output range It also contains a small "track test" showing the v4+ in a fun looping mode, echoing previously recorded notes to two CV-outs using the SEQ duplication effect. We've got over 220GB of input source video files on disk, which will need cutting, speedups and voiceover, but working hard to publish the tutorial soon! :) Have a great new week start and many greets! Peter
  15. Hi jzurd0, am not really experienced with USB MIDI recording, went DAWless a while ago and never looked back ;-). With RTOS as a reliable base and TK.'s code on top, as a first guess, i would not think the latency issues are caused by the SEQ app. The problems might well happen within the operating system or the USB driver itself on your computer. Which OS and which computer hardware are you using? USB MIDI under windows is unfortunately a bit unreliable and i would not wonder, if multiple MIDI streams would cause jitter problems there. Recommendation: if you are using windows currently and have access to a Mac, could you try it with that? If you are already using a MAC, you could use a tool like MIDIPipe https://www.heise.de/download/product/midipipe-28614 to display and log inbound MIDI messages over USB - that way you should be able to analyze any potential latencies, before the MIDI messages are handled by the DAW. If these latencies are reproducable (e.g. by analyzing timestamps of two MIDI packets that should arrive around the same time but do have variable jitter over time, e.g. bassdrum and synth), this would be a starting point to investigate things in the SEQ app.  Many greets and good luck! Peter