Zynewaveis there a reason why the gain and pan dials are shown above the track names in the inspector ?,
The gain and pan dials are positioned in the list according to the order they are processed in the signal flow. So the output of mdaPiano is adjusted with the gain and pan before going into zPEQ. The list thus always shows the correct signal flow, from bottom to top, as indicated by the arrow column at the left edge.
ZynewaveStrange – that was the first thing I tried and if I’d found that straight away I’d have had no problem – but all I get is a menu giving me a selection of tools (pencil etc) no matter where I click on that track.
Click on the track header.
Zynewave@aMUSEd wrote:
Thanks – what would I do if I wasn’t using the compact menu?
It worked but it would be better for me if there was an option to do this from the menu rather than having to know a keyboard shortcut which isn’t really very obvious – is there a menu command that does the same as ctrl B?
Right click the bounce track -> “Render Bounce Track”.
ps I’m finding the compact menu is motivating me to learn Podium now – before it just looked too daunting. However if there are too many options or commands are hidden away as shortcuts that makes it much harder to learn.
I’m glad to hear that. The new menus was redesigned with focus on workflow rather than exposing all barebones track options. Also more track management functionality has been added so that you don’t have to turn to the track inspector to do certain tasks.
ZynewaveIt would be a big help if you can email your project file (no need to attach the wav files).
ZynewaveI haven’t forgotten about this. Currently I’m focusing on getting the compact mode finished. Eventually I’ll look at the issues discussed here.
ZynewaveI tried selecting track properties and clicking the boxes where it says “use track for audio bouncing” and “unload plugins when bouncing” and then got an option to “render bounce track” but nothing happens when I select it – I just get a message saying “there are no bounce track sound events that can be rendered” – what does that mean?
I’m assuming you’re using compact track layout mode (option in the arrangement properties dialog). Undo your bounce option changes in the track properties dialog, and instead use the “insert bounce track” track menu. This will create a separate bounce track and automatically add the bounce sound event. Note that if your effect chain contains sends, you need to insert the bounce track below the sends, or else the sends will not send audio. So right click the topmost non-send effect in your chain and select the “insert bounce track” command. Then use the “render bounce track” menu (Ctrl+B).
For the compact track layout mode I’ll probably remove the bounce option in the track properties, and instead create a “bounce track properties” dialog for bounce tracks that have been created with the “insert bounce track” menu. Your case is a good example of how too many options can be confusing for users that are learning Podium.
Also how do you export a track in an audio format?
The bounce sound event on the bounce track will contain the rendered/exported audio. You can check the sound properties to see the location of the wav file.
Zynewavedo you prefer individual tracks for fx?
When you insert an effect using the new compact mode the effect will automatically be assigned to a separate track, instead of directly on the lane track. That’s the recommended procedure, as this makes it easier to manage and reorder the effect chains.
Zynewavei don’t lose my gain like before but i do lose pan. why?
The pan dial will disappear if the effect mapping you insert is a mono effect. I just checked, and the pan dial is not lost when inserting stereo mappings.
Zynewavewill this change obscure some of the toolbar when the inspector is open ?.
Opening the inspector will shrink the space available for the entire editor instead of just the tracks region, so the toolbars will have less horizontal space. Depending on the screen resolution you use, you may have to trim the elements in your toolbars to avoid that the right edge of the toolbar becomes obscured. That’s about the only disadvantage I can see with the new layout. Overall I think this new layout is a big improvement.
Zynewave@thcilnnahoj wrote:
Turned out great! 8)
Still, here are two cosmetic flaws I noticed:
1- Both the GP and the compact track headers seem to ignore the “active selection text” color setting, making somewhat hard to read with most color schemes. 🙁
2- The input mapping name extends a bit too far. Maybe somebody else can confirm this?
Both flaws fixed for the next release.
Thanks.
ZynewaveAlso why do some plugins make loads of different versions? – Cube for example has a Cube 1. Cube 2 – a dozen variants. It’s making the whole plugin menu look rather messy.
If those mappings are inside a subfolder, then the plugin is imported as a global plugin, meaning there are separate mappings for accessing the multiple input/output and MIDI channels for a single plugin instance. If you only intend to use the plugin with a single MIDI channel and single input/output it will be easier to use the plugin with an insert mapping. Use the “new insert mapping” command when right-clicking one of the plugin mappings in the start page device list.
ZynewaveZynewaveChanging the “default vst plugin folder” in preferences does not cause a rescan. Use the “import plugins from folder…” menu command from the device panel on the start page. Select your root VST folder to do a complete scan. If you had plugins that crashed during scan at project creation, they will also crash when doing the import later on. Podium will log the last scanned plugin, and on restart it will notify you of the problematic plugin and put it on a quarantine list. Repeat the scanning until all crashing plugins have been put on the quarantine list.
Zynewave1.95 is released.
I had a hard time writing the release note. I’m sure there are some new features I’ve forgot to mention. Maybe I just should have written “new and improved” instead of trying to list all the details 😉
If you find bugs in 1.95, please report them in the release topic.
Zynewave