Zynewave@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.
Zynewave@Trancit wrote:
I don´t know…I believe, that “serious” but as well creative producer will not use a mobile phone or pad as much as you think in the next 5-10 years…and development of cpu´s for mobile hardware will very soon reach their limit in point of cooling…remember how much cooling you need in actual PC´s for the given power, that´s impossible to realize in mobile hardware, even laptop´s are far behind “normal” PCs…
Perhaps apps like Rebirth or some instruments with a midisequencer have a chance to be niche product but not more…
I expect to find that the current generation of tablets cannot handle Podium beyond a few tracks. As I mentioned, I’m doing this experiment in preparation for future generation tablets. Looking back at the last few years, it seems that the smartphone processors have multiplied in speed at the same rate as Intel CPUs. They may hit a performance block at some point, but I don’t see signs of it yet. Also note, that I’m doing this mainly to work out the touch-input issues. It may well be that Windows 8 or 9 and Intel chips will be the preferred platform for tablet musicians 5 years from now.
Anyway, it´s you, who decides, but I´d like to know, what do you plan for the future of Podium, what are your priorities for the further development of Podium and all the existing feature requests…
It seems, you don´t like to talk about this, you mostly say, that this or this is on the to-do list, but I´d like to know, what we can expect in nearer future.
Reaper 4 prerelease circle has started and atm Podium falls more and more behind…too much finetuning, which is important as well, but regardless of all the gaps, which need to filled…
Perhaps, you can tell us a little bit more about your personal plans of this product beside this poll topic…
If I publish a list of “things to come within 6 months”, then I assume you would expect me to fulfill that time schedule. New users seeing such a list may purchase a Podium license, expecting to have a certain feature within a few months. If that is going to work, I would no longer be able to adjust the development short-term according to user discussions on this forum. The next 2.40 release has bug-fixes that took an unexpectedly long time to find. So bug-fixes would also occur on a less frequent basis, if I needed to follow a time schedule.
I prefer to work with a dynamic development schedule. That’s possible because I am a one-man developer team. If users would prefer that I publish a release schedule for new features, I cannot be as responsive to feature requests on this forum.
Zynewave@thcilnnahoj wrote:
I’d be very interested to hear Frits’ thoughts on the UI matter, seeing as it should be quite exciting for him. 😉
I noticed all the standard menu buttons are missing in the screenshots – those are one of the conventions I was talking about. We all know how to do it by mouse or keyboard, but how do you reach the functions on a touchscreen? What about buttons that are always visible, like tool buttons, drop-down menus and such – is it reasonable to take them along to the “new world”, or are they better off only appearing when needed (just for example, as a single tool button stuck to the right screen edge that expands into a palette when you hover over it/draw some gesture)?
There are certainly issues with touch-input that requires added functionality in the UI, mainly due to the lack of a mouse cursor. There will need to be a “Use touch-input instead of mouse” option in the Podium settings (when running on Windows). When enabled, the mouse cursor is hidden, and various UI features change behaviour. With a mouse cursor you can position your input over a button without actually clicking the button. This works for showing popup help and other highlighting, such as the zoom snapshot buttons. When using touch-input this will not work.
With a mouse cursor you can be more precise, because you can “home in” on what you want to click. With touch-input it is practically impossible to reliably click for example the drag handles on sequence events, or the point event handles in the curve editor. I’ll need to implement popup controls with larger drag handles, that will appear when clicking events.
Lots of things to work out, and yes, it’s an interesting job for a UI designer. 🙂
ZynewaveIt’s been a while since I last tried Reason, but I seem to remember that you can’t do faster than realtime rendering. Try to use realtime-bounce recording mode in Podium instead.
Zynewave@bladerunner wrote:
i’m pretty much with trancit too. i follow a number of blogs ie. synthtopia, createdigitalmusic etc. and it’s dismaying to see the amount of ipad, iphone, mobile phone etc. apps filling up it’s pages. it’s all catering for what i call the short attention span/disposable culture. if a person is going to do some serious audio work they are not going to sit on a train with a pair of headphones and a device no bigger than the palm of a your hand surely?
anyway, rant over – i think, as development is already fairly slow (not a criticism) this would only serve to impede the main apps development.
in a way though i can fully understand that you may want to develop in this direction as you need to put food on the table after all. it seems like there is a lot of development and interest in this direction generally but i think once the novelty factor has worn off in a couple of years few truly useful apps/devices will remain in the marketplace.
I also have noticed the increased exposure that mobile apps are getting on many audio sites, but I think it is more than just a novelty factor. I agree that an iPhone on a train is never going to replace professional production in a studio, but for the creative tunemakers, it is a revelation to be able to grab your mobile device and record/compose when inspiration strikes you. I think mobile music creation is going to cannibalize the traditional PC/Mac DAWS in the years to come. In 5 years time I expect more than 95% of all music-creators will be using a mobile device as their primary way to record and arrange compositions. Those that are serious about their music will then have their work finalized on a traditional DAW in a studio setting with studio monitors.
The latest 4.2 iOS update added support for external MIDI devices. It is likely that a future iOS update will add support for external USB audio interfaces as well. Compared to a PC DAW, the main limiting factor of an iPad based studio is the CPU processing power. Assuming that in a couple of years we will have quad-core tablets, this will eventually be enough to satisfy the majority of users that just need to record a few tracks of vocal and guitar, and layer some synth and drum tracks.
No matter how good I make Podium, professional studios will never dare taking the risk of using a one-man created DAW as the cornerstone software of their studio. That means my main target are the creative musicians, and they are going towards mobile as I see it. If I stay committed to writing Windows-only software, I don’t see a great future for Podium. But I am not porting Podium to mobile devices because I think I have to, in order to stay in business. I happen to be thrilled about the possibilities that the mobile devices offer.
Zynewave@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.
Zynewave@Lion wrote:
I’m confused why you would need multitouch in a program like this though.
The multitouch support is essential in order to recognize gestures such as pinch-to-zoom. You’ll be able to place two fingers on the timeline and drag each anchor point in order to slide and zoom in/out. Specialized support for multitouch can be useful in some areas of the UI. Such as for dragging multiple faders simultaneously, just like on a real world mixer.
ZynewaveYou don’t need to create the MIDI parameters for each track. The MIDI parameters are created for the device, so they will be available on all tracks that use that device. If you save the track as a track template, the MIDI parameters you create are saved in the template as well. You can use that template in future projects, and not have to create the parameters again.
Zynewave@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.
ZynewaveA while back I managed to compile a x64 version of Podium, but I have not had an opportunity to test and debug this on an x64 OS. I need to purchase a new PC with Windows 7 x64 before I can go further with this.
When Podium x64 is made available, it will only support x64 plugins. I don’t plan to implement my own 32/64 bit bridge system. For that purpose, you can use third-party plugins, such as:
ZynewaveHi,
The reason only a few basic MIDI messages are created by default, is to avoid polluting the parameter list with unused MIDI messages. You can add extra MIDI messages that you require for certain plugins using the “New MIDI Parameter” submenu in the inspector parameter panel.
Frits
Zynewave@batman42ca wrote:
I think one solution to my problem might be to connect the output of my sound card to the input of my sound card. Podium could output on midi port 10 and record from the audio in. I was just hoping there was some internal way to do that.
That may be the only solution, if you want to record the audio output of the synthesis engine on your soundcard. Some soundcards expose an alternative “loopback” audio input that you can assign to an audio track. This audio input will then record the synthesis output before it goes to the physical audio output. My old Yamaha soundcard supported this. I don’t know if soundblaster cards support it.
ZynewaveBeta2 is up, with a fix for the zPEQ display bug.
Zynewave@thcilnnahoj wrote:
It seems zPEQ got under the wheels during the restructuring:
Ouch 😯
I’ll look at that right away. I recommend everyone else wait with testing until I have beta2 ready in a few hours.
Zynewave2.40 beta1 is available with fixes for rendering latency-compensated plugins. Please post your test results in the 2.40 preview topic in the future forum. Sorry it took so long. I had started on some code restructuring that I needed to finish before I could make a release build.
