If there is a countdown and you play note events within the countdown these events are recorded but get the timestamp at the start of the recording.AndreasD wrote:I appologize if I misunderstand!
What you say is the correct behaviour. The countdown is the usual count in and waits until it's zero before start recording.
Bug in Event recorder???
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- Topic Starter
- 5070 posts since 27 Jul, 2004
You shall not record live input...
Make a sequence with starting at 1.1.00000 i.e. with a one bar C3 note followed by a one bar D3 note to trigger chordz...
Set the grid in the event recorder to "No Grid", set countdown to something different than 0 and hit record...
I bet the recorded sequence is missing the chord for C3...
Make a sequence with starting at 1.1.00000 i.e. with a one bar C3 note followed by a one bar D3 note to trigger chordz...
Set the grid in the event recorder to "No Grid", set countdown to something different than 0 and hit record...
I bet the recorded sequence is missing the chord for C3...
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Chordz VST is outputting the events at a wrong time. It seems to simply output the events on audio block boundaries. When MuLab receives the VST events it calculates the precise timestamp but due to the fact that Chordz marks the events on a too early time, the recorded events fall before 1.1.0. These events *are* recorded, but you don't see them in the composer as they fall before 1.1.0. You can see them though in the Event List Editor. Conclusion: Pls contact the VST dev.
-
- KVRAF
- Topic Starter
- 5070 posts since 27 Jul, 2004
The same happens with BlueArp as well!!!mutools wrote:Chordz VST is outputting the events at a wrong time. It seems to simply output the events on audio block boundaries. When MuLab receives the VST events it calculates the precise timestamp but due to the fact that Chordz marks the events on a too early time, the recorded events fall before 1.1.0. These events *are* recorded, but you don't see them in the composer as they fall before 1.1.0. You can see them though in the Event List Editor. Conclusion: Pls contact the VST dev.
Edit: And why it doesn´t happen, if Coutdown in the record options is turned off??? With the grid settings I can imagine, same if it isn´t recorded from 1.1.00000, but why with countdown???
Just tried with the same setup: Chordz is recorded in Reaper without any flaws...
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Same issue i assume.Trancit wrote:The same happens with BlueArp as well!!!mutools wrote:Chordz VST is outputting the events at a wrong time. It seems to simply output the events on audio block boundaries. When MuLab receives the VST events it calculates the precise timestamp but due to the fact that Chordz marks the events on a too early time, the recorded events fall before 1.1.0. These events *are* recorded, but you don't see them in the composer as they fall before 1.1.0. You can see them though in the Event List Editor. Conclusion: Pls contact the VST dev.
Cause then there are no negative times as a result of the VST doing faulty timestamping.Edit: And why it doesn´t happen, if Coutdown in the record options is turned off??? With the grid settings I can imagine, same if it isn´t recorded from 1.1.00000, but why with countdown???
Maybe Reaper always rounds recorded times before 1.1.0 to 1.1.0.Just tried with the same setup: Chordz is recorded in Reaper without any flaws...
You can do the same in MuLab by using a recording grid.
Conclusion: Pls contact the VST dev.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
x deleted x
(and then I hit quote and saved...)
(and then I hit quote and saved...)
Last edited by pljones on Tue May 02, 2017 5:23 pm, edited 1 time in total.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK