You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My playback device's default is 192kHz, but testing suggests MilkDrop 3 beat detection maxes at 96kHz sample rate with my hardware. Is it possible to fix this for HD audio? Some modern (and expensive) DACs go as far as 1024kHz or so; 756kHz is getting fairly common in the HD Audio sphere..
Obviously we don't actually need the visuals responding so fast, but it would be good if Milkdrop functioned with such devices. I know nothing of coding; not sure if you'd need it to process the audio to down-sample on the fly (I'm guessing that's a lot more resource intensive), or if you can get it to recognise the output device's sample rate and adjust the rate at which MD takes a sample as a result..
The text was updated successfully, but these errors were encountered:
Hi, I managed to get my hands on a 96kHz DAC, so the next version will be fully compatible with 96kHz (at the moment it's not, if you click on file > new, it does not detect the full length). It's on my to-do list to get it to support higher sample rate but this will take a bit of time :)
My playback device's default is 192kHz, but testing suggests MilkDrop 3 beat detection maxes at 96kHz sample rate with my hardware. Is it possible to fix this for HD audio? Some modern (and expensive) DACs go as far as 1024kHz or so; 756kHz is getting fairly common in the HD Audio sphere..
Obviously we don't actually need the visuals responding so fast, but it would be good if Milkdrop functioned with such devices. I know nothing of coding; not sure if you'd need it to process the audio to down-sample on the fly (I'm guessing that's a lot more resource intensive), or if you can get it to recognise the output device's sample rate and adjust the rate at which MD takes a sample as a result..
The text was updated successfully, but these errors were encountered: