Zynewaveif I create a new arrangement with a any number of default tracks, including 0, there is no track, and I cannot create new ones
Please explain. I don’t see a problem here when creating new arrangements. Is your project set up properly with audio output mappings etc.?
But in compact mode it is not obvious to do because :
– there is no indication that a track is in record mode if it is hidden
– a R button must be available together the X and E buttons in the Inspector
– something must be visible on the track
I’ll get around to this. The same block that is shown for a track chain in the inspector will be shown on the track header. The record buttons will be available in this panel.
Is there a shortcut to switch between the modular and compact mode ?
No, and it is not stored in the screensets. You may find it necessary to switch between the two modes currently, but hopefully when compact mode is implemented fully it will not be necessary to switch to modular mode to do certain tasks.
ZynewaveBeta 1 of the 1.95 release can now be downloaded from the download topic in the VIP lounge.
There are still things that needs to be fixed, and more features still to come. But since this release has been in development for a long time now, I would appreciate some feedback on the new stuff. Here’s a list of the changes so far:
• The arrangement properties dialog has a new “track layout mode” option which can be set to “compact” or “modular routing”. The modular routing mode is the same as the layout used in previous Podium versions. The new compact mode presents the tracks in a simpler form.
• In compact track layout mode, all parameter tracks are shown at the bottom of the track chains. Parameter tracks controlling plugins further up the chain is shown with the parameter name followed by the plugin name in parentheses.
• The tracks in the group panel are divided into blocks for each effect chain (e.g. master chain, group chain and audio/instrument chain). Each block has a menu button with shortcuts for selecting and creating new tracks within the parent group. At the bottom of the menu is a “move track” submenu, which has commands for moving the selected track within the parent group, moving the track to a different group, and moving a range of tracks into a new group.
• The track context menu in the group panel has been redesigned. New commands include “new effect track”, “new bounce track” and a “move track” submenu which allows moving tracks around in the chain.
• Added “use as group track” option to the track properties dialog. Group tracks will be available in the new group panel menus with commands for managing tracks in groups. Note that normal tracks will appear as group tracks, if you have used modular routing mode to set up more than one child track.
• The “hide track lane” track option is now available for all tracks in compact track layout mode. This makes it possible to e.g. hide the track lanes for bus returns, if you prefer to adjust bus returns in the mixer. Setting up busses in the new arrangement dialog now by default hides the bus return track lanes.
• Shortcuts Ctrl+PageUp and Ctrl+PageDn will move the focus track up and down within the parent group.
• Specifying a color for a track will apply to parent tracks in a track chain if a color is not specified for the parent tracks.
• The buttons in the track headers are tinted with the track color.
• Added “black/white key intensity” setting to the piano roll properties dialog. Setting this to 100% will paint solid black/white keys.
• Added “hide muted ghost notes” option to the piano roll region dialog.
• The project name written in the browser page tab will blink once, as confirmation when saving the project.
• The E shortcut key now closes the editor if the plugin window has focus.
• Fix: The merge sequence command was not working properly when used in arrangements configured for linear time resolution.
ZynewaveZynewaveZynewaveThe option will be available in the next 1.95 release.
ZynewaveIt may prove to consume too much CPU to offer advanced metering on every track, but it could be implemented as a per track option. Most users would probably only need it on the master track.
ZynewaveI agree that there is no practical use for overlapping curve sequences. It will in fact create conflicts when playing back the automation. Later on I’ll probably implement automatic cutting of overlapping curve sequences when you drag or resize a curve sequence.
ZynewaveHow about a “hide muted ghost notes” option in the piano roll region dialog? You would then solo your horn section group track, and then only the horn sequences would be displayed as ghost notes.
ZynewaveZynewaveHere’s a couple of interesting articles about how to get rid of Vista bottlenecks:
Zynewave1. Scanning plugs:
Sometimes Podium will just not pick up certain folders. I have done this soooo many times on XP but on Vista it is very unreliable. I have folders that are set up as Compressors, EQ, Modulation e.t.c about 10+ different types of folders like this but Podium will only successfully find 3 or 4 folders.
Is it random which 3 or 4 folders Podium finds on each scan?
2. CPU spikes:
On XP Podium without any tweaking to the OS can run up to 70% – 80% without that CPU reading changing by more 2 or 3 percent, if that even. On Vista however I have found Podium to utilise 4 CPU’s very well but still on playback the CPU meter can be more “twitchy” on similar settings compared to XP.
This could be related to the soundcard driver. Is it the same soundcard you are using on your XP/Vista machines? Both running ASIO drivers? If you try with another host program, does this run equally stable on your XP/Vista machines?
3. Some plugins that worked in Podium (Sonitus VST) are now not loading properly. At that point I just switched back to XP.
This could be an issue with the plugins.
4. When Podium is accessing my hardrive to load a project sometimes the whole project start page will move diagonally about a cm upwards then fall back into place. Nothing like that in my experience on XP.
Strange. This may be a problem with the way I’ve implemented full screen mode. If you restore the Podium window so that it has a frame, does the window still jump when loading projects?
ZynewaveI think it is certainly very close to XP’s performance levels (Podium) but really there are one too many issues in Podium for serious work on Vista IMO. YMMV.
Can you please describe these issues. Are they all related to CPU spikes?
ZynewaveI don’t have a Vista machine yet, so that is why I can’t officially claim that Podium supports Vista, but some users have reported success with running Podium under Vista. If you have problems with CPU efficiency and spikes, it may be due to audio drivers. Which soundcard are you using? Are you using ASIO drivers? If you increase the buffersize/latency, does this influence the CPU spikes?
ZynewaveZynewave