Stereo Tool

Puh. Linux audio is complicated. I'll do some other things first.

(Supporting Jack seems easy, it looks a lot like ASIO, but I cannot even run jackd here - it crashes with 'core dumped' )

Ok so I've used Baron as a preset, only input (pipeline) and FM output (Trace 8, set to idle at 192kHz) enabled with 0.5 sec buffer. No LQ or Normal output enabled. Machine is an i3, Win 7 32 bit.

Here is info from some quick tests:

7.23 - Input ok, ASIO output ok, non ASIO output ok

(Note: setting ASIO override channel 1 and channel 2 to the same output causes an oddity - sounds like it's running half speed or something...)

7.24 Beta 010 - Input ok, ASIO output ok, non ASIO output - switching within ST (turning off ASIO override) causes red buffer block. (no message in sound cards section) Leaving it set to non ASIO and restarting the application seems to sort this out. (Buffer fills blue)

7.24 Beta 011 - Input work but not 100% ok (seems to be emptying?), ASIO output buffer won't stay full - not passing audio (CPU load only around 30% though?), non ASIO output - switching within ST (turning off ASIO override) causes red buffer block. (message in sound cards section says "Cannot open output (2 channels, 16 bits/sample, sample rate 192000:1)" ) but leaving it set this way and restarting the application kind of sorts it out. (Buffer fills blue, passes audio but empties quickly and causes audio breakup)

7.24 Beta 012 - Same behaviour as Beta 011 (edit: restarting with input and ouput in non ASIO seems to be ok but buffer emptying easily / quickly?)

7.23 Beta 013 - Same behaviour as Beta 011 (edit: restarting with input and ouput in non ASIO seems to be ok?)

I think I saw a flash of a message that said "Creating ASIO buffer failed" before the ASIO (green buffer) starts the filling and emptying...

Testing with Beta 013 - I have just noticed that if I change the input from a pipeline to ASIO input on the Trace 8 then both the ASIO input and ASIO output buffers seem fine. If I change the input to the Trace 8 input without ASIO then I get the same red "Cannot open input" error as with the ouput in non ASIO mode.

Nothing special...
- Full factory reset
- Input VAC, output Juli@
- Bypass ON
- restart application
-> No sound

- Bypass OFF -> there is sound, bypass ON again -> still sound present

Aah! I didn't restart it Confirmed, same behavior here - will check.

Does the Marian trace alpha have drivers for linux? Looks like ST will be available as windows or linux os.Haven't had much experience with the linux os.

http://www.marian.de/en/downloads

Linux, as a whole, is more complicated than it needs to be. I still remember a Linux Zealot who proudly proclaimed that any solution that had Microsoft in it was not a solution at all, and that people who use Microsoft products like things "easy". I just don't understand why he thinks that the whole world should prefer things to be difficult. Time is valuable, so things need to just work. Busting out some code in C, Python, or Ruby to make a device driver is NOT something that the general public "needs" to be doing, and probably greater than 99% don't even "want" to do it.

Hm..... So on your system, 7.23 is working perfectly? Never no input or no output?
I also read that re-starting usually fixes any problems in 7.24-011/12/13, right?

I've made a few changes in the next version (014) that might help here - if it's still not sufficient, I've also made the 'Restart audio' button work again (it didn't work in the previous versions). I hope that the problems are solved; if they are not but the 'restart' button does work, I can easily fix it (by forcing a restart whenever something is changed).

On my test system, ASIO behavior in 014 is identical to v7.23, and the CPU load is also identical.

BETA724-014:
Stand alone: http://www.stereotool.com/download/ster ... 24-014.exe
Winamp: http://www.stereotool.com/download/dsp_ ... 24-014.exe

I hope this version behaves the same as v7.23 (it does on the systems that I tested); if not, please check if the 'Restart audio' button fixes the issue. If it does, I'll add a forced restart whenever a setting is changed (but I prefer not to since it causes ALL the inputs and outputs to be restarted instead of just the one that you're touching).