Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@estwing wrote:
hi Frits
I think this has a kind of yo-yo effect when moving between track-device-preset etc
it seems that re-clicking “track” now has a different result.
why dont they collapse in-situ instead of falling to the bottom ?
martThat’s exactly what bothered me as well. I tried it this way because I wanted the Track panel to appear when you closed any of the other panels. With the old panel behaviour the bottom panel (now Input) would open when you closed one of the other panels. But I think this is a better solution than the panel behaviour in beta4. Beta5 is now uploaded with the old panel behaviour, but still with the input and track panels swapped.
Also in beta5 are two new commands in the preset menus: “Save Program File” and “Save Bank File”.
ZynewaveKeymaster@Conquistador wrote:
I agree with your FR. It also sounds very similar to this…
I’ve tried swapping the track panel to the top, as discussed in the topic you linked to. Please try the 1.96 beta4 and give me your feedback in this topic:
ZynewaveKeymasterBeta 4 is up:
By request I’ve tried to swap the position of the input and track panels in the inspector. This means that the track panel is now at the top and F1 is used to open it instead of F5. Visually this makes more sense, since the panels are now placed in the same order as the controls in the group panel and the mixer. The only problem is that it becomes more difficult to open/close the panels by clicking the panel headers, because the clicked panel slides away from the mouse. Difficult to explain, but please try it and voice your opinion.
ZynewaveKeymasterBut what is the use of a track with childs NOT being a Group Track ?
If you intend to add child tracks to a track, you should enable the group option of the parent track. An alternative implementation could be to remove the group option from the track properties, and instead add a “new group track” command next to the “new track” command.
And since the Compact mode is nice, the Expanded mode remains for me a lot easier to use thanks to dragging.
I’m going to add support for drag reordering effect tracks in compact mode. So please be patient.
ZynewaveKeymasterI found a demo download of the diamond bundle which do not to require an iLok to run. But it appears that the demo plugins are 5.0 and only a couple of them 5.2. Can you name some 5.0 plugins that you have problems with?
ZynewaveKeymasterThis FR will require quite some time to implement so I will save it for another time. After spending a week on the redesign of the inspector I feel I should move on to other areas.
ZynewaveKeymasterButtons, sliders and various shadow effects are not based on bitmaps but is algorithmically rendered by Podium on startup. The rendering depends on color setup, text sizes and user resizing of panels etc. So it is not a matter of simply allowing users to replace a default set of bitmaps.
Some elements can be made skinnable, such as the brushed metal texture. At some point I’ll probably support that.
ZynewaveKeymasterBeta 3 is uploaded. This has a couple of design changes to the EXBSMR buttons. There are also a lot of bug fixes, as it turned out the previous betas did not always respond to key shortcuts and menu commands.
another tab up top seems like more clutter than an arrrow to hide or open the track inspector. am i missing something?
I hope you see that the inspector now uses the maximum available height of the window, instead of the limited space within the tracks region. This was a necessary design change, as the space requirements of the inspector has grown with new features being added over the years.
ZynewaveKeymasterYup, thats how i do it now, but is there planed any change with this?
Not in the near future. But at some point I’ll probably improve the way you add multi-mapping plugins to a set of tracks.
ZynewaveKeymaster@thcilnnahoj wrote:
1- Is there a reason that you have to choose a saturation value before picking the desired hue? Other than that the color would still be gray?
I came to the conclustion that the separate hue/saturation sliders do not work well precisely of the reason you mention here. So I’ve changed it to be a hue/saturation XY field instead of two sliders. Beta 2 is uploaded.
2- Maybe when a track is not color-enabled yet, there could be a button instead of the HSL bars (or they could be grayed-out, acting as a button) to enable it? If I didn’t overlook something, you still have to open the track properties dialog to do that, meaning more clicks.
I’ve added “Enable Track Color” to the lane track menu. This will only appear if the track is not already color enabled.
ZynewaveKeymasterBut if you want to solo one of this instrument outputs it also mutes the midi track, wich means no midi for the instrument. Is there a better way to do this ?
If your drum sampler supports it, I think the easiest way would be to mute/solo the individual outputs in the sampler plugin editor. In Podium you will need to solo both the stereo output track and the MIDI track (or mute the other stereo output).
November 27, 2007 at 23:35 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterIf I remember correctly, there should be a more resent version of eXT1 than 1.3.6. I would suggest updating eXT. There was a crash bug that Jørgen fixed in one of the latest eXT1 versions. Maybe this is the bug you experience. See discussion here:
ZynewaveKeymasterYou will always be able to open your old projects. The .pod file format has not been changed in 1.95/1.96, so you will also be able to go back to 1.94 and open projects saved with 1.95/1.96.
But it’s always a good idea to keep a backup of your projects.
ZynewaveKeymasterFor those that are concerned about the inspector changes: I have uploaded a beta of 1.96. You can download it from the download topic in the VIP lounge.
This beta also has a new color picker tool in the inspector, which allows quick adjustments to track colors.