Open brandflake11 opened 3 years ago
Can you run ecasound
on its own?
Yes, I can run ecasound to play the file just fine using ecasound -i AUDIO_FILE_NAME.FLAC -o jack,system
. I followed instructions from here thinking that the error could be related. Could it be an issue with libsndfile?
Sure, could be.
I guess the command that's used by the SSR is something like this:
ecasound -i sndfile,AUDIO_FILE_NAME.FLAC -o jack,system
It actually uses jack_generic
, but I hope that's not relevant.
I just tried that and it works fine, playing the audio file. I'm going to see if compiling libsndfile from source and then recompiling ecasound and ssr will fix this issue.
You could also try
export ECASOUND=/path/to/ecasound
Just tried that, and that didn't work also. It did remove the ecasound environment variable warnings from the output though.
I also tried compiling my own version of libsndfile, then ecasound, and then ssr to see if libsndfile was the problem. This also didn't result in any difference.
Hmmmm.
Do you have multiple versions of the libecasoundc
library installed?
Maybe the ecasound
program uses a different one than what's used when compiling the SSR?
TBH, I have no idea what's going wrong here.
If you don't get this to work, you can of course use any JACK-aware audio player to send signals to the SSR.
You can use something like the data/scenes/live_input.asd
to use arbitrary JACK inputs in an SSR scene.
I you are adventurous, you can also try the new dynamic scene format I'm currently working on: #155. This doesn't use Ecasound, but there might be a whole range of different problems ...
It doesn't look like I have multiple versions of libecasound:
sudo find / -iname "*libecasoundc*"
./usr/bin/libecasoundc-config
./usr/include/libecasoundc
./usr/lib/libecasoundc.a
I'll probably just use your live_input.asd, as jack makes piping things in easy. Thanks for pointing me to the new dynamic scene format as well, that looks really interesting.
Maybe others with this issue can figure out why this happened later, or hopefully it is just a problem with my setup of ssr.
Hello again,
I am trying to load the live_input.asd file you put on your previous message, but I don't see any inputs from ssr in jack. I am loading it with this command:
ssr-binaural -s ~/Downloads/live_input.asd
Am I doing something wrong with it, or is the command not right?
The -s
flag is for loading the reproduction "setup". Specify a scene in the same way you specified the audio file to be loaded: Don't use a flag, only specify the file. live_input.asd
is a scene description, not a reproduction setup.
Admittedly, the fact that the specification of reproduction setups and of sound scenes uses the same format can be confusing....
Thank you very much, I got my first sound from ssr! Sorry if this isn't about the issue anymore, but what is the difference between an ssr setup "-s" and config "-c" file?
Congrats!
-s
specifies the geometry of the loudspeaker setup. You can also influence, which output channel is routed to which loudspeaker to some extent.
-c
allows you to specify the default values for everything that you would otherwise specify via command line arguments so that you can avoid having to put the same command line arguments every time you start SSR. Examples are what HRTF set to load, what reproduction setup ;), and the like.
Here is an example of a config file that you would load with the -c
flag.
This makes much more sense. When do you need to use the -s option rather than just loading the .asd file directly?
That's for specifying the geometry of the loudspeaker setup if you don't want to use the default one.
One of the main design paradigms of SSR is the separation between the rendering setup and the sound scene. We wanted it to be possible to render the same sound scene with different rendering algorithms and setups (headphones, loudspeakers, etc.). What the description of the loudspeaker setup and the description of the sound scene have in common is that they contain a lot descriptions of geometry (position, orientation, etc.). That's why we're using the same file format for both.
In other words, the sound scene (or in the simplest case a plain audio file) is the input, which you load without a flag, and the loudspeakers are the output, which you load with the -s
flag.
Thank you, this also makes more sense. I guess now I just need to experiment. I still can't figure out why I can't load an audio file into ssr, but for now I'll just do live inputs!
Great, we're hoping you're going to enjoy it!
Let us know if you ever find the solution to this audio file problem.
Hello ssr team, I have been trying to get sound out of ssr on Artix Linux, and it seems no matter what audio file I try to load into it, it doesn't load. Here is the output and command I am using to try to get audio out of ssr:
ssr-binaural ~/Music/Test_Epidemia_Opus.flac -s /usr/share/ssr/reproduction_setups/2.0.asd --hrirs=/usr/share/ssr/impulse_responses/hrirs/hrirs_fabian.wav
I've tried a couple of different sound files, making sure that I'm matching sample rates, and the wave file is the right format, since the manual talks about certain issues with ecasound and the wave files. Each one was the right format (WAVE_FORMAT_PCM). I tried doing the sox conversion as well and that didn't help with this error.
I have also built and installed ecasound and ssr from source from the official Arch Linux PKGBUILDs to see if compiling on my machine would make a difference. This didn't help either.
What could I be doing wrong?
Thank you very much for your help with this!