Well done man, I appreciate you going back over some of these ideas from last year, and looking forward to updating some of my experiments with your knowledge. May your headphones continue to evolve.
If you were looking for another idea for an essentials subject, I'd love thoughts on UI approaches. Specifically also UI approaches that don't tax the CPU/GPU too much. Thanks again! These classes are super helpful!
Don't know if this is your specific issue, but I've had funny stuff happening with snapshot~ where using the `offset` message sorts it (ensuring you're sampling the data in the same vector that you want to). To do this I have [adstatus sigvs] -> [- 1] -> [prepend offset] going in to snapshot~ and then I'm always sampling the data at the last sample before the vector ticks over.
mc.dup~ does convert a single-channel signal to MC, but it doesn’t do the voice management bit, where you generate a ramp on one currently non-busy channel
2 місяці тому
Thanks for the amazing series, enjoying it and learning a lot! Regarding the faster-than-note-length polyphony on distributed MIDI channels, have you considered the mc.snowphasor~ object? It seems to me that it might do exactly what you are looking for, but you check and decide. Consider the following example: [phasor~ 0.5] --> [subdiv~ 16] --> [what~] --> [mc.snowphasor~ @mode 3 @chans 16 @ramptime 1000] --> [mc.midiplayer~ @chanmod 16].
you are doing an amazin set of classes, man
Well done man, I appreciate you going back over some of these ideas from last year, and looking forward to updating some of my experiments with your knowledge. May your headphones continue to evolve.
thank you and haha! i think i’m settled on these beyers for my main studio. they are great!
Good stuff!
If you were looking for another idea for an essentials subject, I'd love thoughts on UI approaches. Specifically also UI approaches that don't tax the CPU/GPU too much. Thanks again! These classes are super helpful!
yes, love that idea! we’ve touched on it here and there in different videos but it deserves its own for sure
Don't know if this is your specific issue, but I've had funny stuff happening with snapshot~ where using the `offset` message sorts it (ensuring you're sampling the data in the same vector that you want to). To do this I have [adstatus sigvs] -> [- 1] -> [prepend offset] going in to snapshot~ and then I'm always sampling the data at the last sample before the vector ticks over.
oh interesting. wasn’t aware of the offset message! i’ll try it - that does sound like it would solve the problem in this case. thanks!!
@24:30 maybe you thought of this but wouldn't [mc.dup~] do what you want? If it doesn't, why?
mc.dup~ does convert a single-channel signal to MC, but it doesn’t do the voice management bit, where you generate a ramp on one currently non-busy channel
Thanks for the amazing series, enjoying it and learning a lot! Regarding the faster-than-note-length polyphony on distributed MIDI channels, have you considered the mc.snowphasor~ object? It seems to me that it might do exactly what you are looking for, but you check and decide. Consider the following example: [phasor~ 0.5] --> [subdiv~ 16] --> [what~] --> [mc.snowphasor~ @mode 3 @chans 16 @ramptime 1000] --> [mc.midiplayer~ @chanmod 16].
ooh super interestnig idea, i will play around with that. thank you!!