ZynewaveHi,
You can’t do this just by organzing the track tree. A track cannot have more than one parent. To route the output of a track to several tracks, you need to use bus send/returns. You place a bus send above your original track, and then insert as many return tracks as you want feeding your target tracks. Note that busses currently does not route MIDI.
Say, I want to configure a MIDI track to send data to several tracks with VSTi-s.
You can work around this by pasting phantom copies of the events to the other tracks.
Frits
ZynewaveIn the image above, if I want to expand the Cs1x dropdown, I currently need to click the ‘+’ symbol to do this. Is there any chance it could be tweaked so that clicking anywhere in the highlighted yellow strip would expand the dropdown instead ?
Then you wouldn’t be able to select an object without it automatically expanding/collapsing. If you use key navigation you can use +/- or arrow right/left to expand/collapse the current object.
When collapsing / expanding track groups, it currently affects the mixer area along with the arrangement window. Would it be possible to allow the groups shown in the mixer to be collapsed / expanded seperately from the arrangement groups ?
Currently they are linked. I may decide to cut the link of the minimize track option (shortcut H), and add an independent “show mixer strip” option. The mixer view menu has some options to override the track collapse states.
ZynewaveThanks for your feedback iain.
1. Inability to load a VST and VSTi in the same track. I see how this is more like a hardware mixer, but as noted elsewhere in this thread, it’s a facility I now expect in a DAW.
You can only have one mapping on each track, but the idea is that you chain together tracks to make a chain of e.g. VSTi > VSTe > sends. This allows for more flexibility but the challenge is to make it easy to handle the setup of the chains. This is a part of the UI that I’m focusing on currently. Recently there have been a number of improvements to the mixer, and I’m continuing work on this.
2. Drag and drop from Stylus RMX was strange.
Proper support for drag and drop from plugin editors and external media browsers was implemented in 1.88/1.89. There is no demo version of these releases, but the next 1.90 will be released as a demo.
3. Waves VST plugins didn’t work properly, but I appreciate this is probably because of their Waveshell system
It’s been a long time since I last tried any Waves plugins, but from what I remember: Once you have selected a plugin from the Waves popup menu, Podium logs this code in the mapping so that the same plugin is opened the following times. To use additional Waves plugins you need to import the plugin multiple times, each time selecting a different plugin from the popup. You then won’t be bothered with the Waves popup when you assign the plugins on tracks.
On the one hand it was beautifully easy to open a plugin and select a program for it. But on the other hand the names of the VSTs were a bit of a shambles – different to how they appear in other VSTs. Multiple instances of the same VST all with the same name and further sub-categories (Stylus and Absynth are two examples of VSTs that looked confusing).
These are “global” plugins (as opposed to “insert” plugins). They have multiple mappings that you use to access the same instance of the plugin.
Finally regarding the VSTs, Podium ‘imported’ them at length each time I opened the program – pretty time consuming.
To avoid the reimport: Once you have created your first project, and have imported all your plugins, you can save that project as a template with the file menu. The next time you start on a new project, you select this template from the new project submenu.
One last thing: reading the forum, I see there may have been some issues with getting sustain working.
Since then, I have implemented a menu popup in the parameter panel, which have shortcut menus for creating default MIDI parameters, including sustain.
Frits
ZynewaveHi,
I looked briefly at the ER-1 MIDI documentation, and I don’t think it supports MIDI time code (MTC). Instead it uses the MIDI timing clock and associated start/stop/continue and song position commands, which is unrelated to MTC. Podium can transmit timing clock (to tempo sync external devices), but does not yet transmit start/stop and song position commands.
ZynewaveZynewaveFor some reason, 1.89 would crash on startup until I deleted my podium.ini file for v1.87 from ‘ Application DataZynewavePodium ‘
Fixed. It was related to the selection of a MIDI interface for the MIDI metronome.
ZynewaveWill we see support for song position pointer and a tempo controlled metronome too?
For this, Podium must support slave sync. As we have discussed in another thread, other features need to be implemented before this is possible.
ZynewaveIt seems to recall an *existing* project with the current settings as I left them in Stylus but if I start a new project, Podium (even though I save the project) will “forget” the settings, so Stylus keeps loading up “empty”.
Could your new project be based on an old template made before automatic preset saving was implemented? Check that there is a library preset assigned to the track.
Zynewave@Conquistador wrote:
I have now had this exact same error with Podium 1.89. 😯 I am using an Edirol UA25. The interface works properly in Sonar but Podium keeps giving me the same error message that Moody B has been getting.
I am having this problem on Windows xp.
Send me your Podium.ini file.
ZynewaveIt seems to be saving the .ini file as it remembered my colour prefs, etc, it just doesn’t activate the midi ports even though they are listed in the .ini file properly.
I think I have an answer to that. I looked at your ini files, and it seems that the EMU interface names have a space at the end. This space is saved in the ini file, but when the Windows API function loads the string from the file, this space is removed. Thus the device name comparison no longer matches.
To make this work I need to remove the trailing spaces from the device names before doing any comparisons. I’ll fix that for 1.90.
ZynewaveYes, please send the 1.87 ini file.
Are you saying that if you select the EMU interfaces, exit and restart, then the interfaces are no longer selected in the interfaces dialog?
If so, that is very strange. It suggests that the Podium.ini file is not saved properly when Podium exits.
ZynewaveIf you select the EMU MIDI interfaces, exit Podium and restart Podium, doesn’t the error message appear then?
Zynewave@MoodyB wrote:
Thanks Frits.
I’m going to see if I can return the Emu interface and get an Edirol one instead tomorrow.
If you have time, please try the EMU interface with release 1.89. I’m curious to know what error message is logged for the EMU.
ZynewaveZynewaveYou’re not the first to report problems with EMU MIDI drivers. I’ve added extra MIDI error logging in the 1.89 release, which is going up later today. When you try this, go to the report page and tell me the MIDI error shown in the report.