I still have to figure out how the category buttons should react. There are at least three functions that should be available in one button: show/hide, mute and solo. Maybe the category setup should include a setting for what the primary purpose of the category is, which will be the action that a normal click on the button will do. The other functions can then be accessed with key shortcuts, or by right-clicking the category button to show an option menu.
Still a lot of design issues to consider :-k
@thcilnnahoj wrote:
but I’ll have to ponder some more about the balance of additional housekeeping vs. the benefits the “categorization” brings to the table. Maybe we’ll get a few ideas about disarming it – if that is necessary at all – after a beta becomes ready.
Setting up track categories will only make sense when you work with a lot of tracks. You can ignore this feature, and it will work like previous Podium releases. If you never work with a large number of tracks, you can choose to remove the track toolbar from the editor.
1. Is there a way to add multiple tracks at once with the “+” button on the toolbar?
Not currently. Clicking will open the track properties dialog, for naming the new track. If you need an initial number of tracks, isn’t it sufficient that you have the track setting in the “new arrangement” dialog?
2. How does this work with group tracks… If you select, for example, the “Bus Returns” group track to be shown, will it automatically show its child tracks? And will it update correctly if you add more child tracks (returns in this example) to it?
If you add a group track to a category, it will automatically include all child tracks.
3. Is it possible to have only child tracks from various groups shown, and if so, how will it affect the visual routing?
I haven’t implemented this yet, but I think that if you include a child track in a category, then it’s parent group track should also be displayed, at least as a collapsed track (6 pixel height). That way the hierarchic structure is intact.
[Edit] 4. (One more): Can you go still back to the a view of all tracks, categorized or not, or do you have to create an “all-encompassing” category first yourself? If it’s the latter, will it update if you add more tracks later on?
If you deselect all categories, it will show all tracks. Otherwise a track would be completely invisible if it wasn’t included in any categories. If you add a new track while you have a category selected, the track will automatically be added to that category.
If you haven’t already gone through it, I can recommend that you read the Getting Started chapter in the guide. Here’s a link to the online wiki page:
http://www.zynewave.com/wiki/doku.php?id=guide:getting_started
This should hopefully help with understanding the Project Start page. For example, it mentions that the device setup you make on the project page is saved as part of the project, and not as a global setup of Podium. So each project has its own device setup.
You can share a device setup across multiple projects by using project templates. Once you have created a device setup that you want to reuse, save it as a project template. When you have opened another project, you can load that device setup into the project using the menu: “project > project templates > load device setup”.
@pernst wrote:
Fritz,
I really appreciate all the work you have been doing on the application, it really is becoming easier to work with and looking great! I say this because the ever discontent masses must wear you good nature thin. Of course, I am bumping this thread to wear another layer off. The activity that takes me out Podium is correcting the timing of performances using the stretching functionality of another application. It would be a great benefit to me to have this capability in Podium.
Thanks for your time,
Paul
Exquisite wording 🙂
I’m working my way towards it. Before I start on time-stretching, I’d like to finish some lose ends I have with the track management. I can’t give a time-estimate yet.
Hi,
I’m using the Kjaerhus plugins under Vista, so that is not the problem. If you are having trouble locating the .zip files you downloaded from the website, try looking in the “Downloads” folder in your user folder with the Windows file explorer. You’ll need to extract the plugin .dll files from the zip files and place them in the folder where you keep your VST plugins. If you previously have installed some VST plugins, there is a chance that you already have a VSTplugins folder somewhere. If so, copy the .dll files to that folder. Otherwise just manually create a “VSTplugins” folder.
Podium should detect if you have a VSTPlugins folder in the expected locations. If you select the “New Project” command, you can see the “VST plugin scan folders” that Podium has found on the “Create New Project” page. If your folder is not there, click the configure button to manually point to the folder where you have put your plugins. Once you have done that, create the project, and Podium should create mappings for all your plugins.
Frits
I don’t have a W7 PC yet, so I can only speculate. Currently Podium does not call MMCSS, but I would expect it should be the audio driver that should set up its thread with MMCSS. It’s the audio driver that calls into Podium, and so the audio driver controls the thread. I could be mistaken though. Generally I will not recommend changing the registry as suggested in the topic you linked, unless you know how to undo your changes.
@thcilnnahoj wrote:
Navigator looks great!
My only gripe is that the “snapshot preview” is rather hard to see most of the time, but especially when previewing a snapshot that’s smaller than the current zoom range.Can you really tell where it is in this picture (thumbnail)?
My suggestion: Instead of showing both the current zoom range and the preview, temporarily remove the zoom pane and only highlight the snapshot area. The current snapshot preview doesn’t have the zoom pane’s handles, so I think the chance of someone mistaking it for the actual zoom pane is not very high anyway.
Good suggestion. Try the new beta5.
Beta5 also has a few bug fixes. If no bugs are reported for this beta, I’ll release 2.25 this weekend.
Follow focus track is nice too, but as expected, it doesn’t work with the embedded editor.
I thought about suggesting the tracks view should scroll to the focus track whenever it gets out of view (unless you manually scroll away from it, of course) – if you didn’t want that, you could just disable follow focus track on the ‘Editor’ editor profile.
…However, this poses another problem, as the event opened in the editor is not necessarily on the focus track at all. 😕So the best solution I can think of right now would be reworking it to just “Follow Selection” – as in follow whatever is actively selected (track or event)… I think that’d work very well. :-k
The purpose of the “Follow focus track” option, is to link track navigation between the mixer and the tracks region. I think extending it to react to event selection can result in mysterious scrolls, as long as it is possible to select events on other than the focus track.
@thcilnnahoj wrote:
A little weirdeness again: If you adjust an audio event’s volume handle and while dragging, move the cursor near the edge of the tracks region, it will start scrolling lightning-fast: Example GIF (the same happens if you increase volume on a track further down, of course). The area in the example is very cramped, but this happens to me sometimes when I’m on the mixer page, where the tracks view only gets ~40% of the screen. Of course it should scroll if you try to move an event up or down, but not while dragging handles, I think.
Fixed. Thanks.
Edit2: A similar thing occurs when you’re resizing a track near the bottom edge. The grabbed edge of the track doesn’t follow the cursor anymore after you hit the scroll area at the bottom: Example GIF.
I think this has been fixed with the new track height system implemented in the 2.25 beta. Let me know if you still have this problem.
I’ve also got a question related to this: What’s the point of being able to scroll down far, far below the last track, almost into infinity? Shouldn’t it behave more like the navigator, stopping when only the last track is visible anymore? Edit: Oh yeah, after you scrolled down so far you no longer see any tracks, the navigator still falsly displays events on the bottom track as visible.
I could add a limit, but I generally try to avoid imposing limits like these. Same reason you can (almost) scroll the timeline to infinity. If the topmost vertical position should be limited to the bottom of the last track, then various UI actions would cause the tracks region to scroll automatically. Say you have zoomed in on one of the bottom tracks. If you then collapse the master group track (in the mixer) this would cause the tracks region to scroll upwards to the now minmized tracks. When you then expand the master group track again you have lost the previous zoom position.
@Mike G wrote:
– When trying to zoom out past the ends of the current selection It’s harder to zoom out so that you can add more stuff after the end of the current arrangement, much harder than it was with a scroll bar. I will just add the scroll bar back in in my profile but wonder if the default setup could be made better. Can you think of a way of making this work in the navigator in an intuitive way?
The bext idea I can come up with is to allow scrolling of the navigator past the end of the last item in the arrangement.
I’ve enabled dragging the zoom pane beyond the length of the arrangement. I think it works ok.
@ronin wrote:
I’ve tested Beta 3 and it seemed to work as expected but I’m not 100% happy with the snapshot feature.
The snapshot feature would be more useful for me if it only remembers the zoom settings and not the view position. Instead the zoom should be centered around the edit cursor. This would allow me to set zoom settings for “edit crossfades” and for “arranging parts” for example. Maybe someone else thinks this is useful? Can this be added as an option for the feature?
Shortcuts would also be very important for that feature. I guess it is intended to speed up zooming so a shortcut would be a lot faster than seek&click 🙂
The new beta4 has key shortcuts for the zoom snapshots. I think it would complicate the snapshot feature a bit too much if it should be optional to exclude the view position from a snapshot.
@Mike G wrote:
– I’m not sure “Snapshot” is the best name, sounds like a freeze/bounce feature!! How about “Zoom setting”, or “navigator setting” or “Zoom notch”…?
Really? I thought the word snapshot was appropriate in the sense that it is a photographic snapshot of the zoom pane in the navigator. It may be more obvious with the snapshot mouse-over highlighting in the new beta4. Anyone else think that “zoom snapshot” is a misnomer?
– When trying to zoom out past the ends of the current selection It’s harder to zoom out so that you can add more stuff after the end of the current arrangement, much harder than it was with a scroll bar. I will just add the scroll bar back in in my profile but wonder if the default setup could be made better. Can you think of a way of making this work in the navigator in an intuitive way?
The bext idea I can come up with is to allow scrolling of the navigator past the end of the last item in the arrangement.
Is that because you use the horizontal zoom slider or the rightmost arrow button on the scrollbar? I mostly use the mouse wheel over the timeline ruler or the navigator to quickly zoom out and then zoom in on the new section. Sometimes I also use the Shift+Alt shortcut for the slide tool.
– I still keep thinking that the editor profile buttons belong at the top near to all the other “view” options/menus etc…
(…Ctd – Pause to wash a baby!)
Basically to me it feels that the editor profile buttons should control all that is below them. Lik emost of the other view options at the top of the screen. It particularly feels odd when you click “Big transport” and the profile buttons all jump away from where they were.
In know last time I suggested this it was for different reasons (I wanted to claim back the space taken up by the buttons)
Anyway i’d be interested to see what others think.
Considering the way that the profiles are implemented, it would make sense to put them at the top, as a container for the entire editor. I placed them at the bottom because then they are closer to the editor/mixer/transport, which is the only part that is different in the default profiles. Less distance to move your mouse.
@LiquidProj3ct wrote:
I don’t know if its the best moment for ask for this. Could have a track a default event colour and event colour relative to track color? Example, if you track color is yellow and you select black as note colour, the note colour will be yellow+black = brown.
I ask this because in nice colours designs I find this:
This is out of scope for this release. Remember to bring it up again when I resume work on updating the editors.
I will say though: With the extensive color customizations available in Podium, it’s impossible to ensure that all color combinations will stand out.