PiginiPiginiPigini@pavouk100 wrote:
@druid wrote:
As I’ve learned in the past (sigh), a person should not rely on how something is going to be in the future. Rather, they should accept what something is now, work with that if it suits them, and hope for future improvements but never expect them (unless it is promised or close to that). Otherwise, they will continue to be disappointed.
Sounds like copypaste from some yoga textbook, maybe except that ‘hope’ part. 😉
Seriously, I agree completely, nicely put together, druid.
Seems like, someone learned a lesson after waiting too long for energy-xt 2 to be bugfree ;).
PiginiBumping an old one here…
The problem with podium not working with the creamware/scope asio driver is still there. Just tried it on winXP with scope v.4/4.5 (which is actually the same driverwise).
I tested some other hosts.
EnergyXT2.5.1 – ok
EnergyXT1.4.1 – not working
Reason4.01 – ok
Orion 7.6 – not working
(my trusted old) Muzys3.14 – not working
EnergyXT1.4.1, Orion 7.11, Muzys3.14 however do work under win98se with the same scope software v.4/4.5, strange. It seems those winxp asio drivers aren’t that great. But there must be a solution, else Reason and energyxt would not work.
(Just realized when testing, that the lowest possible latency with the pulsar/scope under win98se is much lower than in winXP.)
Edit: Solved by installing version 4.0 on a clean system (did not work when installing 4.0 after 4.5 had been on it before). But still, the pulsar performs best on win98.
Pigini@DFusion wrote:
I think that this is a great Feature and i would love to be able to assign multiple midi ins directly like you mentioned Frits 😉
+100.
Yeah, it would be extremely useful for quick sound stacking. Sometimes I like just jamming along with some fat layers with key split zones.
PiginiDid you read that thread too?:
http://www.zynewave.com/forum/viewtopic.php?t=1831
Though it would not help with your particular problem, it could very much improve podiums flexibility, so it could handle some tasks known from modular hosts alot better, but in its own way.
Hope Mikes idea makes it into podium at one point.
PiginiTotally agree with pavouk and liquid. I don’t use timestretching anywhere at all. I work everything in midi and do all changes affecting timing there. Usually I do a dry audio rendering of each track and then only work the effects, mixing and mastering with the audio data.
PiginiIMHO, “Hidden” in podium means just “not visible” and I want to be able to select things, that aren’t visible. Otherwise “hidden” would work as a mask for selections. If it sounds, it should be in the selection.
For masking things out, muting them would be more logical. Podium is an audio app afterall, not a paint program.
I think we could do with an advanced selector box where ranges and types of events, channels etc. could be defined with some sort of filter matrix.
Pigini+1
PiginiHurray!!!
I love having Podium on a removable media. And since such media most probably is a usb-stick, Frits’s suggestion show, that he really has thought it through.
Would it be possible to have one vst-folder within the podium directory without needing a drive letter in the path? When using a usb stick, the assigned drive letter keeps changing from system to system.
PiginiPiginiPigini+1
Great your’e dealing with it already!!! Take all the time you need.
Pigini+1
PiginiWould that be a good moment to come up again with the idea of having midi parts drag and drop to work in both directions?
We already can get midi parts in. Though, the ultimate thing would be to edit and cut some midi in podium, then drag it over to a midi clip collection for later use in the arrangement. Like having some building blocks ready to quickly change things around.