Zynewave.
ZynewavePodium 3.1.1 beta1 is available in the VIP lounge download topic.
Changelog:
• Added support for Unicode file names and text input.
• The Podium file browser sorts the file list according to the current user locale.
• Fix: Adding a new track with the master track hidden would not insert the new track as a child of the master track (Bug appeared in 3.1.0).
No new features in this release, but the Unicode update is something that was way overdue. Almost all new applications developed today support Unicode. Since Podium development began years before Unicode became common, I needed to revise all of my text handling code, which was quite an extensive job.
I would appreciate if some of you faithful beta testers would give this one a try, and report if you find problems. Please take backups of your old projects before you save with this beta. I have tested the beta extensively, but since the Unicode update has affected many areas of the Podium sourcecode, there is a risk I have overlooked something.
Quite some time has passed since the 3.1.0 release. I intend to return to a more frequent update cycle. I have spent time researching other features since the 3.1.0 release, but these will appear in later releases.
Trancit
4micaI ran the 32 bit through a few tracks, and everything was fine.
A request: minor: an option to keep grid resolution settings consistent between the midi/audio editor popup window and the editor at the bottom(2). The tool settings are already the same between the two windows, which is always nice.
Good that you got through unicode. I tried to read up on it but I have my limits.
Glad for the update starter, good day!
TrancitHere it looks fine so far…
One thing I noticed, though it isn´t related to this new features:
If you are in the “Customize Note Map…” window and name a few notes:
1. if you hit the “Edit next” button, the text box “Note Name” looses focus…
If I hit “Edit next”, it´s logical, that you want to enter another note name, so after hitting “Edit next” it should be this way, that you can enter directly the next note name without having the need to click additional into the text box to set the focus again…
2. After entering the note name, I personaly am always feeling the need to finish my entry by hitting the “enter” key on my keyboard, which in this case closes the whole window…
Is it possible somehow, that after entering a name into the text box, the “Enter” key works like the “Edit next” button???
So far, so good!!! 8)
The TelenatorHaven’t tried the new beta yet but thanks for the little fixes. And I think even my coffeemaker and electric toothbrush are Unicode now.
Mainly, though, I just wanted to mention that the hidden master track thing was rather interesting.
druid32-bit seems to work with unicode, I tried loading and saving unicode filenames, and renaming items within Podium with Japanese.
Are there any areas that are still dependant on ASCII or similar, or has everything been uypgraded to unicode? Do notes, device names etc. all support unicode now?
ZynewaveBeta2 is up, with three small changes:
Rerendering a bounce track will truncate the bounced audio file to the length of the new bounce range.
When key focus is in the “Note name” field in the Note Map dialog, the Enter key will activate the “Edit next” button instead of the default OK button.
Fix: The “Adjust tempo and stretch to align grid at cursor” command could freeze if the bpm value was not enabled in the tempo event.
Zynewave@druid wrote:
32-bit seems to work with unicode, I tried loading and saving unicode filenames, and renaming items within Podium with Japanese.
Are there any areas that are still dependant on ASCII or similar, or has everything been uypgraded to unicode? Do notes, device names etc. all support unicode now?
All text handling within Podium is now Unicode. Windows stores Unicode strings as double-byte (16-bit) characters. Whenever Podium needs to save/load strings in files and VST/ReWire plugins, the strings are converted to the single-byte (8-bit) UTF-8 format. A UTF-8 string that does not contain Unicode specific characters is identical to the ASCII version of the string. The UTF-8 conversion is necessary since the VST and ReWire communication interfaces only support strings with single-byte characters.
Using UTF-8 should ensure compatibility with plugins that do not support Unicode. If a plugin supports UTF-8 conversion, then it should be possible to name e.g. VST presets in Podium with Unicode characters, and have them appear correctly in the plugin UI.
druidAh, I would’ve never made presets in plugins with unicode characters because of the fear that it would result in question marks! I’m mostly an English user anyway, but promote unicode throughout all systems (and I do use Japanese folder names). It’s a pity unicode hasn’t caught on more so, but I can understand why it’s taken so long for many people to move to the new standard.
Other than presets, are you aware of any textual data that would transmit between VST and host, that the user can edit, that might contain unicode? Are folder paths transmitted between Podium and VSTs? Naturally if the VST itself loads, it’s entirely within the VST itself, but I was wondering if some VSTs request paths from the host.
Zynewave@druid wrote:
Ah, I would’ve never made presets in plugins with unicode characters because of the fear that it would result in question marks!
It shouldn’t be harmful though, if the question marks appear.
Other than presets, are you aware of any textual data that would transmit between VST and host, that the user can edit, that might contain unicode? Are folder paths transmitted between Podium and VSTs? Naturally if the VST itself loads, it’s entirely within the VST itself, but I was wondering if some VSTs request paths from the host.
Can’t think of any.