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.
Zynewave@frollo9386 wrote:
… is a FR you’re considering to add to the sequencer?
It is a feature I intend to add in the future. I have no estimate for when it will appear.
@adimatis: A host can support MIDI parameter control of a plugin, by intercepting MIDI messages from a controller, and convert them to VST parameter messages for the plugin. This means the host needs to store information in the host project file about which MIDI messages are to be linked to which plugin VST parameters.
Zynewave@frollo9386 wrote:
so it’s not possible to set a midi CC to control a parameter in the vst synth unless the vst plugin support itself midi learn?
Correct.
ZynewaveI can’t tell from the website whether the Antti synths support MIDI learn. If the plugin knobs do not move when you move a knob on your MIDI controller, my guess is that they don’t support MIDI learn. Perhaps you could try with the Zynewave Nucleum plugin, which do support MIDI control of all parameters.
ZynewaveIn which plugin are you trying to control the cutoff?
Zynewave@michi_mak wrote:
@Zynewave wrote:
Unfortunately, I don’t know when implementation of time-stretching will begin. Right now, my todo-list is overflowing with minor things that have been requested over the years, and I intend to thin out that list before I start on new major features. I doubt that time-stretching will be implemented this year.
Frits, would you mind giving some rough ideas about this to-do list???
I keep a list of bookmarks to topics in this forum that deal with stuff I agree should be improved/fixed. This list has currently grown to 50 topics. To keep my sanity, I’d like to thin out this list before moving on to new major features.
Zynewave@kozaberger wrote:
Hi All, I am new to this forum, greetings from Poland 🙂
To the subject – I will probably buy Podium as soon as I have collected money. Time stretching is not critical for me (I’d rather opt for sample rate conversion). However, Zynewave, would you consider using an external library like:
http://breakfastquay.com/rubberband/Maybe it would spare you some development? Just a guess, I am not a programmer.
Anyway thanks for the great work on Podium and generousity with Podium Free!
Hi, welcome to the forum.
Thanks for the link. I already have a simple technology for time-stretching, similar to what this library offers, although my technology is probably lower quality. What is going to require a lot of development time, is integrating it into the Podium UI and audio engine.
ZynewaveUnfortunately, I don’t know when implementation of time-stretching will begin. Right now, my todo-list is overflowing with minor things that have been requested over the years, and I intend to thin out that list before I start on new major features. I doubt that time-stretching will be implemented this year.
ZynewaveBeta3 is up. The zip contains 8 files. Podium.exe and the three zPlugins, in both x86 and x64 builds.
The Podium x86 build is not changed much compared to 2.42, but the three x86 plugins are now compiled using the same tool I’m using for Podium. I’m seeing perhaps 5% performance improvement in zPEQ. Haven’t tested performance on the other two. Please report if you notice any differences with the new zPlugin builds.
I’m done with the coding for 2.43, unless bugs appear. Now I only need to work on a new installer.
Zynewave@4mica wrote:
Not to sound impatient or a worrywart, but when do you expect the new version to come out? It’s been very quiet here the past few weeks-
I have completed the porting of zPEQ, zReverb and zPitch to x64. I need to test those a couple of days before I’ll post a new beta. The zPlugins have not been updated for years, so I also had to spend some time adjusting them for the latest version of the developer tool I am using for Podium. The good news is that this should make them more CPU efficient, and it will be easier for me to work on new zPlugins in the future.
Unfortunately I also have to spend some time looking for a new installer tool. The current installer I’m using does not support x64 distributions.
ZynewaveKey customization is on the future list, but I don’t have a time estimate.
ZynewaveCool video 8)
Is it ok if I add it as a favorite to my channel?