PlugIn Song Position Fix

Song Position Fix (no more missed clock events in your DAW)

 (48 Votes)
1.4 (Updated 17 years ago)
77.1kB
August 04, 2007
Reaktor 5 or lower
Macro Sequencer elements

DESCRIPTION

A replacement for the Song Position module which works as it should in DAW's such as Ableton, aswell as keeping the same functionality when used in standalone.
Its has been noticed a lot that the inbuilt Song Position module tends to have clock event dropouts which can cause some nasty unwanted effects when Reaktor is used as a PlugIn in some Hosts (missed hits and timing errors etc). It got to a point where I couldn't use Ableton with Reaktor because of this annoying issue, as I used a lot of sequenced instruments. So I made this.... This has an internal clock independant of the host but is synced to the Host clock. The result is a more solid clock with NO dropouts. This dropout problem also affects the 1/96th and Sync Pulse modules, so Ive added outputs which imitate these functions. The sync pulse settings can be changed, please check the tooltips on the Rat/Dur ports of the Sync Pulse macro within this macro. This also has the same reset function as Dan Battaglia's original song position fix.
Ive tested this quite alot in Ableton and all seems fine. Hopefully it will be the same for other hosts which have this problem aswell.

Update 1.1: Added a ClockCheck Ensemble to see if there are clock event dropouts in you DAW. It will display any errors on Clist's EventWatcher aswell as sound a bleep. Simply load into your host, press play and wait (I'd say for about 100 bars to be safe) I get 38 errors in Ableton LIVE 6.07 at 120BPM over 100 bars. It does vary depending on BPM.
Update 1.2: Added a Version 2 macro to the download file. Slightly more accurate I think. And posibly fixed a bug with the sync pulse macro.
Update 1.3: Added audio output (thanks to selotape (frank) from the forum for that! Should be a little more accurate aswell.
Update 1.4: Improved the PlugIn Detect macro which is needed for tempo change differences between standalone and plugin versions. When used in a plugin it needs to re-sync when tempo changes occur, where as in standalone, info from the Tempo module is more frequent and doesnt need to re-sync itself. If the PlugIn "re-sync" system operated in standalone it could result in very "choppy" tempo changes - hence the need for this detect macro so that the tempo re-sync only occurs when used as a Plug In.
Enjoy

Matt

COMMENTS  (16)

Please login to add a comment
Goremall
3 years ago
Thank you so much for this. I working on so many updates right now I don't have time to build one of these myself. This is wonderful thank you again!!!!
Jonathan Hoffmann
14 years ago
Thanks for this good work
Derrick Curtis
14 years ago
Im new at reaktor, I was wondering how do I install this fix?
Ma. P.
14 years ago
This solved ALL of my timing problems!!!
Thomas Steinhauer
15 years ago
i was looking soo long for a fix like this.. tyvm!
gergely suto
16 years ago
well.. this fixes any sequenced plug i tried. even gobox(with the pulse version), which was really a drag.
Jedinhopy Xelon
16 years ago
Where are the perfect sequencer with song position and perfect start stop macro.
Robert Tubb
16 years ago
Great, this was so annoying... Thanks.
Jedinhopy Xelon
16 years ago
(PlugIn Song Position Fix v1.4) Is only a self playing clock this is bad. song position will not go to event 0 and constant event on stop music button in music software. play button enables playing the seq stop button stop and reset the sequence to event 0 and constant. Play Button Sequence is on. Stop Button Stop playing + reset to 0.
gergely suto
17 years ago
Thank you so much for this!! I am still progressively discovering it, so it will take some time before I can give serious feedback. Reaktor is a great program but it needs this kind of fixes is you want to use it as a serious instrument, not just f**k around! (So actually you are doing NI's job, here) Thanx again:)
Matthew Todman
17 years ago
BE AWARE: Rendering with this seems to have some dodgy results! I'm looking into why.....
Matthew Todman
17 years ago
For anyone thats interested... the PlugIn detect works because when Reaktor is used as a Plug In (only tested in Ableton & Bidule), the G output from the start/stop module outputs two 1 events, as opposed to just one in standalone. So it uses this to determine if it is being used as a PlugIn.
Karl White
17 years ago
thank you thank you thank you
Matthew Todman
17 years ago
I'd be interested to know what DAW's suffer from these dropouts. Be nice to get comments on what DAW's have dropouts (using the ClockCheck.ens). Bidule is the same. I had 18 dropouts at 120BPM over 100 bars. I've made a few tweaks to to macro too but will need to test a bit before I post it.
Phil Durrant
17 years ago
thanks Matt :-)
Dieter Zobel
17 years ago
i also often had ableton crashes by loading sequenced instruments. hope this is the medicine. much thanks
now