On Mon, Feb 29, 2016 at 11:23 AM, Johannes Kroll <j-kroll@xxxxxx> wrote:
> Which would be kind of the point of an un-synched mode. Desync would
> only happen when a user disables the Sync parameter. If a user
> changes the new BPM control gradually by hand or via automation, the
> loop will also no longer line up, and lose sync.
Ok - still out of sync, but more controllable out of sync :D
> One things I noticed with the new code, pulled just now: The GUI BPM
> Control is 40 to 240 now (cool, thanks!) but the parameter is still
> 60..180. I think it's in masha.ttl.
>
> (Aside: One parameter is called Pass in the GUI, but Dry/Wet Mix in the
> parameter description. I think Pass fits better.)
All fixed in latest AVTK branch, available here for anybody who
wants to try the next-gen AVTK UIs and fixes:
https://github.com/harryhaaren/openAV-ArtyFX/tree/avtk
Cheers, -Harry
--
http://www.openavproductions.com
> Which would be kind of the point of an un-synched mode. Desync would
> only happen when a user disables the Sync parameter. If a user
> changes the new BPM control gradually by hand or via automation, the
> loop will also no longer line up, and lose sync.
Ok - still out of sync, but more controllable out of sync :D
> One things I noticed with the new code, pulled just now: The GUI BPM
> Control is 40 to 240 now (cool, thanks!) but the parameter is still
> 60..180. I think it's in masha.ttl.
>
> (Aside: One parameter is called Pass in the GUI, but Dry/Wet Mix in the
> parameter description. I think Pass fits better.)
All fixed in latest AVTK branch, available here for anybody who
wants to try the next-gen AVTK UIs and fixes:
https://github.com/harryhaaren/openAV-ArtyFX/tree/avtk
Cheers, -Harry
--
http://www.openavproductions.com
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
