Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@Malcolm Jacobson wrote:
Hi Frits,
@Zynewave wrote:
- Clicking the middle mouse button in any of the timeline regions will set the edit cursor position.
I’m finding this very hard to use. My middle mouse button is a scroll wheel, so the timeline often scrolls when I try to set the edit cursor position. Is there some way I can customise the keyboard shortcuts in Podium?
Customization of keyboard shortcuts is not implemented yet.
If you are uncomfortable with using the middle mouse button, then you can still use any of the old methods of adjusting the cursor position.
ZynewaveKeymasterI’m no expert on XT2, but perhaps there is some place in the preferences where you can specify the location of the license file?
Podium is not involved in the XT2 license file validation.
ZynewaveKeymasterWhen Podium is exiting, it will “release” the drivers as one of the final steps. Thus if the driver somehow locks up during deinitialization, then Podium.exe may appear to hang.
ZynewaveKeymasterI’ve tried the DK+ 1.50 demo. I followed your instructions and tried various other things using two instances, but I can’t get it to crash.
Maybe you could try the DK+ demo and check if you can get it to crash.
ZynewaveKeymaster- Redesigned timeline ruler with new workflow enhancements.
ZynewaveKeymasterThe upcoming 2.07 release has several improvements that deal with the timeline ruler and cursor placement. I plan to release 2.07 this weekend.
ZynewaveKeymasterThis is improved in the upcoming 2.07 release. The timeline ruler have several new layout options, and middle mouse button can be used to set the edit cursor in all the timeline regions.
ZynewaveKeymaster@sam c wrote:
how do i set my offline bounce to mono prior to the bounce?
You can unhide the bounce track lane, and then open the properties dialog for the bounce sound.
Note that if you change the bounce sound to mono, Podium will not bounce-record any panning you’ve applied in the chain below the bounce track.
ZynewaveKeymaster@aMUSEd wrote:
With the latest version automation is working properly at the start of the track now but if I stop moving a knob but carry on recording (or move onto a different knob) the knob position is dropping to zero on playback from that point which ruins the track. It should stay where I left it.
I’m considering changing this behaviour in a future update. For the time being you need to resize the curve sequences to the full length of whatever they control, to avoid that the parameter value snaps back to the default value.
ZynewaveKeymasterOoh, what a silly bug 😳 . I assume you are talking about auto-assigned audio inputs. Apparently I have only ever tested recording with auto-assigned MIDI inputs. Auto-assigned audio inputs do not record. Fixed for the next 2.07 release.
ZynewaveKeymasterIt’s possible that DK+ cannot cope with multiprocessing of multiple instances. Try disabling the “plugin multiprocessing” option in Podium preferences, and see if this fixes the crash problem.
ZynewaveKeymaster@sam c wrote:
from someone who did not follow the betas but just downloaded the update tonight i wanted to tell you two initial things-
it is a little difficult to figure out the bounce off line, real time, hide lane, etc. it just is not intuitive.
What do you suggest needs to be changed?
also, i have never been able to render or off line bounce amplitube. but a new difference is the cpu load. in 2.05 and prior amplitube is a 22% hit on the podium mix cpu meter. on 2.06 it is 47%. i have double checked these numbers.
i will keep working with the update to see if i can get a handle on it. hopefully the cpu hit you can check out?
I don’t have Amplitube installed. Is it just with this plugin that you see a difference in CPU usage?
ZynewaveKeymaster- Improved bounce track system, with simpler freeze functionality.
ZynewaveKeymasterI’ve added a “Select All Broken Plugins” command to the Devices menu. You can then right-click the selection to delete them or move them to a new folder.
ZynewaveKeymasterBeta10 is up. This hopefully is the final beta. If I don’t find any bugs tomorrow, I’ll release 2.06 this weekend.
I’ve optimized and made minor changes to the way that solo and mute works. It is now possible to solo a bounced track, and still have the bounce playing. Previously the solo would disable the bounce.
If you have some spare time, please try this beta10 and check if your old arrangements still behave as expected.
@LiquidProj3ct wrote:
Cool, thxs. I think that at least the pan should be untweakable althought, visible but untweakable. It would seem more natural.
Perhaps in a later update. The way I see it, if the pan control should be disabled, then there are a lot of other inactive controls (bypass, sends, automation sliders, plugin editors, etc.) that also should be disabled because they have no effect when the track is bounced. And I think that would be a bit too much.