-
as seen previously on vimeo http://vimeo.com/4444655 my implementation of the successful tonematrix is live
if you have not witnessed the hype surrounding the tonematrix, check it out here http://lab.andre-michelle.com/tonematrix
it is basically a step sequencer, but it features a adorable wave map
For more information, please consult the wiki and feel free to edit the article where you see fit
http://docs.monome.org/doku.php?id=app:flickering_lights
love
robb
Download:
jar version: http://beer2peer.com/monome/flickering%20lights%20v0.4.2%20jar.zip -
hey robb, great app! while still searching for my napoleonic hat, lemme report that it works great on my new built arduinome. who needs flash now! cool app design btw
-
This is totally awesome, just got lost in it for the last few hours.
Midi clock support, pages for each midi channel (maybe hold the bottom right button down and select pages with the bottom row 1-8 buttons), and patch save support would be incredible.
Thank you very much for sharing it. -
thanks for the kind words everybody
@ajbriones
that is strange, im on 10.5.6 as well
The .jar version is not intended for macs as it does not come with the mmj library which is necessary on mac
@auditory canvas
multiple pages? well i knew such a request would come, i really think this is about simplicity but multiple pages is pretty easy to implement and so is save/reload
coming soon
source code will be made available once i am done with implementing features and commenting the code -
@robb
I just have to say I loaded this app up last night on my 128 (I'm running on OSX) and had a blast with it! I think the simplicity of it is what makes it so much fun. I mapped each row to an 808 kit Drum Rack in Live and jammed with that for a long time. It did of course make me want to have it slave to a midi clock, but I know you are working on that already.
After first seeing the video of it I thought the flashy lights would be annoying and extraneous and would be hard to tell what was happening visually with the sequence, but after actually using it, I found it didn't bother me at all. However, it's too bad the Monome firmware doesn't support variable LED intensity (someone please correct me if I'm wrong on that) as it would be a bit easier on the eyes if as a pulse is radiating out it could fade out just as it does in the Tonematrix Flash version. I can't remember if the Tenori-On behaves this way too but I know that thing is very intense on the eyes as well.
Regardless, its a great little app and thanks for putting it out there so quickly!
cheers,
-cm -
from what i have seen on videos, the tenori-on does not allow variable itensity on the leds.
There is a variable LED intensity firmware for monomes (40h only?) floating around, but its not perfect and there are some difficulties with the pulse width modulation it uses, as far as i know -
@alrick, to view the .xml file you need to right click on the flickering lights file, and select 'show package contents'.
You might already know that, but mentioned it just in case. -
make sure the midi port you are using is sending beat clock signals.
Go to Abletons Preferencs, click MIDI sync and enable Sync for every output port you want to use.
Start flickering lights and select that same MIDI port under input devices (left menu), now click beatlock on and dont forget to start the clock in ableton (i.e. press play)
flickering lights is only a midi clock slave, btw
@ auditory canvas
thank you for pointing that out :) -
Hello, I'm having trouble getting it going. Though I'm very close, maybe there's an easy solution. I'm running it with a 256 (with width and height set to 16) on an intel mac with 10.5.6 .jar version with mmj and processing installed. I can press buttons on the monome to see the step light up and flicker, though i can't turn them off.. I just can't get it playing it seems. I even have beat clock set up. Start ableton and the first step flickers and stops there. I'm thinking that's why midi doesn't send to ableton either. Any ideas? Thanks
-
I'm basically experiencing exactly what veiss describes except I'm trying to run it on a 128. The previous version (w/o clock sync) worked fine. Robb are you using the RWMidi library?
-
I can't get 0.2 to run either, last version worked fine, but no joy with this one.
-
@crixmadine
A Lot of monome mac users have mmj because of pages. -
i was able to reproduce that bug, but then even v 0.1 stopped working, so i had to restart mac osx
im still not sure what caused this but i made some changes to the code, would be great if anyone could try these
http://beer2peer.com/monome/flickering%20lights%200.25%20mac.zip
http://beer2peer.com/monome/flickering%20lights%200.25%20jar.zip
and post a screenshot of the midi device lists if does not work
sorry for the trouble -
@robb - just wanted to say THANKS! for this app. Spent hours playing with it last night - even got my girlfriend involved. I played the right half of the 128 and she played the left. Awesome.
-
you mean for an impulse-instance?
ill change the root-note to a C and the default scale to ionian if its that what you mean
i am currently unsure about the multiple layers thing, as i think this is very much about simplicity and i cant think of any unobtrusive way to change the layers
[one mod button plus one to select the layer would require the mod button to activate its step once the button is released or after a slight delay. Id rather have one control row than make one button react differently from the others, but thats just me] -
Just checked 0.25 and all working well again :-)
I actually got the idea of the mod button hold down from the app Pages.
Couldn't you do it like pages does, where if the button is held down and used as a mod it doesn't then activate the apps function - in this case selecting a note?
Perhaps by a time out or something?
I have no idea how they got it to do what it does in pages, but when you hold the farmost bottom row button down, and then press any of the top row buttons 1 onwards, it selects that page, but doesn't send the message to the app on the page you were on - example, if I were running MLR on page 1, and held down the far right button to change pages, it wouldn't trigger the sample in MLR.
Does that make sense?
I guess i wouldn't want to lose a row for the sake of changing pages, this app has already made me want a 256 much more, after using it on a 128, to then only have 7 notes to trigger instead of 8 due to a page changer row would be upsetting :-) -
ok, now you've got multiple layers
press the bottom right button directly followed (i.e. within 350 milliseconds) by a button of the first row to select the corresponding layer, otherwise the step is triggered normally
every layers output is send to a midi channel of its own (thus you cant have more than 16 layers)
by default, every layer makes waves. If this is too messy for you, set settings.xmls activeWavemapOnly to true. If you don't want multiple layers, set layers to 1.
i also set the default root note to c and the default scale to ionian, triggering an impulse instance in ableton is now easier
hopes this works for everybody, let me know how you like it
PLEASE NOTE: your old settings.xml will not work with this. -
Thanks once again Robb, the layers are awesome, and the page change method is perfect.
I'm probably doing something wrong, but can you advise how to change the midi channel for each layer? They all seem to default to the same midi channel, and if I select a layer and change the midi output then it changes for all layers.
I am using the IAC busses on a Mac. -
Dear god this is so much fun. Thanks, robb!
-
Robb, I am using Cubase, but that's basically how i have it running, but all layers send to the same channel one bus 1. or buss 2 etc.
I'll check the config of my IAC busses.
Edit, Robbs link to a post below was actually the problem with Cubase. -
Robb, after thinking it was my busses at fault, it seems they weren't, the post you linked to was actually the problem, thanks for finding it.
I use Live for live performance, but use Cubase for production. So I had set them up before for using the Pages app, but never really used them for anything else until now.
Totally in love with this app, especially now it has layers.
How hard would it be to setup a mute control layer, I mean a layer that enabled you to mute or unmute layers by using the top row buttons?
This would be awesome for using it live.
So for example if I had 8 layers running, I could then hold down the page change mod button, and select the bottom row 1st button, which would then let me press top row buttons 1-8 to mute or unmute any of the playing layers?
Appreciate you have already developed this enough, and it rocks already, so feel free to tell me to !@$% off :-) -
Robb, if you tell me what sort of video you are after, I can try and get this done for you over the next few days.
-
looks pretty easy to implement, ill try it later after uni
im basically looking for any performance video that features it, not necessarily as the only app, maybe in connection with outboard gear, maybe not; i am totally open.
edit: but if you asking to get inspiration and don't know were to start: i want accelerandi and synth sounds set to 'oooahhhhh' :-)
thank you