that's on the list somewhere, yes.

Hi,
I don't reallyw ant to submit an issue, as I've no idea if I'm doing something wrong or not here.

The below code works extremely slowly on my system. I hit the space bar, and the sound plays maybe 0.5-1.0 seconds afterwards.

Here's the code:
]

"""Minimal Synthizer test."""

from typing import Optional

import pyglet
from pyglet.window import Window, key
from synthizer import (Buffer, BufferGenerator, Context, DirectSource,
                       initialized)
from cytolk import tolk


class TestWindow(Window):
    """Override the key handler."""

    audio_context: Optional[Context] = None
    generator: Optional[BufferGenerator] = None
    source: Optional[DirectSource] = None

    def on_key_press(self, symbol: int, modifiers: int) -> None:
        """Intercept the space bar."""
        if symbol == key.SPACE:
            tolk.speak('Shoot.')
            if self.audio_context is None:
                self.audio_context = Context()
                self.generator = BufferGenerator(self.audio_context)
                self.source = DirectSource(self.audio_context)
                self.source.add_generator(self.generator)
            if self.generator is not None:
                if self.generator.buffer is None:
                    self.generator.buffer = Buffer.from_stream(
                        'file', 'shoot.wav'
                    )
                else:
                    self.generator.position = 0.0
        else:
            return super().on_key_press(symbol, modifiers)


if __name__ == '__main__':
    pyglet.options['shadow_window'] = False
    window: TestWindow = TestWindow(caption='Synthizer Test')
    with initialized():
        tolk.load()
        pyglet.app.run()

As far as I can tell it's equally slow playing a wav file or an MP3.

Here are the two files I'm testing with. I converted them from another wav file (not included) using Goldwave.
https://www.dropbox.com/t/FlKInOQWQAM9yMMe.

@305
Yup, 0.7.5 works like a charm. No lag at all... Not sure whether to be sorry or not. Damn Linux!

Ok, for anyone following along here, I'm rolling out a 0.7.7 which rolls back all the things in 0.7.6 until I can fix this performance problem.

@309
Most reverb implementations are bad at preserving panning.  You probably need to lower the gain on it so that the panning of the source dominates.  I have plans to look into improving this eventually and ideas on what to do for it, however.

Also look at raising the late reflections delay, which will additionally emphasize the source's panning some even without gain changes.

But honestly the entire point of reverb is to make panning less obvious because that's what reverb is by definition, at least in the context of 3d audio, so you may just be thinking about it wrong.  In particular, a very little bit of reverb goes a very long way.  Even gains of 0.1 aren't unreasonable for it--if you're hearing the reverb as a discrete thing where you're going "wow, it's a reverb" it's too loud, it should just be "huh, this sounds natural", if that makes sense.  Maybe Synthizer needs some better defaults, in order to make this clearer.

@308
Magic, thank you mate.

@310
I'm not sure as Synthizer's defaults are bad, although admittedly the default reverb sounds like you're in a metal box or something.

You still planning to ship presets? Or have some kind of market place? The second option could actually be a way of making back some cash, although I've 0 idea how it would work in practise. Maybe sell a yaml file that could be loaded into Synthizer or something.

I love reverb, but know absolutely nothing about tuning it, and honestly I've sort of given up on it, until some helpful person releases synthizer_reverbs, with synthizer_reverbs.Room, synthizer_reverbs.hall ETC.

@313
Could always sell support... You'd make a mint off me alone I reckon, with all the questions I've emailed you in the past haha.

What format would you want presets in? I'm thinking of making some kind of reverb editor I can use in my own projects. No idea what output format I'd use yet (code, yaml or whatever). If you've got any ideas, then I could move in that direction, as I'll probably just end up adding in whatever format you want in the future anyways.

@315
OK, thank you, that's great. I'll have me a play.

@317
When I've made my reverb editor, I'll post it so anyone can make presets then send them to @Camlorn.

Won't be starting work on it for a bit though. A week maybe.

The reverb doesn't currently account for distance at all.  If you're simulating a space that is so large that this matters, it probably doesn't deserve reverb in the first place.  I'm going to change this eventually, but it's actually not entirely clear how to go about doing that and I'm not going to touch it until I'm sure what the right answer is.  For the moment, just change the gains on the connections to the effect yourself.

Syz_shutdown destroys handles, or should.  There are a number of bugs related to that which will be fixed in the next release, so it may or may not currently work.  It's probably best to destroy them yourself, at least for now.

so, friends, i got an idea on how to implement play pause
so, when ever we pause, we take the position of the generator and remove the generator. and, when ever we play, we add the generator and seek to the last position.
i don't know if any one got the idea, and, i have not read to all the posts, so.
i just wan't to post my idea here. nothing more.

@322
Yes, you're right, that's how you'd do it. Maybe seek backwards a tiny bit to allow for your computer catching up, since I think propery reads happen by way of a different thread, which is why @Camlorn can't speed them up any... I think that's right anyways.

@323
No, they're not, so @bhanuponguru's solution is best for now, as far as I know.