bladerunner.
aMUSEdI’m trying this now with my Virus Ti but it doesn’t seem to be doing anything. The Ti needs a realtime bounce so I have recorded a track and in the rightclick/bounce menu selected realtime bounce mode. However when I then click on the B button all that happens is 2 orange lines appear (instantly) but it doesn’t seem to be doing anything else (that was all I needed to do with the offline bounce for normal VSTis)
Do I need to select anthing else? – do I need to also select the realtime record ?(not sure what that’s for?)
aMUSEdOh great – now I’ve clicked on the B button again and the whole app has frozen.
aMUSEdI see – I need to record the midi first. Then activate bounce record and play the track back.
Working now
but for some reason it’s recording automation but not playing it back.
aMUSEdAutomation recording seems screwy with regular VSTi’s too – just recorded something with Alpha Cm and playback was all wrong
(Just realised 2.05 has the same bug)
Technophobia@ Frits
I have just tried using Beta 3 ( I know I am one behind ) and it still wants to connect to the Internet but does not crash if I stop access.
When an arrangement was opened up it had finished loading the arrangement it then asks to connect to the Internet.
It is not a big problem as long as it does not start to crash on every opening. I’m guessing it is still some plugin or other causing it somehow ?
UncleAge@Technophobia wrote:
@ Frits
I have just tried using Beta 3 ( I know I am one behind ) and it still wants to connect to the Internet but does not crash if I stop access.
When an arrangement was opened up it had finished loading the arrangement it then asks to connect to the Internet.It is not a big problem as long as it does not start to crash on every opening. I’m guessing it is still some plugin or other causing it somehow ?
Hey Tech, just as a side note on this problem you’re having…
Podium hasn’t done this on my rig. I have had vst’s try to access the internet during a scan or initialization in various daw’s but never Podium itself. Please keep us posted. I am curious about the end results.
Thanks
H-man@UncleAge wrote:
@Technophobia wrote:
@ Frits
I have just tried using Beta 3 ( I know I am one behind ) and it still wants to connect to the Internet but does not crash if I stop access.
When an arrangement was opened up it had finished loading the arrangement it then asks to connect to the Internet.It is not a big problem as long as it does not start to crash on every opening. I’m guessing it is still some plugin or other causing it somehow ?
Hey Tech, just as a side note on this problem you’re having…
Podium hasn’t done this on my rig. I have had vst’s try to access the internet during a scan or initialization in various daw’s but never Podium itself. Please keep us posted. I am curious about the end results.
Thanks
Yeah same boat here. I often disable the network adapter before starting Podium so that I can turn off AV and free up some resources …and minimise distractions 😉
@aMUSEd: I have been using new arangements for the Beta testing as a rule but I did have a ‘lock-up’ with a track that had been bounced using Beta2 when testing Beta 3.
New Arrangement fixed the problem.
Not sure about the automation bug but the rest of the changes are great IMO.
UncleAge@H-man wrote:
Again, I like the new changes.
I did notice that when using the Punch markers to set the bounce range (offline mode …and real-time I think), the bounce process is non-destructive.
That is, you can bounce bars 4 to 8, change the preset of whatever vsti is loaded on that track and then bounce, say, bars 12-14 with the new sound and you end up with the old sound from the previous render and the new sound.
Extending this and again using the Punch Markers, it is possible to add a couple of ef-ex to the track, move the bounce to the end of the chain and render another section with effects with out impacting the previously bounced sections.
I’m not entirely sure but I think that might be brilliant 😯 Maybe this was possible previously but if so, it has transferred seamlessly.
Now all that remains (to rule them all) is a “Bounce audio and copy event to new track” option 😉
H-man, I haven’t been able to wrap my head around the punch markers approach you’re talking about here. I’m still messin’ with it even though I may be making things harder than they need be. When I have tested the real-time bounce I, un-hid the efx, doube-clicked to add a clip, ctrl-b, hit record on the transport and recorded a clip. Any info on how to use the punch markers would be appreciated though.
In addition, I do think its pretty cool that I can add several clips in different parts and have them as separate renders all from the same pass. And again, I can change the efx around and generate different clips. I think this could pan out to be a real handy feature.
H-manHey UA,
The punch-in markers are located on the transport bar and the range is indicated by the red marquee on the time line.
Once you activate the punch-in markers, a new option appears in the new bounce menu (when offline mode is selected – the default) “Render within punch range” (or someting like that).
This can all be done with the bounce track hidden. As mentioned, rendering different ranges along the track preserves any previous renders on that track, even if effects are added and the bounce is moved to the new effect.
😀
UncleAge@H-man wrote:
Hey UA,
The punch-in markers are located on the transport bar and the range is indicated by the red marquee on the time line.
Once you activate the punch-in markers, a new option appears in the new bounce menu (when offline mode is selected – the default) “Render within punch range” (or someting like that).
This can all be done with the bounce track hidden. As mentioned, rendering different ranges along the track preserves any previous renders on that track, even if effects are added and the bounce is moved to the new effect.
😀
Thanks,I appreciate the help and I got this to work. However, when creating a bounce clip this feature creates a clip that is as long as the arrangement. I’m not sure when I would want this type of result.
If I just wanted a small clip of a section of the song I think adding a blank clip is a bit tidier for me. Its really 6-of-one or half-dozen-of-another really because its just as easy to trim the clip as it is to create a blank one. However, there is one advantage to adding the clip(s) ahead of time (instead of punching in) if you want more than one clip created. And that is, you can make several blank clips and render them all at once if you so desired.
With that said I am still trying to think of a practical application for this functionality outside of some stuff I’m trying out on background vocals. Either way, thanks for the help H-man 🙂
H-man@UncleAge wrote:
If I just wanted a small clip of a section of the song I think adding a blank clip is a bit tidier for me. Its really 6-of-one or half-dozen-of-another really because its just as easy to trim the clip as it is to create a blank one. However, there is one advantage to adding the clip(s) ahead of time (instead of punching in) if you want more than one clip created. And that is, you can make several blank clips and render them all at once if you so desired.
That’s cool UA. Just playing with workflow ideas. I think that one of the best things about working with the betas is that you get a very comprehensive understanding of Podium’s (new) capabilites and features (I’m sure I write that after every beta).
Point is, It’s much more fun for me to learn this way than ploughing throug a pile of tutorials. 🙂
BTW, You are talking about unhiding the bounce track and creating multiple blank events that can be rendered in one pass right?
Ben
UncleAge@H-man wrote:
BTW, You are talking about unhiding the bounce track and creating multiple blank events that can be rendered in one pass right?
Yes.
ZynewaveBeta5 is uploaded:
Added “deactivate all bounce tracks” and “render all inactive bounce tracks” commands to the arrangement editor file menu.
Similar to the solo and mute options, the group collapse option is now only available on the bottom source track in the chain. So if you reveal the track lane of an effect track, this will no longer have the collapse button.
Realtime bounce recording will have a “red” waveform overlay showing the progress of the recording.
I think I’m done with adding new features to the 2.06 release. I’m going to spend the rest of the week testing, and hopefully make a release in the weekend.
Zynewave@aMUSEd wrote:
Oh great – now I’ve clicked on the B button again and the whole app has frozen.
Thanks for testing.
Can you remember if the bounce track was set to offline or realtime bounce mode? I.e. did you see the render progress dialog when the app freeze occurred?
Zynewave@Technophobia wrote:
I have just tried using Beta 3 ( I know I am one behind ) and it still wants to connect to the Internet but does not crash if I stop access.
When an arrangement was opened up it had finished loading the arrangement it then asks to connect to the Internet.It is not a big problem as long as it does not start to crash on every opening. I’m guessing it is still some plugin or other causing it somehow ?
If the connect request happens when powering on the arrangement (i.e. when plugins are loaded into memory), it is most likely one of the plugins you have assigned on the tracks that tries to connect.