#21

Thank you! yes I am planning on adding more LFO targets for hnds, right now it just uses pan as a sorta hard-coded target for the autopan sequencer.

2 Likes
#22

Late to the party, but wanted to throw some praise your way, crim. This is outstandingly fun and really brought my Ciat-Lonbarde patch to life this morning. Looking forward to taking a deeper dive soon.

3 Likes
#23

wow thanks! it’s always nice to hear when people other than me are using this stuff. would love to hear any recordings if you feel like sharing.

This also reminds me I want to give this script a little more love sometime soon…

4 Likes
#24

I’ve pushed an update! :tada:

  • Added global clock
  • Hid some params that you can’t update (because the sequencer modulates them)
  • made encoders less sensitive

The clock update means a minor change to the crow integration. From the readme:

Input 2 can be set to “trigger step,” which will cause the sequencer to advance steps on each incoming pulse. This will override your global clock source if it is set to “crow.” Global clock will still sync the delay time, but will no longer advance the sequencer. This behavior enables you to advance the sequencer with an irregular clock, while still tempo syncing your delay to a master tempo.

Planning on adding a few more things this week… stay tuned.

Also, if you haven’t seen the video on the updated norns apps page, I highly recommend checking it out. It features some wonderful performances from lines members using a few different scripts, including a lovely clip of @Olivier using timeparty.

9 Likes
#25

TimeParty is a revelation! Had so much fun putting that clip together.

5 Likes
#26

tried updating via maiden library and got the following error:

Screen Shot 2020-05-04 at 12.31.33 PM
Screen Shot 2020-05-04 at 12.31.33 PM1306×248 7.62 KB

#27

I’ve had this happen with other scripts. If you try it again, it will say already up to date or something of the sort. (assuming it’s the same thing I’ve encountered :sweat_smile:)

3 Likes
#28

@gnome666 let me know if you try again and it’s still not working, although I suspect I’d have to bring in some of our resident maiden experts if it continues to be an issue

#29

@Justmat tip was spot on. re-attempt was successful. THANKS!

4 Likes
#30

Hey @crim! I was wondering if you could help me trouble shoot TimeParty crashing on load. I get the error: init read out on my Norns (a Fates DAC model) when I try to open the software. I also get this printed to the Maiden console:

    # script load: /home/we/dust/code/timeparty/timeparty.lua
# cleanup
# script clear
including /home/we/dust/code/timeparty/lib/delay.lua
including /home/we/dust/code/timeparty/lib/sequencers.lua
including /home/we/dust/code/timeparty/lib/FXSequencer.lua
including /home/we/dust/code/timeparty/lib/Pages.lua
including /home/we/dust/code/timeparty/lib/hnds.lua
pset >> write: /home/we/dust/data/system.pset
# script run
Engine.register_commands; count: 0
___ engine commands ___
___ polls ___
amp_in_l
amp_in_r
amp_out_l
amp_out_r
cpu_avg
cpu_peak
pitch_in_l
pitch_in_r
# script init
### SCRIPT ERROR: init
/home/we/dust/code/timeparty/timeparty.lua:78: attempt to call a nil value (method 'add_group')
stack traceback:
	/home/we/norns/lua/core/norns.lua:126: in method 'add_group'
	/home/we/dust/code/timeparty/timeparty.lua:78: in global 'init_params'
	/home/we/dust/code/timeparty/timeparty.lua:47: in global 'init'
	/home/we/norns/lua/core/script.lua:93: in function 'core/script.init'
	[C]: in function 'xpcall'
	/home/we/norns/lua/core/norns.lua:127: in field 'try'
	/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>
>> reading PMAP /home/we/dust/data/timeparty/timeparty.pmap

I’ve tried updating TimeParty and get the same “Already been updated” prompt that others on this thread have gotten, and I’ve restarted Norns a few times to no avail. Any suggestions on what I need to do to fix this?

Thanks for your help!

#31

you just need to update your norns/fates :grinning:

add_group is a new thing.

3 Likes
#32

yeah, as @Justmat said you’ll need to update your fates (both for new param groups and global clock stuff). I would make sure you follow the update procedure from the fates thread here.

Let me know if you have any trouble after that.

1 Like
#33

as far as we can tell, this is a github backend issue. you will also run into it from time to time in other git clients, seems to have popped up in the last few months, retry usually works.

2 Likes