BLEASS Apps official thread

We've created this discussion in order to give you regular updates about the BLEASS Apps (BLEASS groovebox & BLEASS delay as well as upcoming new Apps)!

Stay tuned for GIVEAWAYS, TUTORIALS, TIPS & TRICKS and feel free to ask for NEW FEATURES!

«1

Comments

  • Hey! to start this thread, we offer 10 Promo codes for the BLEASS delay AUv3 plugin with this giveaway: be quick!
    http://bit.ly/BLEASSdelayGIVEAWAY

  • edited March 12

    Bleass updated with external audio and fx routing options.

  • @bleassapp Would like to see automation of synth parameters and maybe a sampler module added next thanks for the update.

  • Thanks for great Work
    Bleass

  • What is the price for the pro version ? Is it a monthly fee?

  • Thank you all for your feedbacks

    BLEASS groovebox PRO does NOT offer subscription anymore. It's a FULL UNLOCK : purchase once and own forever!

  • @bleassapp said:
    Thank you all for your feedbacks

    BLEASS groovebox PRO does NOT offer subscription anymore. It's a FULL UNLOCK : purchase once and own forever!

    Great to hear.
    Thanks.

  • @bleassapp said:
    Thank you all for your feedbacks

    BLEASS groovebox PRO does NOT offer subscription anymore. It's a FULL UNLOCK : purchase once and own forever!

    :) B)

  • @bleassapp Hey guys... I've found some "bugs" in your midi/au.param mapping in BleassDelay...

    This is all tested in AUM

    1) mapping a midi controller to pitch... It's impossible to get it to land on zero. Midi cc value of 64 should land in the middle at zero, it doesn't it's either +7 something or -7 something
    2) Mapping HP filtrer freq is just wrong... There's almost no "travel" required to go from open to like 80% closed. Like th efirst 105 of cc knob travel eats most of the filter's frequency, thus it's impossible to be precise.
    3) mapping delay time, then in sync mode, doesn't change/move the delay time.
    4) Weird movement for Feedback & Mix... Toward the top they jump. My guess is you're using a lookup/translation table, made a change to parameter range, but didn't update table.
    5) Stereo Phase knobs go to 1% rather than 0 when cc value=64. Should go to zero at "detent" value

  • Hi, thank you for using BLEASS delay and for this very good feedback in the official BLEASS thread!

    • Regarding what you said in 1) & 5), we're gonna take a look but it is difficult for us to correct these problems since it is AUM who's managing to convert MIDI CC to Audio Unit Parameter values ... What's tricky here is that the middle value should be 63.5 then, which is impossible to reach because MIDI does not transmit decimal values ...

    • About frequencies in HP or LP filter, yes it's traveling fast in the lower values because we expose our Audio Unit Parameters as frequencies ... if your MIDI CC curve is linear in AUM then it doesn't really match the nicely sounding frequency curve. We could fix that but it will result a lot of regressions for people who stores presets in the past. Let us take look, maybe exposing a second parameter "MIDI-CC dedicated" could correct this problem.

    • We can correct 3). And we have to investigate on 4). Stay tuned for upcoming updates!

    Don't hesitate to send this feedback to the Kymatica team that develops AUM also as some of these "issues" are more AUM related.

    Again, thank you!

  • @bleassapp said:
    Don't hesitate to send this feedback to the Kymatica team that develops AUM also as some of these "issues" are more AUM related.

    Again, thank you!

    @j_liljedahl

    Weird, because pretty much every other AU works better than BleassDelay in terms of mapping as it is, so I'm not sure why it would be an issue with ONLY with yours...

    Maybe Mr. AUM can shed some light?

  • @bleassapp can you explain to me what a Bleass is or what it stands for? is it a made up word?

  • @bleassapp said:
    Hi, thank you for using BLEASS delay and for this very good feedback in the official BLEASS thread!

    • Regarding what you said in 1) & 5), we're gonna take a look but it is difficult for us to correct these problems since it is AUM who's managing to convert MIDI CC to Audio Unit Parameter values ... What's tricky here is that the middle value should be 63.5 then, which is impossible to reach because MIDI does not transmit decimal values ...

    AUM maps the 7 bit MIDI as follows: value = midiValue/127.0 so that 0 to 127 gives 0.0 to 1.0. It then scales this to the parameters actual min/max values with value * (maxValue-minValue) + minValue for linear params and pow(maxValue/minValue, value) * minValue for logarithmic parameters.

    Indeed since 7 bit MIDI doesn't have an integer corresponding to exactly the middle value, I don't see how this could be solved on my side in a good way. Dividing by 128 would not allow one to reach 1.0, which would be even worse.

    • About frequencies in HP or LP filter, yes it's traveling fast in the lower values because we expose our Audio Unit Parameters as frequencies ... if your MIDI CC curve is linear in AUM then it doesn't really match the nicely sounding frequency curve. We could fix that but it will result a lot of regressions for people who stores presets in the past. Let us take look, maybe exposing a second parameter "MIDI-CC dedicated" could correct this problem.

    AUM handles logarithmic params (such as frequencies), as mentioned above. It checks the param flags AudioUnitDisplayTypeIsLogarithmic(param.flags) which is Apple's macro that specifically checks the kAudioUnitParameterFlag_DisplayLogarithmic flag. Maybe you're using the wrong flags for those parameters?

    • We can correct 3). And we have to investigate on 4). Stay tuned for upcoming updates!

    Don't hesitate to send this feedback to the Kymatica team that develops AUM also as some of these "issues" are more AUM related.

    Again, thank you!

  • @j_liljedahl said:

    @bleassapp said:
    Hi, thank you for using BLEASS delay and for this very good feedback in the official BLEASS thread!

    • Regarding what you said in 1) & 5), we're gonna take a look but it is difficult for us to correct these problems since it is AUM who's managing to convert MIDI CC to Audio Unit Parameter values ... What's tricky here is that the middle value should be 63.5 then, which is impossible to reach because MIDI does not transmit decimal values ...

    AUM maps the 7 bit MIDI as follows: value = midiValue/127.0 so that 0 to 127 gives 0.0 to 1.0. It then scales this to the parameters actual min/max values with value * (maxValue-minValue) + minValue for linear params and pow(maxValue/minValue, value) * minValue for logarithmic parameters.

    Indeed since 7 bit MIDI doesn't have an integer corresponding to exactly the middle value, I don't see how this could be solved on my side in a good way. Dividing by 128 would not allow one to reach 1.0, which would be even worse.

    • About frequencies in HP or LP filter, yes it's traveling fast in the lower values because we expose our Audio Unit Parameters as frequencies ... if your MIDI CC curve is linear in AUM then it doesn't really match the nicely sounding frequency curve. We could fix that but it will result a lot of regressions for people who stores presets in the past. Let us take look, maybe exposing a second parameter "MIDI-CC dedicated" could correct this problem.

    AUM handles logarithmic params (such as frequencies), as mentioned above. It checks the param flags AudioUnitDisplayTypeIsLogarithmic(param.flags) which is Apple's macro that specifically checks the kAudioUnitParameterFlag_DisplayLogarithmic flag. Maybe you're using the wrong flags for those parameters?

    • We can correct 3). And we have to investigate on 4). Stay tuned for upcoming updates!

    Don't hesitate to send this feedback to the Kymatica team that develops AUM also as some of these "issues" are more AUM related.

    Again, thank you!

    Thanks man! It seems to me that a really under developed area is using physical controls with iPad music apps. Prob. Because it’s such a pain in the butt to do mappings. But every little step toward improving that interaction will help...

  • Actually, maybe it would make sense if AUM treated bipolar parameters specially so that MIDI cc value 64 corresponds to 0.0? (Like the MIDI standard says about cc10 pan control)
    If so, this would mean to scale the negative and positive part differently, so we get 64 negative values and 63 positive ones, since we still want 0 and 127 to correspond exactly to minimum and maximum.

  • @j_liljedahl said:
    Actually, maybe it would make sense if AUM treated bipolar parameters specially so that MIDI cc value 64 corresponds to 0.0? (Like the MIDI standard says about cc10 pan control)
    If so, this would mean to scale the negative and positive part differently, so we get 64 negative values and 63 positive ones, since we still want 0 and 127 to correspond exactly to minimum and maximum.

    Would it be a major pain in the ass to expand your mapping curve/line to allow more user mapping? Maybe have a user editable table “behind” the curve interface?

    I can see a table where user can enter to:from values and any empty cells are just interpolated based on nearest cells with values.

  • @sysexual said:
    @bleassapp can you explain to me what a Bleass is or what it stands for? is it a made up word?

    BLEASS is about BEATS & BASSES, so it's a made up word, which refers to "BLISS", the english word.
    got it ? :D

  • @j_liljedahl said:

    @bleassapp said:
    Hi, thank you for using BLEASS delay and for this very good feedback in the official BLEASS thread!

    • Regarding what you said in 1) & 5), we're gonna take a look but it is difficult for us to correct these problems since it is AUM who's managing to convert MIDI CC to Audio Unit Parameter values ... What's tricky here is that the middle value should be 63.5 then, which is impossible to reach because MIDI does not transmit decimal values ...

    AUM maps the 7 bit MIDI as follows: value = midiValue/127.0 so that 0 to 127 gives 0.0 to 1.0. It then scales this to the parameters actual min/max values with value * (maxValue-minValue) + minValue for linear params and pow(maxValue/minValue, value) * minValue for logarithmic parameters.

    Indeed since 7 bit MIDI doesn't have an integer corresponding to exactly the middle value, I don't see how this could be solved on my side in a good way. Dividing by 128 would not allow one to reach 1.0, which would be even worse.

    • About frequencies in HP or LP filter, yes it's traveling fast in the lower values because we expose our Audio Unit Parameters as frequencies ... if your MIDI CC curve is linear in AUM then it doesn't really match the nicely sounding frequency curve. We could fix that but it will result a lot of regressions for people who stores presets in the past. Let us take look, maybe exposing a second parameter "MIDI-CC dedicated" could correct this problem.

    AUM handles logarithmic params (such as frequencies), as mentioned above. It checks the param flags AudioUnitDisplayTypeIsLogarithmic(param.flags) which is Apple's macro that specifically checks the kAudioUnitParameterFlag_DisplayLogarithmic flag. Maybe you're using the wrong flags for those parameters?

    • We can correct 3). And we have to investigate on 4). Stay tuned for upcoming updates!

    Don't hesitate to send this feedback to the Kymatica team that develops AUM also as some of these "issues" are more AUM related.

    Again, thank you!

    Hi guys! First of all thanks to @j_liljedahl for hist valuable technical answers.
    So in the end it's our bad! We've failed to use the logarithmic flag (kAudioUnitParameterFlag_DisplayLogarithmic) for specific parameters who need to be "feeled" as logarithmic.
    Be sure that this will be corrected in the next BLEASS delay update.
    @MonkeyDrummer, Thank again for your great insight and hardcore testing!

    Again, thank you guys for helping us improving our app quality!

  • @bleassapp said:

    @j_liljedahl said:

    @bleassapp said:
    Hi, thank you for using BLEASS delay and for this very good feedback in the official BLEASS thread!

    • Regarding what you said in 1) & 5), we're gonna take a look but it is difficult for us to correct these problems since it is AUM who's managing to convert MIDI CC to Audio Unit Parameter values ... What's tricky here is that the middle value should be 63.5 then, which is impossible to reach because MIDI does not transmit decimal values ...

    AUM maps the 7 bit MIDI as follows: value = midiValue/127.0 so that 0 to 127 gives 0.0 to 1.0. It then scales this to the parameters actual min/max values with value * (maxValue-minValue) + minValue for linear params and pow(maxValue/minValue, value) * minValue for logarithmic parameters.

    Indeed since 7 bit MIDI doesn't have an integer corresponding to exactly the middle value, I don't see how this could be solved on my side in a good way. Dividing by 128 would not allow one to reach 1.0, which would be even worse.

    • About frequencies in HP or LP filter, yes it's traveling fast in the lower values because we expose our Audio Unit Parameters as frequencies ... if your MIDI CC curve is linear in AUM then it doesn't really match the nicely sounding frequency curve. We could fix that but it will result a lot of regressions for people who stores presets in the past. Let us take look, maybe exposing a second parameter "MIDI-CC dedicated" could correct this problem.

    AUM handles logarithmic params (such as frequencies), as mentioned above. It checks the param flags AudioUnitDisplayTypeIsLogarithmic(param.flags) which is Apple's macro that specifically checks the kAudioUnitParameterFlag_DisplayLogarithmic flag. Maybe you're using the wrong flags for those parameters?

    • We can correct 3). And we have to investigate on 4). Stay tuned for upcoming updates!

    Don't hesitate to send this feedback to the Kymatica team that develops AUM also as some of these "issues" are more AUM related.

    Again, thank you!

    Hi guys! First of all thanks to @j_liljedahl for hist valuable technical answers.
    So in the end it's our bad! We've failed to use the logarithmic flag (kAudioUnitParameterFlag_DisplayLogarithmic) for specific parameters who need to be "feeled" as logarithmic.
    Be sure that this will be corrected in the next BLEASS delay update.
    @MonkeyDrummer, Thank again for your great insight and hardcore testing!

    Again, thank you guys for helping us improving our app quality!

    Glad Incould help. It’s refreshing to see a dev that asks for input and actually works to fix things instead of the more typical response of ignoring the issue...

  • edited March 18

    @bleassapp wow - this is really good - easy to learn Just got demo but will get PRO.
    Not sure if in Pro version but if not can you add the Save box/tab available in all screens. Seems you have to go back back to get to Save. Also is there a way to take off all the flashing / blinking lights can get a bit too much on the eyes. Great app though Going to get beats going with this.
    1.How many Pads in full version? Can they be spiit into smaller squares to give more pads?
    2.How many Tracks in full version?
    3.Can I sample into this via external soundcard if yes maximum sampling time?
    4.Resample to Pads?
    5.Export 24bit or 16 only or both?
    6.Maximum sample time for Sample Import? 16/24bit or both?
    7.Is there record count in & metronome - I cannot find the settings?
    Sorry about the many questions but really really like this app :-)

  • @bleassapp is there an option in Pro version to copy/paste a sample to different pads & slice to pads?
    Audioshare Import or just files app and iCloud

  • @stormbeats to answer you :
    1. You have the same amount of Pads in the Pro version. BLEASS is live performance oriented, therefore we prefer using big fat pads. (and if you need, you can use up to 4 different Drum Machines for a total of 24 pads in one song)
    2. 4 tracks is the current "limitation" of BLEASS : for stability and performance stake, but also to boost creativity : making 4 tracks sound great and groovy is always a challenge. If you need more tracks, you can use several devices with Ableton link, ideal for live performance!
    3. You can record from an external soundcard output. The max size of samples is 10seconds, which is way more than needed to make percussive samples.
    4. resample and sending slices to pads is not a feature at the moment. You have to load a sample and edit it your own way in each pad, for more precision
    5. audio export is16 bits only (24 bits audio export would make more sense if BLEASS groovebox was a 32 tracks DAW :-)
    6. sample import : WAV 44100 16 bits (mono). We have to check if 24 bits files do import correctly, haven't tested yet! if you can give us a feedback on this, that would be awesome.
    7. no metronome or record count at the moment : ideally use a hihat or kick with the repeat function can be a good way to start a beat.
    8. Audioshare import is not available, yet you have files and iCloud functionalities.

  • @bleassapp said:
    @stormbeats to answer you :
    1. You have the same amount of Pads in the Pro version. BLEASS is live performance oriented, therefore we prefer using big fat pads. (and if you need, you can use up to 4 different Drum Machines for a total of 24 pads in one song)
    2. 4 tracks is the current "limitation" of BLEASS : for stability and performance stake, but also to boost creativity : making 4 tracks sound great and groovy is always a challenge. If you need more tracks, you can use several devices with Ableton link, ideal for live performance!
    3. You can record from an external soundcard output. The max size of samples is 10seconds, which is way more than needed to make percussive samples.
    4. resample and sending slices to pads is not a feature at the moment. You have to load a sample and edit it your own way in each pad, for more precision
    5. audio export is16 bits only (24 bits audio export would make more sense if BLEASS groovebox was a 32 tracks DAW :-)
    6. sample import : WAV 44100 16 bits (mono). We have to check if 24 bits files do import correctly, haven't tested yet! if you can give us a feedback on this, that would be awesome.
    7. no metronome or record count at the moment : ideally use a hihat or kick with the repeat function can be a good way to start a beat.
    8. Audioshare import is not available, yet you have files and iCloud functionalities.

    @bleassapp hi thanks for the info . Much appreciated. Respect to you for creating a really good app and your customer response. I can see the future of Bleass being Bliss :-) The filters are very good as well as the other effects. If possible the Save/Save as tab on all screens and if can be done in future plans some choke groups pad layering. Cheers again .

  • @bleassapp one last question is the Export also Multi Stem Export?

  • @stormbeats said:
    @bleassapp one last question is the Export also Multi Stem Export?

    it's not : it's a master export

  • @bleassapp said:

    @stormbeats said:
    @bleassapp one last question is the Export also Multi Stem Export?

    it's not : it's a master export

    @bleassapp ok thanks

  • NEW TUTORIAL!

  • I’ve got the pro version but don’t seem to have multiple outputs listed in Audiobus, is this possible?

  • @GrimLucky said:
    I’ve got the pro version but don’t seem to have multiple outputs listed in Audiobus, is this possible?

    @GrimLucky No

  • @stormbeats said:

    @GrimLucky said:
    I’ve got the pro version but don’t seem to have multiple outputs listed in Audiobus, is this possible?

    @GrimLucky No

    That's the point of my other post... They mention IAA support AND multi-outputs, which pretty much anyone here would interpret to mean exactly what it sounds like. But if you take out your lawyer glasses, they qualify it as individual outs to a sound card. I have no idea why in the F anyone would think that was something anyone wanted!

    It's ESPECIALLY baffling in the video they claim "clears things up" they are routing to their own damn AU fx?! WTF?!! So they are routing from an iPad, into an audio interface, out to a desk, then using an insert or send on the desk to route BACK INTO the iPad for the FX and then prob. back into the desk's return!!! why... in... the... hell...??! Insane latency issues aside, this is stupid...

    Yea, I'd much rather lug around a big audio card and a mixing desk than, oh I don't know... route them to different IAA channels in AUM like it seems to suggest...

    It's misleading (I don't think they intended to mislead) and I think it needs to be changed in the description to be more clear, as I'm obviously not the only one that interpreted it this way...

    I get he just wants to be different and "edgy", and I do think this app has some potential if some of the horrible UI elements are improved (you can't tap/drag most parameters.. You have to sit there an poke at + and - minus buttons like a damn woodpecker with a palsy!).

    It's a $3.00 app at this point.

Sign In or Register to comment.