Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_dsp_ambio (Read 10589 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_dsp_ambio

I recently learned about Ambiophonics and I wanted to try it but the available software was unsatisfactory. As is often the case, I ended up writing my own.

foo_dsp_ambio.zip

Features:
•   Native foobar2000 plugin. No VST wrapper required.
•   Works with any sample rate and file format supported by foobar2000.
•   Calculates stereo crosstalk delay time based on speaker placement dimensions.
•   Setup parameters can be overridden by track metadata (tags).
•   4 channels can be arranged as front/rear, front/front, or rear/rear. The latter two are for situations where the high and low frequency drivers have different left/right separations and thus different crosstalk delays.

foo_dsp_ambio

Reply #1 –

It works so fine.

The instructions manual is very useful.

When applying the real measures of depth and width, the result sounded like the exact real thing for my music station.

I tried almost every other ambio component I found around, and this is both the one wich gives more space to personal configurations, and the one wich leaves less space to loss the point of ambiophinics through error and trial experiments.

Thank you so much,

Rozzo

foo_dsp_ambio

Reply #2 –
Thanks so much for your work!... this plugin is wonderful!
Everybody, give it a try... I bet you'll never be back to traditional stereo :-)

foo_dsp_ambio

Reply #3 –
I noticed a constant memory growth of foobar with this plugin active.
I did not investigate further but I suspect a memory leak in this plugin (v1.0).
In theory, there is no difference between theory and practice. In practice there is.

foo_dsp_ambio

Reply #4 –
this is really interesting and providing excellent results so far, thankyou for the plugin, preset saving in the future maybe ?

foo_dsp_ambio

Reply #5 –
I’m withdrawing support for foo_dsp_ambio. I’ve been advised that it has a significant memory leak and I don’t have the time to deal with it.

I wrote foo_dsp_ambio to evaluate Ambiophonics because I found the available software unsatisfactory. In the end, Ambiophonics did not enhance my listening experience: I don’t use it and I have no further interest in it. I posted foo_dsp_ambio assuming it might be useful to others exploring Ambiophonics. I didn’t realize the plugin has a defect that makes it unsuitable for long-term use. Sorry.

foo_dsp_ambio

Reply #6 –
ah that's a shame, thank you for sharing your work anyway

foo_dsp_ambio

Reply #7 –
Quote from: k8o on
preset saving in the future maybe ?

You can use foobar2000's "DSP chain presets" to accomplish that, if you like.
In theory, there is no difference between theory and practice. In practice there is.

foo_dsp_ambio

Reply #8 –
any src so other developers could fix the leak?

foo_dsp_ambio

Reply #9 –
Quote from: mudlord on
any src so other developers could fix the leak?

There are few opportunities for memory leaks in the code. That’s why I was reluctant to waste time chasing an undocumented claim of a leak. With the holiday, I found time to examine the claim and was surprised to observe a leak; except there is nothing I can do about it.

foo_dsp_ambio uses three memory objects: the history buffer, declared in the foo_dsp_ambio class, and two strings, declared in the tag parsing function. It is my understanding that memory for the history buffer object is allocated when the class is instantiated and freed when the class is deleted. Memory for the strings is allocated when the function is entered and freed when the function returns. The only other possibility for a leak is a side effect of my misusing an sdk function.

Line by line, I removed code from the program looking for the source of the problem until there was nothing left but the minimum functionality of any dsp plugin: The leak remained, unchanged. Finally, I created a 30-track playlist and repeated playing it using a clean installation of foobar v1.1.8, alone, with foo_dsp_ambio, and with foo_dsp_sample, a foobar supplied dsp plugin that does nothing special. All instances showed similar memory usage.

As far as I’m concerned, foo_dsp_ambio does not leak. For anyone who tries it and doesn’t like the way it works…Don’t use it. If you think there is an urgent need for another Ambiophonic plugin, write it yourself.

foo_dsp_ambio

Reply #10 –
Thanks for looking into it. I'm sorry that I suspected the ambio plugin and it turned out I was wrong. It was just that that I noticed foobar using an incredible 800+ MB of memory, on the same day I had been testing foo_dsp_ambio for a long time.
I have removed the component since, but have experienced another such memory used again today. Next time I put some effort with processexplorer to help find the cause.

BTW this was with foobar 1.1.10 (final)
In theory, there is no difference between theory and practice. In practice there is.

foo_dsp_ambio

Reply #11 –
I love this plugin.  No memory leak worries here.  I had to play with its order in the DSP chain, but looks like right after SoX works great.

foo_dsp_ambio

Reply #12 –
Because the Ambiophonic delay is an integral number of sample times, the best resolution comes with the highest sample rate. It is also essential that nothing downstream alters the channel balance because that will spoil the Ambiophonic effect.

foo_dsp_ambio

Reply #13 –
Quote from: j_b on
Because the Ambiophonic delay is an integral number of sample times, the best resolution comes with the highest sample rate. It is also essential that nothing downstream alters the channel balance because that will spoil the Ambiophonic effect.



Good to know. I tried Electromusic AmbiofonicDsp playing music at 192000 Hz and was unable to move the delay knob ahead from 60-70 ms. I'm hearing now with your plugin at 192000 hz and 115 ms delay. Good.

Ys,
Rozzo

foo_dsp_ambio

Reply #14 –
HI,
I write in this old thread because I'd be very interested in the Abiophonics foobar2000 plugin, but the link is broken. Can anyone post a valid link or share the file, please?