ButterSynth Is Released!

dendy

simple description

when you are holding let’s say 4 notes, arp is playing, normally it plays single note for every step

when it comes to step where you have selected let’s say bottom 3 blue recrangles, then single note which would be normally played on that step, is not played and first 3 held notes (counted from left to right) are played instead

if you check blue box in bottom line, then you leave 2 empty boxes and then you check 4th, then your first and 4th note from left to right will be played at that given step

just imagine all you pressed keys stacked as they come from left to right, just rotated 90 degrees anti-clockwise, to form rows in arpeggiator config..

Robin2

@dendy said:
simple description

when you are holding let’s say 4 notes, arp is playing, normally it plays single note for every step

when it comes to step where you have selected let’s say bottom 3 blue recrangles, then single note which would be normally played on that step, is not played and first 3 held notes (counted from left to right) are played instead

if you check blue box in bottom line, then you leave 2 empty boxes and then you check 4th, then your first and 4th note from left to right will be played at that given step

just imagine all you pressed keys stacked as they come from left to right, just rotated 90 degrees anti-clockwise, to form rows in arpeggiator config..

Brilliant, got it, thank you very much @dendy!

Antos3345

I think the sound of this synth has a lot of potential. The sound is the same or better than many VSTs. I think like any synth it’s just getting into it and knowing how to use it.

[Deleted User]

The user and all related content has been deleted.

wim

I wonder, why the crash in the wavetable editor is not fixed yet.

Especially when all it takes is a simple snap of the fingers to fix software bugs. 🤷🏼‍♂️

[Deleted User]

The user and all related content has been deleted.

OnfraySin

I have a interest about this synth. When is expected to go out from beta?

Birdpie

hey guys,
on my iphone i can barely see the keyboard and can't use mod and pitchbend.
is there a way to see the keyboard a little bit more?

dendy

@Birdpie said:
hey guys,
on my iphone i can barely see the keyboard and can't use mod and pitchbend.
is there a way to see the keyboard a little bit more?

slide up on left or right gray border - keyboard appears .. slide down there then hides it again

Birdpie

wow thanks!

boomer

How do you specify rate in the LFOs in ms/seconds? I can only seem to set it to relative beat sync. This is in standalone version - have not checked auv.

dendy

@boomer said:
How do you specify rate in the LFOs in ms/seconds? I can only seem to set it to relative beat sync. This is in standalone version - have not checked auv.

unfortunarelly you can’t, LFO’s are just tempo synced .. if you want free run use curve envelope as LFO ..

boomer

@dendy said:

@boomer said:
How do you specify rate in the LFOs in ms/seconds? I can only seem to set it to relative beat sync. This is in standalone version - have not checked auv.

unfortunarelly you can’t, LFO’s are just tempo synced .. if you want free run use curve envelope as LFO ..

Thanks! The curve env with free run is still influenced by tempo but much less so. Might be workable to use a vibrato. I have never seen an lfo that could not be set in absolute time. Guess I gotta get out more

boomer

Is there anything in the future roadmap that would enable saving states of the 4 tabs on top left separate from entire patches.

Birdpie

where can i send bug reports to the developer?
having chrashs standalone iphone when trying to choose another arp preset.

[Deleted User]

The user and all related content has been deleted.

Birdpie

@tja said:

@Birdpie said:
where can i send bug reports to the developer?
having chrashs standalone iphone when trying to choose another arp preset.

[email protected]

And yes, immediate crash confirmed!
😑

thanks

Robin2

Do any of the tutorials/reviews out there cover how to use the wavetable bin editor?

Robin2

@Robin2 said:
Do any of the tutorials/reviews out there cover how to use the wavetable bin editor?

Just bumping my own question. All references to the wavetable bin I’ve seen just say in passing that it exists so you can do additive synthesis but don’t give any clues as to how to actually use it? And the manual only has one paragraph on it.

For example, do you really need to set values for all 1023 bins to fully sculpt a sound? Seems a bit daunting. Is there a way to ‘zero’ all bins to start from scratch? @Kirnu? @dendy? Anyone?

dendy

@Robin2 said:
For example, do you really need to set values for all 1023 bins to fully sculpt a sound? Seems a bit daunting. Is there a way to ‘zero’ all bins to start from scratch? @Kirnu? @dendy? Anyone?

well, you need to set just those bands which you need to set to achieve sound you want to achieve :-)) Just experiment with it ..
Start with sine wave (which is basically just one band) and then start adding other bands, whatch (and listen) whan it does to wave .. in general higher bands add higher frequencies ..

It's all about experimenting and learning how .. don't be afraid to experiment .. as i said, ideally aways start with just plain sine wve and then keep adding various bands and observe what happens .. you get very quickly familiar with the concept, not need to read any tutorial about it, just keep you brain figure it, it's pretty self-explanatory ...

Birdpie

when i draw a saw going downwards , i never get it done without a spike at the beginning/end.
is it a real spike or just a graphic error?

dendy

@Birdpie said:
when i draw a saw going downwards , i never get it done without a spike at the beginning/end.
is it a real spike or just a graphic error?

graphic error

Robin2

@dendy said:

@Robin2 said:
For example, do you really need to set values for all 1023 bins to fully sculpt a sound? Seems a bit daunting. Is there a way to ‘zero’ all bins to start from scratch? @Kirnu? @dendy? Anyone?

well, you need to set just those bands which you need to set to achieve sound you want to achieve :-)) Just experiment with it ..
Start with sine wave (which is basically just one band) and then start adding other bands, whatch (and listen) whan it does to wave .. in general higher bands add higher frequencies ..

It's all about experimenting and learning how .. don't be afraid to experiment .. as i said, ideally aways start with just plain sine wve and then keep adding various bands and observe what happens .. you get very quickly familiar with the concept, not need to read any tutorial about it, just keep you brain figure it, it's pretty self-explanatory ...

Thanks @dendy, really appreciate your input as always.

Thing is, everything is self explanatory if you actually already understand it beforehand. Obviously I have been experimenting with it but that lead me to seek more information about exactly what’s happening and how to practically use it.

Each bin represents a frequency - is that correct? From my experimenting, it seems like the first bins affect the sound wave much more than the later/higher ones - are the highest bins perhaps representing frequencies which are outwith the human hearing range? What range of frequencies are covered by the bins?

Also, scrolling back and forth through 1023 bins is really impractical and overwhelming. I wonder whether it would be better were it possible to start out at a lower resolution of frequency bins, which would all fit on the screen, to roughly sculpt a sound before then zooming into higher resolution to finely tune as required? That could really help unless I’m missing the point of how it is to be used? Possible feature request @Kirnu?

Is the bin editor, in practice, really more likely to be used for fine tuning your existing waves rather than creating them from scratch?

espiegel123

@Robin2 said:

@dendy said:

@Robin2 said:
For example, do you really need to set values for all 1023 bins to fully sculpt a sound? Seems a bit daunting. Is there a way to ‘zero’ all bins to start from scratch? @Kirnu? @dendy? Anyone?

well, you need to set just those bands which you need to set to achieve sound you want to achieve :-)) Just experiment with it ..
Start with sine wave (which is basically just one band) and then start adding other bands, whatch (and listen) whan it does to wave .. in general higher bands add higher frequencies ..

It's all about experimenting and learning how .. don't be afraid to experiment .. as i said, ideally aways start with just plain sine wve and then keep adding various bands and observe what happens .. you get very quickly familiar with the concept, not need to read any tutorial about it, just keep you brain figure it, it's pretty self-explanatory ...

Thanks @dendy, really appreciate your input as always.

Thing is, everything is self explanatory if you actually already understand it beforehand. Obviously I have been experimenting with it but that lead me to seek more information about exactly what’s happening and how to practically use it.

Each bin represents a frequency - is that correct? From my experimenting, it seems like the first bins affect the sound wave much more than the later/higher ones - are the highest bins perhaps representing frequencies which are outwith the human hearing range? What range of frequencies are covered by the bins?

Also, scrolling back and forth through 1023 bins is really impractical and overwhelming. I wonder whether it would be better were it possible to start out at a lower resolution of frequency bins, which would all fit on the screen, to roughly sculpt a sound before then zooming into higher resolution to finely tune as required? That could really help unless I’m missing the point of how it is to be used? Possible feature request @Kirnu?

Is the bin editor, in practice, really more likely to be used for fine tuning your existing waves rather than creating them from scratch?

I recommend doing a web search about wavetables. There is a lot of info about how they work.

By ‘bin’, do you mean the frames? Wavetables aren’t additive . Each frame represents a single cycle of a waveform. If the wavetable’s index isn’t modulated, it will play just one of those frames as its waveform. You can turn a knob to cycle through them by hand.

Typically, you modulate the index so that the oscillator sequences through each of the waveforms in the wavetable’s frames.

Robin2

@espiegel123 said:

@Robin2 said:

@dendy said:

@Robin2 said:
For example, do you really need to set values for all 1023 bins to fully sculpt a sound? Seems a bit daunting. Is there a way to ‘zero’ all bins to start from scratch? @Kirnu? @dendy? Anyone?

well, you need to set just those bands which you need to set to achieve sound you want to achieve :-)) Just experiment with it ..
Start with sine wave (which is basically just one band) and then start adding other bands, whatch (and listen) whan it does to wave .. in general higher bands add higher frequencies ..

It's all about experimenting and learning how .. don't be afraid to experiment .. as i said, ideally aways start with just plain sine wve and then keep adding various bands and observe what happens .. you get very quickly familiar with the concept, not need to read any tutorial about it, just keep you brain figure it, it's pretty self-explanatory ...

Thanks @dendy, really appreciate your input as always.

Thing is, everything is self explanatory if you actually already understand it beforehand. Obviously I have been experimenting with it but that lead me to seek more information about exactly what’s happening and how to practically use it.

Each bin represents a frequency - is that correct? From my experimenting, it seems like the first bins affect the sound wave much more than the later/higher ones - are the highest bins perhaps representing frequencies which are outwith the human hearing range? What range of frequencies are covered by the bins?

Also, scrolling back and forth through 1023 bins is really impractical and overwhelming. I wonder whether it would be better were it possible to start out at a lower resolution of frequency bins, which would all fit on the screen, to roughly sculpt a sound before then zooming into higher resolution to finely tune as required? That could really help unless I’m missing the point of how it is to be used? Possible feature request @Kirnu?

Is the bin editor, in practice, really more likely to be used for fine tuning your existing waves rather than creating them from scratch?

I recommend doing a web search about wavetables. There is a lot of info about how they work.

By ‘bin’, do you mean the frames? Wavetables aren’t additive . Each frame represents a single cycle of a waveform. If the wavetable’s index isn’t modulated, it will play just one of those frames as its waveform. You can turn a knob to cycle through them by hand.

Typically, you modulate the index so that the oscillator sequences through each of the waveforms in the wavetable’s frames.

Thanks for commenting @espiegel123 but with great respect, I recommend you look at the app you’re talking about…underneath the frames you are talking about (which I do understand) there is a bin editor. See at the top where it says ‘Wavetable and Bin editor’? That’s what I’m referring to, the thing underneath the actual waveform editor - that, apparently, though I may have understood incorrectly, is additive. Presumably that means you don’t know how to use it if you hadn’t even noticed it?

Robin2

Duplicate post, sorry.

espiegel123

@Robin2 said:

@espiegel123 said:

@Robin2 said:

@dendy said:

@Robin2 said:
For example, do you really need to set values for all 1023 bins to fully sculpt a sound? Seems a bit daunting. Is there a way to ‘zero’ all bins to start from scratch? @Kirnu? @dendy? Anyone?

well, you need to set just those bands which you need to set to achieve sound you want to achieve :-)) Just experiment with it ..
Start with sine wave (which is basically just one band) and then start adding other bands, whatch (and listen) whan it does to wave .. in general higher bands add higher frequencies ..

It's all about experimenting and learning how .. don't be afraid to experiment .. as i said, ideally aways start with just plain sine wve and then keep adding various bands and observe what happens .. you get very quickly familiar with the concept, not need to read any tutorial about it, just keep you brain figure it, it's pretty self-explanatory ...

Thanks @dendy, really appreciate your input as always.

Thing is, everything is self explanatory if you actually already understand it beforehand. Obviously I have been experimenting with it but that lead me to seek more information about exactly what’s happening and how to practically use it.

Each bin represents a frequency - is that correct? From my experimenting, it seems like the first bins affect the sound wave much more than the later/higher ones - are the highest bins perhaps representing frequencies which are outwith the human hearing range? What range of frequencies are covered by the bins?

Also, scrolling back and forth through 1023 bins is really impractical and overwhelming. I wonder whether it would be better were it possible to start out at a lower resolution of frequency bins, which would all fit on the screen, to roughly sculpt a sound before then zooming into higher resolution to finely tune as required? That could really help unless I’m missing the point of how it is to be used? Possible feature request @Kirnu?

Is the bin editor, in practice, really more likely to be used for fine tuning your existing waves rather than creating them from scratch?

I recommend doing a web search about wavetables. There is a lot of info about how they work.

By ‘bin’, do you mean the frames? Wavetables aren’t additive . Each frame represents a single cycle of a waveform. If the wavetable’s index isn’t modulated, it will play just one of those frames as its waveform. You can turn a knob to cycle through them by hand.

Typically, you modulate the index so that the oscillator sequences through each of the waveforms in the wavetable’s frames.

Thanks for commenting @espiegel123 but with great respect, I recommend you look at the app you’re talking about…underneath the frames you are talking about (which I do understand) there is a bin editor. See at the top where it says ‘Wavetable and Bin editor’? That’s what I’m referring to, the thing underneath the actual waveform editor - that, apparently, though I may have understood incorrectly, is additive. Presumably that means you don’t know how to use it if you hadn’t even noticed it?

Sorry, I should have had the app open before replying. I appreciate your patient, kind way of pointing out my error.

The histogram below the waveform display is the harmonics of the waveform (presumably derived by FFT analysis ). High-order harmonics will often be out of the audible range which is why you aren't noticing an impact when editing them.

Robin2

@espiegel123 said:

@Robin2 said:

@espiegel123 said:

@Robin2 said:

@dendy said:

@Robin2 said:
For example, do you really need to set values for all 1023 bins to fully sculpt a sound? Seems a bit daunting. Is there a way to ‘zero’ all bins to start from scratch? @Kirnu? @dendy? Anyone?

well, you need to set just those bands which you need to set to achieve sound you want to achieve :-)) Just experiment with it ..
Start with sine wave (which is basically just one band) and then start adding other bands, whatch (and listen) whan it does to wave .. in general higher bands add higher frequencies ..

It's all about experimenting and learning how .. don't be afraid to experiment .. as i said, ideally aways start with just plain sine wve and then keep adding various bands and observe what happens .. you get very quickly familiar with the concept, not need to read any tutorial about it, just keep you brain figure it, it's pretty self-explanatory ...

Thanks @dendy, really appreciate your input as always.

Thing is, everything is self explanatory if you actually already understand it beforehand. Obviously I have been experimenting with it but that lead me to seek more information about exactly what’s happening and how to practically use it.

Each bin represents a frequency - is that correct? From my experimenting, it seems like the first bins affect the sound wave much more than the later/higher ones - are the highest bins perhaps representing frequencies which are outwith the human hearing range? What range of frequencies are covered by the bins?

Also, scrolling back and forth through 1023 bins is really impractical and overwhelming. I wonder whether it would be better were it possible to start out at a lower resolution of frequency bins, which would all fit on the screen, to roughly sculpt a sound before then zooming into higher resolution to finely tune as required? That could really help unless I’m missing the point of how it is to be used? Possible feature request @Kirnu?

Is the bin editor, in practice, really more likely to be used for fine tuning your existing waves rather than creating them from scratch?

I recommend doing a web search about wavetables. There is a lot of info about how they work.

By ‘bin’, do you mean the frames? Wavetables aren’t additive . Each frame represents a single cycle of a waveform. If the wavetable’s index isn’t modulated, it will play just one of those frames as its waveform. You can turn a knob to cycle through them by hand.

Typically, you modulate the index so that the oscillator sequences through each of the waveforms in the wavetable’s frames.

Thanks for commenting @espiegel123 but with great respect, I recommend you look at the app you’re talking about…underneath the frames you are talking about (which I do understand) there is a bin editor. See at the top where it says ‘Wavetable and Bin editor’? That’s what I’m referring to, the thing underneath the actual waveform editor - that, apparently, though I may have understood incorrectly, is additive. Presumably that means you don’t know how to use it if you hadn’t even noticed it?

Sorry, I should have had the app open before replying. I appreciate your patient, kind way of pointing out my error.

The histogram below the waveform display is the harmonics of the waveform (presumably derived by FFT analysis ). High-order harmonics will often be out of the audible range which is why you aren't noticing an impact when editing them.

Thanks @espiegel123. Yes, I think I understand what it is doing but unfortunately I’m finding it wildly impractical to actually use, hence my suggestion that it might be better with switchable levels of resolution. That’s also why I was I was hoping one of the tutorial/review videos might have shown someone actually using it so I could see if I was missing something. Thanks for confirming that the higher order harmonics are probably out of the audible range - I wonder at what point in the 1023 bins that happens? Cheers.

espiegel123

@Robin2 said:

@espiegel123 said:

@Robin2 said:

@espiegel123 said:

@Robin2 said:

@dendy said:

@Robin2 said:
For example, do you really need to set values for all 1023 bins to fully sculpt a sound? Seems a bit daunting. Is there a way to ‘zero’ all bins to start from scratch? @Kirnu? @dendy? Anyone?

well, you need to set just those bands which you need to set to achieve sound you want to achieve :-)) Just experiment with it ..
Start with sine wave (which is basically just one band) and then start adding other bands, whatch (and listen) whan it does to wave .. in general higher bands add higher frequencies ..

It's all about experimenting and learning how .. don't be afraid to experiment .. as i said, ideally aways start with just plain sine wve and then keep adding various bands and observe what happens .. you get very quickly familiar with the concept, not need to read any tutorial about it, just keep you brain figure it, it's pretty self-explanatory ...

Thanks @dendy, really appreciate your input as always.

Thing is, everything is self explanatory if you actually already understand it beforehand. Obviously I have been experimenting with it but that lead me to seek more information about exactly what’s happening and how to practically use it.

Each bin represents a frequency - is that correct? From my experimenting, it seems like the first bins affect the sound wave much more than the later/higher ones - are the highest bins perhaps representing frequencies which are outwith the human hearing range? What range of frequencies are covered by the bins?

Also, scrolling back and forth through 1023 bins is really impractical and overwhelming. I wonder whether it would be better were it possible to start out at a lower resolution of frequency bins, which would all fit on the screen, to roughly sculpt a sound before then zooming into higher resolution to finely tune as required? That could really help unless I’m missing the point of how it is to be used? Possible feature request @Kirnu?

Is the bin editor, in practice, really more likely to be used for fine tuning your existing waves rather than creating them from scratch?

I recommend doing a web search about wavetables. There is a lot of info about how they work.

By ‘bin’, do you mean the frames? Wavetables aren’t additive . Each frame represents a single cycle of a waveform. If the wavetable’s index isn’t modulated, it will play just one of those frames as its waveform. You can turn a knob to cycle through them by hand.

Typically, you modulate the index so that the oscillator sequences through each of the waveforms in the wavetable’s frames.

Thanks for commenting @espiegel123 but with great respect, I recommend you look at the app you’re talking about…underneath the frames you are talking about (which I do understand) there is a bin editor. See at the top where it says ‘Wavetable and Bin editor’? That’s what I’m referring to, the thing underneath the actual waveform editor - that, apparently, though I may have understood incorrectly, is additive. Presumably that means you don’t know how to use it if you hadn’t even noticed it?

Sorry, I should have had the app open before replying. I appreciate your patient, kind way of pointing out my error.

The histogram below the waveform display is the harmonics of the waveform (presumably derived by FFT analysis ). High-order harmonics will often be out of the audible range which is why you aren't noticing an impact when editing them.

Thanks @espiegel123. Yes, I think I understand what it is doing but unfortunately I’m finding it wildly impractical to actually use, hence my suggestion that it might be better with switchable levels of resolution. That’s also why I was I was hoping one of the tutorial/review videos might have shown someone actually using it so I could see if I was missing something. Thanks for confirming that the higher order harmonics are probably out of the audible range - I wonder at what point in the 1023 bins that happens? Cheers.

The histogram is a real representation of the waveform. While being able to edit it gives you additive tools to edit the waveform, the oscillator is playing back the waveform. Reducing the number of harmonics displayed , would reduce the accuracy of the display. It keeps it computationally simple to just translate back and forth directly.

To get a sense of which harmonics are audible, set the wavetable to sine wave. Set the lowest harmonic to 0. And set some other harmonic to go to max. Try this with increasingly higher order harmonics. Play different pitches on your keyboard.

Explore in this way to get a feel for the harmonics.

Robin2

@espiegel123 said:

@Robin2 said:

@espiegel123 said:

@Robin2 said:

@espiegel123 said:

@Robin2 said:

@dendy said:

@Robin2 said:
For example, do you really need to set values for all 1023 bins to fully sculpt a sound? Seems a bit daunting. Is there a way to ‘zero’ all bins to start from scratch? @Kirnu? @dendy? Anyone?

well, you need to set just those bands which you need to set to achieve sound you want to achieve :-)) Just experiment with it ..
Start with sine wave (which is basically just one band) and then start adding other bands, whatch (and listen) whan it does to wave .. in general higher bands add higher frequencies ..

It's all about experimenting and learning how .. don't be afraid to experiment .. as i said, ideally aways start with just plain sine wve and then keep adding various bands and observe what happens .. you get very quickly familiar with the concept, not need to read any tutorial about it, just keep you brain figure it, it's pretty self-explanatory ...

Thanks @dendy, really appreciate your input as always.

Thing is, everything is self explanatory if you actually already understand it beforehand. Obviously I have been experimenting with it but that lead me to seek more information about exactly what’s happening and how to practically use it.

Each bin represents a frequency - is that correct? From my experimenting, it seems like the first bins affect the sound wave much more than the later/higher ones - are the highest bins perhaps representing frequencies which are outwith the human hearing range? What range of frequencies are covered by the bins?

Also, scrolling back and forth through 1023 bins is really impractical and overwhelming. I wonder whether it would be better were it possible to start out at a lower resolution of frequency bins, which would all fit on the screen, to roughly sculpt a sound before then zooming into higher resolution to finely tune as required? That could really help unless I’m missing the point of how it is to be used? Possible feature request @Kirnu?

Is the bin editor, in practice, really more likely to be used for fine tuning your existing waves rather than creating them from scratch?

I recommend doing a web search about wavetables. There is a lot of info about how they work.

By ‘bin’, do you mean the frames? Wavetables aren’t additive . Each frame represents a single cycle of a waveform. If the wavetable’s index isn’t modulated, it will play just one of those frames as its waveform. You can turn a knob to cycle through them by hand.

Typically, you modulate the index so that the oscillator sequences through each of the waveforms in the wavetable’s frames.

Thanks for commenting @espiegel123 but with great respect, I recommend you look at the app you’re talking about…underneath the frames you are talking about (which I do understand) there is a bin editor. See at the top where it says ‘Wavetable and Bin editor’? That’s what I’m referring to, the thing underneath the actual waveform editor - that, apparently, though I may have understood incorrectly, is additive. Presumably that means you don’t know how to use it if you hadn’t even noticed it?

Sorry, I should have had the app open before replying. I appreciate your patient, kind way of pointing out my error.

The histogram below the waveform display is the harmonics of the waveform (presumably derived by FFT analysis ). High-order harmonics will often be out of the audible range which is why you aren't noticing an impact when editing them.

Thanks @espiegel123. Yes, I think I understand what it is doing but unfortunately I’m finding it wildly impractical to actually use, hence my suggestion that it might be better with switchable levels of resolution. That’s also why I was I was hoping one of the tutorial/review videos might have shown someone actually using it so I could see if I was missing something. Thanks for confirming that the higher order harmonics are probably out of the audible range - I wonder at what point in the 1023 bins that happens? Cheers.

The histogram is a real representation of the waveform. While being able to edit it gives you additive tools to edit the waveform, the oscillator is playing back the waveform. Reducing the number of harmonics displayed , would reduce the accuracy of the display. It keeps it computationally simple to just translate back and forth directly.

To get a sense of which harmonics are audible, set the wavetable to sine wave. Set the lowest harmonic to 0. And set some other harmonic to go to max. Try this with increasingly higher order harmonics. Play different pitches on your keyboard.

Explore in this way to get a feel for the harmonics.

Great, thanks for the clear explanation @espiegel123, I really appreciate it. I’ll play around using the method you describe and see how I get on. Cheers.