Step Sequencer for the Mu !

[sebastien.harvey]

StepSeq_SH is a simple step sequencer for the Mu. You can control the Pitch, Octave, Velocity, Duration, Loop, steps, sequences, direction, interval. There is an editor to modify visible tracks.

http://www.jazzmutant.com/lemuruser_moduledetails.php?id=198

[Greg.g]

HI Seb HQ,

Thanks a lot.

[Greg.g]

Hi again Seb,

Problem
STEPSEQ SH FREEZZEEEE!!!!!!! MU

Step is load in device A (OR B). "OK fine work"
I load a another effect in device B and Mu CRASH.

thanks or it s my config


repeat crash test freeze mu step"
RESCAN NO CONNECTION
TURN ON/OFF/ON POWER LEMUR
CLOSE JAZZDEAMON (CRASH), IF I NOT CLOSE PROGRAM JAZZDEAMON CONNECTION IS LOST.
AND RESCAN AFTER 5 SECONDE.....FAST RELOAD CONNECTION
RELOAD JAZZDEAMON
load device A and B
crash.


loopbrace sh work fine with another port 8000?
by example port 7998 ALL buttom work
you have just selected clip (name) don t work.

WHY?



regards
greg.g

[Greg.g]

Problem

with Knok, when i transfert 64 48 24 16 8....steps in position 1 step, loop in position 1 IS FREEZZE WHEN I REPOSITION IN 8 16 24 48 64

MAX DON'T REMEMBER ALL POSITION....

SOUND IS LOST....




KING REGARDS

[sebastien.harvey]

Hi Greg.g

Waouw, that's a lot of problem

Ok, i'll check this out

Sorry for the bugs, i'm still at a very experimental state with all this

Thanks for you report Greg.g

[sebastien.harvey]

Hi Greg.g

I load many things at the same time, with the StepSeq in deviceA or deviceB, and I dont have that problem.

- Wich version of Mu are you using ?
- Are you only using Mu ?
- Do you have other interfaces loaded in the Lemur ? Do you use many interfaces, and switch from one to another with the arrows on the Lemur ?

That could be a possible reason for the freezing. If the Lemur run out of memory available, it freeze.

Mu takex something like 35% of the Lemur memory, and StepSeq 8%. So normally you should have enough memory left to load something else in deviceA or B. In that case you would have 57% left, what is enough to load anything.

If you edit the StepSeq_SH.amxd file, you'll see that it's a little sketchy. I should have indicate "Beta Version"... I didn't really check how to properly "init" a device, so I just put a Mu.device-container.maxpat. I saw it being use with the Mu.LemurHost.amxd instead of the Mu.amxd. There is probably a better way to init a device with the Mu. So maybe the problem come from there. If anyone can comment that point it would be useful.

About the steps Knob, it need to be improved so it will be more useful in a live performance. I just took the StepSequencer example in the Mu_Framework folder included in the Mu 1.1 and modify it a little bit so it would be loadable in the devicebrowser of the Mu. So it's the way the StepSeq is built that have to be modify.

Finally, about the LoopBrace, all the buttons work without a valid IP except the clipname monitor. The IP adress is just used for that little function. I could work this out, it could be simpler.

Let me know about the memory question, and I'll do my best to fix this bugging problem.

Have a good day !

Sébastien

[Greg.g]

Hi seb,


Live 10 tracks 280 clips (700 samples),3 vst, 3 effects by track master 6 effect
Mu 1.1 + 3 interfaces buttom (adition on mu) and 3 interfaces switch
3 deamon osc with 3 daemon midi
over limit 85%!!!!!!!!!!!!!!!!!!!


So, i reduice my config and transfer 3 interface in 3 Mu.device-container.maxpat
I test

Confirm
Loopbrace are limited 256 clips on 256 track (256 µfader in mu) no......
It s not a good utilisation
By example 1024 clips on 10 track max

Have a good day
Parlez vous francais?

best regards.
Greg.g

[sebastien.harvey]

Bonjour Greg.g

Donc si j'ai bien compris, vous utilisiez 3 interfaces en plus du Mu ?

Cela expliquerait le problème, manque de mémoire.

Ce que j'ai fais dernièrement pour utiliser une interface qui prenait a elle seule 42% de la mémoire du Lemur, c'est ajouter un bouton directement dans le Mu qui efface ce qui est dans les container deviceA et deviceB et qui par la suite importe l'interface. J'ai ajouté également un bouton dans l'interface qui détruit tout lorsque je désire retourner au Mu.

Ce serait une solution simple.

Si vous avez des questions concernant cette façon de faire il me fera plaisir de vous donner un coup de main.

Concernant le LoopBrace, ses capacités seraient effectivement à améliorer.

Êtes vous confortable avec MaxMSP ? Si quelqu'un désirait me filer un coup de main, ces petits outils pourraient devenir plus complets et utiles.

Merci

Au plaisir

Sébastien

[Greg.g]

VIVA.....LA REVOLUTION MAX....

All collaboration.


king regards

[cyclyk]

Merci Sebastien pour tes nombreuses créations, je teste celle-ci ce week end.

[Greg.g]

Hi cyclyk seb

i confirm it s just a problem of memory.

work perfect no crash...

nice day all

[Anonymous]

It needs to be improved so it is more alive. I took StepSequencer Mu_Framework example, a folder with the Mu 1.1 and modify it slightly to make the device loaded in the browser is Mu. So you do not StepSeq is built, which must be changed.

[sebastien.harvey]

I mentioned in the install.txt file that the StepSeq SH was just an integration into the Mu of what was already done.

If you improve it I'll be happy to try it