Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@LiquidProj3ct wrote:
edit: *this is a possible bug, it isnt’ a mockup or FR*
I don’t know if you’re aware of this mini-font:
To replicate add a mda DX10 (maybe any plugin), add all parameters and do the inspector the thinnest you can.
Best regards
That’s not a bug, it’s a new feature. I insist 😉
You’ll see the same if you open a generic editor window and resize it. In previous releases, when you resized the editor to narrow the width, the parameter name and value texts would eventually overlap each other, making them unreadable. Now they are placed on double lines when the width reaches below 200 pixels. I chose to use the smaller font in this case to save vertical space.
ZynewaveKeymaster@thcilnnahoj wrote:
Umm… a minor mixer strip docking problem: If you put too many effects (or with 2.24 – too many parameters!) on them, they’ll start to extend beyond the screen like any other track. However, since they are docked – thus not affected by the non-docked tracks’ vertical scrollbar, and have no scrollbar of their own either, it could become a problem.
It’s an unlikely case that one would really run out of space even after adjusting mixer height or hiding a few elements, but it’s still a little weird.I assume you mean the docked master and return tracks. I’ll try to fix it so that the vertical scrollbar appears here too.
December 16, 2009 at 17:44 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.December 16, 2009 at 17:27 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.December 16, 2009 at 17:22 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterHeh, quite a shock to see how the Podium UI looked not that long ago. 😆
That method of dragging is no longer supported, but you can still drag tracks into group tracks. You need to set the “use as group track” option on the track. Then when you drag a track below the group track, it will be added into the group.
ZynewaveKeymasterBeta5 is up.
There’s a new “Editor” option button in the inspector parameter panel. Selecting this option will show checkboxes in the parameter list, for adding/removing parameters to the rack and mixer embedded editors.
Beta5 also has various minor changes all around. Such as: Empty rack editors show “No parameters are added to the rack editor” (let me know if you can come up with a better message). Renamed the menus for managing embedded parameters. The 64 maximum limit is removed from the “add all…” command, and instead a dialog pops up to ask if the user really wants to add so many parameters.
I think I’m done adding features to 2.24, unless you guys can think of something essential that is missing. I’ll start perusing the bug reports tomorrow. I hope to have a release ready for the weekend.
ZynewaveKeymasterBeta4:
Made several changes to the appearance and mouse actions of the zPEQ editor:
The embedded rack and mixer editors will not show the parameter fields, but will instead show a popup with info for the band closest to the mouse cursor.
The curve is drawn centered around 0dB.
Moving the mouse in the display will highlight the nearest band handle.
Double-click the background to enable the next unused band.
Double-click a band handle to disable the band.
Right-click to show a band type menu for the nearest band.
Click to drag frequency and gain of the nearest band.
Alt+Click to drag the Q value of the nearest band.ZynewaveKeymasterThanks. A follow-up question:
What happens if you try to create a feedback routing? I.e. you route the output of track1 to track2, and then either track2 to track1, or track2 to track3 and track3 to track1, etc.
If that is possible in either of the hosts, what do they do about latency compensation? I would guess they at least introduce one full buffer latency (varying with the selected ASIO buffer size) to a track that feeds back into a track that already has been processed.
ZynewaveKeymaster@LiquidProj3ct wrote:
Good morning. It’s nice the mixer zoom 🙂 I’d like that meters were scaled too, and volume faders keep at the left of each strip when zooming. I consider it more classy.
Wider meters will require a bit of work, so that will come in a later release.
The fader and meter share the meter dB markings. The translucent fader slides on top of the markings so that you can use the dB markings as hints for what the fader dB value is. If the fader is moved to the left edge, you would lose that link.
ZynewaveKeymaster@Conquistador wrote:
But what happened to all of those plans? (Based on your own comments) I thought it would surface in 2.21, then 2.22 then 2.23 now it looks like its fallen off the radar for 2.24 as well. Have you abandoned the idea or is it part of the scope for 2.24?
It’s not abandoned. I just shifted priorities around. I thought that it would be best to get the new track header layout sorted out, before I started adding another feature layer on top of it. And then in the 2.23 preview topic discussion, the consensus was that it would be best to migrate the new layout to the mixer, for consistency. And that’s why I’m currently working on the mixer. I’ll get back to the track toolbar eventually.
ZynewaveKeymaster@UncleAge wrote:
@thcilnnahoj wrote:
I wouldn’t say no to the kind of feature Mike suggested in the opening post. As far as real modularity – which isn’t the topic though, I guess – is concerned, I stand by my comment that it’d better be kept (visually) separate from the normal tracks view.
Every host is a bit different in this regard and I for one don’t miss the modularity of an app like energyXT when I’m working in Podium.
The link for the video (about 5 minutes long) below shows how routing is handled in Reaper and Live for those who have never used those apps. I still don’t have an answer for how it should be displayed in Podium but maybe there’s something to glean from seeing how its presented to the user in two other apps.
Warning: It’s about 20MB so if you are on a slow connection beware 🙂
http://www.uncleage.com/ftp_music/Routing.wmvNice video, thanks.
As I see it, what you achieve with the “from” combobox on a track, is that you move the setup of send/return entirely to the target track. You get an implicit return on the target track, and a hidden send on the source track.
Q: It looks like the Reaper routing window allows to mix the output from multiple tracks onto a single target track. Can you do that in Live also with the combobox?
ZynewaveKeymasterBeta3 is uploaded. Just one new feature, which is neat though:
Added a zoom slider to the mixer toolbar. This will zoom the widths of the strips from 100% to 200%. Removed the obsolete “minimum strip width” setting from the mixer properties.
The zoom slider is a quick way to enlarge the strips so that for example the embedded zPEQ curves are more detailed and easier to edit.
Next on my schedule is adding functionality to the zPEQ display, so that you don’t need to open the editor to enable bands. For example: Double-clicking in the display should enable the next unused band with freq and gain set to the clicked point. Clicking anywhere in the display should grab the nearest band. Right-clicking should show a menu for selecting band type.
I’ll get back to the bug reports in this topic later on.
ZynewaveKeymasterQuestion to you all:
I think the “[Stereo]” and “[Mono]” texts that are added to multiple configuration plugins are taking up too much space. What would be a better solution? Shorten the texts to “
” and “[m]”?ZynewaveKeymasterBeta2 is up. The full change-log now read:
The inspector rack and the mixer strips can show embedded plugin editors. The Zynewave plugins will show their custom editor, while all other plugins use the Podium generic editor.
The parameters shown in the embedded generic editors can be configured separately for the rack and the mixer. Right-click the plugin selector and use the “embedded editor parameters” submenu to select the parameters. The selector menu in the rack also has shortcut commands for selecting and clearing all embedded parameters. The parameter selection applies globally to all instances of the plugin.
Added an “Editors” option button to the track inspector toolbar. When enabled, a show/hide button will appear next to each plugin selector in the rack.
A scrollbar will appear in the inspector rack panel if the rack is too large to fit in the panel. The panel can be resized by dragging the bottom of the panel.
Removed the redundant gain/pan/send controls as well as the embedded plugin editor from the track panel in the inspector.
The track panel in the inspector now always show information for the source track even if an effect track is selected.
Added “show embedded plugin editors” option to the mixer. Each plugin will show a generic editor, with the exception of the zPEQ plugin, which will show a miniature frequency response curve with handles for dragging frequency and gain of the EQ bands.
The generic plugin editors embedded in the mixer use a smaller font, and the parameter name and value dial are on separate lines.
Changed the appearance of the zPEQ editor response curve so that is centered around 0dB.