#21

512 is noticeable latency (I can’t record anything live from a mic at 512) I don’t know where your issue lies here but 512 is quite high buffer size. (I mostly work at 128, 256 if the session is heavy)

#22

yeaaa but I’m the one not having latency issues

#23

Ahah, I’m off you C++ nerds! Go javascript the world away!

1 Like
#24

Will try to do something tomorrow. Would an Ableton set be helpful?

#25

nah - I think I’m really just trying to understand how long the delay is, and if I’m getting that long of a delay too. maybe just like record yourself recording a loop so I can hear the transition from input -> loop, if that makes any sense ?

1 Like
#26

oh, hello. This is really, really good.

I’m still wrapping my head around a few things - timing decent loops, which I’m getting to; working out how to have channels fed to different places - it sounds like ekphras is my friend there - and how metonomy works.

I’ve found issues where, having replaced a loop, I then hit the metonymy “location” button… and metonymy starts playing the old loop. Unsure as to why that is, it may still be user error.

My main note about usage would be gain staging, and that metonymy sends seem cooler than the anachronism output. My only real feature request would be - and I have no idea of how to implement UI for this - having speed options beyond powers-of-two multiples, to get effects more interesting than octaves…

#27

It’s actually something I wanted on norns mlr as well, I guess I should go and try to code that myself, ah…

1 Like
#28

the idea is that anachronism sort of has a small, curated set of controls mapped to the grid, whereas ekphras allows you to access all the parameters in softcut without much moderation. it has a separate pitch control that’s un-quanitized for example.

I just pushed updates to both their repos that include preliminary versions (I pulled out controls that weren’t working) of anachronism.remote and ekphras.satellite, which allows the anachronism interface to directly control ekphras instances rather than outputting the loop form the anachronsim device. this allows for loops to live in separate tacks at the default location, and adds additional controls to each loop.

I am still very much working out how to explain all this.

might this be a result of the buffer selection on the right ? (metonymy, specifically, is hella untested rn. I bet this breaks it)

1 Like
#29

I welcome additions to prosidy (it’s part of the point of it), but the codebase is very undocumented and there will likely be changes to the standards I’m using (diction, a JSON format for doing cross-device communication, and an un-named javascript api for grid stuff) sooooo: later

would very much like to hear what kind of things developers would want to get into and how much help would be needed

#30

Without recording an example the best way I can explain it is if I am recording drums the beginning of the first kick lets say doesn’t make it in on the first transient. My buffer is set to 256 but I don’t experience this issue in any other recording situation in Ableton

#31

right, yea, I’m figuring it out, that seems consistent with what I’m getting - this won’t be a priority fix for me but I’ll work on it at some point.

do you think it’s only ever clipping the beginning of the loop? it never misses anything at the end?

#32

oook: update: took out the metonymy/location stuff cuz it wasn’t working super well but I added a “”“beta”"" of the ekphras/multi-tracking stuff which is running pretty smooth so far. plz experiment/break/have fun. fixed some buffer switching bugs too but timing is still whack

#33

I am loving Anachronism, even with this rubbish cellphone video.

(moved from the Anaphora thread, because I was being a wally).

3 Likes
#34

role call: would anyone be bummed if I went down to 4 voices in the nxt version of anachronism ? I’m finding it’s more useful to focus on less (esp. with overdubbing between voices) & 8 voices feels like wasted real estate but happy to version stuff if it’s useful to others

3 Likes
#35

i still haven’t used it but i almost always only focus on one buffer, 2 if i am feeling spiced out therefore is see 4 as luxurious and 8 as ridiculous.

2 Likes
#36

yea I’m feeling u here

#37

I’ve liked using more than 4 loops that I can then bring in and out of a mix using either the volume control or the play/mute button.

So I’d vote for splitting the 8 voice into a different version (even if you focus development, bug fixed etc on the 4 voice version).

Although having said that, there’s nothing stopping me from just renaming the “old” 8 voice version…

#38

might as well just do that in the main repo tho ! easy to do, and there’s already multiple versions between the remote script & standalone anyway. just need to find a reasonable way of naming stuff so it isn’t painfully confusing

2 Likes
#39

! added a 64 grid x 4 voices layout !

ignore the minor change in the 128 layout, forgot to update that in code. route button is still the 4th key from the end

4 Likes
#40

I haven’t really checked this out thoroughly on my end but just quickly wondering if this might be the same bug (is sounds like the problem w/ anachronism also has to do with loop length)