ZynewaveBeta3 is uploaded. Bug-fixes and:
• Solo and mute commands are now always applied to the bottom source track in the chain. A muted track will automatically mute all effect tracks in the chain.
@H-man wrote:
Also, I think it is a problem that the meter doesn’t jump to the bounced track. I don’t mind changing it but you know, grizzle grizzle 😉
Good point. In the new beta3 the meters will automatically show the output of the bounce track when bounce is activated. This means you don’t have to change the meter track assignment, and as soon as bounce is decactivated the displayed meters will revert to the configured meter track.
Additionally, I don’t think that moving the fader to the bounced track is having any effect? I’ve tried several times but I’m sure it’s not working 😕
The bounce is captured after gain, pan and any level and pan automation is processed. So if the gain and pan controls are on the bounce track they will become inactive when bounce is activated.
Zynewave@UncleAge wrote:
@Zynewave wrote:
Hmm, where do you see the “blank title”? When I show the lane for the blank effect track named “Bounce”, the word Bounce is shown correctly in the track lane header.
Beta2
Ok, the blank line in the chain panel. I thought you meant the track lane header title. I’ve changed it so that a dimmed “Bounce” is written in the chain panel (and inspector group panel) if there is no effect assigned on the bounce track.
Zynewave@UncleAge wrote:
Now, if I could make one more suggestion, it might not be a bad idea to give the bounce track a name, when there isn’t one. When a user bounces an effect track the freeze/bounce is right there, so, no need for a name because a new track/lane was not created. However, when bouncing the source or bottom track there is a new lane created and if it is unhidden it will be present in the track header with a blank title. Clicking the properties for this lane already shows that it has a place holder name of “bounce”. I think this is good and I think it should show up in the track header as well (when that lane is not hidden). Maybe even in italics or right justified to make it stand out a little (not necessary though, just thinking out loud).
Hmm, where do you see the “blank title”? When I show the lane for the blank effect track named “Bounce”, the word Bounce is shown correctly in the track lane header.
However, I would still like to hear what the other users think.
So would I 🙂
Zynewave@LiquidProj3ct wrote:
@Zynewave wrote:
@LiquidProj3ct wrote:
I’m getting lots of crashes when Podium 2.06 scans my VST folder for create a new project. Usually the plugin that gives problems Tone2 Gladiator, last official version. But other plugins as IL Delay Bank (Image line Juice Pack) too. Sometimes Tone2 Warmverb too.
I think that those plugins are slow to load, maybe that could be the problem. The crashes are random.
Edit: Gladiator tries connect to internet when you load it
There are no changes in 2.06 that should affect plugin scanning behaviour. Can you confirm that the crashes also occur with 2.05?
Yes, I just tried in 2.05 and it crashes also (i’m on a VERY poor internet conection and my company is trying to solve). I noticed too that after the crash while I don’t press the buttons of the error windows (Podium.exe has detected a problem and it must close) of send or don’t do it, I can tweak Podium controls, and use it. then I open the plugin quarantine and the plugin that crash is always Gladiator. I can create an arragement and enter in it with the error window opened even!
I’m on Windows XP Home SP3, 1ghz dual core pentium, 1gb ram
I downloaded the Gladiator demo. I could not make it crash. The demo perhaps does not try to connect to the internet. Also I noticed that the Gladiator plugin refused to load when I’m running Podium in debugging mode. So even if I did manage to make it crash, it would be difficult for me to determine which VST function provoked the crash.
If you have the Gladiator.dll on the quarantine list, you can try to import it manually after a new project scan. Use the “import plugin” command from the Devices menu. If the crash is timing-related then it’s possible that importing the plugin this way will work without crashing.
Also note that if you complete a plugin scan and save a project template, you don’t have to scan all your plugins every time you create a new project.
Zynewave@Technophobia wrote:
I can confirm the crashes on the Beta.
It is on the first load/opening of the day of Podium.It wants to connect to the Internet and the Beta crashes if you don’t allow access (sometimes my connection is purposefully disconnected to stop interrupts upsetting the audio).
I have just tried the last full version (2.05) and though it wants to connect to internet, it does not crash if you don’t allow access, so the problem seems to be with the Beta.
Even on the Beta, once the first crash has happened and you open it again, it does not seem to want to connect to the internet so it runs fine.
Is it during the scanning of a particular plugin that it tries to connect to the internet?
Is it your firewall software which notifies you that internet access is attempted?
Zynewave@LiquidProj3ct wrote:
I’m getting lots of crashes when Podium 2.06 scans my VST folder for create a new project. Usually the plugin that gives problems Tone2 Gladiator, last official version. But other plugins as IL Delay Bank (Image line Juice Pack) too. Sometimes Tone2 Warmverb too.
I think that those plugins are slow to load, maybe that could be the problem. The crashes are random.
Edit: Gladiator tries connect to internet when you load it
There are no changes in 2.06 that should affect plugin scanning behaviour. Can you confirm that the crashes also occur with 2.05?
ZynewaveBeta2 is uploaded.
There is a new “Effect Track Properties” dialog, which is very similar to the “Track Properties” dialog, minus the “use as group track” option which only is relevant for source tracks. Settings that only are relevant for effect tracks have been removed from the “Track Properties” dialog.
Pressing the B shortcut key will enable offline bounce mode on a track that is not already bounce enabled.
@UncleAge wrote:
In a one track lane scenario as soon as I click the sub-menu for offline bounce a new lane is added to the track header, just as if I had added an effect track. The difference comes when there are effect tracks already present.
I opened up the project again to play around and figured out what should have been obvious. If I just disabled the effects on the track and did a bounce then I got the bounce I was looking for (which was a bounce of the bottom most track). Once bounced it appeared in the hidden lane of the upmost effect track. And this result is a bit different if all you have is just a bottom track.
The bottom track in the bounce submenu is no longer disabled. Selecting it will then insert a blank bounce track at the bottom of the effect chain, unless the parent effect track is blank and thus can be used as the bounce track. This should make it simple to set up bouncing of just the bottom instrument without the effect chain.
So there is a discrepancy in the visual feedback that I get. Now if I were bouncing the effect track the lane would be hidden. And the effects that are above this effect track would still be adjustable. Since this is the case why not create the bounce track above whatever track lane is used and make its default state “visible” instead of “hidden”. This gives instant feedback as to where the track is and doesn’t affect the hierarchy at all (I would think). And in the case where all effects have been bypassed I would want the bounced track to appear immediately above the last trak lane processed (in this case that would be the bottom most track). And the effect of this is to alow the user to offload some cpu intensive VSTi while still allowing them to sculpt the sound after bouncing the VSTi.
I wanted to make the default appearance of bounce enabled tracks appear as a simple freeze track. That means hiding the separate lane with the bounce events, and letting Podium handle the bounce event. I think that simple “freeze” functionality is what the majority of users want. Unhiding the bounce track with the option in the bounce menu I think will result in the appearance that you request.
Zynewave@H-man wrote:
So if I want to capture all the audio from a bounced delay effect the idea would just be to extend the track event well beyond the notes, or use the end marker you mentioned above?
Either solution would work.
Interestingly the bounce overlay on the master track extends when extending the event on any track automatically, however if the bounce track on the master is shown (un-hide) it does not resize.
The automatic resizing only occurs when the bounce track is hidden. I’m assuming that if the user has shown the bounce track lane, it’s because the user want to be in control of the events on the lane.
One thought, and I would be interested in opions of others here, is that (and I think this is what UncleAge was getting at) activating bounce is a bit-of-a chore.
Following the layout of the meter & fader menus is cool but it would be good to have hot-key bounce activation (with the ability to select mode) or move it to a more accessible place.
I could extend the “B” key shortcut to enable bounce mode when bounce is disabled on the track.
I’m going away for the weekend, so I won’t be here to answer questions until sunday night (GMT).
Zynewave@H-man wrote:
@Zynewave wrote:
@UncleAge wrote:
Will “Realtime Bounce” keep the tail end of the audio? I’m not familiar with “Realtime Bounce” and was only using “Offline Bounce” in the above example. Either way the bounce rendered fine except it was the same length of the midi clip which means there wasn’t a trailing reverb at the end. Will “RealTime Bounce” correct this situation?
Realtime bounce will not behave different to rendering in this respect. What I think will be my official recommendation is to put an “End” marker at the point where you would like the song fadeout to stop. The bounce sound events will resize to the position of the marker.
Delays & reverbs bouncing just fine here in both modes? I did notice tho that the bouce track is sizing to something unrelated to the recorded audio.
Could this be the loop/punch-in marker even tho it’s not activated?
The bounce events will resize to the full length of the arrangement. Not just the events on the bounced track.
Zynewave@UncleAge wrote:
Once again I may be reading you wrong here but… Are you saying that, by design, we won’t be able to bounce the bottom track?
You will be able to bounce the output of the bottom track, but the bounce track need to be above it in the chain. That’s how the old “insert bounce track” command worked. You should not configure the bottom track to be both the bounce track and the instrument track, because the bounce sound events and the note sequence events would then overlap on the same track lane.
Zynewave@UncleAge wrote:
After downloading 2.06 beta1, I only found three issues…
Thanks for testing.
**Offline Bounce**
In the bounce sub-menu it lists the name of the track and the effect tracks as the available choices. Except the track name is grayed-out and is not an available option. Which means in this case I can’t record TruePianos (at least not yet).If I go into the track properties and enable the bounce feature, I can then go back to the track and bounce the main VST, TruePianos. At this point, in the bounce sub-menu, the track name is grayed out still but this time it has a check mark.
At this point if I choose one of the effect tracks for bouncing and then return to the sub-menu again to try and check mark the track name again:
1. The option is still grayed and won’t allow me to choose it as an option.
2. The option for bouncing audio is un-checked in the track properties as well.
The track is grayed out because it should not be possible to bounce enable the bottom track in the chain. This is because the bounce sound events otherwise would overlap any other sound or note sequence events that is on the track. I’m going to change the track properties dialog so that the bounce options are disabled for the bottom track. I decided to include the grayed out track name in the menu, to keep the same chain structure as is shown in the Fader and Meter menus.
Note that if all tracks are grayed out in the bounce menu, enabling one of the options in the bounce mode submenu will insert a blank “Bounce” effect track above the bottom track.
In addition I would like to ask if it is proper to have the options split out into different menus (track properties vs bounce-sub menu). I know this may have been overlooked but I thought this would be a good time to bring it up.
I don’t have a problem with this. The same would apply to the Fader and Meter submenus. At least they are all located close to each other.
Will “Realtime Bounce” keep the tail end of the audio? I’m not familiar with “Realtime Bounce” and was only using “Offline Bounce” in the above example. Either way the bounce rendered fine except it was the same length of the midi clip which means there wasn’t a trailing reverb at the end. Will “RealTime Bounce” correct this situation?
Realtime bounce will not behave different to rendering in this respect. What I think will be my official recommendation is to put an “End” marker at the point where you would like the song fadeout to stop. The bounce sound events will resize to the position of the marker.
Let’s say I bounce at the EQ track. Then I change the sub-menu option to the reverb track because I want a rendered bounce at that stage in the tree. As soon as I change the option in the sub-menu the bounced audio in the EQ track is automatically transferred to the reverb track. No harm done really as I can move it or bouncerecord over the top of it. But I’m wondering why it wouldn’t just stay put and let me add another ender at a different stage in the chain.
Managing multiple simultaneous bounce tracks in an effect chain would complicate the bounce submenu I think. In these rare situations you will need to do a bit of manual work with the bounce options in the track properties dialog.
Zynewave2.06 beta1 is available in the VIP lounge.
Changelog so far:
• The bounce waveform on hidden bounce tracks will be drawn on top of the events on the track lane.
• Bounce sounds on hidden bounce track lanes will automatically resize to fit the entire length of the arrangement.
• The “B” bounce button is shown on the track headers and mixer strips, if there is any bounce enabled track in the effect chain.
• The old “insert bounce track” menu command has been replaced with a “Bounce” submenu. All effect tracks in the chain are listed in the menu, making it possible to select at which point in the chain the bounce should be executed.
• The Bounce track submenu has a “Bounce Mode” submenu with options for selecting offline rendering or realtime recording mode.
• Tracks set to realtime recording bounce mode now have a dedicated “activate realtime record” option in the Bounce submenu. This replaces the previous realtime record method of activating both the bounce and record button. The bounce button is painted red when recording mode is activated.
• Added “hide bounce track lane” and “unload plugins when activated” options to the “Bounce” submenu.
• Changed the key shortcuts for switching bounce playback and rendering. Pressing the “B” button or the B shortcut key will now perform a render, effectively acting as a freeze button. Holding Ctrl while pressing B will switch playback of previously rendered audio.
• Starting a bounce render will automatically create a new sound event on the bounce track if the previous event has been deleted or moved to another track.
• Extended the “control type” combobox in tracks region properties with a choice for hiding all controls on the headers.
• The controls on the track panel in the inspector will use the control style selected in the inspector view menu.
Note that the new bounce mode options are not yet saved in the project file.
ZynewaveYou can use the copy/paste menus in the object list. Load the project where you have made the drumkit presets. Open a List Window (Ctrl+L) and locate the drum kit preset objects in the device definition folder. Select all the objects you want to reuse and use the Copy command to copy these objects to the clipboard. Now load your new project, locate the proper device definition, and use the Paste command to insert the drumkit presets.
Zynewave@bladerunner wrote:
i have tried this with the ‘open new browser window option’ but its not as ideal as i had hoped. you can pull the mixer up as far as it will go but you still see lots of other elements within the same window(scrollbars and the timeline etc.).
You are on the right path. The Podium default setup includes an “Arrangement – Split Mixer” profile. Select this profile from the view menu in the second browser window. You can then customize this profile as you like.
Zynewave@ronin wrote:
It’s not very important what I have to say but If you (frits) are really going to implement the “track wide mute” please consider that some plugins produce noise or constant signals. I guess the lane track is the track where the midi/audio stuff resides? In this case a noisy guitar amp would still be audible if the bottom track is muted.
As part of the change, muting the bottom track will automatically mute all chained effect tracks.
