feedback
23 views
Skip to first unread message
cip
Jan 10, 2011, 12:36:41 AM1/10/11
to Su-Preme MPA
Been playing around today, lots of potential here!
Questions:
- Whats millis? Sounds like milliseconds, but I'm not sure why that
would be a button..
- The sequences make sense (they're like patterns I take it), but what
are the tracks? Some kind of part layer? I'm not sure exactly how to
use them.
- Song mode is not working at the moment, right?
- Cutoff '("cut" in the sample edit) isn't supposed to do anything
yet, right?
Comments / wishlist:
- Some sort of step sequencing would be nice. Not sure of the best way
to do this because of the off-grid-ness (and I'm guessing you probably
want to stick with the hardware metaphor rather than go with a full-on
piano roll), but maybe the mp-you-know-what has a good solution. Some
way of sequencing volume changes on the hits is kind of missing.
- Would like to see effects + resampling for doing some sample
scuplting on-device. Would love EQ/decimator-bitcrush/compression/
flanger/distortion suite (even a simple implementation...). offline
rendering would be fine, though some sort of parameter control would
make it pretty powerful.
- Capability to sample from the mic would be nice (is that possible
currently?).
-I killed my other tasks, but latency is still an issue on my droid 2.
It's a bit weird - sometimes the latency is short, but it seems to
vary quite a bit from one hit to the next, which is in some ways worse
than a consistently long lag. I realize until the low latency NDK
versions of android get more widely adopted, your hands might be tied,
but if you guys could push further on this front, it would be worth
it, given how important unquantized beats are to hiphop.
- This isn't as important to me, but you'll probably want to think
about how to make it noob-friendlier so people don't poo-poo the app
rating when they get lost in the first 5 minutes with it. Maybe a
sweet default loop on ready to play on the first startup or
something...
Still though, it looks like a really good start, really looking
forward to seeing how it evolves! Android is definitely crying out for
an app like this. Will play with it some more and give more feedback
if that would be helpful... respect!
~C
Questions:
- Whats millis? Sounds like milliseconds, but I'm not sure why that
would be a button..
- The sequences make sense (they're like patterns I take it), but what
are the tracks? Some kind of part layer? I'm not sure exactly how to
use them.
- Song mode is not working at the moment, right?
- Cutoff '("cut" in the sample edit) isn't supposed to do anything
yet, right?
Comments / wishlist:
- Some sort of step sequencing would be nice. Not sure of the best way
to do this because of the off-grid-ness (and I'm guessing you probably
want to stick with the hardware metaphor rather than go with a full-on
piano roll), but maybe the mp-you-know-what has a good solution. Some
way of sequencing volume changes on the hits is kind of missing.
- Would like to see effects + resampling for doing some sample
scuplting on-device. Would love EQ/decimator-bitcrush/compression/
flanger/distortion suite (even a simple implementation...). offline
rendering would be fine, though some sort of parameter control would
make it pretty powerful.
- Capability to sample from the mic would be nice (is that possible
currently?).
-I killed my other tasks, but latency is still an issue on my droid 2.
It's a bit weird - sometimes the latency is short, but it seems to
vary quite a bit from one hit to the next, which is in some ways worse
than a consistently long lag. I realize until the low latency NDK
versions of android get more widely adopted, your hands might be tied,
but if you guys could push further on this front, it would be worth
it, given how important unquantized beats are to hiphop.
- This isn't as important to me, but you'll probably want to think
about how to make it noob-friendlier so people don't poo-poo the app
rating when they get lost in the first 5 minutes with it. Maybe a
sweet default loop on ready to play on the first startup or
something...
Still though, it looks like a really good start, really looking
forward to seeing how it evolves! Android is definitely crying out for
an app like this. Will play with it some more and give more feedback
if that would be helpful... respect!
~C
ivan
Jan 10, 2011, 1:50:09 AM1/10/11
to Su-Preme MPA
Cip,
Replies are below.
On Jan 10, 7:36 am, cip <austi...@gmail.com> wrote:
> Been playing around today, lots of potential here!
>
> Questions:
>
> - Whats millis? Sounds like milliseconds, but I'm not sure why that
> would be a button..
This is a toggle button to make the wheel more fine-grained. By
default it modifies most fields by 10s but if MILLIS is on, you work
on 1s.
> - The sequences make sense (they're like patterns I take it), but what
> are the tracks? Some kind of part layer? I'm not sure exactly how to
> use them.
That's right, tracks are layers on the same sequence. Thus you can
record kick and snare on one track, hats on another and piano on yet
another one. Tracks are recorded independently of each other. Another
advantage is the ability to regulate volume of each track in the seq.
> - Song mode is not working at the moment, right?
Right. It will in the release.
> - Cutoff '("cut" in the sample edit) isn't supposed to do anything
> yet, right?
It's actually the "cut group" setting. Samples in the same cut group
will cut each other when played back and recorded.
>
> Comments / wishlist:
>
> - Some sort of step sequencing would be nice. Not sure of the best way
> to do this because of the off-grid-ness (and I'm guessing you probably
> want to stick with the hardware metaphor rather than go with a full-on
> piano roll), but maybe the mp-you-know-what has a good solution. Some
> way of sequencing volume changes on the hits is kind of missing.
>
We'll have step recording in the first release.
> - Would like to see effects + resampling for doing some sample
> scuplting on-device. Would love EQ/decimator-bitcrush/compression/
> flanger/distortion suite (even a simple implementation...). offline
> rendering would be fine, though some sort of parameter control would
> make it pretty powerful.
>
Yeah, we do plan at least EQ/filters and reverb for one of the next
releases.
> - Capability to sample from the mic would be nice (is that possible
> currently?).
>
No, perhaps we might some day have a separate app to do that (it will
integrate with MPA).
> -I killed my other tasks, but latency is still an issue on my droid 2.
> It's a bit weird - sometimes the latency is short, but it seems to
> vary quite a bit from one hit to the next, which is in some ways worse
> than a consistently long lag. I realize until the low latency NDK
> versions of android get more widely adopted, your hands might be tied,
> but if you guys could push further on this front, it would be worth
> it, given how important unquantized beats are to hiphop.
>
That IS weird because we tested on Droid 2, plus I have Droid 1 and
the latency is good.
Supreme also recommends from his experience to try to go to settings
and disable background sync, if you can afford that.
If that problem persists, I'll ask you to send some logs to us.
> - This isn't as important to me, but you'll probably want to think
> about how to make it noob-friendlier so people don't poo-poo the app
> rating when they get lost in the first 5 minutes with it. Maybe a
> sweet default loop on ready to play on the first startup or
> something...
>
Yeah, that's right. We are considering this question. In fact, we are
already working on some videos to help users get around. In addition,
we will have a simpler sample editor etc.
> Still though, it looks like a really good start, really looking
> forward to seeing how it evolves! Android is definitely crying out for
> an app like this. Will play with it some more and give more feedback
> if that would be helpful... respect!
>
Thanks man. Glad you liked MPA. Have fun!
> ~C
Replies are below.
On Jan 10, 7:36 am, cip <austi...@gmail.com> wrote:
> Been playing around today, lots of potential here!
>
> Questions:
>
> - Whats millis? Sounds like milliseconds, but I'm not sure why that
> would be a button..
default it modifies most fields by 10s but if MILLIS is on, you work
on 1s.
> - The sequences make sense (they're like patterns I take it), but what
> are the tracks? Some kind of part layer? I'm not sure exactly how to
> use them.
record kick and snare on one track, hats on another and piano on yet
another one. Tracks are recorded independently of each other. Another
advantage is the ability to regulate volume of each track in the seq.
> - Song mode is not working at the moment, right?
> - Cutoff '("cut" in the sample edit) isn't supposed to do anything
> yet, right?
will cut each other when played back and recorded.
>
> Comments / wishlist:
>
> - Some sort of step sequencing would be nice. Not sure of the best way
> to do this because of the off-grid-ness (and I'm guessing you probably
> want to stick with the hardware metaphor rather than go with a full-on
> piano roll), but maybe the mp-you-know-what has a good solution. Some
> way of sequencing volume changes on the hits is kind of missing.
>
> - Would like to see effects + resampling for doing some sample
> scuplting on-device. Would love EQ/decimator-bitcrush/compression/
> flanger/distortion suite (even a simple implementation...). offline
> rendering would be fine, though some sort of parameter control would
> make it pretty powerful.
>
releases.
> - Capability to sample from the mic would be nice (is that possible
> currently?).
>
integrate with MPA).
> -I killed my other tasks, but latency is still an issue on my droid 2.
> It's a bit weird - sometimes the latency is short, but it seems to
> vary quite a bit from one hit to the next, which is in some ways worse
> than a consistently long lag. I realize until the low latency NDK
> versions of android get more widely adopted, your hands might be tied,
> but if you guys could push further on this front, it would be worth
> it, given how important unquantized beats are to hiphop.
>
the latency is good.
Supreme also recommends from his experience to try to go to settings
and disable background sync, if you can afford that.
If that problem persists, I'll ask you to send some logs to us.
> - This isn't as important to me, but you'll probably want to think
> about how to make it noob-friendlier so people don't poo-poo the app
> rating when they get lost in the first 5 minutes with it. Maybe a
> sweet default loop on ready to play on the first startup or
> something...
>
already working on some videos to help users get around. In addition,
we will have a simpler sample editor etc.
> Still though, it looks like a really good start, really looking
> forward to seeing how it evolves! Android is definitely crying out for
> an app like this. Will play with it some more and give more feedback
> if that would be helpful... respect!
>
> ~C
cip
Jan 10, 2011, 12:48:24 PM1/10/11
to Su-Preme MPA
Thanks for the insight.
re: step sequencing - it would be cool if you could have control over
fine-nudge timing of individual events.
Any plans to incorporate lower sampling rate samples? I think jasuto
renders things at 22khz... would be nice to bounce things back and
forth.
Speaking of lofi, downsampling (or maybe lower bit-depth) audio output
may be a nice option to have for compatability with underpowered
devices or to try to push the performance/responsiveness further on
higher end devices. I think sunvox does things at 18khz 12 bit or
something funky like that to enable enough computing horsepower for
real-time modular synth/effects chains on mobile devices. Maybe it's
too much work to support multiple sampling rates, but ... just an
idea.
BTW - nice trick rendering the mix for playback... talk about
squeezing out CPU cycles! I guess this imposes some limitations in
terms of real time control/tweaking, but those are constraints I can
deal with if it means better latency.
Will keep experimenting with the latency stuff and other features...
~C
re: step sequencing - it would be cool if you could have control over
fine-nudge timing of individual events.
Any plans to incorporate lower sampling rate samples? I think jasuto
renders things at 22khz... would be nice to bounce things back and
forth.
Speaking of lofi, downsampling (or maybe lower bit-depth) audio output
may be a nice option to have for compatability with underpowered
devices or to try to push the performance/responsiveness further on
higher end devices. I think sunvox does things at 18khz 12 bit or
something funky like that to enable enough computing horsepower for
real-time modular synth/effects chains on mobile devices. Maybe it's
too much work to support multiple sampling rates, but ... just an
idea.
BTW - nice trick rendering the mix for playback... talk about
squeezing out CPU cycles! I guess this imposes some limitations in
terms of real time control/tweaking, but those are constraints I can
deal with if it means better latency.
Will keep experimenting with the latency stuff and other features...
~C
ivan
Jan 10, 2011, 3:45:31 PM1/10/11
to Su-Preme MPA
Cip,
Did you check out our quantization feature? It's available in the MODE
-> TRACK screen.
We are working to support as many input formats as possible, so yes,
22050 should work fine at some point. Did you try?
Unfortunately, we are not going to do additional work to support
underperforming devices. In fact, we are targeting the higher end of
devices. In our opinion, the margin is moving very quickly so today's
high end devices are becoming average in a short time. So rather than
spending effort on supporting slower devices, we plan and implement
new cool features - some of which might indeed require a better
device. That is our strategy.
Glad you're enjoying MPA. We are very happy that there are guys like
you who care to get in touch with us. In a way, you become a developer
of the product :)
-Ivan
Did you check out our quantization feature? It's available in the MODE
-> TRACK screen.
We are working to support as many input formats as possible, so yes,
22050 should work fine at some point. Did you try?
Unfortunately, we are not going to do additional work to support
underperforming devices. In fact, we are targeting the higher end of
devices. In our opinion, the margin is moving very quickly so today's
high end devices are becoming average in a short time. So rather than
spending effort on supporting slower devices, we plan and implement
new cool features - some of which might indeed require a better
device. That is our strategy.
Glad you're enjoying MPA. We are very happy that there are guys like
you who care to get in touch with us. In a way, you become a developer
of the product :)
-Ivan
cip
Jan 10, 2011, 9:35:21 PM1/10/11
to Su-Preme MPA
> Did you check out our quantization feature? It's available in the MODE
> -> TRACK screen.
Yep! Nice, though I'm looking to play with the pocket though. Like
> -> TRACK screen.
let's nudge the bass a few ms before the beat and the snare a few ms
after... that sort of thing.
> We are working to support as many input formats as possible, so yes,
> 22050 should work fine at some point. Did you try?
preview the sample, but when I load it, there's an X by it. I assumed
this was a sampling rate issue, though I didn't double check the
samples on my computer.
> Unfortunately, we are not going to do additional work to support
> underperforming devices. In fact, we are targeting the higher end of
> devices. In our opinion, the margin is moving very quickly so today's
> high end devices are becoming average in a short time. So rather than
> spending effort on supporting slower devices, we plan and implement
> new cool features - some of which might indeed require a better
> device. That is our strategy.
relatively good phone (droid 2), I'd be willing to sacrifice sound
quality for latency reduction (if it made a difference, I might use
lower SR for recording, then up the SR for rendering). Still, I think
you're on the right track...
Reply all
Reply to author
Forward
0 new messages