can confirm I had the same error with TimeParty folder that was resolved with changing folder name to all lowercase “timeparty”…

been having a party with this script for the last few, so haven’t even downloaded the update, but kudos on this one sir…fantastic work…:ok_hand::+1::muscle::metal:

1 Like

: ) very nice thank you!

1 Like

Played with this last evening, really nice little patch!

9 Likes

sounds great! thanks for sharing.

1 Like

made a lot of updates to this! I think it’s a much more interesting/versatile effect now. Would love for people to try it out and let me know what you think!

Updates:

  1. Timeparty is now 7 sequencers (time, rate, feedback, reverb, filter cutoff, buffer position and autopan (thanks to the wonderful hnds lua LFO library from @justmat )

  2. Rate has “scale” modes in parameters and can now be set to “major” or “minor” (default is “perfect” intervals 1,4,5)

  3. You can shift the modulation values for each sequencer, which means it can now go from pretty slow to karplus-strong fast!

  4. Independent Sequencer directions - forward, reverse, pendulum, random, drunk

  5. Freeze buffer with key 2

  6. configurable crow inputs to toggle freeze, reverse, clock the sequencer, or sync the delay time. The “sync” code was basically copied verbatim from an example @zebra posted awhile back on how to implement a tap tempo, so thanks for that :slight_smile:

  7. The grid appearance/behavior is different, and roughly 95% more fun to look at.

  8. Fixed my math for the time sequencer which was way off.

I updated the top post with a hastily thrown together demo featuring a drum break and 2 simple synths recorded in one take through Timeparty.

More info in the readme on github. Enjoy!

10 Likes

Woah that’s interesting, hope to give it a go tomorow!

1 Like

Few issues on a fresh clone of the new version

# script init
### SCRIPT ERROR: init
/home/we/dust/code/timeparty/lib/delay.lua:33: attempt to call a nil value (field 'pan_slew_time')
stacktrace
stack traceback:
	/home/we/norns/lua/core/norns.lua:190: in field 'pan_slew_time'
	/home/we/dust/code/timeparty/lib/delay.lua:33: in field 'init'
	/home/we/dust/code/timeparty/timeparty.lua:60: in global 'init'
	/home/we/norns/lua/core/script.lua:74: in function 'core/script.init'
	[C]: in function 'xpcall'
	/home/we/norns/lua/core/norns.lua:191: in field 'try'
	/home/we/norns/lua/core/engine.lua:89: in function </home/we/norns/lua/core/engine.lua:88>
>> reading PMAP /home/we/dust/data/timeparty/timeparty.pmap

/home/we/dust/code/timeparty/timeparty.lua:67: attempt to index a nil value (global ‘crow’)

stacktrace
stack traceback:

/home/we/norns/lua/core/norns.lua:190: in metamethod '__index'

/home/we/dust/code/timeparty/timeparty.lua:67: in global 'init'

/home/we/norns/lua/core/script.lua:74: in function 'core/script.init'

[C]: in function 'xpcall'

/home/we/norns/lua/core/norns.lua:191: in field 'try'

/home/we/norns/lua/core/engine.lua:89: in function </home/we/norns/lua/core/engine.lua:88>

>> reading PMAP /home/we/dust/data/timeparty/timeparty.pmap

Is this because I don’t have a crow or is it because I need to update my norns version since crow was introduced?

First issue is something else, not sure.

Commented those bits out and things seem to be working now!

Yes, you’ll need to update your norns version since crow was introduced, but it should still work fine without crow after updating.

I think that should also fix the “pan_slew_time” error, since that’s a softcut parameter that was introduced in a newer version

2 Likes

Updating indeed fixed both issues, sorry for the false report and thank you for timeparty :slight_smile:

2 Likes

loved the initial release. can’t wait to give this a spin…

1 Like

congrats on the update! looking forward to playing with this tomorrow :partying_face:

it’s also super nice to see hnds in the wild! :smiling_face_with_three_hearts::smiling_face_with_three_hearts::smiling_face_with_three_hearts::smiling_face_with_three_hearts:

2 Likes

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

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

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

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

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

5 Likes

tried updating via maiden library and got the following error:

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

@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

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

4 Likes