CAUSTIC 1.1 adds lots of new features

[RPH]

Bought a Asus transformer TF101 Tablet 16GB, Caustic runs great on it.
The tablet is quite powerfull, think Caustic barely uses CPU power on the tablet ( if it's a CPU usage bar in the lower left ).
If developers decide to create tablet ( android 3.x ) versions, there is a lot of room for added features i think..( nvidia tegra2 processor rules! )
Graphics are a bit blown up, but looks ok.

Cheers,
Rob.

[Numanoid]

I really want to try Caustic, but seems my phone can't run it.

I've got a ZTE Blade phone:

-3,5" screen, 800x480 pixels resolution
-600 MHz ARM 11 processor, Adreno 200 GPU, Qualcomm MSM7227 chipset
-Android 2.1
http://www.gsmarena.com/zte_blade-3391.php

Is the specs of the phone too low, or is the problem that it's running on Android 2.1?

[SingleCell]

I really want to try Caustic, but seems my phone can't run it.

I've got a ZTE Blade phone:

-3,5" screen, 800x480 pixels resolution
-600 MHz ARM 11 processor, Adreno 200 GPU, Qualcomm MSM7227 chipset
-Android 2.1
http://www.gsmarena.com/zte_blade-3391.php

Is the specs of the phone too low, or is the problem that it's running on Android 2.1?

The ZTE Blade (Orange SanFrancisco) is a bit of an exception. It's got a large enough screen but gets filtered on the market because the processor class is ARMv6 instead of the required ARMv7. Technically, the processor is underpowered but I've had one user report back that CAUSTIC actually runs ok on it.

I'm trying to sort out my market listing to add this phone, but it's tricky...

In the meantime if you're interested, here's the special ZTEBlade build I put together for testing. No garantees on performance though, you'll just have to try it and report back.

http://dl.dropbox.com/u/28029604/Caustic_ARMv6.apk

[Numanoid]

Thanks a lot!

Had no problem installing it now.

It runs, and works.

First impressions is that there is some problems with latency, but I look forward to diving further into the programme

[SingleCell]

First impressions is that there is some problems with latency, but I look forward to diving further into the programme

Yup, that's the state of things on Android right now, as others have mentioned in your previous thread. Now you know why there aren't more synths.

Caustic, like most other music apps, creates the smallest buffer possible but on most devices that's still too big. To get your device's audio latency, pull up the menu from inside the app, the value is given there.

Until Google addresses this, there nothing devs can do. Which is why Caustic and most other apps rely on sequencing. The only reason I put the keyboards there was to help design and preview sounds.

Anyway, enjoy the app.

[fred-hal]

Awesome app, is this the place for feature requests?

It would be nice to be able to easier export the subsynth patch as .wav (simple C4 or something) or even directly into the sample based devices.

[SingleCell]

Awesome app, is this the place for feature requests?

It would be nice to be able to easier export the subsynth patch as .wav (simple C4 or something) or even directly into the sample based devices.

Thanks! A better place to discuss features is the dev email (causticapp@gmail.com) because it's easier to remember ideas if they're all in one place. Your feature is interesting (and has been asked before) but I have some usage questions if you're willing to discuss a little... on email.

[fred-hal]

Awesome app, is this the place for feature requests?

It would be nice to be able to easier export the subsynth patch as .wav (simple C4 or something) or even directly into the sample based devices.

Thanks! A better place to discuss features is the dev email (causticapp@gmail.com) because it's easier to remember ideas if they're all in one place. Your feature is interesting (and has been asked before) but I have some usage questions if you're willing to discuss a little... on email.

Coolies, u got PM

[UltraJv]

I really want to try Caustic, but seems my phone can't run it.

I've got a ZTE Blade phone:

-3,5" screen, 800x480 pixels resolution
-600 MHz ARM 11 processor, Adreno 200 GPU, Qualcomm MSM7227 chipset
-Android 2.1
http://www.gsmarena.com/zte_blade-3391.php

Is the specs of the phone too low, or is the problem that it's running on Android 2.1?

I tried this on my LG GT540 which is low spec ARM6 and it works here too, fantastic stuff

[SingleCell]

I tried this on my LG GT540 which is low spec ARM6 and it works here too, fantastic stuff

I bet the graphics aren't very clear on that phone, with its low resolution, some of the thin lines in the Beatbox and Sequencer are probably missing.

Still, glad to hear it runs.

I'm working on a stripped down version that has bigger controls and a reduced set of machines for low-spec phones. It'll be more like ReBirth, 2x 303's and a simple drum sequencer.

[maximilians1]

I'm working on a stripped down version that has bigger controls and a reduced set of machines for low-spec phones. It'll be more like ReBirth, 2x 303's and a simple drum sequencer.

thats sound great!

[maximilians1]

First impressions is that there is some problems with latency, but I look forward to diving further into the programme

Yup, that's the state of things on Android right now, as others have mentioned in your previous thread. Now you know why there aren't more synths.

Caustic, like most other music apps, creates the smallest buffer possible but on most devices that's still too big. To get your device's audio latency, pull up the menu from inside the app, the value is given there.

Until Google addresses this, there nothing devs can do. Which is why Caustic and most other apps rely on sequencing. The only reason I put the keyboards there was to help design and preview sounds.

Anyway, enjoy the app.

Just wondering will the gingerbread update fix the latency issue? Google mentioned something about real time audio with gingerbread but I havn't read anything about how the update effects music apps.

[Numanoid]

I was just looking at a low price 5" android tablet called Kendo M5 (I think maybe it is in only Scandinavia this name is used), quick specs is:
-800x480 resolution
-Android 1.5 (can be upgraded to 2.1)
-600MHz Dual-Core processor
-128 MB RAM, 4 GB internal memory

Is it known if this can run Caustic?

[SingleCell]

I'd be worried about a tablet that's not even on Android 2.1 ... that's been out for almost two years now.

Odds are that 600 MHz processor will be underpowered for Caustic and most other basic tasks on a screen that big. Phones with those kinds of hardware specs pair up better with small screen (320x240) to lessen the load on the graphics chip.

Also, I din't know anyone made 600MHz dual-core processors, suspicious ... from a quick Googleing on that tablet, I'm not even sure you can get the Android market on it.

[Numanoid]

I'd be worried about a tablet that's not even on Android 2.1 ... that's been out for almost two years now.

Odds are that 600 MHz processor will be underpowered for Caustic and most other basic tasks on a screen that big. Phones with those kinds of hardware specs pair up better with small screen (320x240) to lessen the load on the graphics chip.

Also, I din't know anyone made 600MHz dual-core processors, suspicious ... from a quick Googleing on that tablet, I'm not even sure you can get the Android market on it.

Online community in Denmark have made a firmware upgrade that updates to android 2.1 and allows for android market.

But I agree with your comments the specs are probably too low to run caustic properly.