Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterI’ve edited my original post to show a screenshot of how the arrangement looks with the current 1.94 release. One thing that has annoyed me for a long time, is the large space occupied by the group bars to the left of the track lanes. With just a few sends and fx plugins you soon get a huge number of bars. The new compact mode offers an option to reduce this space. What you loose is e.g. the ability to freely drag effect tracks horizontally to a specific group level. You’ll need to use the group panel for these kinds of edit actions.
On the other hand, I find that many newcomers to Podium often is lost in the editing flexibility of the track hierarchy. The compact mode will also offer simpler menu commands for arranging tracks in groups etc. and put some restraints on what can be done. E.g. the “increase/decrease group level” commands will not be available in compact mode, as these commands if misused can mess up the hierarchy.
Note that all the existing hierarchic routing possibilites are still achievable in compact mode. I’m just trying to simplify the UI.
ZynewaveKeymasterGet it before the server falls over….
Maybe it already has fallen over. I get an “Error because of misconfiguration.” message when I try to enter the YellowTools site.
ZynewaveKeymasterWill this also be the case when saving without using Keyboard shortcuts?
Yes.
September 7, 2007 at 00:44 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymaster@haiku wrote:
sounds like it’ll just blink when you use the keyboard shortcut so you know it worked – right?
Right.
ZynewaveKeymasterThoughts?
It’s going to be a post Podium 2.00 task. I’ve got my hands full with the track layout changes.
Some clarification:
The objects you see on the project start page device list are a direct reflection of the actual objects in the project. The tracks only store a link to these objects, so deleting the objects will automatically remove the object references on the tracks.ZynewaveKeymasterI browsed the DK+ pdf guide (by DarkStar) and found this hint:
“to enable the Step Sequencer – send MIDI note C#3 on MIDI channel 16”
Are you doing this? There also appears to be a on/off button on the UI for enabling the sequencer.
ZynewaveKeymasterI have some ideas for a simpler track layout, but I need to experiment with this before I can reveal it.
September 3, 2007 at 06:54 in reply to: Adding effects using the keyboard + closing plugin editors #10754ZynewaveKeymaster1) The upcoming changes to the group panel will do something about this.
2) I’ve added “E” as shortcut for closing a plugin window when it has focus. This shortcut won’t work if the plugin uses the E key for something.
This would be especially useful for those editors that seem to block Ctrl+Tab from cycling through open windows.
Which plugins block Ctrl+Tab?
ZynewaveKeymaster1. It’s like a guitar pedal rig where the signal goes into the first pedal, through the others and out the last one to the amp; turning each one on and off as needed?
Something like that. The zGrid plugin would be an insert plugin, and so each effect plugin used within the zGrid instance would be local to the track. On each track you place a zGrid instance, you can have a different effect setup.
ZynewaveKeymasterI assume you are talking about bundled events. I’m not keen on using italics. I’ll keep this FR in mind for the future.
ZynewaveKeymasterI’ve added a save-confirmation blink to the project name written in the top title bar.
ZynewaveKeymasterSo Frits how far do you think the GP feature wise should go…?
I’m going to add more elements to the group panel, but they will all be options in the view menu, like the current gain, pan and send options.
ZynewaveKeymasterI’ve thought about moving the “Track” panel to the top of the list. What kept me from doing it so far, is that it will mean a few changes that may affect users workflow:
The F1-F5 keys need to be shuffled around, so that F1 instead of F5 will open the Track panel.
Today, clicking the header of an open panel will close it towards the top, meaning the remaining panels slides on top of the closed panel. This way the bottommost panel will always be the default open panel, and therefore I placed the Track panel at the bottom. If the Track panel is placed at the top, then closing a panel needs to slide it to the bottom of the inspector, i.e. the clicked panel will slide away from the mouse. Little things for sure, but that’s why I placed the Track panel at the bottom. At some point I’ll experiment with placing it at the top.
ZynewaveKeymaster@Jaegerteam wrote:
the new Big Transport I like very well but the the BSMR buttons
appear a little bit to massive for me, especially if the colour of the characters is black (=activated) and not grey (=inactive).would it be possible to choose a less fat font or a different colour than black?
It’s not possible currently. Some time in the future I may open up for skinning the button images.