monokinetic
-
Posts
325 -
Joined
-
Last visited
-
Days Won
5
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by monokinetic
-
-
you will notice that this is about a CONTROL SURFACE PCB :P
aha, after the 14th page my focus on the topic title must have waned ;-)
if you don't want to wait for mios32/seqv4, you can use this for an all-on-one seq pcb:
Cheers, but I have had a Seq running for the last year or so on MIOS, I'm looking forward to having MIOS 32 for my second Seq!
Dave
-
Hiya,
This weekend I had another long MB Seq session, TK the Seq is one of my favourite devices - thanks a million :)
After the marathon session (which, when I had a mild headache in the morning, reminded me I need to dim a few of my LEDs with resistors!) I have a few suggestions and would be interested in how other Seq users feel about them:
I think the Mutes page would be more useful if it were possible to create groups of mutes, so that multiple tracks could be switched on/off with one button. My idea was to have a function where if one of the group buttons is held down and then the GP buttons are used to unmute/mute a track, this track is added to a mute group, which can then be toggled using the group button. I think this would be especially relevant when MB Seq 4 arrives and we have untold tracks to control. Anyone else think this might be useful?
Quite often this weekend, when I switched to the Song page to use pattern mode to quickly switch to the next part of the Song, I forgot to press Layer B. This means that the GP buttons skip to the next song and the Seq stops playing. IMO it would be nicer if the default screen element selected was the setting chosen by layer button B. Just a small detail but would make me more comfortable in a live situation....
But anyway, they are just suggestions after some major usage. Of course I would love to say that I'll look at the code but I'm busy learning Smalltalk to coax more strangeness from the Capybara ;-) maybe when MB Seq 4 is in C. .....maybe....
Best
Dave mK
-
Hi,
I just worked my way through the whole thread (slow day at work, hurrah!) and I would like to ask:
if you haven't already done the run of PCBs, would it be worth changing this over to MIOS 32 Core? Or at least offering some headers for the DIN/DOUT/BankStick/IIC lines so that we can easily upgrade?
TIA
Dave mK
-
Hi TK,
I had a bit of a play with this new version, uploaded the latest 3.4 Seq and tested another box as a matter of interest.
All working fine here, good job - as always :-D
Thanks as ever!
Dave mK
-
TK: Thanks! Wow those are amazing figures! I'm even more impressed by GM5 now ;-)
Can't wait to get this project up and running.....
David
-
Whahoo, Christmas is here already! Many thanks to TK and Ploytec.
has much less latency when events are sent over multiple ports
As a matter of interest, has anyone done some measurements of the latency of the new driver?
I ask because I learnt a lot about MIDI latency through a great XP tool which is here:
http://miditest.earthvegaconnection.com/#about
This helped me realise which of my MIDI ports has almost 10ms latency. I would be really interested if someone could post their results (if not as soon as mine is made I will post my findings!)
Back to the soldering :-)
David
-
Well without wanting to seem like I enjoy talking to myself.......
I thought I should post the conclusion of this thread. Which is that I found the problem, I had not connected the extra cable between IIC Midi R1 and the Core J6 SI.
So if anyone searching the forum later on comes across the initial problem of this thread, make sure you double check http://www.ucapps.de/midibox_seq/mbseq_v3_interconnections.pdf to ensure your IIC Midi in works ;D
I'm off for some experimentation with synchronising all 3 of my sequencers, hurrah!
Dave mK
-
Hiya Smash,
Thanks for taking the time to reply and to try if the hex file is weird etc. I forgot to mention in my original post that I am using the MB Pic Burner hardware. I have burnt the MIOS bootloader and the IIC midi.hex previously into quite a few PICs with my hardware and the pbrenner software. It seems strange to me that just this latest version of the IIC.hex is not working. Anyway, I checked out the software you mentioned but in the list of hardware I'm not sure which programmer to choose if I'm using the MB PIC burner. Anyone know?
Also, is there anyone else out there with a similar setup who could confirm burning this IIC MIDI .hex file is not just a problem for me?
Dave mK
-
Well today I tried to recompile the IIC .Hex file and low and behold it loads into the P44NG software fine!
I knew it was a good idea to set up the MIOS development platform :-)
IMO there's a problem with the .Hex in the download from ucapps because the original downloaded file is 4k and my recompiled version is 3.9K.
Anyway I hope this helps anyone else who runs into the same problem.
@TK and the other gurus: is it worth double checking this and if I am right about the current file being weird uploading a working version of the IIC .Hex file to ucapps?
Dave
-
Hi,
I am trying to reflash the PIC 16F88 for my IIC module and I have come across a slightly strange problem using any of the software from www.sprut.de. When I try to load the project.hex found in the mbhp_iic_midi_v1_0c.zip file from ucapps.de I get the error as seen in the attached screen shot. A quick internet translation makes me think that there could be something wrong with the IIC hex file.
I can open up various other .hex files (from ucapps and others as well) with no problems. I have tested three computers now and always the same error. I also tried a few of the applications from the www.sprut.de site (pbrenner37u, pbng44 and even the P18) and none of them like this .hex file. Maybe I am missing something because my German is very bad!
Could someone else please try the IIC project.hex firmware file and see if they can just open it?
Thanks in advance
David Moss
-
Hi Mike,
Thanks for the input, interesting point, it's not something I really thought about! I will have a play with some of the options tonight when I get home from work. You also prompted me to re-read the manual at ucapps and I realised I shouldn't be sending MIDI clock in to the IIC either!
However, the behaviour is the same if I send MIDI clock or notes from both my keyboard or my PC sequencer. The IIC Rx LED flashes to indicate that it has received approx 28 events. Then the light stops. Sending MIDI in to the IIC does not control things on the MBSeq (i.e. an arpeggio track etc)
I'll see what this evenings fiddling leads to!
Best
Dave mK
D
-
I had a go at soldering another 1K resistor between SC and Vd, checked that I got 1500 Ohms across the SC and SC lines and tried a few goes but I still have exactly the same problem still :( I also double checked that the bankstick board and the IIC board both have infinite resistance between SD and SC when not connected to the core, individually and connected together on the IIC bus.
Any other suggestions? I'm contemplating trying to flash the PIC again, long shot I know but I'm out of ideas!
D
-
Hi nILS,
I am pretty sure stryd was referring to the IIC board without anything connected to it. In that case the resistance should be infinite (not "no resistance").
Aha, OK thanks for clarifying that. I do indeed have infinite resistance on my IIC MIDI board and the bankstick board when removed from the Core.
When connected to the Core ~2k is correct since both traces have a 1k pullup on the core.
Check! I have 2K between SD and SC on the Core.
Did you add the second 1k pullup on the core as described http://ucapps.de/mbhp_iic_midi.html (Second image under "Configuration and Interconnections")
Hmmmm, I had referenced this picture when working out how to install the extra MIDI In parts on my IIC board. I am using a MB Core V3 PCB from Mike and my understanding was that this picture is referring to the Core V2 (from the note underneath it). I have R2 and R12 on the Core, so as mentioned previously I have 1K resistance between SD and VD and 1K resistance between SC and VD.
If you have the resistor in place your total resistance should be ~1500 Ohms (1k in series with 2x 1k in parallel).
So if I understand you correctly, in fact I need one more 1K resistor between SC and VD even though I am using a MB Core V3 (you seem to be talking about 3 resistors in total). Is that what you mean? (sorry if it seems obvious, it's Monday!)
TIA for your assistance!
Dave mK
-
Hiya,
I removed all of the IIC stuff from the bus, still the same 2K resistance between SD and SC. I then traced my Core V3 carefully and I cant see any bridges even with a magnifying glass :(
@Stryd are you 100 percent sure there should be no resistance? I ask because on the Core schematic SD and SC both go through 1K resistors to the 5V line. So my original logic was that in fact there would be 2K resistance between the SD and SC. Or am I missing something?
D
-
Hi all,
to get an extra Midi in on my MB Sequencer I installed the remaining parts for my IIC module. FYI the 4 banksticks and the IIC Midi out work absolutely fine. I seemed to have most things working, except that after receiving 10 or 12 events the TX light on the IIC board stops flashing :(
To do some testing I loaded up the loopback IIC test application and noticed in the readme:
Note:
the yellow LED will only flicker until the MIDI buffer of the MBHP_IIC_MIDI slave is full. This scenario can happen if the core cannot poll for the incoming data. This means in other words: this effect can be noticed, if the SC/SD lines are not connected correctly.
I have traced the SD and SC lines from the core through the IIC module and to my 4X bankstick module and most things seems to be ok. The only things that seems a bit strange is that if I measure the resistance between SD and SC I get 2K. Is that right?
TIA for any help!
Dave mK
-
Hi,
I noticed in the thread that the remaining GM5 chips will be sold tonight. I would like to ask:
are there many spares?
If yes, what do I need to do to have a chance of buying one of these?
Thanks in advance
Dave mK
-
@ stryd:
Bingo that fixed it perfectly, I had forgotten to put the .hex extension after the name of the .asm file in Makefile.orig!
I just compiled it with no problems at all. I do like make :)
Thanks for the help
D
-
Hi,
I have been playing with this for the last two days and WOW, amazing work. The documentation is first class and the implementation is super, well done all ;D
But, (there's always a but) I have a small question. Is it possible to adjust the make process to include a customised setupXXXX.asm? I ask because I have a different setup for my MBSEQ hardware to the supplied files. What I was hoping to do was just to have my own setupXXXXmyHW.asm file and then make.
Just putting the file in the folder obviously didn't work so I tried adding my file to the Makefile.orig and it gave the following error:
make: *** No rule to make target `setup_mbseq_v3_3b_dejfHW', needed by `all'. Stop.
Is there any other way to do this? Or should I just replace the original setup_mbseq_v3.asm with my customised file using the same name and leave well alone? ::)
Thanks in advance
Dave mK
-
Hi,
I have been following your posts here and over at electro music and I just realised that maybe I can help you with this request:
I REALLY wish there were PCBs available like this for the remaining 9090 voices as well... someday I'll be adept at protoboarding from schematics I hope.
I was wondering the same a while ago and somebody pointed me to the introspectiv group at yahoo. If you join up and check the files area the PCB layouts and schematics etc for the whole 9090 are there. From memory it's a double layered board, so in the end I made a few of this guys 909 kick:
http://www.bionicdimension.de/_drummachine-909-bassdrum.html
Which will soon be finished :-)
Dave
ps personally I'm not building any more modular drum stuff till the MPS is ready ;-)
-
2) How is the built in mixer feature of the seq v3? would building in an extra control surface be redundant? Can I assign the seq's mixer freely to any midi command?
I'm not sure how you envision the mixmap page. The name is a little confusing IMO.
It's not something I've used a lot in my SEQ, but the way I understand it is as a static CC mixer. What I mean by this is that patterns can have CCs set in the mixmap that are sent out when the pattern is changed. This allows you to reset CC's before a SEQ tracks modifies the values. Also this can be used to automate volume changes etc (if anyone wants to correct me feel free!!)
However, what I was originally hoping for in the mixmap page is a mode where I can use the encoders to send out the assigned CC's as I twiddle live. If this could be used in addition to a loopback channel then the 16 encoders could be used for tweaking tracks (for example assign the encoder to a CC that controls a tracks overall note length). As far as I can tell its doesn't work like this, yet :)
I hope that clarifies it...
Dave mK
-
Hi,
I have had some strange redraw issues as well, I'm not by my sequencer at the moment but from memory it mainly happened when in the Utility page using functions like Copy/Move steps. I think I would hold down the move button, then use an encoder to move the step. When I let go of the move button the utility page would be redrawn as though everything had moved 50 percent to the left and scrambled! Once I left the utility page all was fine again. All other functions on the box are fine....
Oh and while we are talking about strange issues (without wanting to hijack)
I have had some weirdness when I have selected more than one track and then changed the length (of the pattern i.e. number of steps). Again this is all from memory but I think what happened is that the pattern only played the 1st 16steps, even though the display said the pattern had 32 steps. I'm not sure if that makes sense, I can try to replicate the problem over the weekend if it helps...
But, just in case you think I'm being critical, I still have to say that the SEQ is my absolute favourite tool in the studio these days (well that and the Capybara!!), TK you are the man :-)
D
ps I think I currently have mios 1.9e rather than 1.9f installed, not sure if that matters...
-
Hi Mike,
indeed, I must agree. The MBSeq is the most remarkable Sequencer I have ever used!
re: the heatsink, I found that running the 2 LCDs and the LEDs meant my regulator got so hot that it cut out after 10 minutes or so. After some forum suggestions, I mounted the reg. on a pretty thin heatsink and can sequence almost all night now :)
HTH
Dave mK
-
Hi all,
I would like to ask if someone could open their MBFM to take some test measurements for me? You can find background information here:
http://www.midibox.org/forum/index.php?topic=10139.0
Basically my board is behaving really strangely and it would help a lot to know what voltage I should expect to measure on the following pins:
IC3 OP3 and OP4
IC5 OP3 and OP4
These pins are on the right hand side of the TL074, at the top and bottom.
Anyone?
TIA
Dave mK
-
I stumbled accross some web images of someone who has built a OPL3 successfully:
It looks like his board has quite a lot of tantulum caps (I'm guessing they are tantalums).
I have used all ceramic caps for the non-polarised caps.
I just double checked the reichelt orderlist and realised that in fact the 9 x 100nF caps are VIELSCHICHTKONDENSATOR.
My German is not very good I'm afraid. Can anyone tell me exactly what this type of cap is please?
In the meantime I will buy some tantulum's and experiment to see if it makes a difference.
D
Some ideas for Seq enhancements
in MIDIbox SEQ
Posted
Glad you like the suggestion, I was originally going to post this in the thread you mentioned but I decided I shouldn't hijack. Thanks for the pointer though :)
Ooops I meant the Track buttons, sorry. I won't have group buttons till I finish my second Seq....
I think a dirty solution for the time being while we wait for MB Seq 4 going public would be great. As long as it doesn't take lots of development time away from Seq 4 ;)
Best
Dave