sobaka.
kingtubbyIt’s not something I see myself ever using, but FWIW, I think it’s a good move for Frits and the future of Zynewave.
Zynewave@H-man wrote:
@Zynewave wrote:
The screenshots you see in my first post in this topic is the full Podium 2.40, where I just have modified the default editor profiles to fit on the smaller screen.
So what’s it like? You said in a previous post that you were excited about the project (or was it the possibilities?). Does it feel workable even on the touch?
I have not fully implemented the multi-touch gestures yet. There are some gestures that needs to be tested in real life before I know if it feels intuitive.
I think the iPhone/iPod 3.5″ display is too small for serious arrangement work. It will be handy as a portable recorder, and as a quick way to make beats in the drum map editor. I would not find it enjoyable to work on a full arrangement. For that, you’ll need a tablet size device.
LionHas this been tested on android, at least in the emulator?
This is really making me want the archos 43 even more, which seemed impossible before this. 😆
Zynewave@4mica wrote:
No VST support is alright, if you get these 3rd party plugs….would it be possible, you think, to integrate the sampler/synth/effects into regular Podium?
The embedding of plugins is something I think would also be a good idea for Podium:
The zSuite plugins are currently compiled as independent projects that build the dll files. Instead of these separate projects, I would include the plugin source files in the main Podium project, and call the plugin code directly instead of through the dll interface. This will work on iOS because the zSuite plugins do not have their own native UI editor, and thus are not using any Windows specific functionality. All plugin UIs would need to be implemented in Podium, like it is done with the zSuite plugins.
Having the plugins embedded this way is more efficient, and it will also make it easier for me to implement new plugins in the future. Using the VST interface to access the embedded plugins means it will be easier to take existing VST plugin projects and repack them for compilation into Mobium/Podium.
Zynewave@Lion wrote:
Has this been tested on android, at least in the emulator?
This is really making me want the archos 43 even more, which seemed impossible before this. 😆
I don’t have an Android device to test with. The development tool I’m using creates one executable file that is used for both iPhone and Android devices. However, I’m still not sure that this development tool is the right choice. I may encounter some feature limitations that will make it impossible to use it for the completed Mobium. So please don’t buy Android devices expecting that Mobium will appear on Android.
LionTry the emulator, thats what they have that for 😛
Either way, I’m getting that device. This doesn’t make or break such decision.
Zynewave@Lion wrote:
Try the emulator, thats what they have that for 😛
Either way, I’m getting that device. This doesn’t make or break such decision.
There is no dedicated Android emulator. There is an emulator for the executable file which is supposed to work identically on iOS and Android devices, but I can’t say for sure if it will work on Android. There are a lot of different hardware specs for Android devices, so there may be memory problems or timing problems, etc.
LionThere is so, In the the Android SDK.
Unless I’m mistaken here.
Zynewave@Lion wrote:
There is so, In the the Android SDK.
Unless I’m mistaken here.
Yes, but I’m not using the Android SDK.
LionI THINK you just run the emu and load up whatever app you’re testing.
I’m not entirely sure, I haven’t gotten my hands wet in android development yet.
But I’ve seen the Android Emu start in the OS itself and not straight into whatever app in question. From there, I’m assuming you can load the apk like you would on a device itself.
Still, I’m not entirely sure as I haven’t dove into it myself.
Zynewave@Lion wrote:
I THINK you just run the emu and load up whatever app you’re testing.
I’m not entirely sure, I haven’t gotten my hands wet in android development yet.
But I’ve seen the Android Emu start in the OS itself and not straight into whatever app in question. From there, I’m assuming you can load the apk like you would on a device itself.
Still, I’m not entirely sure as I haven’t dove into it myself.
That is correct. I guess I could download the Android SDK and test with the emulator, but one of the benefits of the tool I’m using is that I don’t have to deal with the native development environments for iOS, Android, WebOS, Maemo, Symbian, etc. Saves me a lot of time.
pj geerlings@a while back Zynewave wrote:
… If I publish a list of “things to come within 6 months”, then I assume you would expect me to fulfill that time schedule. …
quite true, if you ask me 😉
If you choose not make any commitments then what message is being sent about the future of Podium?
-pj
Zynewave@pj geerlings wrote:
@a while back Zynewave wrote:
… If I publish a list of “things to come within 6 months”, then I assume you would expect me to fulfill that time schedule. …
quite true, if you ask me 😉
If you choose not make any commitments then what message is being sent about the future of Podium?
-pj
What message do you receive?
I think I’ve made plenty of commitments to future feature updates. I just haven’t put them down in a time-schedule.
Is it really that unusual? Can you point me to some examples of other host developers, that publicly announce long-term development time-schedules?
I’ve been doing it this way since the beginning, years ago. People can look back at the release history, and determine if they feel Podium is evolving in a good direction.
pj geerlings@Zynewave wrote:
… What message do you receive? …
Excellent question! Thank you for asking
The messages I’ve gotten lately …
() The smaller screen ( & touch screen ) mobile platforms are more sexy than desk top
… because …
() GUI enhancements to directly support smaller screens have received quite a bit of attention lately
… which strongly suggests …
() bug fixes and feature requests which are not specific to the mobile market may continue to be be prioritized lower
… the direct result of which is …
() Some bug fixes and feature requests may not even appear on a road map any time “soon”
Perhaps none of this matters because it is your baby Frits – and I will defer to you to raise it properly 😉
May you have all the success you desire
-pj
Zynewave@pj geerlings wrote:
The messages I’ve gotten lately …
() The smaller screen ( & touch screen ) mobile platforms are more sexy than desk top
… because …
() GUI enhancements to directly support smaller screens have received quite a bit of attention lately
… which strongly suggests …
() bug fixes and feature requests which are not specific to the mobile market may continue to be be prioritized lower
… the direct result of which is …
() Some bug fixes and feature requests may not even appear on a road map any time “soon”
If you follow the discussions and my posts in this forum, you should know that my development focus changes direction in small steps, as a consequence of the frequent 0.01 version updates. That a number of updates have focused on a certain area should not be taken as an indication that I’m heading in that direction indefinitely.
I hope users realize that I’m not neglecting certain features just because a few 0.01 updates are concentrating on a specific area. Otherwise, my other option is to be silent about what I’m working on presently, and only release 0.1 or 0.5 version updates each 6 months. These larger updates will then have a wider range of features that hopefully will include something useful for most users.