Spire Synthesizer

[sound_dev]

I like this Init button, I keep hitting it all the time.

We implement undo function in nearest releases.

[lavenderaudio]

I'm amazed you guys find it so easy to hit the init button by mistake, unless you're using your DAW with a tablet or something? o_O Maybe I'm just used to having a ridiculously huge monitor.

Regardless, a dialogue box to confirm init would be really annoying, as it is my go to point for starting a new patch, and having to press it then another button would be really irritating. If anything, make it a double hit, something I see very little of, click it twice deliberately to reset the patch.

[GeorgeZ]

Making factory patches for Spire... can't say I've accidentally init'd once. Would never have thought this to be a problenm at all Anyway, on the topic of init, what I would like is a full init, ie. NOT have the filter env active in any way (buuuuut that's just me I guess, as no one else has mentioned anything about it). In the currrent init state there is an env already "set up" to filter 1, with full amt, so if you init, and pull down filter 1's cut, that env kicks in. Maybe not a biggy, but from a sound designer's point of view it's a bit of a PITA (kinda like Massive with it's Env 4 that doesn't have the sustain up full in the init patch, not a problem, but a bit annoying as you have to change it pretty much everytime you make a new patch).

[Ghostwave]

Making factory patches for Spire... can't say I've accidentally init'd once. Would never have thought this to be a problenm at all Anyway, on the topic of init, what I would like is a full init, ie. NOT have the filter env active in any way (buuuuut that's just me I guess, as no one else has mentioned anything about it). In the currrent init state there is an env already "set up" to filter 1, with full amt, so if you init, and pull down filter 1's cut, that env kicks in. Maybe not a biggy, but from a sound designer's point of view it's a bit of a PITA (kinda like Massive with it's Env 4 that doesn't have the sustain up full in the init patch, not a problem, but a bit annoying as you have to change it pretty much everytime you make a new patch).

For that, I made my own init patch (several actually) which I just load when I start working in Spire.
I do that for most of the synths I work on.

[sqigls]

I'm amazed you guys find it so easy to hit the init button by mistake, unless you're using your DAW with a tablet or something? o_O Maybe I'm just used to having a ridiculously huge monitor.

Regardless, a dialogue box to confirm init would be really annoying, as it is my go to point for starting a new patch, and having to press it then another button would be really irritating. If anything, make it a double hit, something I see very little of, click it twice deliberately to reset the patch.

yes, I don't understand how you can keep hitting it by mistake. The undo function will be cool tho.

I wonder, is it possible store your own 'init' patch, which can be then recalled when you press the INIT button...?

[Anonym32339]

Someone from Germany out here who bought this synth via giro pay?

I try to buy it all day, but the payment fail everytime... Never had problems with Giro Pay before.
Any idea someone?

[GeorgeZ]

Making factory patches for Spire... can't say I've accidentally init'd once. Would never have thought this to be a problenm at all Anyway, on the topic of init, what I would like is a full init, ie. NOT have the filter env active in any way (buuuuut that's just me I guess, as no one else has mentioned anything about it). In the currrent init state there is an env already "set up" to filter 1, with full amt, so if you init, and pull down filter 1's cut, that env kicks in. Maybe not a biggy, but from a sound designer's point of view it's a bit of a PITA (kinda like Massive with it's Env 4 that doesn't have the sustain up full in the init patch, not a problem, but a bit annoying as you have to change it pretty much everytime you make a new patch).

For that, I made my own init patch (several actually) which I just load when I start working in Spire.
I do that for most of the synths I work on.

That is of course a solution, but when I'm making a sound bank I need a hole bank of inits, so that amounts to a lot of copying and pasting of patches

EDIT: Reveal Audio guys, please read your PMs! The support email is acting..errr.. funky (re factory patches).

[zvenx]

Both BigTone and Himalaya had expressed an early interest in this synth.
I am hoping they too are part of the final factory sounds... or shortly there after
rsp

[sqigls]

Both BigTone and Himalaya had expressed an early interest in this synth.
I am hoping they too are part of the final factory sounds... or shortly there after
rsp

AMEN

[woodsdenis]

I would have thought the major job for the devs would be to reduce the CPU usage, rather than worrying about init buttons. It seems a relatively minor complaint in the scheme of things.

[balx]

I would have thought the major job for the devs would be to reduce the CPU usage, rather than worrying about init buttons. It seems a relatively minor complaint in the scheme of things.

All requests are valid. Tackling a huge issue like CPU usage can take a lot of time and effort, which during said time smaller and easier changes can be made. This is the nature of software development, so don't fret.

[Davias]

I like this Init button, I keep hitting it all the time.

We implement undo function in nearest releases.

Sorry if you misunderstood, but I really like the init button, I was half-joking saying I kept clicking on it all the time because I'm creating some presets, and when I'm done with one I just have to click on the init button and start another one. I find it really useful and really easy


Now I understand some people could click on it without wanting it and I think making an undo function could be really helpful, I just hope it will not use too much resources.

EDIT : Oh and I wouldn't want a confirmation dialog, one click one the init button is enough as others mentioned.

[Aiynzahev]

I like this Init button, I keep hitting it all the time.

EDIT : Oh and I wouldn't want a confirmation dialog, one click one the init button is enough as others mentioned.

Actually that can be true too, dialogue boxes can be a pain. I've never hit the init button by mistake either, I just thought it is probably quite easy to do and would be a real pain. Undo function is best. Multiple undo's can be really helpful to some too.

[sound_dev]

I would have thought the major job for the devs would be to reduce the CPU usage, rather than worrying about init buttons. It seems a relatively minor complaint in the scheme of things.

Init button is our minor job

[GeorgeZ]

I would have thought the major job for the devs would be to reduce the CPU usage, rather than worrying about init buttons. It seems a relatively minor complaint in the scheme of things.

Init button is our minor job