bladerunner.
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.
H-manOkay, interesting.
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?
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.
Having written that I do agree it means practically nothing …just playing.
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.
H-manOh, and I do like the incorportation of the punch range into the bounce menu 8) .
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).
UncleAge@Zynewave wrote:
@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.
Ok. I think I found out what I was doing wrong and also have a suggestion.
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.
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.
Also, I hope you have a great weekend. As a matter of fact I hope you have already turned all of this off and have left the building 🙂
And yes, I know I’m a little too long winded at times 🙂
LiquidProj3ctI’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
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@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?
TechnophobiaHi Frits,
Good weekend I hope… 🙂
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.
I do not have Gladiator installed at the moment, so it is not that causing the problem. I have Kubik, Ogun, Morphine, Cameleon and Atomic installed at present.
Using Win XP with Dual core, if that helps. Any other info you need, let me know.
UncleAge@Zynewave wrote:
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.
So far, so good. 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).
I got some more testing to do so I write back later if I find anything else. Otherwise it is shaping up to pretty much what I would expect from this type of functionality. However, I would still like to hear what the other users think.
LiquidProj3ct@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
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:
@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@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 🙂
