Jump to content

monokinetic

Programmer
  • Posts

    325
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by monokinetic

  1. TK, you beat me to it! I installed Lemur for exactly that reason 2 days ago and now you have it running already, that's just amazing :)

    I'm away from my studio for Christmas etc but the first week in January I will be rocking this out. I will also test it with my USB MIDI as well and let you know how that works.

    Cheers, this is a perfect end to 2011

    David

  2. Hello all,

    I think I may have found a problem with transmitting SysEx using MBSeqV4. I'm running version 4.054.

    I have the MBSeq set up to use the router function to send MIDI from USB1 > OUT1 and IN1 > USB1, because I wanted to send SysEx from my Mac to my MB FM while using the MBSeq but I just couldn't get the SysEx to work. So decided to monitor the SysEx coming out of the MBSeq and compare it to what my other MIDI interface - a MIDISPORT2x2 - sends.

    Here's the results:

    with MIDISPORT OUT A connected back to MIDISPORT IN A =

    
    [MIDI OUT][13:10:17:000042]: [MIDISPORT 2x2 Port A][f0 00 00 7e 49 00 06 08 00 1c 01 f7]
    
    [MIDI IN ][13:10:17:000052]: [MIDISPORT 2x2 Port A][f0 00 00 7e 49 00 06 08 00 1c 01 f7]
    
    
    with MBSeq OUT 1 connected to MIDISPORT IN A =
    
    [MIDI OUT][13:08:49:000819]: [MIDIbox SEQ V4 Port 1][f0 00 00 7e 49 00 06 08 00 1c 02 f7]
    
    [MIDI IN ][13:08:49:000833]: [MIDISPORT 2x2 Port A][f0 00 00 7e 49 00 7e 49 00 06 08 00 06 08 00 1c 02 f7]
    
    [MIDI IN ][13:08:49:000834]: [MIDISPORT 2x2 Port A][f0 1c 02 f7]

    I've tried this test with 2 different pieces of software now (Cubase 6 and Ctrlr v5), exactly the same behaviour.

    My guess is that something is wrong here. Any ideas?

    David

  3. Hi Frankie ('tini actually),

    I haven't used JSynthLib on Mac OS Lion, but on my SnowLeopard (10.6.8) install I had to install the MMJ library to get sysex working correctly.

    TK has the MMJ link in his post at the top of the thread. Not sure if you have installed that yet?

    David

  4. Hi Cutter,

    Maybe you have tried this info from the SammichFM guide already, but just in case you missed it:

    Have you got a multimeter? If yes, have you tried measuring for continuity between each SMD chip pin and the next part of the track on the PCB that is connected to it? i.e. to make sure that the solder joint is connecting the SMD chip's pin to the rest of the circuit.

    Have you checked for continuity between all the adjacent pins on each of the SMD chips? i.e. to make sure there are no shorts between the pins next to each other.

    For more info see Step 1.12 and 1.13 from the SammichFM building guide! :)

    David

  5. Hi, I've been experimenting with MBSeq4.54 and phrase mode. I've been having a lot of fun with it, but can see some areas that might be enhanced and one slightly strange behaviour.

    1: I really like the ability to set mutes on position 1, then the selected patterns on position 2. But it seems a shame that then position 3 and onwards cant be used in phrase mode. It would be nice to be able to have phrases be the 8 Positions long. I think this could make performing songs live more interesting because then phrases become more than 1 pattern long. Even more fun would be to have the actions like mutes, jump, mixer and so on, available as actions as well. This would enable things like:

    A1:Mutes, A2:Repeat 1st patterns x3, A3:Mutes, A4: Play fill x1, A5:Repeat 2nd patterns x8, A6: Jump > A1

    :)

    2: It seems that each time I load up the seq, the first time I hit the song button the right LCD shows something different than what I have stored on GP1. When I press GP1, or switch to any other GP then back to GP1, the correct patterns are shown on the right LCD.

    Is that the expected behaviour?

    3: Could phrase mode have external MIDI CC control of which of the phrases is currently playing? I'd like to use another MIDI controller to set the current phrase while on the MBSeq Mutes page. Again would make playing live with the phrase mode more flexible IMO!

    David

  6. gomiboy99,

    Due to the coolness of Wikis, you can see the history of the page edits here:

    http://www.midibox.org/dokuwiki/doku.php?do=revisions&first=20&id=wilba_mb_seq_pcb_bulk_order

    I'd suggest that you should be allowed to insert your name back in to the list according to this (the date is clearly shown and the order of user edits). But I think the admins / page owner should make any final decision on that!

    David

    (edited for clarity)

  7. The height of the (soldered) transistors is 6mm (almost the same as for the LEDs), whereas the height of the buttons is 9.5mm

    This means, that the 2mm acryl panel will sit on the top of transistors, LEDs will be under the (transparent) panel.

    Christian will continue to work on this once he's back from vacation.

    Best Regards, Thorsten.

    OK thanks for the clarification TK, sounds like you've thought of everything :)

    I'll go and sign up then!

    Cheers

    David

  8. Well at least the buttons will have to be exposed to be any useful, don't you think? :whistle:

    Aha OK maybe I wasn't clear enough, I want to know if there will be a drilled front panel covering the PCB as part of the box or not (similar to Wilba's front panel for the MBSeq full version). The reason I'm asking is that you can see on the photo that there are the 8 BC337 transistors in the right hand top corner of the PCB. These look almost as high as the buttons and I'm not sure how this will be handled.

    Hope that's clearer...

    David

  9. Yes, it's exactly the same MagJack!

    Since some people have ordered the PCB without an ethernet socket, I will have some spares.

    OK great, it's a new connection for me so just wanted to be sure!

    Update: almost all people already confirmed the order, money requests will be sent today - thanks for the easy handling of this bulk order! :)

    Just sent my order, thanks to you for offering this exciting new platform :)

    To ensure that the MagJack won't be damaged during transport, I'm planning to solder it on the PCBs.

    This will take the same time like packaging it properly.

    Wow, cool. One less thing to solder ;)

    Cheers Thorsten!

  10. yes, thats intended - I prefer immediate response on value changes.

    Best Regards, Thorsten.

    Hi TK, thanks for clarifying. Would it be possible to request a switch to control this behaviour?

    It also raises another question from me: what is the purpose of the generate button in this case?

    Cheers

    David

  11. Hi, I have been using the random generator over the weekend and found something a bit strange:

    I thought on MBSeq3 that when you used the encoder to change the LayA / B / C parameter that you still had to press Generate to modify the layer. It seems on MBSeq4 that as soon as I move the encoder under LayA that my layer gets randomised. Is that normal?

    David

  12. I have been thinking about this and thought it would be better to keep the info in this thread rather than starting a new one. Anyway, I would like to ask:

    Would there be "better" sync between MBSeq and a DAW if MIDI timecode (MTC) was used? (I don't have any sync issues so far, but it would interest me if MTC would be tighter than Midiclock)

    If there would be an advantage to making MBSeq a MTC master, would it be possible to implement at some point?

    Cheers

    David

  13. Hi,

    It's great this is going to happen finally. But I would like to make sure I understand:

    Everybody on the list get a PM from me with a Sheet that must be filled!

    Have you sent the PMs already? So far I have nothing, but sent you a PM today to make sure I'm registered!

    Are you shipping from inside Europe? (there are new tax laws in my country and packages from outside EU take up to 3 months in customs!!)

    Thanks in advance

    David

    [edited] because I forgot the quote

  14. Hi,

    It's great this is going to happen finally. But I would like to make sure I understand:

    We need to register by 12th June. So do we just send you a PM to say "I want to register"?

    Are you shipping from inside Europe? (there are new tax laws in my country and packages from outside EU take 3 months in customs!!)

    Thanks in advance

    David

  15. aha OK thanks for confirming it! Interesting idea with the G/T buttons. I already have Track-Select on a bookmark :)

    @TK: I know there is not many of us with the V3 panel, but it might solve this problem if the GP > Assign/Trigger page allowed you to select the trigger layer currently being edited. I have a feeling this worked at some point, because on that page you can "choose" a trigger by pressing the A to H buttons i.e. it starts flashing.

    David

  16. Hi nuke, Thanks for the reply.

    But I think I can see that my original question was not clear enough. I should also mention that I use a MBSeqV3 front panel and not the MBSeq V4 panel i.e. no trigger layer buttons....

    Anyway, I have done more testing and here is the process I'm following:

    Track 1 set to a normal note track (i.e. with 256 notes, 4 ParL and 8 TrgL), I can use the trgsel page (page 4) in a bookmark to select the trigger layer to be edited. No problem.

    Track 2 set to a drum track, which as I mentioned in my first post, should have 2 trigger layers. But when I use the trgsel page to select a trigger layer I get only the 16 drum sounds (BD SD CH and so on). If I remember correctly, in MBSeqV3 I could use "Menu > Assign (Trigger on V4 panel)" and press the GP button below a trigger layer to switch to a trigger layer (I thought that's why it flashes?). But currently with Beta41, it seems it is not possible to edit the Trigger B layer in this way, as far as I can see.

    So is there another way to select the trigger b layer on a drum track?

    David

  17. Hi I'm playing around with programming some rhythms today and would like to check something:

    My track is set to "Drum (64/2*64)" which AFAIK has 2 trigger layers. I go to the trigger select page, set R.G. to layer B. Then I press the GP button below to select this trigger layer (i.e. it starts flashing), I thought then it is possible to edit the trigger layer. But it seems that when I press Edit to make the changes I'm still on the TA:Gate layer! Is there some other way of selecting to edit all of the steps trigger B layer that I'm missing?

    in

    On non-drum tracks I can edit the trigger using the trigger view mode, but this seems to do nothing on drum tracks, even if in theory they have 2 triggers. Any ideas?

    Thanks in advance

    David

×
×
  • Create New...