Hi,
I'm using Gigperformer. This is a host for live-performing. I want to use MDrummer, but when I activate 'Play' in Gigperformer *and* I start a MDrummer-loop by using a midi note e.g. c-1, MDrummer starts skipping notes. Not all but some. They also do not appear in the midi output of MDrummer, so its not an audio issue. This goes for Gigperformer version 3.8 and 4 as well. I'm using MDrummer 15.00 now, but 14.x had the same problem.
I could use Gigperformer without pressing "play", but then the tempo does not sync with the host anymore. Running MDrummer in a separate host opens up a whole can of worms with respect to syncing.
I've played already with the additional settings (perfect sync, sequencer mode) but that made no difference.
Does anyone have the same experience? Workarounds? Keep in mind that I'm using it for live-performance. Had it been in a recording-setting, I would have had multiple work-arounds, the main being not using Gigperformer. E.g. Reaper works perfect, but then, Reaper is not very suitable for live-performance (although doable)
Thanks.
MDrummer skipping notes
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Hi, that sounds like Gigperformer doesn't produce correct timing info. Please report it to them. I'll check when possible, but we had crazy issues with them in the past, so I'm pretty sure this is on their side again.
-
- KVRer
- 4 posts since 3 Oct, 2019
AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
Hi @frank1119,may I suggest you to visit the Gig Performer community forum and expose your issue:
https://community.gigperformer.com/ (https://community.gigperformer.com/)
You will find a lot of Gig Performer users as well as MDrummer users (I am one of them). In the GP community we have many serious musicians and software engineers, but we are not as good as MeldaProduction to know a priori and without analysis where the problem comes from.
David-san
-
- KVRist
- 59 posts since 24 Mar, 2014
Out of curiosity (I don't generally use drum sequencers myself), I put together a quick test using Superior Drummer and as you can see from the video below that I just uploaded, it behaves perfectly fine, syncing with the Gig Performer playhead, responding to BPM changes and so forth. So it would at least seem that Gig Performer is producing the correct timing information.
I also queried users on our forums and it seems we have numerous customers using various different drum sequencers without any issues. I do not know offhand whether any of them are specifically using MDrummer.
Of course, Melda can reasonably make the same argument pointing out that MDrummer works fine with some other plugin hosts.
Combining the two, i.e. GP works fine with other drum sequencers and MDrummer works fine with other plugin hosts, that suggests that there is something funky that either Gig Performer is doing or MDrummer is doing that is causing the problem.
That said, we prefer not to blindly point fingers at other companies. We recognize that Gig Performer, like any piece of software can have bugs. Assuming this problem can be reproduced by others, we would be quite happy to work with Melda to figure out exactly what's going wrong so that the issue can be resolved, either by a fix in GP, a fix in MDrummer, or possibly both.
Dr. David Jameson
Co-founder, Deskew Technologies, LLC
https://gigperformer.com
I also queried users on our forums and it seems we have numerous customers using various different drum sequencers without any issues. I do not know offhand whether any of them are specifically using MDrummer.
Of course, Melda can reasonably make the same argument pointing out that MDrummer works fine with some other plugin hosts.
Combining the two, i.e. GP works fine with other drum sequencers and MDrummer works fine with other plugin hosts, that suggests that there is something funky that either Gig Performer is doing or MDrummer is doing that is causing the problem.
That said, we prefer not to blindly point fingers at other companies. We recognize that Gig Performer, like any piece of software can have bugs. Assuming this problem can be reproduced by others, we would be quite happy to work with Melda to figure out exactly what's going wrong so that the issue can be resolved, either by a fix in GP, a fix in MDrummer, or possibly both.
Dr. David Jameson
Co-founder, Deskew Technologies, LLC
https://gigperformer.com
-
- KVRist
- 377 posts since 19 Jul, 2013 from Chile
As most all know by now Mr Melda works fast, deep and thorough. Having done that for long entitles him to cite concepts and proven and tried conclusions along the way. This community allows for that and complements it in several ways, either by providing ideas, FRs, usage cases, strange applications, conflicting outcomes, further testing and what not? Including times where more attention is called into specific aspects, which appears to be the case here.
It is inspiring to see you all taking part in this.
It is inspiring to see you all taking part in this.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
It looks like they have timing info buggy (again actually). I let them know, we'll deal with that somehow.
-
- KVRist
- 59 posts since 24 Mar, 2014
@frank1119
Could you please report your issue on our community forums (https://community.gigperformer.com)? Several of our users have tried to reproduce your problem but it seems to be working fine. We need to have a reproducible example to be able to start the process of tracking this issue down?
Please include the version of MDrummer you are using, the version of Gig Performer you are using and an example gig file would be helpful as well.
Could you please report your issue on our community forums (https://community.gigperformer.com)? Several of our users have tried to reproduce your problem but it seems to be working fine. We need to have a reproducible example to be able to start the process of tracking this issue down?
Please include the version of MDrummer you are using, the version of Gig Performer you are using and an example gig file would be helpful as well.
-
- KVRer
- Topic Starter
- 5 posts since 2 Jan, 2010
Sorry folks: you are busy trying and I’m not responding. I think my mailsettings must wrong, cause I did not receive mails about your responses.
But the problem still remains.
Using MDrummer 15.00 now, but the former 14.x had the same problem. Gigperformer latest 4.0.54 if I remember well.
@deskew: problem is not that MDrummer does not ‘obey’ the bpm setting, but that it starts dropping notes. Key here is to start the loop using midi, Gigperformer in play mode. And it may take a while…
I was (falsely as now appears) that there was no reaction on my topic, but I’m very glad and thankful for the effort.
Again: sorry for not responding. I will check this forum on a more regular basis and try to get the notifications right.
Tomorrow I will send a Gig, but that will only contain MDrummer, an audio out and a midi in, so that will not be too exciting, I fear
Thanks,
Frank
But the problem still remains.
Using MDrummer 15.00 now, but the former 14.x had the same problem. Gigperformer latest 4.0.54 if I remember well.
@deskew: problem is not that MDrummer does not ‘obey’ the bpm setting, but that it starts dropping notes. Key here is to start the loop using midi, Gigperformer in play mode. And it may take a while…
I was (falsely as now appears) that there was no reaction on my topic, but I’m very glad and thankful for the effort.
Again: sorry for not responding. I will check this forum on a more regular basis and try to get the notifications right.
Tomorrow I will send a Gig, but that will only contain MDrummer, an audio out and a midi in, so that will not be too exciting, I fear
Thanks,
Frank
.-
- KVRist
- 59 posts since 24 Mar, 2014
Well, it seems that Vojtech was correct….we found a very subtle problem with the way timing was being handled and the problem has been fixed. I cannot however say when a version with this fix will be released as the next scheduled update is this coming Thursday (October 7th) so it will be in the release after that, whenever that will be!
Thanks for everyone’s patience.
Thanks for everyone’s patience.
-
- KVRer
- Topic Starter
- 5 posts since 2 Jan, 2010
Well, it is now almost 8 months later and today Gigperformer 4.5.8 was released. I installed it and tried MDrummer and... (suspension builds...) Yes, the issue has been solved.
Thanks for everyone's efforts (and my own patience
)
Thanks for everyone's efforts (and my own patience
)-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Ugh... well, sometimes it takes time 