![]() |
![]() ![]() ![]() ![]() ![]()
|
next newest topic | next oldest topic |
Author | Topic: GrainCloud problem |
Bill Meadows Member |
![]() ![]() ![]() I have discovered a problem with the GrainCloud. The GrainDur and CyclesPerGrain parameters appear to have a peculiar interaction when using the VCS. If I set GrainDur to "0 s" in the GrainCloud, and use a HotParameter for CyclesPerGrain, it behaves as expected. If I use a HotParameter for GrainDur and set it to zero in the VCS, then the CyclesPerGrain control no longer works properly - it no longer changes the grain duration. In fact, the grain is reduced to a positive-only blip. (Half-cycle.) IP: Logged |
SSC Administrator |
![]() ![]() ![]() The grain duration is calculated differently when GrainDur is a constant 0. When you make it hot, it has to be protected against the eventuality that the cyclesPerGrain and grainDur add up to a zero duration (because the inverse of the duration is used in the code). When the parameters are hot, the minimum value for cyclesPerGrain is 1 cycle and 1 ms (for grainDur). When you hard code one of those parameters to zero, it is ignored in the calculation of the grain duration. But if one or both are "hot" they go only as low as their minimum values because the resultant grain duration cannot be allowed to go to zero. IP: Logged |
Bill Meadows Member |
![]() ![]() ![]() quote: That would be o.k. if that's what it did, but when GrainDur is "hot" and set to zero, CyclesPerGrain no longer causes any change in duration. IP: Logged |
All times are CT (US) | next newest topic | next oldest topic |
![]() ![]() |
This forum is provided solely for the support and edification of the customers of Symbolic Sound Corporation.