Brand new Liberation user here, as someone who used to do node-based visual VFX with Nuke and Fusion in the film industry, I feel right at home so far! Love what you’re doing.
The only real issue I’ve ran into Is that enabling sound input (selecting my sound interface in the global settings), the output from my sound interface screeches to a halt, and outputs a pretty nasty buffer overflow type noise.
Upon further inspection this looks to be because it’s forcing the sample rate to 48khz, while my interface is set globally to 44.1khz. The interface is a Motu Ultralite AVB, who have what are considered pretty mature/stable ASIO drivers. I saw in another thread you spoke of having quite an annoying time so far dealing with sound card driver interfacing on windows which is understandable.
Is it possible to change it from ASIO to just regular windows input? Or at the very least, manually select a sample rate? Thanks! Happy to perform any required testing. This is all I have from the logs:
This is clearly an area I need to work on (especially in Windows) but I did change it in version 1.0.0 to use the “preferred” sample rate. But obviously no idea how this is handled in some windows drivers.
Woops! Thought I included that - the latest, 1.0.0 - indeed it seems the “suggested” sample rate is not very reliable on windows, I have my asio settings, soundcard control panel settings, and windows sound settings mixer/control panel settings all set to matching 44.1khz, so not sure where it’s getting 48khz from
OK I’ve done a bit of research, it seems many ASIO drivers always report a hard-coded “driver default” sample rate when queried, regardless of what’s set in their control panel or Windows sound settings. In your case, the MOTU driver is probably telling Liberation it’s 48 kHz even though you’ve set it to 44.1 kHz.
I will add a sample rate picker so you can override this in a future release, but for now the easiest workaround is to set your interface to 48 kHz everywhere (ASIO panel, Windows sound settings, etc.) so Liberation and your device agree and hopefully you won’t get so much glitching.
Awesome, thanks! I was going to say, you could just avoid windows’ whole sample rate detection/reporting in the first place with a simple dropdown of common sample rates - then when something is mismatched, you can blame the user
Hey @seb ! I hate to look a gift horse in the mouth (as Liberation is 99% amazing), but is there any chance for a fix to this soon? Even if it’s a simple undocumented config file parameter, an exe launch parameter, a one-off build with 44.1khz forced, anything to force liberation to 44.1khz? Where I am often taking my laptop and gear is a small event space that I feed audio to over AVB networking from my motu - the venue rig is all 44.1khz - so if I change my Motu’s samplerate to 48khz to get Liberation working, I can no longer provide an AVB feed to the house desk/system as the clocks / samplerate must all match exactly - it’s driving me a bit batty
This has now been implemented and will be available in the next build. This should be out sometime within the next few weeks but it will likely be Mac first, then PC.
