ZynewaveIs this something that have started to occur after an update of Podium/driver/hardware, or have you always had this problem?
ZynewaveYour account should now have access to the VIP lounge, and I’ve sent you an email with download instructions.
Zynewave@michi_mak wrote:
i see, so we can only keep posting requests and keep our fingers crossed, can’t we? i thought keeping in touch with existing customers and listening closely was a great chance for small companies to stay in business?
I’m sorry if you read my response as being dismissive. It’s the very fact that I DO try to listen and respond to user requests, that I don’t put out a roadmap. If I commit to a deadline of a series of features, then I have no room to adjust the development according to problems and good suggestions posted on this forum. I’ve tried in the past to come up with predictions on when certain features would be available, and the predictions never held up because discussions on the forum resulted in implementation of unplanned features. So I stopped giving estimates on new features, since I don’t want to give users false hopes. This is a standpoint I’ve had for a couple of years now, and something I’ve expressed in many topics in the past.
ZynewaveHi,
Welcome to the forum 🙂
On June 27 I sent you an email with instructions on how to get access to future Podium updates. I sent it to the email address you used with share-it. I’m going to resend it now, in case it got lost somehow.
In your share-it order you specified “astangel” as user name, which I couldn’t find at the time. I did not realize you had registered the “xx” account instead. Could I ask you to change the name of your account from “xx” to “astangel”? Also, change your password to something else. You can change this by clicking the “Profile” link at the top of the page, when you are logged in.
Once you’ve done that, I’ll give the “astangel” account access to the VIP lounge.
Frits
Edit: Changed the account name to “xx”.
Zynewave@michi_mak wrote:
you may call my nosey but i’d really like to get an idea of what to expect in the next releases – something like a roadmap or a list divided into a) high priority b) normal c) when i’ve finished a) and b) !
or maybe hold a poll where every licensee can vote for his / her top 3 features out of a list of your 50 topics ?!?
All I can say is that the next few releases will be maintenance releases. I haven’t laid out all the reported issues in a roadmap, as that is not the way I prefer to work. Once I start to look deeper into the 50+ topics I have on my todo favorite list, I may find that I need to rethink the priorities.
ZynewaveFor controlling the mixer, Podium currently only supports the Mackie MCU and other devices capable of emulating MCU.
ZynewaveZynewave@michi_mak wrote:
update – after a second install of rc3 i can’t reproduce this issue ( i kept preferences again ) …
Could it be the timeline zoom that tricked you the first time?
Zynewave@michi_mak wrote:
@Zynewave wrote:
@michi_mak wrote:
had a quick run with rc3 : it got an issue with midi note lengths : when recording with my mpd18 i can NOT alter the note lengths to say 1/32 – they stay at about 2 bars length ( does not happen with 2.42 ) – xp 32bit sp3 with respective rc3
I can’t reproduce this problem (Vista 32bit). Can you provide more details please? What do you mean with “stay at about 2 bars length”; Did you record them at 2 bars length, or can’t you resize them smaller than 2 bars?
rc3 recorded the notes with a length of around 2 bars ( not precisely 2 bars btw ) and i was not able to resize them ( smaller ) later on. in 2.42 these notes get recorded with a length of around 1/32 to 1/16…
And if you uninstall 3.0, and reinstall 2.42, (and not change your device setup/project), then you are able to record lengths below 2 bars?
Is the realtime plugin playback ok, when you record?
Have you tried the various ways you can resize note events, e.g. alt+clicking the note value buttons in the note editor? Still not able to resize the note events? If not, please provide a screenshot or mail me the project file.
Zynewave@michi_mak wrote:
had a quick run with rc3 : it got an issue with midi note lengths : when recording with my mpd18 i can NOT alter the note lengths to say 1/32 – they stay at about 2 bars length ( does not happen with 2.42 ) – xp 32bit sp3 with respective rc3
I can’t reproduce this problem (Vista 32bit). Can you provide more details please? What do you mean with “stay at about 2 bars length”; Did you record them at 2 bars length, or can’t you resize them smaller than 2 bars?
Zynewave@druid wrote:
I’d like to bring up my previous concerns over the installer insisting on installing certain folders even you install elsewhere, such as in Program Files, and copying color setups and the like in, if I recall correctly, AppData folders, where I don’t want them. Is this installer going to be more flexible in terms of unnecessary creation of folders and shortcuts?
The new installer allows you to specify separate locations for the Podium application and the Zynewave plugins. Color setups and Note Maps are still written to AppData. The majority of software writes their settings in this folder. What is your concern about that?
ZynewaveI think 3.0 is finally done. I’ve tested the installation on all the different Windows configurations I have available. The VIP download topic contains a new “3.0 release candidate” download. I hope some of you could give this a try, and let me know if it installs and works properly. If all is well, I’ll officially announce 3.0 in the releases forum.
ZynewaveNot yet. It’s on my todo list.
Zynewave@4mica wrote:
I’m curious: what are the six packages? My limited brain can only conceive of a 32bit and a 64 bit.
Podium, Podium Free and Podium Demo, each in x86/x64.
ZynewaveJust a quick update on my progress:
The work with creating an installer is taking longer than I had hoped. With the addition of x64, I now need to build six installer packages for each release, so I wanted a tool that in one command could build them all. I tested various trials of installer tools, but could not find one that satisfied me. (I ignored the tools that cost 1000$ or more :roll:). I settled on using “WiX”, which is an open-source project maintained by Microsoft. It’s a very flexible tool, but the things you need to know in order to work with it are ridiculously complex and unintuitive 👿
While researching, I noticed that the predominant version numbering scheme today is x.x.x (major.minor.revision). Not only in general software, but also the majority of DAW hosts use this scheme. I started with the x.xx scheme many many years ago. To get with the times, I plan to change the version numbering for the next release. Using the version number 2.4.3 would cause a conflict when installing over the previous Podium release (2.42 is larger than 2.4.3), so I thought this would be a good time to bump up the version number to 3.0.0. Seems fitting with the introduction of the x64 version. I’m not planning to change the way I implement features and fixes bugs in the future, but with the x.x.x style I can indicate whether a release contains new major/minor features, or just maintenance/bug fixes. Any opinions on this?
Another cause for the delayed release, is that I’m setting up my new PC. I developed the previous Podium x64 betas on a borrowed laptop, but I’ve finally purchased myself a new Windows 7 x64, i7, 16GB RAM PC. I also purchased Kontakt 4, so that I’ll be able to fill up those 16GB of RAM 🙂
I hope to have the release ready within a week. Still need to fix one remaining installer bug.