LinnStrument Firmware Public Beta : v2.0.0-beta4 (with step sequencer)

[gbevin]

@PHY6 We'll continue this further through email, thanks for contacting through there.

Cool, lemme know if you want me to try anything. As of now it's still dead.

I'll follow up through email.

[gbevin]

We've just uploaded v2.0.0-beta2, @bbrylow and @BobDog, this should fix the issues you reported.

The download links are at the beginning of this thread.

Thanks a lot for testing!

[MarkPowell1976]

Just upgraded to beta2 and all seems to be working well. Kudos to Geert and Roger for adding yet another feature that makes this the easiest to use and most versatile expressive controller out there in my opinion. I had a problem with beta1 stopping the sequencer seemingly randomly, but it's not done it since the upgrade. I've just upgraded my Reaktor license to R6 and using the step sequencer to drive Blocks is great.

From when I used to use the Monome step sequencers I found having a vertical bar that moved across the sequencer much easier to keep track of. Having a single light moving along the bottom is probably just a matter of getting used to it, but how difficult would it be to have the option of a vertical bar of purple lights that lit every pad in that column if it wasn't already lit due to having the step switched on?

[Roger_Linn]

I don't know how the Monome worked, but the problem is that if the entire play head colum is magenta, you wouldn't be able to see the note data in that column. I would find it difficult to not be able to see the step that playing. Please give this method a try and see how you feel after a while.

[MarkPowell1976]

Hi Roger,
Thanks for the quick reply. What I'm suggesting is only those cells that don't have a playing step (i.e. the currently unlit cells in that column) being lit in magenta. Not a big deal though - I'm sure I'll get used to it and it's excellent to have the balance of the step sequencer on one split and the expressive playing surface on another.

Thanks,
Mark.

[MarkPowell1976]

Here's a quick example of what I mean for the Monome - 5 second video, but as you can see it's less awkward than you'd expect.

[bbrylow]

@gbevin - new firmware worked just fine for me so far. Once I get the "cannot retrieve setting error" I am able to continue with new "skip using defaults" button. FYI I am using the original supplied USB cable plugged directly into a USB 2 port on a Pentium i7 laptop, Windows 10 and only USB plugged in to the machine. Let me know if you would like any addition info, but it is working just fine now. Thanks for the quick turnaround. You rock!

[SolarWind]

I just got the update installed on a Windows 7 64 bit PC, I first tried on my main recording rig which is a Windows XP 32 bit PC but the install failed, I kept getting this error "install failed (unsigned)".
I'm digging the new colors, the orange is great for Halloween, also the lime green and regular green go great together. I have a suggestion for the color options, how about being able to save color scheme presets, maybe have 4 save-able presets placed under the 4 button color options, that would be great to switch the look quickly between songs instead of flipping through each individual color everytime.
Thanks for the update!

[PHY6]

Can someone please make a video of the sequencer possibilities ?

[gbevin]

@gbevin - new firmware worked just fine for me so far. Once I get the "cannot retrieve setting error" I am able to continue with new "skip using defaults" button. FYI I am using the original supplied USB cable plugged directly into a USB 2 port on a Pentium i7 laptop, Windows 10 and only USB plugged in to the machine. Let me know if you would like any addition info, but it is working just fine now. Thanks for the quick turnaround. You rock!

Do you remember which firmware version you were running before? Could you try applying the 2.0.0-beta2 update again to see if this time it can retrieve the settings? It concerns me that you're seeing this message, you shouldn't if the firmware you're running is at least 1.1.0.

[BobDog]

Hi,

I have been playing with the sequencer for a bit, mostly beta 1 though I have got beta 2 installed now.

Fist of all nice job guys, I'm a bit of a sequencer fan so it's rather nice to have one on the linnstrument, especially a polyphonic MPE one!

I think you have the interface spot on as well, once I got my head around it I am finding it fast and simple to use.


I have found some problems:

1. The odd missed note on or note off, this is with Ableton Live I need to check with another DAW as well.

2. Loop ignores end of sequence. To replicate set a seq length to 8 and set loop on.


And some requests:

1. The sequencers can get out of sync if you mess about with seq length or speed. It would be nice if we could have the ability to sync the start. Either a manual global bar length (like the Cirklons GBAR) or maybe just a manual keypress to sync on the next step 1 of the currently displayed seq.

2. Start of seq as well as end of seq

3. Some form of record. Say a quantised real time record or some form of step record. I guess the step record would be a problem for poly stuff so maybe just a simple mono step record function.

4. Strum type thing for steps with multiple notes. Delay each note a bit

5. Arp type thing for steps. For a single note this could also be used for ratcheting

Cheers

Andy

[BobDog]

Just found another one:

Copy sequence doesn't set end correctly.

[Chick Sangria]

Thank you for adding these awesome features! Thank you for reacting to user feedback so quickly. And also thank you for returning to a serifed font. Will there be a replacement top panel for sale?
Feels great to use the sequencer. Just one problem so far: In the Page Select section, I can't choose "Rows 1-7 / Steps 1-16". While the other three pads turn violet, this one stays green and the drum view doesn't switch to this section of the sequence.

[gbevin]

First of all nice job guys, I'm a bit of a sequencer fan so it's rather nice to have one on the linnstrument, especially a polyphonic MPE one!

I think you have the interface spot on as well, once I got my head around it I am finding it fast and simple to use.

Thanks a lot for the testing and the kind words!

I have found some problems:

1. The odd missed note on or note off, this is with Ableton Live I need to check with another DAW as well.

That should indeed not happen, could you please check with a MIDI Monitor also if you have the opportunity. Just to make sure of what is going on. This would also make it possible to more easily reproduce.

2. Loop ignores end of sequence. To replicate set a seq length to 8 and set loop on.

This behavior is be design, but maybe we got the design wrong, I'll touch base about this with Roger.

And some requests:

1. The sequencers can get out of sync if you mess about with seq length or speed. It would be nice if we could have the ability to sync the start. Either a manual global bar length (like the Cirklons GBAR) or maybe just a manual keypress to sync on the next step 1 of the currently displayed seq.

2. Start of seq as well as end of seq

3. Some form of record. Say a quantised real time record or some form of step record. I guess the step record would be a problem for poly stuff so maybe just a simple mono step record function.

4. Strum type thing for steps with multiple notes. Delay each note a bit

5. Arp type thing for steps. For a single note this could also be used for ratcheting

Thanks a lot for these suggestions, we'll take them under consideration.

[gbevin]

Just found another one:
Copy sequence doesn't set end correctly.

Great catch, thanks! Will be fixed in next update.