ButterSynth Is Released!

cyberheater

Have bought it.

satchnut

@Pictor said:
Who the Fred is fuck? (cit.)

This guy, apparently:
https://www.youtube.com/c/Fredagainagain/videos

Antos3345

Great synth ..sounds like Serum on IOS. Thanks for the great work!

offbrands

@Pictor said:
Yes i also see it as an apology rather than abandonment.

All in all it has been quite stable; got a bunch of crashes (either as AUv3 and standalone) in cases where RAM wasn’t enough, or when I set 3-4 instances at the same time.
I reduced the max polyphony number, but all the crashes were already on patches with only 1 voices per OSC.
It’s pretty usable most times, I wouldn’t judge it as brittle based on couple resource-related crashes.

However when i try the “Re-sample synth to 16 waves” the app crashes systematically. So, yeah, some bug there but in general functionality is quite stable.
It just sucks a shit load of battery and RAM 😁

Resampling, I’m not very familiar with in this context. What were your plans with resampling the synth?

Yeah it’s a battery hog. Once I took down the polyphony it helped the app a lot.

I often notice clicking the settings / menu crashes the app. So there might be some work needed there. Typically when I’ve just changed a preset but happens even if not.

@offbrands said:
Will do. Unfortunately I’ve just got around to listening to Fred again.. for the first time and oh man. He’s brilliant

Now I’m having an existential crisis of why even make music. I’ll snap out of it soon and report back after some through usage.

Who the Fred is fuck? (cit.)

A UK artist / producer who shares the same name as I and happens to be Maslows Hierarchy personified into a musician. Had to reframe my judgement.

One thing that threw me off was that I make, admittedly nowhere near as well, a similar style he does. Heavy vocal samples, electronic, club style music. I guess if I ever put music out regularly I’ll just have to use a different name.

Maybe “ Fred again.. but not him” - a conundrum. 🤣

Pictor

@offbrands said:

@Pictor said:
Yes i also see it as an apology rather than abandonment.

All in all it has been quite stable; got a bunch of crashes (either as AUv3 and standalone) in cases where RAM wasn’t enough, or when I set 3-4 instances at the same time.
I reduced the max polyphony number, but all the crashes were already on patches with only 1 voices per OSC.
It’s pretty usable most times, I wouldn’t judge it as brittle based on couple resource-related crashes.

However when i try the “Re-sample synth to 16 waves” the app crashes systematically. So, yeah, some bug there but in general functionality is quite stable.
It just sucks a shit load of battery and RAM 😁

Resampling, I’m not very familiar with in this context. What were your plans with resampling the synth?

I dunno either lol, I was just exploring features from the app ^^
But basically Butter Synth can take its output signal, split the waveform in 16 pieces and reassign those pieces as separate waves of a wave-table (can then twist the WT Index knob to choose which wave (fragment) to use in an oscillator.

Pretty powerful idea

I often notice clicking the settings / menu crashes the app. So there might be some work needed there. Typically when I’ve just changed a preset but happens even if not.

This is quite peculiar, interesting…; SM2 has similarly problems with presets and crashing; maybe it’s an tricky issue in how the AUv3 API is used by developers and some race condition triggers when having to update the application instance state (i mean… what would be the reason otherwise for an operation that should simply display a static/non-changing menu?).
I guess the settings function somehow goes check for some condition and finds inconsistencies, triggering some exception.
Or is a performance/resources issue related to wrong memory access or some cpu operation following some wrong pathway.

Still it’s a good insight…. it really reduces the scope of the issue, highlighting the settings functions as place where to investigate the bug.
Did you mention this on the Discord channel or via email support?

@offbrands said:
Will do. Unfortunately I’ve just got around to listening to Fred again.. for the first time and oh man. He’s brilliant

Now I’m having an existential crisis of why even make music. I’ll snap out of it soon and report back after some through usage.

Who the Fred is fuck? (cit.)

A UK artist / producer who shares the same name as I and happens to be Maslows Hierarchy personified into a musician. Had to reframe my judgement.

One thing that threw me off was that I make, admittedly nowhere near as well, a similar style he does. Heavy vocal samples, electronic, club style music. I guess if I ever put music out regularly I’ll just have to use a different name.

Maybe “ Fred again.. but not him” - a conundrum. 🤣

Aaaah now I get it! 😁

offbrands

@Pictor said:

@offbrands said:

@Pictor said:
Yes i also see it as an apology rather than abandonment.

All in all it has been quite stable; got a bunch of crashes (either as AUv3 and standalone) in cases where RAM wasn’t enough, or when I set 3-4 instances at the same time.
I reduced the max polyphony number, but all the crashes were already on patches with only 1 voices per OSC.
It’s pretty usable most times, I wouldn’t judge it as brittle based on couple resource-related crashes.

However when i try the “Re-sample synth to 16 waves” the app crashes systematically. So, yeah, some bug there but in general functionality is quite stable.
It just sucks a shit load of battery and RAM 😁

Resampling, I’m not very familiar with in this context. What were your plans with resampling the synth?

Yeah it’s a battery hog. Once I took down the polyphony it helped the app a lot.

I often notice clicking the settings / menu crashes the app. So there might be some work needed there. Typically when I’ve just changed a preset but happens even if not.

This is quite peculiar, interesting…; SM2 has similarly problems with presets and crashing; maybe it’s an tricky issue in how the AUv3 API is used by developers and some race condition triggers when having to update the application instance state (i mean… what would be the reason otherwise for an operation that should simply display a static/non-changing menu?).
I guess the settings function somehow goes check for some condition and finds inconsistencies, triggering some exception.
Or is a performance/resources issue related to wrong memory access or some cpu operation following some wrong pathway.

Still it’s a good insight…. it really reduces the scope of the issue, highlighting the settings functions as place where to investigate the bug.
Did you mention this on the Discord channel or via email support?

Yeah hopefully that can help. If you or anyone who sees this has a dialogue with the dev, feel free to share this.

I’m not a fan of Discord but I hadn’t thought of email since the dev was MIA and doesn’t seem to be the most communicative other than on Discord. I don’t want to be another person adding to the deluge of requests or bugs. Usually not one to assume but just feels off to reach out all things considered.

Since I’ve been using it with less polyphony it’s been solid as long as I don’t touch the settings. Which is all I could ask for. I’ll update my iPad one day in the relative future.

pseudophysics

is MPE on the roadmap for this one?

offbrands

Just noticed Buttersynth is off the App Store again. Not sure if it was mentioned elsewhere.

gusgranite

No, it should be there now. The were a couple of glitches but the developer sorted it quickly.

offbrands

@gusgranite said:
No, it should be there now. The were a couple of glitches but the developer sorted it quickly.

Oh okay! That’s good then.

I don’t know how App Raven gathers their data or even how often it updates their set but that’s where that screenshot is from. Still listed as off and greyed out. Strange.

Alfred

Mpe seems to be working allready. However the sheer amount of cc, pb and at being received crashes the synth. Reducing the amount of data being sent by my Osmose (through mozaic) caused Buttersynth to stop crashing.