Dialekt by Sugar Bytes

[apeshake]

Anyone have any idea what’s happening with the iOS app release and how much it’ll be? This sounds perfect for my iphone

[BoogerSnot]

Anyone have any idea what’s happening with the iOS app release and how much it’ll be? This sounds perfect for my iphone

Someone at the Loopy Pro forum said it was scheduled to be released at the same time as desktop, but there was a problem of some sort which delayed it, so I would expect it relatively soon.

And yes I agree, it looks like it will be great for iPhone, as they used big grandpa font type of interface so that it would be suited for iPhone (as compared to other companies that don't take the small screen into consideration and so you get the ridiculously tiny font).

[BoogerSnot]

I didn't know this exist till less than 3 minutes ago when I saw this thread.
So went to their website.
https://sugar-bytes.de/dialekt

99 Euros is too steep for all this supposedly can do?
wow.
rsp

Absolutely inflated given that sugar bytes systematically abandons each plugin after release and moves on to the next without delivering vital updates or necessary improvements for the older ones. No, thanks.

When you say "vital" and "necessary" it kind of seems like you mean to say they don't deliver "stuff that I want" because in my experience Sugar Bytes is pretty good at upkeep, though I will admit a few iOS bugs lingered for kind of a long time before a fix came after I made contact with them about it. They eventually got to it though.

[Sugar Bytes]

Their tendency to versionize critical updates is definitely grating.

I bought Effectrix 2 and there's definitely an argument to be made that it should have been just an update to the original since it addresses critical issues but pretty barebones in additions.

Drum Computer is "nearly" one of the best drum machines out there but there's a few fatal flaws that prevent it from being that. (shitty kick drums mainly)

Having said that one of the things that sets sugarbytes apart (apart from the versionising) is that they are very forward looking. They don't get stuck in iterating and forge ahead with something new.

Dialekt very much continues that tradition. It's a very novel take on sequencing and once you get your head around it it's extremely powerful and very addictive.

The demos and presets for some reason don't really do it justice. It's far more expansive/expressive than what they suggest.

For example, a lot of the demos use the same snare sound (Which is the ring modulated snare). A perfectly fine snare for certain genres but can sound a bit flabby in others. But in the Dialekt there's a whole bunch of snare engines that sound very different but they seem to be underutilised.

The demos have a kind of weird unprocessed/raw character (almost chip tune like) but it's capable of a lot more refined sounds.

The meat of Dialekt is how ideas are assembled either by copying parts or via randomisation. Like a lot of Sugarbytes plugins there's some really compelling ingenuity. It kind of reminds me of the Ableton Move's workflow in how you zone in on a phrase within a bigger sequence.

It's a very deep plugin with a lot of potential. Like a less obscure/esoteric version of Nest.

We messed up the presets in the initial release big time. They were batch processed, and something went wrong. We immediately built new versions with the correct presets.
If your presets sound bad and all have the same synths and settings in the engines, please download again.

[Sugar Bytes]

We intended to release all platforms at the same time, but apple had a different opinion.
Due to easter holidays adding further delay, the ios versions might come up next week.

[Sugar Bytes]

From possible flaws, bpm hard linked to host, no free tempo mode. (The same seems for playback,

Why would you want the Dialekt bpm differ from the host?

[Sugar Bytes]

I was thinking the same thing. But I didn't see AuV3 support?

Dialekt iPad has AuV3 support.

[Sugar Bytes]

I feel like I have to make that statement even if it tastes funny.
We do not abandon our software, and it is not buggy. Each reported bug is fixed within days.
Each feature request is realized if possible, but sometimes the architecture does not allow for certain features or changes,
especially if it would compromize existing songs and presets of users.
After the release, drumcomputer received many new features, including eq, the sampler and the analog osc.

Dialekt will also have more stuff added, like more genres, synth engines and another editing range which allows for editing one step in all patterns/parts.

[kraster]

I feel like I have to make that statement even if it tastes funny.
We do not abandon our software, and it is not buggy. Each reported bug is fixed within days.
Each feature request is realized if possible, but sometimes the architecture does not allow for certain features or changes,
especially if it would compromize existing songs and presets of users.
After the release, drumcomputer received many new features, including eq, the sampler and the analog osc.

Dialekt will also have more stuff added, like more genres, synth engines and another editing range which allows for editing one step in all patterns/parts.

Cool. First of all, congrats on the release. I’m having a ball with it. Really addictive and productive.

I’ve a few small issues. Not deal breakers but slightly annoying.

Randomising the cymbal when starting from init doesn’t seem to work. It defaults to an empty Rom setting and stays like that until you manually change it. The slicer has a similar problem. It doesn’t really change the default loop until you do it manually.

I’ve managed to get my own wavetables into Dialekt by dragging them into the wave table folder. I’d love to be able to do the same for one shot samples. Particularly for the Drum components.

I’d love to be able to randomise slice numbers in the slicer discretely. Maybe you could use the syn parameter in the slicer’s randomiser to do this for the slicer.

In some instances resetting parameters in the memory page resets things you’d like to keep e.g Chord type in the chord synth. Having some way exclude more parameters would be cool.

Is there away of having a chord with less than four notes?

There are times when synth controls become unresponsive. Flicking to another synth and back restores functionality.

I would LOVE a way to adjust micro timing on sequence steps. Humanise works for overall sloppiness but having discrete offsets for steps would be fantastic.

[c_voltage]

From possible flaws, bpm hard linked to host, no free tempo mode. (The same seems for playback,

Why would you want the Dialekt bpm differ from the host?

Well, for experiment with polytempo. Including ability to automate this (for achieve some little deviations with main tempo and other fun tricks).
Second thing - for using\have control in modular area (like VCV), where there is no transport. (although it can be simulated, but this is additional quest)

[Sugar Bytes]

Well, for experiment with polytempo. Including ability to automate this (for achieve some little deviations with main tempo and other fun tricks).
Second thing - for using\have control in modular area (like VCV), where there is no transport. (although it can be simulated, but this is additional quest)

You have polytempo in the sequencers, where each track can have its own tempo, including triplets and dotted. But I see the point. I think I know a way to implement that.

[Sugar Bytes]

Randomising the cymbal when starting from init doesn’t seem to work. It defaults to an empty Rom setting and stays like that until you manually change it. The slicer...

-Cannot reproduce this on PC, will have to check on OSX. I definately have to change the Init preset which comes with empty Roms (what did I think?)

I’ve managed to get my own wavetables into Dialekt by dragging them into the wave table folder. I’d love to be able to do the same for one shot samples. Particularly for the Drum components.

-Wow, how did you assume our wavetable format? Single Samples are not impossible and I thought about that, but given the fact that I want monolithic presets, where all samples are included, we quickly arrive at critical file sizes. The Drums come with tons of samples, is it really necessary to use your own samples? I will have a long thought about that.

I’d love to be able to randomise slice numbers in the slicer discretely. Maybe you could use the syn parameter in the slicer’s randomiser to do this for the slicer.

-That will be difficult to include in the generic architecture. But I see the point. Another long thought to be had.

In some instances resetting parameters in the memory page resets things you’d like to keep e.g Chord type in the chord synth. Having some way exclude more parameters would be cool.

-Absolutely. The first thing that I thought about was to exclude pitch. Not impossible!

Is there away of having a chord with less than four notes?

-This is actually a bug: you can drag a chord note onto another, and you come out with 3 notes in the chord. But it´s still a 4-voice synth, so the arpeggiator will always play 4 notes. I the case above, it will repeat that double note.

There are times when synth controls become unresponsive. Flicking to another synth and back restores functionality.

-if I can reproduce that, it´s gold. I know that there is a deadlock situation which was impossible for me to find/reproduce until now.

I would LOVE a way to adjust micro timing on sequence steps. Humanise works for overall sloppiness but having discrete offsets for steps would be fantastic.

-Yes, Step delay. Thats a hard one to include in the GUI. But it´s on the list.

[c_voltage]

Well, for experiment with polytempo. Including ability to automate this (for achieve some little deviations with main tempo and other fun tricks).
Second thing - for using\have control in modular area (like VCV), where there is no transport. (although it can be simulated, but this is additional quest)

You have polytempo in the sequencers, where each track can have its own tempo, including triplets and dotted. But I see the point. I think I know a way to implement that.

Hmm, ok thanks (by both points).

[c_voltage]

What else liked yet from finds, it's method "Pin Needle" for pattern. Which allows you to focus on a small area (and this state saveable in project ie incl certain selected part), catching it out from the whole song diversity and experimenting with it separately.
Useful made.

Untitled.jpg

[kraster]

-Wow, how did you assume our wavetable format? Single Samples are not impossible and I thought about that, but given the fact that I want monolithic presets, where all samples are included, we quickly arrive at critical file sizes. The Drums come with tons of samples, is it really necessary to use your own samples? I will have a long thought about that.

Lol.

I just dragged in some random wavetables in wav format and they worked straight off.

Samples would be really handy to have. The samples that are there are cool but having your own would be great. We all have millions of samples.

-Absolutely. The first thing that I thought about was to exclude pitch. Not impossible!

Maybe you could include pitch in the trigger option by default in the memories page since it's easy to reset pitch within the synth pages on a global level. More often then not I have a part that I want to keep the triggers AND pitches but want to reset everything else

-This is actually a bug: you can drag a chord note onto another, and you come out with 3 notes in the chord. But it´s still a 4-voice synth, so the arpeggiator will always play 4 notes. I the case above, it will repeat that double note.

Great to know

-if I can reproduce that, it´s gold. I know that there is a deadlock situation which was impossible for me to find/reproduce until now.

This issue is tricky to reproduce. It's pretty intermittent. One possible lead is that I often get it when I go from Live mode in the synth page back to one of the other modes.

-Yes, Step delay. Thats a hard one to include in the GUI. But it´s on the list.

Not that I'm a UI designer or anything but the obvious place to put it is where the probability and ratcheting controls are.