Vojtech please help
earlier in my project i observed this but it was too little(because i used 32 bars insted of 4)
but today i tried to observe it and it was damm high to be observed
is it some glitch or is it due to the 1024 sample delay due to the other plugin in my other track chain??
EDIT:i am talking about the sync issue which can be observed when i am paused at a 2bar position the sigh in mrhythmizer is offset by some amount
is this a bug in MRhythmizer or ??
-
- KVRian
- 707 posts since 29 Dec, 2016 from India
You do not have the required permissions to view the files attached to this post.
REAPER, Phase Plant , Unfiltered Audio TRIAD and LION, NI classic collection,......... ETC
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Hmmm, ok, so I'm not sure how to react here 
. Is the actual sound wrong? If you mean just that the indicator is a bit ahead of time, I think it's because the host actually asks it to process at an exact quarter, hence position 0, but after that it is not 0 anymore, because, well, it processes something .
It's actually pretty classic - if you look at meters etc. in plugins and especially if you have a latency inducing plugin for instance, then the meters (and other visualisation) is usually ahead of time, because the plugin processes some data at some point, but it cannot really know it will actually be auditioned in a different time, and even if it would know, it would consume too much resources to delay everything in many cases.
. Is the actual sound wrong? If you mean just that the indicator is a bit ahead of time, I think it's because the host actually asks it to process at an exact quarter, hence position 0, but after that it is not 0 anymore, because, well, it processes something . It's actually pretty classic - if you look at meters etc. in plugins and especially if you have a latency inducing plugin for instance, then the meters (and other visualisation) is usually ahead of time, because the plugin processes some data at some point, but it cannot really know it will actually be auditioned in a different time, and even if it would know, it would consume too much resources to delay everything in many cases.
-
- KVRian
- Topic Starter
- 707 posts since 29 Dec, 2016 from India
ok now i opened it in a new project file and still it is at that offset position without any pdc
and regarding sound
if i use it for a 1 sec clip or near the buildup of my song
then the timing issue is clear to be heard
other wise for long rewinding effect its not that huge* issue
and regarding sound
if i use it for a 1 sec clip or near the buildup of my song
then the timing issue is clear to be heard
other wise for long rewinding effect its not that huge* issue
REAPER, Phase Plant , Unfiltered Audio TRIAD and LION, NI classic collection,......... ETC
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
I'm not exactly sure if that was a yes or no 
, anyways if you think there is some kind of problem, please contact me via info@meldaproduction.com and send me some small project to try.
, anyways if you think there is some kind of problem, please contact me via info@meldaproduction.com and send me some small project to try.-
- KVRian
- Topic Starter
- 707 posts since 29 Dec, 2016 from India
in short yes ...
and that problem occurs even if i open a new project file in reaper with a single track loaded with only MRhythmizer in it.
thats a fixed problem that i can find in it or is the only possible bug in it
and that problem occurs even if i open a new project file in reaper with a single track loaded with only MRhythmizer in it.
thats a fixed problem that i can find in it or is the only possible bug in it
REAPER, Phase Plant , Unfiltered Audio TRIAD and LION, NI classic collection,......... ETC