Recent problem I had: You have two .wav files. You're playing through an external sound card. 'A' always plays fine. 'B' plays sometimes, and sometimes not, randomly. If you play *both* at once, it makes no difference: you always hear 'A' and sometimes 'B' mixed in.
-
Show this thread
-
You're using 2 channels on the interface (files are stereo). It has a hardware level meter. The level meter always shows activity (in both L/R channels), even when playing 'B', regardless of whether it worked that time or not. When playing both files, mixing is done in software.
1 reply 0 retweets 0 likesShow this thread -
It's not a stereo cancellation issue: you can hear both channels and it doesn't sound like 'A' is suffering from cancellation. It's not a software channel routing issue: you've verified that both files mix into the same two main outputs, every time.
1 reply 0 retweets 1 likeShow this thread -
What is this sorcery? How can one file show up on the level meter consistently but only output sound half of the time, while the other file always works? Hint: 'B' was recorded earlier on the same interface. I already figured it out, but any guesses?
1 reply 0 retweets 4 likesShow this thread -
Replying to @marcan42
the same interface 'A' was recorded on, or the same interface they're being played on?
1 reply 0 retweets 0 likes -
-
Replying to @marcan42
is there an extremely evil resampler or DAC (or its conversion from PCM to delta-sigma) involved? or is there some sort of extremely evil in-band signaling?
1 reply 0 retweets 1 like -
my first thought was "maybe if on input something upsampled by inserting 0 every other sample, and on output something's downsampling by dropping every other sample, so it works half the time and is completely silent the other half"
1 reply 1 retweet 9 likes -
which should be too absurd to even contemplate but I dunno, I've seen some extremely bad audio hardware and software
1 reply 0 retweets 0 likes -
Replying to @11rcombs
That is *exactly* what happened. Well done! It was some kind of confusion in the interface (a power cycle fixed it) that caused it to drop every second sample and replace it with a 0. The aliasing wasn't entirely obvious due to the audio I was using.
2 replies 0 retweets 6 likes
I noticed when I turned on spectrogram view for 'B' and saw the mirror image spectrum... which wasn't *completely* implausible given 'B' was chiptune stuff recorded digitally, but bizarre... then I zoomed in to the PCM and saw every other sample was 0.
-
-
It wasn't strictly speaking up/downsampling since everything involved was nominally 48kHz (so I was getting aliased 24kHz audio), but same effect.
1 reply 0 retweets 1 like -
Replying to @marcan42
was I right that the recording had made the same error
1 reply 0 retweets 0 likes - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.