mongrol

Aah. I didn't realise the current core's weren't fully utilised. I just kept reading here and there that there was memory limitations but thought that applied to the STM32F4. In that case I have a feature request. In Song mode I would like to chain individual tracks and have the option of doing away with pattern groups. I did read that pattern groups were the smallest chainable unit because of memory limitations. Even the option of reducing the number of tracks to 8 would be good if they were individual chainable units.

What is mbseq v4+? Is it an upgraded core? Is there a specificv4+ wishlist or just the normal wishlist in the repo?

Awesome work there Psykhaze. Well done.

and 5 seconds later my post in another thread is irrelevant.... :)

First I'd like to hear from the other PCB designers on the forum. What does Latigid On, Hawkeye etc use? On a related note, I find it difficult to find PCB designs for the various projects. It would be nice if some index page of available designs existed that cross referenced to the projects. On another related note, wouldn't it be grand to find a design for the Wilba CS so we could mod it.

As usual I find it 5 minutes after posting (in the BLM scalar firmware readme). It looks doable. I suppose the hard part isn't the communication but the building and scanning of a 16x16 RGB matrix. Let the chinrub commence.

Hi folks, Since the BLM talks to the SEQ over MIDI. Would it be possible to build a bespoke BLM just using access to the Midi-map and MIOS codebase? I can't seem to locate the BLM midi protocol anywhere but I presume it must exist somewhere. Are there any other "gotchas" or SEQ unique things that restrict BLM's to the current designs (Latgids, Lemur, Launchpad etc?)

I'm now a few weeks into learning my SEQ and I'm much more comfortable with the UI now the muscle memory is kicking in. However, there are still some niggles niggling away about usability aspects. I feel like remapping some buttons but before I do. What remapping have you done from default if any and why?

I'd check if the 4x16 BLM is still supported or at least usable with the current/next firmware from TK.

All good. Thanks TK.

I have a bug (maybe) and also a request. On drum tracks can we have (2*64/2*128), so 64 steps long, 2 parameter layers + 2 trigger layers with 8 instruments? Also, when I change a drum track (128/2*128) parameter LayerA to CC, GPK10 doesn't let me select the CC number. It just shows "---" I'm being selfish here as I have an LXR, with 7 instruments and I'd like to throw 2 layers of CC at it.

Thanks TK. Perhaps a "Reset pattern" Action would do it. I've got around the LFO by doing it manually and found the ALL button trick to do a ramp between 0 and 90 (nice).

Hi folks, I"m working in Song mode and trying to do a volume ramp to fade in some pads. I'm using a CC Parameter layer to do this and a one shot LFO set to ramp up the volume CC over about 2/3's of the pattern length. In phrase mode this works fine but in Song mode it doesn't do it. My pad comes in at around Position A4 after the intro but comes in with Volume set high as if the LFO has already ran it's course. If I play this pattern at Position A2 (after the mutes) it ramps fine. This seems to indicate that the LFO is triggering right at the start of the song. Now I've said all that I'm sure I don't fully understand the loop lengths. My G1T1 is 16 steps, my G1T2 is 128 steps. I notice that in song mode if I Actx4 then G1T2 comes in half way through, so I loop 8x to fit it in. When it comes to the pad (G3T1) also 128 steps the ramp just doesn't happen unless its the start of the song. Am I confused or is this a limitation?

Would these be usable with the Minicore or perhaps a Duino/Teensy board? I get dismayed everytime someone mentions "core". It's just so bloody big. In this case it'll be as big as a 4x4 pcb,

Oooh, lovely happy joy joy. Make it so young Latigid on, your audience awaits!

Nice. I presume this means no tons of soldering with LED's everywhere. Would it be possible to modularise it like the trellis, in that you can opt for 16, 32, 64 configurations by adjoining boards?

Necrobump. I've just found this awesome thread. What's the latest on the MBProg? This looks just perfect for my axoloti synth build. The axo can change synths on demand (using Program Changes) which makes it difficult to design a usable panel for it. Would be awesome to have a on demand, changing dynamic control surface for it that matches the underlying synth engine perfectly on changes.

18% sounds like it's the old Inkscape DPI issue. Basically Inkscape runs SVG at 90dpi while other editors, like Illustrator run at 72dpi. Not sure what Pawaga used to make that file and I also can't find the Ponoko forum posts I read about it. Try this; Get and open Ponoko's P3 inkscape template. Open Pawaga's file Copy and paste the contents over to the P3 template. The p3 template has settings in it that should correct the sizing issue.

I got my LXR around July last year.

Midi Thru from the Nova has fixed it. Good stuff.

Good idea @Rowan. I'll pass it through my Nova and see how it goes. @latigid on. Tried that one. I've tried so many different things I was even looking at the source code. The LXR has a number of bugs left in it. Shame Julian doesn't seem interested in updating it. Still, at least its open and Brendan Clarke is doing a fine job with his custom firmware.

Hi Folks, I'm trying to driving my LXR from my SEQv4 and I'm having weird clock problems. Here's my setup Drum track set to channel 10 BPM set to 100 or above. MClk OUT set to On on BPM page. LXR set to anything with "N" in it meaning it receives notes. Voices set to channel 10 and any note (makes it easier to troubleshoot) I want to export clock as I have other synths with arpeggiators etc. The LXR specifically doesn't need clock, I just want to play notes on it. The problem. With MClk OUT set to On the LXR will only play 1 note every 9 16th's. No matter what the voice. If I slow BPM down it'll play something like 1 note every 6 or 7 beats. Basically it's not playing all the notes. If I turn MClk OUT to Off to stop exporting clock timing, the LXR behaves and plays every note, no matter how fast the BPM. Other tests with MClk enabled; Without the SEQ clock running I can bang away on my keyboard and play the LXR as fast as I can. Soon as the SEQ runs with clock exported, the LXR will only play a note every so often (as above). With clock enabled the SEQ can drive any other synth no problems with the drum track. Anyone with an LXR seen this?

Geez, is Australia (using NZ ponoko) my SEQ case costs about 80USD

How much was the Bamboo from Ponoko? Seeing how hard it is to get no-indicated 11m plastic knobs, it's a shame similar in brass won't exit. :|