I'm currently having a problem syncing a drum machine plug in (Jamstix) with Logic Pro which causes the plugin to lose it's place in terms of bar/beat location when there is a time signature change in Logic.
I had hoped to debug this by using PnS and it's transport data to see what's going on but it appears that it has the same problem because all it reports is beats from the beginning and the "current" time signature. So, it is not able to calculate the correct song position if there have been previous time signature changes.
Is actual song position passed to plugins? A very old response from the Jamstix developer for a similar problem suggests that it should be possible. A user had the same problem in Reaper and support claimed the problem was in Reaper because the song position was not properly reported but it worked as expected when Jamstix was used in Sonar.
Anyone have any ideas about this?
Plug'n Script Question
-
- KVRer
- Topic Starter
- 28 posts since 17 May, 2008
Problem solved - my error. Jamstix songs are made up of a sequence of parts and there can be no time signature change within a part.
It appears that plugins are not sent the current SPP and so they need to calculate it on the fly. Given that playback can start at any arbitrary point this can only be achieved if the plugin is independently pre-programmed with an exact copy of the time signature map as that which is programmed within the DAW.
It appears that plugins are not sent the current SPP and so they need to calculate it on the fly. Given that playback can start at any arbitrary point this can only be achieved if the plugin is independently pre-programmed with an exact copy of the time signature map as that which is programmed within the DAW.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981 - KVRAF
- 6345 posts since 8 Sep, 2004 from Paris (France)
Sorry for the delay in our reply. Thanks for sharing this information with the community! Tempo or time signature changes within a song may indeed cause odd behavior regarding beats and measures, and all hosts & plug-ins do not manage it the same way. The APIs for all plug-in formats do not let you do better than that because they cannot report the cumulative history from the beginning of a song.