Topic: Preview 3.2.5: Minor improvements
- This topic has 33 replies, 9 voices, and was last updated 9 years, 8 months ago by
Zynewave.
-
August 4, 2015 at 00:35 #28787
ZynewaveKeymasterPodium 3.2.5 beta is available on your account downloads page.
After a long period working on other projects, I’ve now resumed Podium development. In this version I’m going to begin with some minor features before I tackle some of the larger features in later versions.
Changelog for beta2:
- Added ‘Assign Tracks with Events at Edit Cursor’ and ‘Assign Tracks with Events in Loop Range’ to the track tag options menu (right-click a tag button in the track tag bar). These commands are helpful when you are working with a large number of tracks in your project template, and need to quickly focus on only the tracks currently playing.
- Fix: Layout of some dialogs did not adjust correctly to the Windows DPI scaling setting.
In addition to the changes, I’ve updated my development tool the latest Visual Studio C++ 2015 version, released last month. This should imply improved performance and stability, but there may be unexpected side-effects, as Microsoft revises its SDK for each major version update of Visual Studio. As mentioned in a VIP topic, I’ve also spent a lot of time revising the entire Podium code-base to take advantage of the latest advancements of the C++ language (C++11/14). This ‘modernization’ of the Podium code-base will make further development of Podium easier for me.
With that in mind, please save backups of your projects before trying the beta, and report here if you notice problems.
August 4, 2015 at 13:56 #28789
H-manParticipantWell hello there! Good to have you back Frits XD
One quick question and forgive me if this is not the correct place for it but I am a “Lifer” who would like to chip-in to the dev fund. Do I just pay for a subscription? Let me know.
BH
August 4, 2015 at 17:36 #28798ZynewaveKeymasterWell hello there! Good to have you back Frits XD
One quick question and forgive me if this is not the correct place for it but I am a “Lifer” who would like to chip-in to the dev fund. Do I just pay for a subscription? Let me know.
BH
Hi Ben. It’s good to be back in development mode.
I appreciate your wish to contribute to the development. If you want to donate, you can either make a purchase, or send money to my paypal account: shop at zynewave.com (replace the ‘ at ‘ with @)
August 29, 2015 at 14:49 #28922ZynewaveKeymasterBeta3 is up. Apart from further code optimizations, I’ve added one small new feature:
- The metronome click sound can be customized. Saving wav files with the names “Metronome1.wav” and “Metronome2.wav” (bar/beat sounds) in the Podium setup folder will make Podium use these sounds instead of the built-in click sound.
Would it be worthwhile to make the metronome sound folder location configurable in the Preferences dialog? Any other wishes for metronome enhancements?
Some ideas I had:
Allow “Metronome3.wav”, “Metronome4.wav” etc. to make it possible to have custom sounds for each beat. You could e.g. record yourself saying One, Two, Three, Four.
Add a second pair of bar/beat gain settings in the Metronome preferences, to have separate levels for preroll and punch-range. That would e.g. allow you to mute the metronome in the punch range.September 2, 2015 at 05:43 #28953H-manParticipantHi Frits,
Additions to the track tag right-click menus are welcome and working here. Thx.
Metronome changes working too however accelerating the tempo via the bpm value (say …120bpm and key in 200bpm) in the Tempo Event Properties box gives me an instant app hang if the song is playing at the time.
Please note that the hang/crash doesn’t happen when going the other way (eg. 200bpm to 120bpm) and doesn’t happen if you stop playback first.
Also, it does not seem be related to the new sound (Metronome1.wav) as it will occur with the default metronome as well.
Suggestions above all look good IMO. Especially the separate levels for preroll and punch.
Still running Win7 64bit running 32-bit beta 3
September 11, 2015 at 12:27 #29024
nicholas.hParticipantHi, given the SDK changes, can Windows XP continue to be supported for foreseeable versions? Thanks.
September 29, 2015 at 02:15 #29136ZynewaveKeymasterHi, given the SDK changes, can Windows XP continue to be supported for foreseeable versions? Thanks.
That’s a good question. I haven’t yet tested the latest Podium beta on my old XP box, but compilation of XP compatible code is still supported in Visual Studio 2015. However, I read somewhere on the Microsoft site, that they intend to drop XP support in the next major VS upgrade. If Podium should continue to support XP, I will have to continue to use VS 2015, which means I won’t be able to take advantage of future improvements to both the C++ language and the VS compiler 🙁
I don’t know when, but at some point I will have to drop XP support. Another incentive to drop XP support, is that the libraries the compiler uses to enable apps to run on XP are older and not as optimized as the newer non-XP libraries. The newer libraries takes advantage of more advanced API’s introduced in newer Windows OS versions.
October 2, 2015 at 14:05 #29165
Guy MayberryParticipantFrits,
On your metronome thoughts – yes – these sound great to me (no pun intended).
Would it be worthwhile to make the metronome sound folder location configurable in the Preferences dialog? Yes.
Allow “Metronome3.wav”, “Metronome4.wav” etc. to make it possible to have custom sounds for each beat. You could e.g. record yourself saying One, Two, Three, Four. Yes – but maybe configurable, as opposed to having to have a dedicated file name.
Add a second pair of bar/beat gain settings in the Metronome preferences, to have separate levels for preroll and punch-range. That would e.g. allow you to mute the metronome in the punch range. Yes – this sounds great too.
October 16, 2015 at 20:48 #29266
thcilnnahojParticipantChangelog for beta2:
[…]
Fix: Layout of some dialogs did not adjust correctly to the Windows DPI scaling setting.Some text is still cut off for me at 125% DPI setting, for example:
– “Note: new sounds on bounce tracks will use the engine bit” (Preferences/Engine)
– “Automatically search for missing plugins when loading a projec” (Preferences/Plugins)
– “Panel texture image file (leave blank to use” (Preferences/Appearance)Windows 8.1, Podium 3.2.5 beta 3 (both 64-bit).
October 24, 2015 at 01:19 #29325ZynewaveKeymasterThanks for the feedback and for testing. I plan to upload a new beta next week.
October 26, 2015 at 21:16 #29379thcilnnahojParticipantQuick bug report, not related to beta features:
Minimize Podium while plugin windows are open, then restore it. The effect selectors’ “active state” color isn’t applied until the UI is refreshed in some way (change track values, change editor profile, open/close inspector, etc.).
November 9, 2015 at 01:03 #29453ZynewaveKeymasterApologies for the delay with the next beta. I have spent the last couple of weeks working on my iOS part-time job. I will return to Podium development again this coming week.
December 8, 2015 at 16:46 #29641ZynewaveKeymasterThanks for the bug reports. New beta is finally up. Apart from a lot of code optimization, the following issues have been fixed:
Metronome changes working too however accelerating the tempo via the bpm value (say …120bpm and key in 200bpm) in the Tempo Event Properties box gives me an instant app hang if the song is playing at the time.
Some text is still cut off for me at 125% DPI setting, for example:
Minimize Podium while plugin windows are open, then restore it. The effect selectors’ “active state” color isn’t applied until the UI is refreshed in some way (change track values, change editor profile, open/close inspector, etc.).
December 8, 2015 at 22:48 #29643nicholas.hParticipantHi, I gave Podium_325_x86_beta4 a test tonight, focusing on the new features reported here.
The custom metronomes worked nicely as described. A restart is required to hear them, which is to be expected. And there’s still just the two of them for now! No problems encountered using them with tempo changes in this version, and I couldn’t upset them even with manic loop range changes – using a 1/128 snap in arrange view, then moving loop markers around to create a nice granular-style scrub of the metronome sounds.
I was happy with how the new track tagging options worked. To note:
– The “Assign… in Loop range” option included the events within the range, and excluded the events that only bordered the range. That is exactly what’s you’d expect, and it works great.
– The “Assign… at Edit Cursor” option included events that spanned the cursor, and included events that began right on the cursor, but *excluded* events that ended exactly on the cursor. I’m pretty sure that is exactly how it should work, so yeah, it’s all good.Tested on Windows XP SP3!
December 9, 2015 at 02:12 #29644ZynewaveKeymasterThanks for testing Nicholas. Good to know it still works on XP 😉 It was on my todo list to test that the new compiler creates code that still is compatible with XP.
- You must be logged in to reply to this topic.