Launchpad for iOS // Version 2.0 - Realtime Tempo & Link Support - Out Today

AndyPlankton

@gonekrazy3000 said:

@AndyPlankton said:

@gonekrazy3000 said:

@AndyPlankton said:

@TheMaestro said:
I was just including you in the conversation brother, as am I. I will create a track and bounce it to sound cloud later. I'm mixing it with one of the packs they have with my equipment, and samples. Loaded all of old guitar files into blocs and it broke the app. I literally had to reinstall the damn thing.

What happened to blocs ? Fail to start ? Let them know if you can, they'll want to know in order to fix it if it is caused by a bug.

pretty sure whatever engine tweak they did in the recent updates broke 32bit ipad support. it seems like ipad2-4 are all having various issues.

I'm guessing the new engine is based on the Blocs Wave one. Do you have issues with Blocs Wave too ?
They have said they use iPad 2 for development, rest assured that they will fix it.

Since the sections update to blocs my ipad3 can't even run 5 blocs before becoming unresponsive. And opening any bloc.the edit screen can take upto 10-15 seconds to display a waveform. Considering I could jam for hrs with 3-4 second waveform loading it's a considerable performance hit.

The iPad 3 is actually worse than the ipad2 they use to develop. I'm just a bit afraid they might abandon it completely.

It seems strange that having more space for loops (sections) would have a performance hit if you are not using that extra space. This does suggest that a fix can be made. Have confidence in them, they have delivered so far

gonekrazy3000

@AndyPlankton said:

@gonekrazy3000 said:

@AndyPlankton said:

@gonekrazy3000 said:

@AndyPlankton said:

@TheMaestro said:
I was just including you in the conversation brother, as am I. I will create a track and bounce it to sound cloud later. I'm mixing it with one of the packs they have with my equipment, and samples. Loaded all of old guitar files into blocs and it broke the app. I literally had to reinstall the damn thing.

What happened to blocs ? Fail to start ? Let them know if you can, they'll want to know in order to fix it if it is caused by a bug.

pretty sure whatever engine tweak they did in the recent updates broke 32bit ipad support. it seems like ipad2-4 are all having various issues.

I'm guessing the new engine is based on the Blocs Wave one. Do you have issues with Blocs Wave too ?
They have said they use iPad 2 for development, rest assured that they will fix it.

Since the sections update to blocs my ipad3 can't even run 5 blocs before becoming unresponsive. And opening any bloc.the edit screen can take upto 10-15 seconds to display a waveform. Considering I could jam for hrs with 3-4 second waveform loading it's a considerable performance hit.

The iPad 3 is actually worse than the ipad2 they use to develop. I'm just a bit afraid they might abandon it completely.

It seems strange that having more space for loops (sections) would have a performance hit if you are not using that extra space. This does suggest that a fix can be made. Have confidence in them, they have delivered so far

In addition to sections they mentioned some tweaks were made to improve performance. I have a feeling it's these same tweaks that might have caused the problem on older devices....

[Deleted User]

@Launchpadforios said:

@yug said:
Great update but seems that my iPad 2 is too slow for the new version. I can't get it to work without crackling and stuttering. The previous version used to work just fine.

Maybe it's time to update the compatibility section in the app description

Hey @yug, we're looking into this now. Our developers actually use iPad 2s to develop our apps, in order to encourage support even down to even these slow devices. Having said that, we're looking into this, and shall report back.

So, I have to state that version 3 is out but the problem still remains