welcome to the machine
I wrote about this previously, in cyghfer's mysterious gained seconds topic. See here. Basically, amarec is giving me recordings that are some seconds faster than real time. I'll refrain from repeating all of the details here.
My original solution was to just switch setups and record/stream using vdub. Well, I tried that a few days ago, and after 50 minutes of streaming the sound suddenly decided to delay by a second. Then half an hour after restarting the recording, the same thing happened. That doesn't show up in the file so I could probably still /record/ using that, but I couldn't stream at the same time, so whatever. May as well actually solve the particular problem this topic is focused on, since I suspect others have been hit by it too, unbeknownst to them.
so. I have an Ecco run. The recording comes out to be 18:14.9. The problem is that the final time should be closer to 18:17 or 18:18. This is verified by Wsplit and my xsplit local recording, which both match up. I can't record runs anymore until I get a setup that won't make my final time a lie, soooo yeah.
I recorded using amarectv v2.10b-en. Switching to a later version didn't help, and the program seemed more unstable besides. I screencapped pics of the relevant settings and attached them. I've also attached the MQ encode (from anri) and the anri logs. The source is 11 gigs big; I'm not opposed to torrenting that in but I'd like confirmation it'd be useful to someone first.
links:
ecco mq encode
xsplit local recording



My original solution was to just switch setups and record/stream using vdub. Well, I tried that a few days ago, and after 50 minutes of streaming the sound suddenly decided to delay by a second. Then half an hour after restarting the recording, the same thing happened. That doesn't show up in the file so I could probably still /record/ using that, but I couldn't stream at the same time, so whatever. May as well actually solve the particular problem this topic is focused on, since I suspect others have been hit by it too, unbeknownst to them.
so. I have an Ecco run. The recording comes out to be 18:14.9. The problem is that the final time should be closer to 18:17 or 18:18. This is verified by Wsplit and my xsplit local recording, which both match up. I can't record runs anymore until I get a setup that won't make my final time a lie, soooo yeah.
I recorded using amarectv v2.10b-en. Switching to a later version didn't help, and the program seemed more unstable besides. I screencapped pics of the relevant settings and attached them. I've also attached the MQ encode (from anri) and the anri logs. The source is 11 gigs big; I'm not opposed to torrenting that in but I'd like confirmation it'd be useful to someone first.
links:
ecco mq encode
xsplit local recording
Thread title: