[TK.]

In your configuration:

BPM_Mode 2
MIDI_IN_MClock_Ports 0x000f0c01
MIDI_OUT_MClock_Ports 0x7ffffef0

- MIDI Slave mode (2) is selected
- only USB1 MIDI In is enabled for receiving the MIDI Clock
- no USB MIDI Out is enabled for transmitting the MIDI Clock

Is this really the setup which leads to an extremely high BPM rate in Ableton Live?

Best Regards, Thorsten.

[janvanvolt]

hrm, actually no.
let me send you the correct one (sorry)

[vcfool]

Well, I finally finished the V4 SEQ... I am using Wilba's CS, and HW file. Can't help on that USB tests, my Panther-G4 doesn't seem to recognize the MIDI USBs... maybe it's time to update to Tiger. But I have some other questions and suggestions:

-When choosing Parameter/Trigger Layers with Button C: Holding the button for selecting is fine, but I think it would be nice to select the "Last Selected one" by just pressing and releasing the button. This way it would be easier to toggle between say Note/CC, or Note/Length or whatever you are working on at the moment. What do you think? Would this be possible?

-Why is it that when you disable the Vel. layer all notes turn ON? I mean when I remove the Vel. from all layer assignments I get all notes playing C-3, even on the steps where there were no Gates or Notes. Then turning Gate ON/OFF doesn't remove (or insert) notes anymore. I have to manually turn each GP encoder all the way down to remove them. Or turn all Gates ON and then use the ALL function. The ALL won't affect those notes that don't have the Gate ON... it's all kind of weird. Gates and Notes get completely independent when no Velocity assigned. Maybe there's a reason for this that I don't get.

-I can't access the Multi-trigger function in Length Layer by turning the encoders beyond Glide. Glide is the MAX, no matter how much I turn the encoders. Is there any Parameter I may have touched that could have disabled this?

-The DIN Sync doesn't sync correctly my 606 or my 303. Some clocks get lost or something. I think it may be something about the pulse-width of the clock pulses. Using the Clock output to trigger an envelope doesn't trigger it always the same, sometimes you get longer or shorter notes. Anybody got a TR synced correctly?

I have some more questions but I think that's enough for now... Thanks a lot!!!

[janvanvolt]

vcfool: I'll have a doepferr MSY-2 and a tr606. will try dinsync directly and compare it with MSY-2. I'll keep ya updated.

[TK.]

vcfool, on 17 November 2009 - 13:30, said:

Can't help on that USB tests, my Panther-G4 doesn't seem to recognize the MIDI USBs... maybe it's time to update to Tiger.

Yes, USB MIDI is "only" supported from Tiger (MacOSX 10.4) upwards

Quote

When choosing Parameter/Trigger Layers with Button C: Holding the button for selecting is fine, but I think it would be nice to select the "Last Selected one" by just pressing and releasing the button. This way it would be easier to toggle between say Note/CC, or Note/Length or whatever you are working on at the moment. What do you think? Would this be possible?

Problem: Layer C button is also used to quickly check the layer activities (therefore the lower line displays VU meters)
I already see many dummy bug reports like "Layer selection goes wild when pressing C button" made by people who are not aware about this mechanism.

So, I built an alternative solution into Beta13: By pressing&holding Layer C button you can increment/decrement the layer with A/B button. This isn't a complete replacement for your request, but I find it very useful for myself.

Quote

-Why is it that when you disable the Vel. layer all notes turn ON? I mean when I remove the Vel. from all layer assignments I get all notes playing C-3, even on the steps where there were no Gates or Notes. Then turning Gate ON/OFF doesn't remove (or insert) notes anymore. I have to manually turn each GP encoder all the way down to remove them. Or turn all Gates ON and then use the ALL function.

fixed in Beta13

Quote

I can't access the Multi-trigger function in Length Layer by turning the encoders beyond Glide. Glide is the MAX, no matter how much I turn the encoders. Is there any Parameter I may have touched that could have disabled this?

Multi Triggers have been replaced by the Roll function which can be assigned to an individual layer.
Advantage: now multi triggers also change their velocity.
Another advantage: higher granularity for Length parameter (1..96 ticks)

Quote

the DIN Sync doesn't sync correctly my 606 or my 303. Some clocks get lost or something. I think it may be something about the pulse-width of the clock pulses. Using the Clock output to trigger an envelope doesn't trigger it always the same, sometimes you get longer or shorter notes. Anybody got a TR synced correctly?

Beta13 allows you to define the pulse width in your MBSEQ_HW.V4 file

Best Regards, Thorsten.

[TK.]

Beta 13 is available; ChangeLog:

  o pulsewidth of DIN Sync clock pulsewidth now definable in MBSEQ_HW.V4 file
    (DIN_SYNC_CLK_PULSEWIDTH parameter)

  o Parameter/Trigger Layer selection can now be quickly incremented/decremented
    by pressing&holding Layer C button, and incrementing with Layer A button,
    resp. decrementing with Layer B button.

  o various minor bugfixes

Best Regards, Thorsten.

[vcfool]

Just quick tried the DIN Sync.
TR-606 syncs just fine changing the value to 5.

Thaaaaaaaanks!!!!

[vcfool]

TK., on 18 November 2009 - 21:11, said:

Yes, USB MIDI is "only" supported from Tiger (MacOSX 10.4) upwards

So I updated to Tiger 10.4.11 yesterday and still no luck. My iBook G4 still doesn't see the USB MIDI. Is there any additional install or something that I must do?

MB-SEQ V4 shows on the USB tab on System Profiler and mounting the SD Card goes fine too. But no USB MIDI recognized by any application... everything is just as it was with Panther.

Thanks!

[TK.]

vcfool, on 21 November 2009 - 17:29, said:

So I updated to Tiger 10.4.11 yesterday and still no luck. My iBook G4 still doesn't see the USB MIDI. Is there any additional install or something that I must do?

MB-SEQ V4 shows on the USB tab on System Profiler and mounting the SD Card goes fine too. But no USB MIDI recognized by any application... everything is just as it was with Panther.

No, an additional installation isn't required.

Do you see the device in the Audio-MIDI Setup Application?
(see Attachment)

Best Regards, Thorsten.

Attached File(s)

•  Bildschirmfoto 2009-11-21 um 18.37.59.png (71.14K)
  Number of downloads: 29

[vcfool]

TK., on 21 November 2009 - 18:39, said:

No, an additional installation isn't required.

Do you see the device in the Audio-MIDI Setup Application?
(see Attachment)

Best Regards, Thorsten.

Nope. There's only my MOTU FastLane (and IAC driver, and Network), as usual. Already tried Rescan several times before.

[TK.]

Then I've no idea. Maybe google helps you to find more informations about using a Standard USB MIDI device on a PowerPC based Mac.

Best Regards, Thorsten.

P.S.: it could be important that your core module is powered from an external PSU, or from an USB hub with a "strong" PSU supply.

[vcfool]

TK., on 21 November 2009 - 23:00, said:

Then I've no idea. Maybe google helps you to find more informations about using a Standard USB MIDI device on a PowerPC based Mac.

Best Regards, Thorsten.

P.S.: it could be important that your core module is powered from an external PSU, or from a USB hub with a "strong" PSU supply.

Thanks a lot. I've googled a little and didn't found much, I will post here if I find a solution.
The Core is powered from it's own external PSU. The USB MIDI has been working on a Windows PC since day 1. I've uploaded the .hex files from there through USB. I never got MIOS Studio to work under Panther, so it's been good to update to Tiger, because now it works great... at least with "normal" MIDI through the FastLane.

Anyway I just wanted to know if there was some step I may have missed, I don't wanna turn this topic into "troubleshooting my USB", so...
...back to the suggestions:

TK., on 18 November 2009 - 21:11, said:

Multi Triggers have been replaced by the Roll function which can be assigned to an individual layer.
Advantage: now multi triggers also change their velocity.
Another advantage: higher granularity for Length parameter (1..96 ticks)

As the beyond-the-glide mode is still in the V4 Manual I thought it was still working.
I didn't knew that Length had some effect in Roll. I have been trying. In V3 you could define the ticks in between repeats quite nicely. For what I undestand, now you do it with the Length, but it only seems to work when 4 or 5 Repeats in Roll are selected. When 2 or 3 it always does the same. How can you do it in Drum Tracks when no Length Layer is there?

And... some more thoughts:

-In a Note Parameter Layer, and maybe also in a Chord Layer, activating "FAST" could switch the encoders to octave jumps. I'd find that really useful. What do you people think?

-In Drum Mode Trigger Layers. Maybe removing a Gate could also remove the ACCent. And inserting an ACCent could also insert a Gate.

-Wouldn't it be nice to apply Grooves to the DIN SYNC clock output? ;)

Thanks again!

[TK.]

Quote

As the beyond-the-glide mode is still in the V4 Manual I thought it was still working.

I have to overwork this section.

Quote

I didn't knew that Length had some effect in Roll.

No, it doesn't have an effect on Roll. The gatelengths are predefined:

                    // force gatelength depending on number of triggers
                    if( triggers < 4 ) {
                      //   number of triggers:    2   3   4   5
                      const u8 gatelength_tab[4] = { 48, 32, 36, 32 };
                      // strategy:
                      // 2 triggers: played within 1 step at 0 and 48
                      // 3 triggers: played within 1 step at 0, 32 and 64
                      // 4 triggers: played within 1.5 steps at 0, 36, 72 and 108
                      // 5 triggers: played within 1.5 steps at 0, 32, 64, 96 and 128

                      // in addition, scale length (0..95) over next clock counter to consider the selected clock divider
                      gatelength = (gatelength_tab[triggers-2] * t->step_length) / 96;
                    }

Quote

-In a Note Parameter Layer, and maybe also in a Chord Layer, activating "FAST" could switch the encoders to octave jumps. I'd find that really useful. What do you people think?

In order to implement such a feature properly, I would have to overwork the concept how encoder speed is handled, and finding a better concept will take some time.
So - only a quick idea or really an important feature?

Currently the FAST button exclusively controls the encoder speed (which is handled by MIOS32) - for this feature, I would have to make an exception when a "Note" or "Chord" layer is selected. It will become complicated and error prone once switching between layers, switching to a menu page, etc. have to be considered as well... therefore a different concept would be required which considers certain layer/parameter type specific constraints.

Quote

-In Drum Mode Trigger Layers. Maybe removing a Gate could also remove the ACCent. And inserting an ACCent could also insert a Gate.

Such a mechanism wouldn't allow you to handle accent and gate separately, which is important whenever you are working with "prepared grooves", which are starting with a small number of gate triggers, and are enriched by more triggers (or at the end: all steps triggered) while the sequence is playing.
I get use of this possibility very often to vary the patterns during a session.

Quote

-Wouldn't it be nice to apply Grooves to the DIN SYNC clock output? ;)

You could simply trigger your drummachine from a J5.A0..A7 gate, controlled from a dedicated track which plays 16 notes at the desired clock rate. The clock rate is defined by the clock divider value and normal/triplet mode.
Now activate a groove style for this track -> done.

Best Regards, Thorsten.

[TK.]

Btw.: is any Mac user interested on a BLM_SCALAR emulation?
I'm using it to test the protocol with matrix dimensions which I would never build myself ;)



The application communicates with your MBSEQ via MIDI. Planned features: track editing, drum pattern editing, piano roll editor, pattern selection, mixer control, VU meters, etc.. all implemented in the MBSEQ firmware, the BLM_SCALAR application only acts as a stupid display/data entry device.

Best Regards, Thorsten.

[Schrittmacher]

TK., on 22 November 2009 - 22:06, said:

Btw.: is any Mac user interested on a BLM_SCALAR emulation?
I'm using it to test the protocol with matrix dimensions which I would never build myself ;)



The application communicates with your MBSEQ via MIDI. Planned features: track editing, drum pattern editing, piano roll editor, pattern selection, mixer control, VU meters, etc.. all implemented in the MBSEQ firmware, the BLM_SCALAR application only acts as a stupid display/data entry device.

Best Regards, Thorsten.

I am Interested

[janvanvolt]

Schrittmacher, on 23 November 2009 - 14:17, said:

I am Interested

Me as well.

[Gridracer]

I toyed a little around with the SCRUB function as it works now for-and backwards in V4,
which is real fun using the datawheel as some sort of scratchpad.
(absolutely no sequencer hickups or anything, WOW!)

Then I thougth I could stop or pause the sequencer and use the SCRUB function to scroll through the pattern. But I had to realize that using the SCRUB function always causes the SEQ to start. Is there a special reason for this behavior?

If there is no conflict with an other usage concept and only if it would be really easy to change, I would suggest to prevent the scroll function from starting the sequencer. But to be honest, why would I ever want to stop the SEQ? as it it is one of the main features that you don't ever have to...

Best regards

Gridracer

[TK.]

Gridracer, on 23 November 2009 - 21:47, said:

I toyed a little around with the SCRUB function as it works now for-and backwards in V4,
which is real fun using the datawheel as some sort of scratchpad.
(absolutely no sequencer hickups or anything, WOW!)

It's the big advantage of the MIDI event scheduler, that even such features are possible now

Quote

Then I thougth I could stop or pause the sequencer and use the SCRUB function to scroll through the pattern. But I had to realize that using the SCRUB function always causes the SEQ to start. Is there a special reason for this behavior?

Not really, it should work in pause mode. I will check this sooner or later.

Best Regards, Thorsten.

[TK.]

Beta14 is available:

  o prepared support for MBHP_BLM_SCALAR.
    The MIDI port can be configured in Options menu (Utility->Opt.)

  o various minor bugfixes

Link to BLM_SCALAR emulation (Mac OS Leopard/Snow Leopard only)
http://www.ucapps.de...r_emulation.zip


Setup:
MIDIbox SEQ: select the MIDI port to which the BLM is linked in the Utility->Opt. page with GP Encoder #16
Emulation: select the same MIDI In/Out port

The matrix should be updated automatically.
Try different dimensions - 64x16 is a really useful configuration.

Currently we have display buttons for Triggers (e.g. Drum patterns), Tracks and Patterns.
One function that I'm planning to add next is the possibility to display Accents in the trigger page with the Red LEDs, and to activate accent by pressing "Triggers"+BLM button.

Gridracer: it would be interesting if your BLM configuration is still working, since I had to change a lot of code which is also used for common 16x4 BLMs directly connected to the core.

Best Regards, Thorsten.

[Gridracer]

Quote

Gridracer: it would be interesting if your BLM configuration is still working, since I had to change a lot of code which is also used for common 16x4 BLMs directly connected to the core.

Everything seems to work as supposed to, as far as I can tell from a few minutes of testing.
I tried differernt TRACK lengths / play directions / LOOP mode and STEP VIEW -> everything OK

Intensive testing latest on the weekend....

Best regards
Gridracer