Topic: MIDI input recording in 2.08
- This topic has 24 replies, 3 voices, and was last updated 17 years, 2 months ago by
Zynewave.
-
January 14, 2009 at 21:48 #13724
H-manParticipant@H-man wrote:
I have just re-confirmed the above and am now testing with the TimeStamps from driver setting disabled.
Okay …seems to have eliminated the problem. Recording resumes as expected.
Any ideas on why this occurs Frits?
PS: michi_mak, did you get similar results?
January 14, 2009 at 21:55 #13725
michi_makParticipantSorry Frits, it makes no difference … with or without time stamp from driver
sadly enough my quest for a new daw is not overJanuary 15, 2009 at 03:38 #13727
ZynewaveKeymaster@H-man wrote:
@H-man wrote:
I have just re-confirmed the above and am now testing with the TimeStamps from driver setting disabled.
Okay …seems to have eliminated the problem. Recording resumes as expected.
Any ideas on why this occurs Frits?
Faulty driver, I would guess. This problem has popped up many times over the years. Apparently there are not many sequencers that utilize the driver timestamping so that could explain why there are so many drivers where this is not implemented/tested fully.
January 15, 2009 at 03:41 #13728
H-manParticipant@Zynewave wrote:
@H-man wrote:
@H-man wrote:
I have just re-confirmed the above and am now testing with the TimeStamps from driver setting disabled.
Okay …seems to have eliminated the problem. Recording resumes as expected.
Any ideas on why this occurs Frits?
Faulty driver, I would guess. This problem has popped up many times over the years. Apparently there are not many sequencers that utilize the driver timestamping so that could explain why there are so many drivers where this is not implemented/tested fully.
Okay, cool. What does one miss out on by not having it?
January 15, 2009 at 16:18 #13729
ZynewaveKeymaster@H-man wrote:
Okay, cool. What does one miss out on by not having it?
A small amount of precision. But I don’t think that it is anything you would notice with todays faster PCs. Years ago you could risk that Windows would occasionally hickup a few millisecs, so the host application would then receive the MIDI messages a little later than they were received by the driver. If you use the timestamps from the driver then these small delay variations would not show up in the recording.
January 15, 2009 at 21:19 #13747
H-manParticipantOh-kay then, thx for the info.
I’m guessing that with a multi-core PC and my keyboard skills there really isn’t any need to have this checked :).
January 16, 2009 at 21:24 #13763
michi_makParticipantFrits, i’m still thinking what could cause this troubles :
i tried with several synths and got same results – sometimes first note is sounding but not recorded –> can’t be the vsti i guesswhat i found today is that there is a difference in the number of clips recorded – sometimes it is just one and sometimes there ar two!?!
will try with different ASIO settings – will report back!!
January 16, 2009 at 21:43 #13765
ZynewaveKeymaster@michi_mak wrote:
Frits, i’m still thinking what could cause this troubles :
i tried with several synths and got same results – sometimes first note is sounding but not recorded –> can’t be the vsti i guesswhat i found today is that there is a difference in the number of clips recorded – sometimes it is just one and sometimes there ar two!?!
I may be able to figure out the problem if you can email me a project file saved after you recorded the double clips.
January 16, 2009 at 22:31 #13767
michi_makParticipantdid some more testing :
this problem does not depend on punch in/out
i have set my asio buffer to the lowest value possible ( 64 frames )
now it is getting “better”
i found that i have to play some note before the loop start point and then it records ok !!
will send a project at info@zynewave.com ?January 16, 2009 at 22:33 #13768
ZynewaveKeymaster
- You must be logged in to reply to this topic.
