SALOME - Simple Audio Sampler with MPE - Available now!

Gavinski

@brambos said:
Yes, I am already working on drag/drop, but iOS won’t let me use iCloud files which are not downloaded yet (with the little cloud icon). Is that normal with other apps too? (I never use drag drop because it’s so clunky)

Not sure, I never use icloud really. That's great about drag and drop! I know what you mean about it not being ideal tho - just trying to drag sth and end up almost deleting it 😂

HotStrange

@Gavinski said:

@brambos said:
Yes, I am already working on drag/drop, but iOS won’t let me use iCloud files which are not downloaded yet (with the little cloud icon). Is that normal with other apps too? (I never use drag drop because it’s so clunky)

Not sure, I never use icloud really. That's great about drag and drop! I know what you mean about it not being ideal tho - just trying to drag sth and end up almost deleting it 😂

lol that’s the worst 😂 I can tolerate it more with the extra benefits samplecrate has though. Like auditioning tracks.

brambos

@HotStrange said:

@brambos said:
Yes, I am already working on drag/drop, but iOS won’t let me use iCloud files which are not downloaded yet (with the little cloud icon). Is that normal with other apps too? (I never use drag drop because it’s so clunky)

So I can’t say for certain but I wanna say when you click on the sample that’s in the cloud it automatically downloads and then can be uploaded into the app. That’s how it’s always been for me anyway. Unless I’m misunderstanding what you mean.

No, that's the situation I'm talking about. Once it has downloaded itself it will import without a hiccup.
But I can also drag an icon that is still "in the cloud only", and that will not work.

And I can't programmatically force a file to pre-download, it seems (which I can understand).

I don't like releasing a feature that doesn't work in all common situations - as that will lead to a lot of emails to be answered

HotStrange

@brambos said:

@HotStrange said:

@brambos said:
Yes, I am already working on drag/drop, but iOS won’t let me use iCloud files which are not downloaded yet (with the little cloud icon). Is that normal with other apps too? (I never use drag drop because it’s so clunky)

So I can’t say for certain but I wanna say when you click on the sample that’s in the cloud it automatically downloads and then can be uploaded into the app. That’s how it’s always been for me anyway. Unless I’m misunderstanding what you mean.

No, that's the situation I'm talking about. Once it has downloaded itself it will import without a hiccup.
But I can also drag an icon that is still "in the cloud only", and that will not work.

And I can't programmatically force a file to pre-download, it seems (which I can understand).

I don't like releasing a feature that doesn't work in all common situations - as that will lead to a lot of emails to be answered

I don’t blame you at all. It’s easier with samplecrate, but I’m sure the less annoying emails, the better lol.

FWIW, I think an app working natively and importing directly from files is much easier so I prefer how it is now. I guess some people prefer drag and drop but it’s way more fiddly, imo.

brambos

@HotStrange said:

@brambos said:

@HotStrange said:

@brambos said:
Yes, I am already working on drag/drop, but iOS won’t let me use iCloud files which are not downloaded yet (with the little cloud icon). Is that normal with other apps too? (I never use drag drop because it’s so clunky)

So I can’t say for certain but I wanna say when you click on the sample that’s in the cloud it automatically downloads and then can be uploaded into the app. That’s how it’s always been for me anyway. Unless I’m misunderstanding what you mean.

No, that's the situation I'm talking about. Once it has downloaded itself it will import without a hiccup.
But I can also drag an icon that is still "in the cloud only", and that will not work.

And I can't programmatically force a file to pre-download, it seems (which I can understand).

I don't like releasing a feature that doesn't work in all common situations - as that will lead to a lot of emails to be answered

I don’t blame you at all. It’s easier with samplecrate, but I’m sure the less annoying emails, the better lol.

I think I can detect whether a file is offline available, or not, so I'll have to add a descriptive message and hope that explains the solution sufficiently.

HotStrange

@brambos said:

@HotStrange said:

@brambos said:

@HotStrange said:

@brambos said:
Yes, I am already working on drag/drop, but iOS won’t let me use iCloud files which are not downloaded yet (with the little cloud icon). Is that normal with other apps too? (I never use drag drop because it’s so clunky)

So I can’t say for certain but I wanna say when you click on the sample that’s in the cloud it automatically downloads and then can be uploaded into the app. That’s how it’s always been for me anyway. Unless I’m misunderstanding what you mean.

No, that's the situation I'm talking about. Once it has downloaded itself it will import without a hiccup.
But I can also drag an icon that is still "in the cloud only", and that will not work.

And I can't programmatically force a file to pre-download, it seems (which I can understand).

I don't like releasing a feature that doesn't work in all common situations - as that will lead to a lot of emails to be answered

I don’t blame you at all. It’s easier with samplecrate, but I’m sure the less annoying emails, the better lol.

I think I can detect whether a file is offline available, or not, so I'll have to add a descriptive message and hope that explains the solution sufficiently.

Maybe put a few of these bad boys **** and put it right at the top lol

Jumpercollins

@brambos said:

@HotStrange said:

@brambos said:
Yes, I am already working on drag/drop, but iOS won’t let me use iCloud files which are not downloaded yet (with the little cloud icon). Is that normal with other apps too? (I never use drag drop because it’s so clunky)

So I can’t say for certain but I wanna say when you click on the sample that’s in the cloud it automatically downloads and then can be uploaded into the app. That’s how it’s always been for me anyway. Unless I’m misunderstanding what you mean.

No, that's the situation I'm talking about. Once it has downloaded itself it will import without a hiccup.
But I can also drag an icon that is still "in the cloud only", and that will not work.

And I can't programmatically force a file to pre-download, it seems (which I can understand).

I don't like releasing a feature that doesn't work in all common situations - as that will lead to a lot of emails to be answered

@brambos

It’s strange some Apps can see iCloud samples eg Koala, some cannot.

I been chatting to Imaginando about it as they are having exactly the same problems trying to get it to work.

brambos

@Jumpercollins said:

@brambos said:

@HotStrange said:

@brambos said:
Yes, I am already working on drag/drop, but iOS won’t let me use iCloud files which are not downloaded yet (with the little cloud icon). Is that normal with other apps too? (I never use drag drop because it’s so clunky)

So I can’t say for certain but I wanna say when you click on the sample that’s in the cloud it automatically downloads and then can be uploaded into the app. That’s how it’s always been for me anyway. Unless I’m misunderstanding what you mean.

No, that's the situation I'm talking about. Once it has downloaded itself it will import without a hiccup.
But I can also drag an icon that is still "in the cloud only", and that will not work.

And I can't programmatically force a file to pre-download, it seems (which I can understand).

I don't like releasing a feature that doesn't work in all common situations - as that will lead to a lot of emails to be answered

@brambos

It’s strange some Apps can see iCloud samples eg Koala, some cannot.

I been chatting to Imaginando about it as they are having exactly the same problems trying to get it to work.

I can see them, but I can't force them to download in order to access them. And Apple's internal error messages aren't helpful.

So I'll leave it up to the user to tap the files to download them before importing.

Kashi

@bygjohn said:

@Samu said:

@brambos said:

@Samu said:

@Kashi said:
Hmm, I still don’t get the octave up/down thing….
If I want to play a sample at C1 and C2 simultaneously, for example, then do I have to open another instance of the app?

I think this must be a 'bug' since the latched notes don't 'move' when switching the octaves up/down which they should in order correctly indicate which notes are latched.

No it’s not a bug. Active notes stay visible at all times. That was how it is designed.

That means only one C can be playing, but it will remain always in view, to allow the “Faderboard” control method.

Bummer, it's sometimes handy do drone a 'sub octave'

One option is to switch up or down an octave, then use the note next to the one that’s being latched and use the per-note pitch bend to add the octave note.

Good idea. Cheers @bygjohn !

Gavinski

@Kashi said:

@bygjohn said:

@Samu said:

@brambos said:

@Samu said:

@Kashi said:
Hmm, I still don’t get the octave up/down thing….
If I want to play a sample at C1 and C2 simultaneously, for example, then do I have to open another instance of the app?

I think this must be a 'bug' since the latched notes don't 'move' when switching the octaves up/down which they should in order correctly indicate which notes are latched.

No it’s not a bug. Active notes stay visible at all times. That was how it is designed.

That means only one C can be playing, but it will remain always in view, to allow the “Faderboard” control method.

Bummer, it's sometimes handy do drone a 'sub octave'

One option is to switch up or down an octave, then use the note next to the one that’s being latched and use the per-note pitch bend to add the octave note.

Good idea. Cheers @bygjohn !

Yes, great idea - you can latch it down low, where the volume is imperceptible, then drag on the x axis to where you want it. I would really just prefer that you could latch the same note on different octaves, as in most keyboards. So I’ll probably stick with the workaround of using several keyboards if that ability is not added.

brambos

@Gavinski said:

@Kashi said:

@bygjohn said:

@Samu said:

@brambos said:

@Samu said:

@Kashi said:
Hmm, I still don’t get the octave up/down thing….
If I want to play a sample at C1 and C2 simultaneously, for example, then do I have to open another instance of the app?

I think this must be a 'bug' since the latched notes don't 'move' when switching the octaves up/down which they should in order correctly indicate which notes are latched.

No it’s not a bug. Active notes stay visible at all times. That was how it is designed.

That means only one C can be playing, but it will remain always in view, to allow the “Faderboard” control method.

Bummer, it's sometimes handy do drone a 'sub octave'

One option is to switch up or down an octave, then use the note next to the one that’s being latched and use the per-note pitch bend to add the octave note.

Good idea. Cheers @bygjohn !

Yes, great idea - you can latch it down low, where the volume is imperceptible, then drag on the x axis to where you want it. I would really just prefer that you could latch the same note on different octaves, as in most keyboards. So I’ll probably stick with the workaround of using several keyboards if that ability is not added.

Or, if you don't need the "Faderboard"-interface of Salome, you can use a conventional MPE controller instead. It works out of the box.

Gavinski

@brambos said:

@Gavinski said:

@Kashi said:

@bygjohn said:

@Samu said:

@brambos said:

@Samu said:

@Kashi said:
Hmm, I still don’t get the octave up/down thing….
If I want to play a sample at C1 and C2 simultaneously, for example, then do I have to open another instance of the app?

I think this must be a 'bug' since the latched notes don't 'move' when switching the octaves up/down which they should in order correctly indicate which notes are latched.

No it’s not a bug. Active notes stay visible at all times. That was how it is designed.

That means only one C can be playing, but it will remain always in view, to allow the “Faderboard” control method.

Bummer, it's sometimes handy do drone a 'sub octave'

One option is to switch up or down an octave, then use the note next to the one that’s being latched and use the per-note pitch bend to add the octave note.

Good idea. Cheers @bygjohn !

Yes, great idea - you can latch it down low, where the volume is imperceptible, then drag on the x axis to where you want it. I would really just prefer that you could latch the same note on different octaves, as in most keyboards. So I’ll probably stick with the workaround of using several keyboards if that ability is not added.

Or, if you don't need the "Faderboard"-interface of Salome, you can use a conventional MPE controller instead. It works out of the box.

Sure! The faderboard thing is super cool though! I just don't fully understand why we can't have the faderboard running across the various octaves.

brambos

@Gavinski said:

@brambos said:

@Gavinski said:

@Kashi said:

@bygjohn said:

@Samu said:

@brambos said:

@Samu said:

@Kashi said:
Hmm, I still don’t get the octave up/down thing….
If I want to play a sample at C1 and C2 simultaneously, for example, then do I have to open another instance of the app?

I think this must be a 'bug' since the latched notes don't 'move' when switching the octaves up/down which they should in order correctly indicate which notes are latched.

No it’s not a bug. Active notes stay visible at all times. That was how it is designed.

That means only one C can be playing, but it will remain always in view, to allow the “Faderboard” control method.

Bummer, it's sometimes handy do drone a 'sub octave'

One option is to switch up or down an octave, then use the note next to the one that’s being latched and use the per-note pitch bend to add the octave note.

Good idea. Cheers @bygjohn !

Yes, great idea - you can latch it down low, where the volume is imperceptible, then drag on the x axis to where you want it. I would really just prefer that you could latch the same note on different octaves, as in most keyboards. So I’ll probably stick with the workaround of using several keyboards if that ability is not added.

Or, if you don't need the "Faderboard"-interface of Salome, you can use a conventional MPE controller instead. It works out of the box.

Sure! The faderboard thing is super cool though! I just don't fully understand why we can't have the faderboard running across the various octaves.

Because I want to have all active faders visible at all times. So if you move between octaves, I want the active notes to stick around on the screen.

Or another way to think about it: every fader is assigned to a dedicated note (first fader is always C, second fader is always C#, etc.) and you can simply choose which octave each fader uses.

Gavinski

@brambos said:

@Gavinski said:

@brambos said:

@Gavinski said:

@Kashi said:

@bygjohn said:

@Samu said:

@brambos said:

@Samu said:

@Kashi said:
Hmm, I still don’t get the octave up/down thing….
If I want to play a sample at C1 and C2 simultaneously, for example, then do I have to open another instance of the app?

I think this must be a 'bug' since the latched notes don't 'move' when switching the octaves up/down which they should in order correctly indicate which notes are latched.

No it’s not a bug. Active notes stay visible at all times. That was how it is designed.

That means only one C can be playing, but it will remain always in view, to allow the “Faderboard” control method.

Bummer, it's sometimes handy do drone a 'sub octave'

One option is to switch up or down an octave, then use the note next to the one that’s being latched and use the per-note pitch bend to add the octave note.

Good idea. Cheers @bygjohn !

Yes, great idea - you can latch it down low, where the volume is imperceptible, then drag on the x axis to where you want it. I would really just prefer that you could latch the same note on different octaves, as in most keyboards. So I’ll probably stick with the workaround of using several keyboards if that ability is not added.

Or, if you don't need the "Faderboard"-interface of Salome, you can use a conventional MPE controller instead. It works out of the box.

Sure! The faderboard thing is super cool though! I just don't fully understand why we can't have the faderboard running across the various octaves.

Because I want to have all active faders visible at all times. So if you move between octaves, I want the active notes to stick around on the screen.

Or another way to think about it: every fader is assigned to a dedicated note (first fader is always C, second fader is always C#, etc.) and you can simply choose which octave each fader uses.

Yes, would it be desirable maybe to put a toggle for whether it would act like that or act the way the aum keyboard Latch works? Seems some here would love that.

bygjohn

@Gavinski said:

@brambos said:

@Gavinski said:

@brambos said:

@Gavinski said:

@Kashi said:

@bygjohn said:

@Samu said:

@brambos said:

@Samu said:

@Kashi said:
Hmm, I still don’t get the octave up/down thing….
If I want to play a sample at C1 and C2 simultaneously, for example, then do I have to open another instance of the app?

I think this must be a 'bug' since the latched notes don't 'move' when switching the octaves up/down which they should in order correctly indicate which notes are latched.

No it’s not a bug. Active notes stay visible at all times. That was how it is designed.

That means only one C can be playing, but it will remain always in view, to allow the “Faderboard” control method.

Bummer, it's sometimes handy do drone a 'sub octave'

One option is to switch up or down an octave, then use the note next to the one that’s being latched and use the per-note pitch bend to add the octave note.

Good idea. Cheers @bygjohn !

Yes, great idea - you can latch it down low, where the volume is imperceptible, then drag on the x axis to where you want it. I would really just prefer that you could latch the same note on different octaves, as in most keyboards. So I’ll probably stick with the workaround of using several keyboards if that ability is not added.

Or, if you don't need the "Faderboard"-interface of Salome, you can use a conventional MPE controller instead. It works out of the box.

Sure! The faderboard thing is super cool though! I just don't fully understand why we can't have the faderboard running across the various octaves.

Because I want to have all active faders visible at all times. So if you move between octaves, I want the active notes to stick around on the screen.

Or another way to think about it: every fader is assigned to a dedicated note (first fader is always C, second fader is always C#, etc.) and you can simply choose which octave each fader uses.

Yes, would it be desirable maybe to put a toggle for whether it would act like that or act the way the aum keyboard Latch works? Seems some here would love that.

@brambos Might be worth adding that description to the manual, so it’s clear it doesn’t work like a “normal” keyboard and manage expectations? Or maybe have it switchable like @Gavinski suggests.

Is there any possibility of making the controller available as a MIDI plugin, like you did with Mononoke Pads?

brambos

@bygjohn said:

@Gavinski said:

@brambos said:

@Gavinski said:

@brambos said:

@Gavinski said:

@Kashi said:

@bygjohn said:

@Samu said:

@brambos said:

@Samu said:

@Kashi said:
Hmm, I still don’t get the octave up/down thing….
If I want to play a sample at C1 and C2 simultaneously, for example, then do I have to open another instance of the app?

I think this must be a 'bug' since the latched notes don't 'move' when switching the octaves up/down which they should in order correctly indicate which notes are latched.

No it’s not a bug. Active notes stay visible at all times. That was how it is designed.

That means only one C can be playing, but it will remain always in view, to allow the “Faderboard” control method.

Bummer, it's sometimes handy do drone a 'sub octave'

One option is to switch up or down an octave, then use the note next to the one that’s being latched and use the per-note pitch bend to add the octave note.

Good idea. Cheers @bygjohn !

Yes, great idea - you can latch it down low, where the volume is imperceptible, then drag on the x axis to where you want it. I would really just prefer that you could latch the same note on different octaves, as in most keyboards. So I’ll probably stick with the workaround of using several keyboards if that ability is not added.

Or, if you don't need the "Faderboard"-interface of Salome, you can use a conventional MPE controller instead. It works out of the box.

Sure! The faderboard thing is super cool though! I just don't fully understand why we can't have the faderboard running across the various octaves.

Because I want to have all active faders visible at all times. So if you move between octaves, I want the active notes to stick around on the screen.

Or another way to think about it: every fader is assigned to a dedicated note (first fader is always C, second fader is always C#, etc.) and you can simply choose which octave each fader uses.

Yes, would it be desirable maybe to put a toggle for whether it would act like that or act the way the aum keyboard Latch works? Seems some here would love that.

@brambos Might be worth adding that description to the manual, so it’s clear it doesn’t work like a “normal” keyboard and manage expectations?

It's funny. If this were a hardware device, people would not expect that behavior, but somehow in software some people do

Is there any possibility of making the controller available as a MIDI plugin, like you did with Mononoke Pads?

You can already use it as a MIDI/MPE controller. Just mute the volume and point the MPE output of Salome at any MPE compatible synth!

Gavinski

@brambos said:

@bygjohn said:

@Gavinski said:

@brambos said:

@Gavinski said:

@brambos said:

@Gavinski said:

@Kashi said:

@bygjohn said:

@Samu said:

@brambos said:

@Samu said:

@Kashi said:
Hmm, I still don’t get the octave up/down thing….
If I want to play a sample at C1 and C2 simultaneously, for example, then do I have to open another instance of the app?

I think this must be a 'bug' since the latched notes don't 'move' when switching the octaves up/down which they should in order correctly indicate which notes are latched.

No it’s not a bug. Active notes stay visible at all times. That was how it is designed.

That means only one C can be playing, but it will remain always in view, to allow the “Faderboard” control method.

Bummer, it's sometimes handy do drone a 'sub octave'

One option is to switch up or down an octave, then use the note next to the one that’s being latched and use the per-note pitch bend to add the octave note.

Good idea. Cheers @bygjohn !

Yes, great idea - you can latch it down low, where the volume is imperceptible, then drag on the x axis to where you want it. I would really just prefer that you could latch the same note on different octaves, as in most keyboards. So I’ll probably stick with the workaround of using several keyboards if that ability is not added.

Or, if you don't need the "Faderboard"-interface of Salome, you can use a conventional MPE controller instead. It works out of the box.

Sure! The faderboard thing is super cool though! I just don't fully understand why we can't have the faderboard running across the various octaves.

Because I want to have all active faders visible at all times. So if you move between octaves, I want the active notes to stick around on the screen.

Or another way to think about it: every fader is assigned to a dedicated note (first fader is always C, second fader is always C#, etc.) and you can simply choose which octave each fader uses.

Yes, would it be desirable maybe to put a toggle for whether it would act like that or act the way the aum keyboard Latch works? Seems some here would love that.

@brambos Might be worth adding that description to the manual, so it’s clear it doesn’t work like a “normal” keyboard and manage expectations?

It's funny. If this were a hardware device, people would not expect that behavior, but somehow in software some people do

Is there any possibility of making the controller available as a MIDI plugin, like you did with Mononoke Pads?

You can already use it as a MIDI/MPE controller. Just mute the volume and point the MPE output of Salome at any MPE compatible synth!

Hardware and software are totally different though, of course people have different expectations! Being able to latch the same note on different octaves is super useful. As is the Faderboard thing. The 2 together would be a powerful and convenient combo!

brambos

@Gavinski said:

@brambos said:

@bygjohn said:

@Gavinski said:

@brambos said:

@Gavinski said:

@brambos said:

@Gavinski said:

@Kashi said:

@bygjohn said:

@Samu said:

@brambos said:

@Samu said:

@Kashi said:
Hmm, I still don’t get the octave up/down thing….
If I want to play a sample at C1 and C2 simultaneously, for example, then do I have to open another instance of the app?

I think this must be a 'bug' since the latched notes don't 'move' when switching the octaves up/down which they should in order correctly indicate which notes are latched.

No it’s not a bug. Active notes stay visible at all times. That was how it is designed.

That means only one C can be playing, but it will remain always in view, to allow the “Faderboard” control method.

Bummer, it's sometimes handy do drone a 'sub octave'

One option is to switch up or down an octave, then use the note next to the one that’s being latched and use the per-note pitch bend to add the octave note.

Good idea. Cheers @bygjohn !

Yes, great idea - you can latch it down low, where the volume is imperceptible, then drag on the x axis to where you want it. I would really just prefer that you could latch the same note on different octaves, as in most keyboards. So I’ll probably stick with the workaround of using several keyboards if that ability is not added.

Or, if you don't need the "Faderboard"-interface of Salome, you can use a conventional MPE controller instead. It works out of the box.

Sure! The faderboard thing is super cool though! I just don't fully understand why we can't have the faderboard running across the various octaves.

Because I want to have all active faders visible at all times. So if you move between octaves, I want the active notes to stick around on the screen.

Or another way to think about it: every fader is assigned to a dedicated note (first fader is always C, second fader is always C#, etc.) and you can simply choose which octave each fader uses.

Yes, would it be desirable maybe to put a toggle for whether it would act like that or act the way the aum keyboard Latch works? Seems some here would love that.

@brambos Might be worth adding that description to the manual, so it’s clear it doesn’t work like a “normal” keyboard and manage expectations?

It's funny. If this were a hardware device, people would not expect that behavior, but somehow in software some people do

Is there any possibility of making the controller available as a MIDI plugin, like you did with Mononoke Pads?

You can already use it as a MIDI/MPE controller. Just mute the volume and point the MPE output of Salome at any MPE compatible synth!

Hardware and software are totally different though

But I tend to design my UIs in such a way that they could be executed in hardware with only minimal adaptations

Samu

@Gavinski said:

Hardware and software are totally different though, of course people have different expectations! Being able to latch the same note on different octaves is super useful. As is the Faderboard thing. The 2 together would be a powerful and convenient combo!

+1

unlink

Oh so you can't latch the same note in different octaves? A bit of a shame.

skiphunt

OMG! I’ve only been playing with this for a little under an hour and I’m obsessed 🤩 with this app!

I’m going to have a blast with this one… can’t wait to play with it for weird field soundtrack recordings too.

Bravo & Gracias 🙏 @brambos !!!

gusgranite

@brambos said:

@Gavinski said:

@brambos said:

@bygjohn said:

@Gavinski said:

@brambos said:

@Gavinski said:

@brambos said:

@Gavinski said:

@Kashi said:

@bygjohn said:

@Samu said:

@brambos said:

@Samu said:

@Kashi said:
Hmm, I still don’t get the octave up/down thing….
If I want to play a sample at C1 and C2 simultaneously, for example, then do I have to open another instance of the app?

I think this must be a 'bug' since the latched notes don't 'move' when switching the octaves up/down which they should in order correctly indicate which notes are latched.

No it’s not a bug. Active notes stay visible at all times. That was how it is designed.

That means only one C can be playing, but it will remain always in view, to allow the “Faderboard” control method.

Bummer, it's sometimes handy do drone a 'sub octave'

One option is to switch up or down an octave, then use the note next to the one that’s being latched and use the per-note pitch bend to add the octave note.

Good idea. Cheers @bygjohn !

Yes, great idea - you can latch it down low, where the volume is imperceptible, then drag on the x axis to where you want it. I would really just prefer that you could latch the same note on different octaves, as in most keyboards. So I’ll probably stick with the workaround of using several keyboards if that ability is not added.

Or, if you don't need the "Faderboard"-interface of Salome, you can use a conventional MPE controller instead. It works out of the box.

Sure! The faderboard thing is super cool though! I just don't fully understand why we can't have the faderboard running across the various octaves.

Because I want to have all active faders visible at all times. So if you move between octaves, I want the active notes to stick around on the screen.

Or another way to think about it: every fader is assigned to a dedicated note (first fader is always C, second fader is always C#, etc.) and you can simply choose which octave each fader uses.

Yes, would it be desirable maybe to put a toggle for whether it would act like that or act the way the aum keyboard Latch works? Seems some here would love that.

@brambos Might be worth adding that description to the manual, so it’s clear it doesn’t work like a “normal” keyboard and manage expectations?

It's funny. If this were a hardware device, people would not expect that behavior, but somehow in software some people do

Is there any possibility of making the controller available as a MIDI plugin, like you did with Mononoke Pads?

You can already use it as a MIDI/MPE controller. Just mute the volume and point the MPE output of Salome at any MPE compatible synth!

Hardware and software are totally different though

But I tend to design my UIs in such a way that they could be executed in hardware with only minimal adaptations

RESPECT!

Love that philosophy. It really shows in your design decisions.

espiegel123

@brambos said:
Yes, I am already working on drag/drop, but iOS won’t let me use iCloud files which are not downloaded yet (with the little cloud icon). Is that normal with other apps too? (I never use drag drop because it’s so clunky)

That is normal…unfortunately

Model10000

Thanks for considering drag and drop. Will def pick this up. Personally, I never use files in icloud, only downloaded in the on my ipad section. I could see Photos app screen recordings, drag to converted audio into Salome being more interesting than icloud, but really will stop at a request to drag and drop from Files/Sample Crate. Totally understand not wanting to deal with any admin/bug reports, even just one nasty one can kills a day's creativity. Sort of the same I feel about recreating sample structures in new app browsers too though

oddSTAR

I haven't actually bought it yet but just wanted to say I'm very excited about the idea of this app, @brambos ! Thanks for making it!

mikewb

@Model10000 said:
Thanks for considering drag and drop. Will def pick this up. Personally, I never use files in icloud, only downloaded in the on my ipad section. I could see Photos app screen recordings, drag to converted audio into Salome being more interesting than icloud, but really will stop at a request to drag and drop from Files/Sample Crate. Totally understand not wanting to deal with any admin/bug reports, even just one nasty one can kills a day's creativity. Sort of the same I feel about recreating sample structures in new app browsers too though

He just announced via twitter that the next update will contain drag and drop from the files app. I nice ease of workflow (for some) to an already great mpe sampler.

ambrosiajam

Can’t wait to mess around with this on my various guitars and other noisemakers

cytone

Hopefully the drag and drop will also be added to Fluss 😊

brambos

Gavinski

@brambos said:

Sexy!