Jump to content

Nirokesan

Members
  • Posts

    46
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Nirokesan

  1. Nirokesan

    10 copy.jpg

    What knob are you using for data wheel?
  2. Welcome! Glad I could help (though I had the smallest of parts)
  3. I received an email from someone attempting to sign-up for the forum. He says the sign-up and contact forms are broken. I tried to create a dummy account and could not pass the security screen, and I'm sure I had the correct answers. Can someone look into this? Is there another thread already discussing this? I searched and did not find one. thanks!
  4. Thanks for the help. I don't know that this is "fixed", but I too logged in using my username after resetting a password and it seems to be working. Cheers!
  5. I just looked at my account settings and it shows my password being 8 characters long but the password I just created to log in and write this post is 12 characters long
  6. This is terribly frustrating. Every time I try to log in, I'm told my password doesn't match. I request a change, change it, write it down, and next time it's "wrong" again. Why is this happening?
  7. I opened the 303 and tested the socket connections which all seemed fine, but there was no solder on Pin 2. Maybe it broke free from the pad and pin? I don't know. Added solder there and reflowed the other pins. Works fine now, trigger length is 3-4ms here, can't remember
  8. https://i.imgur.com/7CDCKkM.gifv DIN Sync out via the DOUT Clock+S/S SR# works fine with my 606, however, I needed to use a trigger length of 2ms at least otherwise the 606 played in some broken sort of half-time. The above GIF shows a trigger length of 3ms (maybe 4ms) and a tempo of 128 bpm. So the failure I experienced before must be the fault of my 303. I've tried with two different cables that have both been tested for continuity. I just did a test between my 606 and 303 alone and discovered some irregularities. Both units play fine by themselves. When I connect the two together, the clock rate on the 606 also flashes on the 303 showing that the clock is getting through the socket and interrupting the internal (this is different from the connection to the DOUT as the MIDIbox clock is not running until you press play). When I press Run on the 606, the clock on the 303 stops flashing but the Run light is on, no sound from the 303 (just like with the MIDIbox). Obviously I need to look at the schematics and take this issue elsewhere. (edit: looked at schematics, a bad pin 3 solder joint on the 303 socket could be the problem. Will examine) Bottom line is.....DIN Sync from the DOUT works just fine if the trigger length is set larger than 1ms (increase if necessary), I can keep my breakout box design, and I can use different timing divisions.
  9. Thanks for your reply, Gerald. Yes, I'm using SeqV4 with latest software. I cannot test J5B without disassembling my sequencer enclosure, and I'd prefer not to if there is another solution, especially as there is no room on the rear panel to add any more ports. my hardware and config file are all set up as you can see in this GIF : https://i.imgur.com/BFUeDRB.gifv The right-most column of sockets and LEDs is showing the SR assigned to clock and start/stop. You can see that I have different clock divisions set for the separate clock outs, and all Start/Stop outputs are held "high". I'd prefer to use this DOUT SR for DIN Sync to my Roland gear since I can supply different clock divisions to each machine, and because the case is already built with the provision for two DIN ports. The questions are....why is this DOUT SR failing to drive my 303, has anyone else got this working with STM32 and DOUT, and how?
  10. I thought this was going to be simple, but I haven't got it to work. Is anyone using a DIN Sync out with an STM32? I searched the forum and most of the posts involve the older core and boosting the signals from 3.3V to 5V. During my build, I just assumed that I could use a DOUT SR set to clocks and start/stop, wire a pair to a DIN Socket, and be good to go. That didn't work. I thought perhaps I had the pin-out of the socket wrong (top two google images for DIN Sync out contradict one another), but swapping them didn't work either. In fact, one way made the Run light of my 303 come on, and the other way made the selected pattern light flash. I don't get that. I traced the signal from the 303 back thru the cable and believe that the correct configuration of the socket (face side) is: clock S/S NC. NC Gnd I started looking into DIN Sync standards and read that the clock should be a square wave and should have a delay of 9ms for the first step. Could this be the issue? I also read in the other threads mentioned above that some people got the Sync to work from the old core using clock lengths of 3-6ms (this must depend on the chosen tempo, not optimal). What are my options here? I'd prefer to use the Clock SR from my DOUT as the Sync sockets are already built into that box, but if I'm forced to connect directly to the STM32, I will. Thanks for any advice/shared experience. Surely someone must have DIN Sync working from the STM32!
  11. https://imgur.com/a/dwaIr made this quick GIF to show the breakout box and LED drivers in action.
  12. Thanks, yes I know in this case the offset is only for the bipolar null adjustment, I meant that other devices have an offset and scale (VCO, VCF, etc) It might have been a good idea to make the AOUT_NG accept a through-hole socket so the SMD DAC could be soldered to an adapter board and easily swapped out to find a good one. Although, this isn't like swapping out a transistor. $$$ Can you share with me the values for your channels (what you've decided is usable and unusable)? I haven't tried an "ear test" yet, still waiting for my new output boards to arrive. Maybe I won't even notice the non-linearity, it amounts to 1cent between 0-1V, half a cent from 1-2V, but not too bad above that. Perhaps I can just use from 2V and above and pitch my VCOs down, I'd still have a decent 6 Octave range.
  13. Can we agree on a procedure and update the WIKI page? I did a preliminary calibration of my board last night. I assume I did it correctly, but maybe there's something I've overlooked or misunderstood. Basically did this: 1. Connect DMM to output header pins. 2. Select 1V, adjust scale trimmer so DMM reads 1V, repeat up to 8V. (Of course, now my 1V is off my an average of +10mV and 2V is off by +4mV) 3. Switch to bipolar modes. 4. Select "middle", adjust bipolar trimmer so that DMM reads 0V Is this correct? Usually when adjusting something for v/oct, there is a scale and an offset trimmer, right? That way the scale is correct across the full range. Perhaps I need to first monitor the outputs at "min", then add that value to each test level? Or do I just have to trim back the 8V result to 7.997V or so to get 1V result back closer to 1.000V? thanks!
  14. I understand. How exactly do the LEDs correspond to a track position? I can't tell what I'm seeing in your breadboard video. I appreciate your help,
  15. From the videos I've seen online, I can't quite figure out what the LED matrix is actually displaying. Can you explain? thank you!
  16. Is there a specific post/thread with people willing and able to provide programmed PICs (specifically 16F88 for Quad_IIc)? I purchased mine from MIDIbox Shop some time ago and would like to be able to point future builders to a reliable source.
  17. As there is no shroud on the LCD's header, the orientation of the notch on that end really doesn't matter either. What matters is that the cable goes "straight/flat" to the LCD, no twist.
  18. I have good news and bad news.... The good news is that my SeqV4 works perfectly. The bad news is that I'm an idiot and embarrassed, especially since I've been using MIDI and analog gear for almost 30 years. The reason my Waldorf did not respond to messages from the MIDIbox is that I was connecting to the SeqV4's MIDI In1, not Out1! All the "issues" I had were user errors, and all have been sorted. Thanks again to all who commented to help!
  19. Thanks for your reply. I have not tried the midi monitor page yet. And but your suggested set up method sounds like what I followed, basically the same steps outlined in the beginner's guide. I added additional steps to the 4\16, but none more than a few clicks up or down, so I don't think they would have been out of range. I am at work now for the day, so I will not get a chance to reinitialize a track until later
  20. Still stuck here..... have to correct my statement above: when connected to MIOS Studio, my midi out LEDs are only lit when I press play. Firmware is updated but MIOS Studio still shows GMx as the only option for In/Out ports. Pressing play produces the message "fa" in the MIDI In window, and pressing stop produces "fc". Pressing the keyboard at the bottom of MIOS Studio and adjusting the CC sliders shows reports in the MIDI Out window, but nothing happens at the MIDIbox. I'm pretty sure I ran midibox.org_gm5driver_X64_1.0.10 when I set up my discovery board. I'm not sure why I thought that was necessary, and I see now that this driver is "currently not supported for the MBHP_CORE_STM32F4 module". Was this a mistake? Can I undo?
  21. Thanks Slo. I just installed the latest firmware the other day, but didn't notice any change. I suppose I would have needed to reload MIOS Studio to see the changes. I can say that my Output LEDs are always on (flickering slightly) even when the sequencer is stopped. Is it still possible to use the USB port for updates when the "USB power" jumper is pulled and external power is applied to the 5V jumper?
  22. Do I need to flash this 2x2 utility before my MIDI_IO boards will work? Or is this just for testing with MIOS Studio? I ask because I hooked up my SeqV4 today for the first time, set the port to Out1/Ch1, made a pattern, connected to my MWxt set to omni, and it received no midi messages. Port IIc1 didn't work either (I have a quad_IIc as well). Output activity LEDs are all glowing. Currently, my In and Out ports in MIOS Studio say GM5 Port x, not MIDIbox SEQ V4 Port x.
  23. TK, Thank you again! Yes, that installation page is what I referred to when setting up my discovery board, I'm not sure how I managed to add the file extension on to the configuration file. I replaced the .txt on my card with the latest V4.094 and now everything seems to work as it should. However, before I reassemble the enclosure, I need to confirm that my external power is suitable. Can I use that 5.27VDC supply? Or do I need to get it below 5V (like the 4.89V from my USB port)? Enjoy a couple of beers with my appreciation, but do let us know what you're having!
  24. I may have spoken too soon.... yes, my displays are working, but my CS is not. More on that in a moment. As for the contrast pot: I just tested the voltage at the V0 pin on J15A, and it sweeps from 0V to 4.89V. So I'm not sure what's wrong with that feature. But this reminds me to ask, am I ok to power the system using that 5.27V supply? When I tested earlier today and sent that celebratory image above, the only connections to the Core were those of the LCDs. Since arriving home from work, and after testing the contrast voltage, I plugged in the other modules to try and test/verify that they work. (I'm not sure how to do this using MIOS Studio or where to find a list of suitable commands for the modules I'm using.) My MIDI_IO boards all lit up momentarily upon powering, but after that first time, each time I turned it on I would notice that some LEDs did not flash. The Quad_IIc also flashed, but it occurred at a slight delay if compared to the MIDI_IO. I'll assume these are probably OK until I can verify. However the CS seems to be confused. When I connect to the Core and power up, the LEDs at "track group 4", "trigger layer 3", "parameter layer 3", "fast", and "all" are all illuminated, and no others. Pressing buttons does not seem to do what it should, multiple buttons perform the same function, and some buttons do nothing. For example, multiple buttons caused this display: multiple others caused this display (edit recording was flashing over other text): Pressing C/3/Manual caused this display: Pressing Pattern: Pressing Fast: and there were more.... Is this another case of a reversed ribbon?? I thought I had been so careful throughout this build! Below is the entirety of the .txt file on my SD card which should be the recommended Wilba-compatible configuration with no modifications....yet. MBSEQ_HW.V4.txt
×
×
  • Create New...