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.
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.
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.
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.
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.
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@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.
Zynewave@LiquidProj3ct wrote:
I didn’t see thcilnnahoj video, so hopefully this could be the same problem. Anyway this was the problem I reported in the support thread.
When I do a master offline bouncing there is some parts in random tracks which….
Please try beta3, and let me know if you still have these issues.
Zynewave@Zynewave wrote:
@thcilnnahoj wrote:
Hmm, I’m afraid I don’t see any change from how it was before… are you sure you uploaded the correct version? 😛
Video here: http://www.youtube.com/watch?v=-7NxUCJ96OY (only just uploaded; should become available soon)
It might be interesting to know it happens even when you put the bounce track before the effect that’s creating latency.
Bug confirmed. Thanks for the video. This is a different latency bug than the one I already have fixed. The fixed bug was a blank gap appearing at the start of a track with latency plugins. I’ll start looking at this tomorrow, and upload a new beta when it’s fixed.
Wow :shock:, that was a good bug to fix. Please try beta3 and let me know if it fixes all your issues. I remember you once reported a problem with one of your projects, where Nucleum would misbehave at a certain point on the timeline. Please check if this is still present with beta3.
ZynewaveThe concern some people are expressing in this topic is perhaps based on some misunderstandings. I’ll try to clarify a few things:
It is possibly misleading to name the app “Mobium”, because in essence it is Podium.
I’m not going to make Mobium into a toy. It is going to be the full Podium DAW, just with a different default editor layout. Some of the advanced Podium features will, at least initially, be hidden from the Mobium UI. For example, the track tags and editor profile customization will not be available in Mobium.
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.
I’m not going to work on features specifically for Mobium. Any future feature development will seamlessly make its way into both Mobium and Podium. If my plan was to make Mobium into a different beast, I would never have started this experiment. I started this project because I found a simple way to port Podium to another OS, and thereby make Podium available to a larger audience.
Zynewave@H-man wrote:
@Zynewave wrote:
@H-man wrote:
I am intrigued buy the multi-touch aspect tho, and would be pretty enthusiastic about a remote-control capability for the “full-version”. Given the challenges of instruments etc, could this be a half-way step to full mobility?
If you mean an app that can show and control the UI of Podium running on your PC, then that is an entirely different app that would require extensive coding. For that purpose I would suggest trying some of the many available remote-desktop connection apps.
Sooo ..do you expect to integrate the touch features with the main app as well as the mobile app?
I really like the idea of being able to use multi-touch for midi/paramter curve editing.
Yes. The touch support will be available in both Mobium and Podium. The touch support is the same, whether it is Podium running on an iPhone, or Podium running on a Windows 7 all-in-one PC with a 24″ multitouch-screen.
Zynewave@khaos wrote:
I think you’re dreaming if you think that 95% of music will be made with a primary mobile devices in 5 years..
If you want to target creative musicians, built a matrix like interface in Podium like there is in Ableton Live, put in OSC support, add a sampler, a looper…
I’m not saying that 95% of the music you hear in the radio is going to originate on a tablet device. In the 95% I’m including “teenagers” that are doing their first music experiments on their iDevice to figure out if they can become the next pop-idol. And in 5 years, I still expect the majority of users to have a PC/Mac besides their tablet device. I just see the tablet form factor as an excellent tool for capturing musical ideas, field recordings, etc.
Zynewave@Infinitoar wrote:
… I was wondering my next PC build will be having a x64bit O.S. , namely Windows Vista Ultimate, but I was wondering does this mean there is no x64bit Podium version on ANY x64bit version of Windows or just Windows 7? It may sound stupid to ask, but I figure it’s also good to know, just in case I have to have one HDD with a windows x32bit version and another with a x64bit version.
You should be able to run the current Podium 32bit version on any 64bit Windows OS. The main limitation is that Podium won’t be able to use more than 4 GB RAM. However, if you use the jbridge wrapper plugin, you can go beyond the 4 GB for each plugin.
Plenty of users are running Podium on 64bit Windows 7, according to this poll:
Zynewave@ronin wrote:
@Zynewave wrote:
@ronin wrote:
Well, I could help testing those builds if you like.
At the time I think Conquistador tested the x64 build I made, and it didn’t work. So I left it there. I need to run it in a debugger to find where it goes wrong.
I may be able to do that too but probably you would have to provide a build with debugging information compiled in. At least a build with some symbols in it would do so I can provide some more or less valid stack traces.
Thanks for the offer, but I fear it will take a lot of beta versions before it will be working. It’s going to be much quicker if I can step through the code and fix things as I go along. Even if we do get it working, I won’t be releasing it until I have an x64 Windows machine that I can test with before each new release.