Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterA function where you can quickly zoom out all tracks is on the plan. It may not be possible to make it a smooth percentage zoom, like the current 100-200%.
Is there a need for extra-minimizing individual tracks? I’m thinking about a minimize button on each strip, similar to the minimize button at the top right corner of the track lane headers.
June 7, 2010 at 16:15 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
ZynewaveKeymasterThe minimum width of the embedded inspector/browser is limited to avoid graphic layout issues that would occur if the width was smaller. You can get smaller sizes if you open the panels in separate windows from the “Window” menu.
ZynewaveKeymaster@thcilnnahoj wrote:
Nitpicks: The grid color behaves slightly differently in the editors than in the arrangement view. Looks like they don’t use the exact same timeline fill color. I also don’t like the horizontal note divisions too much.
It’s the same code that paints the vertical grid lines in all editors. The grid lines are however painted with translucency (~50% for bar lines) onto the background, so if you see a difference, then it should be because the background in the editors are different.
ZynewaveKeymaster@Trancit wrote:
If I name notes in the pianoroll, I would suggest, if I swith to the drum map, that this would reflect the name changes as well…I think those two should interact and it would be nice, if you could figure this out…
Don’t worry. The note naming will become available in the drum map as well.
The Drum map isn´t named correctly in the View menu…it only shows two times “Timeline”
That’s because the old default setup did not specify the editor type in the profile name. The first “Timeline” is the piano roll and the second is the drum map. This issue will go away if I choose to merge the two editors into one.
ZynewaveKeymasterBeta12 is up. Some bugs are fixed, and the import/export buttons in the note map dialog are now implemented. Podium will look for a “Note Maps” subfolder in the setup folder. For this beta you can create this subfolder manually, or just save the files in the main Podium setup folder. I’ll add the creation of the “Note Maps” subfolder to the installer, along with a few default files for “GM Drum Kit”, “iMap Standard Drum Kit” and “iMap Extended Drum Kit”. Are there other common drum layouts that should be included?
ZynewaveKeymaster@siegfried wrote:
Possibility to set default velocity is great idea in my opinion. 64 is often too low.
Would you be happy with a default velocity of 100?
ZynewaveKeymaster@LiquidProj3ct wrote:
Highlighted blackkeys works fine too. If I can reproduce them I’ll tell you how.
Please note: If a scale is active, then it will override the black key highlighting. Previously both scale and black keys were highlighted, which resulted in an unreadable mess.
ZynewaveKeymasterThere is no setting, but if you add new notes with the pencil tool, it will use the velocity of the previously selected event.
I can easily change the default velocity for new notes to 100, but is a “default note-on velocity” setting in the piano roll properties dialog preferrable? Anyone else have different preferences to default velocity?
ZynewaveKeymaster@LiquidProj3ct wrote:
Two bugs, selecting multiple events with far zoom doesn’t work fine:

I can’t see what the bug is here?
And, I barely use them having scales though, “highlight blackkeys” option doesn’t work.
The two options are working fine here. Please explain?
About “note map for track” doesn’t work in drums, i don’t know what’s your plan with this window, so I’ll wait a little before give more feedback. (because I see that drums roll view isn’t saved yet).
The new note map dialog will be available in the drum map editor eventually. I’m trying to figure out how it’s going to work in the piano roll before unifying the two editors. So I’m looking for comments on the note map changes to the piano roll editor, and not the drum map editor.
ZynewaveKeymaster@LiquidProj3ct wrote:
Please I need more contrast, I don’t see the guidelines, at least allow define the contrast in Piano Roll option
Try the new beta11:
I’ve added a “timeline grid” color setting to the colors setup dialog. Editing this color is also possible with the track inspector color picker right-click menu.
ZynewaveKeymasterBeta10 is up. This beta has some changes to the piano roll editor.
There is a new menu button in the piano roll, with a “Customize Note Map” command for opening a dialog. The dialog can also be opened by right-clicking a key on the piano roll keyboard.
In this dialog you can enter a color and a name for each key. It’s also possible to enable/disable each note, similar to the drum map editor. Multiple notes can be selected in the listbox with the standard shift/ctrl click shortcuts. When you enter a name or select a color, this will be applied to all selected notes.
The names you enter for a note will be written on the piano roll keyboard, if zoomed in. For smaller zoom settings, I’m planning to implement a popup that will show the name of the key under the mouse cursor.
I’ve also modified the way that black keys and scale keys are highlighted.
Let me know what you think of this.
ZynewaveKeymasterI’ve now fixed this by adding some code in Podium that will reset the floating-point bit precision back to defaults, if the plugin has changed it. I’ve sent an email about this to Wallander Instruments, as this may be an issue that can affect other hosts as well.
ZynewaveKeymasterThis is the code for the fxp header format I use in Podium:
// Based on fxProgram from vstfxstore.h in VST API
struct VstProgramFileHeader {
ULONG_BE m_FileMagic;
ULONG_BE m_ByteSize;
ULONG_BE m_TypeMagic;
ULONG_BE m_TypeVersion;
ULONG_BE m_PluginID;
ULONG_BE m_PluginVersion;
ULONG_BE m_NumParams;
char m_Name[28]; // Null-terminated.
// m_TypeMagic == 'FxCk':
// float_BE m_Params[m_NumParams];
// m_TypeMagic == 'FPCh':
// ULONG_BE m_ChunkSize
// UBYTE m_Data[m_ChunkSize]
};Whether the data is stored as an array of floats or an unspecified chunk of data, will depend on the plugin.
ZynewaveKeymasterThat is one spooky bug 😯
It appears that the plugin changes the floating point precision or rounding method, and does not set it back to default before returning to the host. This causes malfunction in some optimized code in Podium that relies on the default floating point behaviour. I’m trying to find a fix for this.
