Did you compile the firmware first?
did it compile successfully?
Sorry I don't really do windows, but I know the Mac OS X/Linux scripts work ' out of the box' , and windows should as well
How to record knob modulation into a table and play it back?
@thetechnobear No, I can't seem to compile the firmware, It says 'make' is not reconized, and I assume it's something a bit too geeky for my small technical level. Don't worry about it, I can wait for the next updates, I was just impatient for this object and gave it a try.
Thanks anyway, you're doing a great job
If you haven't , you need to run platform_win/build.bat and follow instructions, this will setup the build environment.
( needs to download a few things etc)
I'm getting further... Still doesn't work (now get stuck compiling the patch), I'm sure I messed up with the different builds I have now installed. I'll spend more time with it, but I've gone back to the release version for the moment, needed to get some patching done.
Thanks anyway, I'm sure I'll get there soon (and I'm starting to understand a bit more)
I use a version I build from Github a few weeks ago. On Mac.
Firmware ID: 58DE7602
Firmware version: 1.0.01, crc=0x58DE7602, entrypoint=0x20011000
The patch works here...
Yeah or some LFOs that is syncable to ppq. That could solve the sync to clock problem.
why would you not just use 24ppqn (or 6) output from a clock to trigger the reset , and therefore you will be in sync?
the 24ppqn output is a simple sync'd counter, so as I did on another thread you can divide this, and then run into another counter, so you can get bars/beats, or what ever divisions you want,
using this you could then have a control which forced the modulation to loop every 4 bars (or whatever)
if you want modulations in sync, which is not really what this was designed for... which was more 'live performance', then that is a different thing, thats about quantising... could easily be added to this object (its simply a matter of 'quantising the clock') but you can also quantise externally to the object (either on input or output, depending on your needs really)
the trick with all these things, is not to try to get one component to do everything, rather to give it the inputs that allow other things to drive it.
again on another thread, I said, I think we could do with a clock thats a bit more a musically oriented (rather than time/samples) , with tempo input, and bar/beat outputs... i think if it has external inputs (for midi sync, and perhaps tempo 'detection') , it probably would be close to what most people 'expect' to find and have been attempting to do with existing objects (which is possible)
its trivial to write, just a matter of finding the time to get around to writing it
Yes it only records when recording is turned on.
That is why I connected the "end" of the loop object to the "Rst in" on the square lfo that I use for the gate input . Cause then the recorder will restart everytime it reaches the end of the "up" and starts over. If you use lfos as clock this works pretty good.
Still no idea why you think an LFO is necessary.
But hey, what ever works for you... I'm sure you have your own reasons
Well at first there was a toogle connected to the gate input it didnt record here. Then I tried with a sq lfo and that worked...I probably did something wrong to start with... So I just continued using an lfo. Maybe I'll try without again.
EDIT just tried again and it still doesnt record when the toggle is connected to the gate input. Atleast I am not sure how it should react. I am looking for recording something and then loop it in sync with some other sequencers. And for this connecting an lfo to gate works well.
I also tried with midi clock and that also works.
THough I might add It had crashed Axoloti software a few times here.
This is great and handy!!
I experience a problem recording note-numbers:
The last note recorded is most of the times wrong...
Any ideas?
Thanks!!
bumping this as I'm working on a simple looper event/note sequencer.
I posted here
but it seems to me the object by @thetechnobear is a good way of doing it.
I'm having hard time understanding the playback though.
I made this patch and it doesn't seem to playback recorded events.
I'm a bit stucked.
seqtestNEW2.axp (10.4 KB)