windows

[FIVIL]

Hi, can we create windows .exe file, or is there any code made for windows??

[jmvalin]

The code is C90 and should compile fine on Windows

[techsin]

is there windows version?

[jobeninc]

Has anyone had success with running this on Windows 7 or 10 x64?

It works great on Linux, Mac and MSYS2 in Windows when the compiled dll has a dependency on MSYS-2.0.dll.

However, I am unable to get it to run on Windows with no dependencies. On two separate Windows 7 64bit computers, it compiles in Visual Studio 2015 and MSYS2 MingW64 environments and then the example program runs but cuts out before processing the entire file. Upon further inspection with custom code, the vad probability after each call to rnnoise_process_frame is always 0. The same exact code works on Mac, Linux, and MSYS2 when it is dependent on MSYS-2.0.dll.

Please comment on why this might only work on linux variants or confirm/negate/augment my findings.

I noticed this project popped up a couple months ago but it does not appear to be complete. https://github.com/jagger2048/rnnoise-windows , I suspect the project owner was unsuccessful and abandoned the project.

Thanks,

[jagger2048]

Has anyone had success with running this on Windows 7 or 10 x64?

It works great on Linux, Mac and MSYS2 in Windows when the compiled dll has a dependency on MSYS-2.0.dll.

However, I am unable to get it to run on Windows with no dependencies. On two separate Windows 7 64bit computers, it compiles in Visual Studio 2015 and MSYS2 MingW64 environments and then the example program runs but cuts out before processing the entire file. Upon further inspection with custom code, the vad probability after each call to rnnoise_process_frame is always 0. The same exact code works on Mac, Linux, and MSYS2 when it is dependent on MSYS-2.0.dll.

Please comment on why this might only work on linux variants or confirm/negate/augment my findings.

I noticed this project popped up a couple months ago but it does not appear to be complete. https://github.com/jagger2048/rnnoise-windows , I suspect the project owner was unsuccessful and abandoned the project.

Thanks,

Hi, I recently update the vs2017 project so it can run on win10 x64 platform successfully.

Meanwhile, the rnnoise_process_frame() return 0 maybe is that your input data is not correct. The parameters of the function are S16 format PCM and treat them as float data, not truly F32 format PCM data.

[contribu]

windows file io has the binary mode and text mode. binary mode is not specified in rnnoise_demo.c. (i have not tested if specifying binary mode fix the bug)

[NileZhou]

I compile on Windows and Linux. However run with same PCM files, get diffierent F32 files

[NileZhou]

I compile on Windows and Linux. However run with same PCM files, get diffierent F32 files

two F32 have the same size, data Not

[jobeninc]

Meanwhile, the rnnoise_process_frame() return 0 maybe is that your input data is not correct. The parameters of the function are S16 format PCM and treat them as float data, not truly F32 format PCM data.

Thanks. This is exactly what I was doing wrong. If anyone else runs into this issue. The floats submitted to rnnoise_process_frame() should be values between -32,768 and 32,767 rather than -1 and 1.

[raikarsagar]

Meanwhile, the rnnoise_process_frame() return 0 maybe is that your input data is not correct. The parameters of the function are S16 format PCM and treat them as float data, not truly F32 format PCM data.

Thanks. This is exactly what I was doing wrong. If anyone else runs into this issue. The floats submitted to rnnoise_process_frame() should be values between -32,768 and 32,767 rather than -1 and 1.

I am trying to run this on real time microphone stream in a plugin. Do we have to convert the samples(float32 by default) to short int and then load it to float type array? Direct conversions are giving distorted output. Any leads will be great in this regard. Thanks

[jagger2048]

Meanwhile, the rnnoise_process_frame() return 0 maybe is that your input data is not correct. The parameters of the function are S16 format PCM and treat them as float data, not truly F32 format PCM data.

Thanks. This is exactly what I was doing wrong. If anyone else runs into this issue. The floats submitted to rnnoise_process_frame() should be values between -32,768 and 32,767 rather than -1 and 1.

I am trying to run this on real-time microphone stream in a plugin. Do we have to convert the samples(float32 by default) to short int and then load it to float type array? Direct conversions are giving distorted output. Any leads will be great in this regard. Thanks

No, you can simply convert the f32 PCM sample to target RNNoise data format，i.e. data_to_proc = f32 * 32768.0f, not the short int. For more details, you can reference the following link B&R Jagger

[raikarsagar]

Meanwhile, the rnnoise_process_frame() return 0 maybe is that your input data is not correct. The parameters of the function are S16 format PCM and treat them as float data, not truly F32 format PCM data.

Thanks. This is exactly what I was doing wrong. If anyone else runs into this issue. The floats submitted to rnnoise_process_frame() should be values between -32,768 and 32,767 rather than -1 and 1.

I am trying to run this on real-time microphone stream in a plugin. Do we have to convert the samples(float32 by default) to short int and then load it to float type array? Direct conversions are giving distorted output. Any leads will be great in this regard. Thanks

No, you can simply convert the f32 PCM sample to target RNNoise data format，i.e. data_to_proc = f32 * 32768.0f, not the short int. For more details, you can reference the following link B&R Jagger

Thanks for the suggestion. This seems to be not resolving issue. The input audio samples are converted to [-32768,32767] from [-1,1] but the output samples are having too small in magnitude. (FYI: I am using JUCE framework for this plugin)

[jagger2048]

Meanwhile, the rnnoise_process_frame() return 0 maybe is that your input data is not correct. The parameters of the function are S16 format PCM and treat them as float data, not truly F32 format PCM data.

Thanks. This is exactly what I was doing wrong. If anyone else runs into this issue. The floats submitted to rnnoise_process_frame() should be values between -32,768 and 32,767 rather than -1 and 1.

I am trying to run this on real-time microphone stream in a plugin. Do we have to convert the samples(float32 by default) to short int and then load it to float type array? Direct conversions are giving distorted output. Any leads will be great in this regard. Thanks

No, you can simply convert the f32 PCM sample to target RNNoise data format，i.e. data_to_proc = f32 * 32768.0f, not the short int. For more details, you can reference the following link B&R Jagger

Thanks for the suggestion. This seems to be not resolving issue. The input audio samples are converted to [-32768,32767] from [-1,1] but the output samples are having too small in magnitude. (FYI: I am using JUCE framework for this plugin)

the output samples are having too small in magnitude

In rnnoise, its output range [ -32768, 32767], you can just convert to [-1, 1], the PCM format. For the magnitude, maybe you need to add an AGC model after applying noise suppression.

[wegylexy]

windows file io has the binary mode and text mode. binary mode is not specified in rnnoise_demo.c. (i have not tested if specifying binary mode fix the bug)

Solved in #130