Zynewave's Forum Page

@thcilnnahoj wrote:

@Zynewave wrote:

Btw. I’ve modified the default track coloring slightly in the new beta14, and specified a new default track color. Let me know if the new default colors present problems.

I only did a quick test – is it correct that default track color is not applied to colorless tracks anymore when you save a project? That’s the reason I never used it in the first place, as it quickly became a mess, but it looks like it has been fixed already somewhere along the way…?

Correct. I changed this very early in the 2.23 development.

From what I can tell, these are the problems I’ve found that made it as far as beta 14:
– Slider value pop-ups become stuck when changing profiles or closing the inspector with shortcut keys.
– The bypass buttons on the selectors do not update to a newly selected mute color until the UI is refreshed.
– If you open the mixer and then select a track in the arrangement view, the mixer strip uses the active selection font color instead of the inactive one.
– Sometimes, the group expand/collapse button will ignore the track color and be colored with the panel background color instead.
– When you’re dragging a device to a track, the selector button’s pop-up help gets a little in the way as it blocks the view of the chain.
– When you drag-and-drop an instrument to a track in a particular way, the “drop here” box overlay on the track becomes stuck. You can even ride it up and down using the scroll-wheel. Yee-ha! 😆
Here’s a GIF animation:

Thanks for the summary. Beta15 fixed these issues, except:

– If you open the mixer and then select a track in the arrangement view, the mixer strip uses the active selection font color instead of the inactive one.
– When you’re dragging a device to a track, the selector button’s pop-up help gets a little in the way as it blocks the view of the chain.

These are now fixed.

@Mike G wrote:

When selecting a track in arrangement it slides the track into view in the mixer, which is great.
However when selecting a track in the mixer it doesn’t slide the track into view in the arrangement… please can it, (Is there some config I need to set, I thought it used to do this… but I could be mistaken)

Good suggestion. Not going to make it into this release though.

@H-man wrote:

@Zynewave wrote:

@H-man wrote:

As mentioned I’d like the state of the inspector and browser to be stored/recalled across tabs as well.

Please clarify.

A feature request really. At present the Inspector/Browser is independent of the Editor Profiles. I just though that if one was working on the Editor page with the Browser open, switching to the Mixer might have it hidden and on the Tracks page (profile) it could be shown but the inspector (for presets) rather than the browser.

Ok, understood. That’s a FR for a later release.

@Zynewave wrote:

@H-man wrote:

Clicking on a track in the rack doesn’t highlight the corresponding track in the mixer or track headers (ie. Group track).

If the track is shown in the rack, then it is already the focus track, and so should already be highlighted in the tracks and mixer regions?

I guess all I was saying was that clicking on a track in the rack, group, parameter or otherwise doesn’t update the focus on the Mixer or Track Header. If that’s the desired behavior then …okay.

I’m still not sure what you mean. Are you referring to effect tracks? They were previously highlighted individually on the track headers/strips, but this was something I never liked. With the new chain panels, all key shortcuts will influence the source track, and so the selection of an effect track is now only relevant for the inspector list panels.

One final thing, is intended that “Insert new effect track” is now gone from the Track Menu?

Yes. I’m trying to trim down the track header/strip menu to a minimum. I’m thinking that if you want to insert effects, you would want to do that using the new chain panel, where you visually can verify the result of the insert command. If it was available in the track menu, you could keep inserting effects without any visual indication of the action.

@pavouk100 wrote:

Automation recording bug(?); have track with some recorded audio, add some effect and try to record automation like this:

– unassign track input
– arm track for recording
– press ‘record’ and then ‘play’ button on the toolbar.

If you fiddle with any effect control on the armed track, automation lanes are properly created and recorded, but there is no sound coming out of the track at all. Or is it my misunderstanding how automation should work now?

Tested is on beta14.

Well, this is because I so far haven’t done enough testing 😳

The track is silent, because Podium currently mutes record enabled tracks.

As I see it, there are two ways I can fix this issue:

1/ Enable playback of a record enabled track, if there is no input assigned or if the input is bypassed.

2/ Add a new “Automation Record” track option. This will be placed below the “Record” option in the track menu. I would like to avoid having to add another button for this, so perhaps Ctrl+R key shortcut or Ctrl+clicking the R button could toggle this track option. This solution adds the complexity of having another track option with a somewhat hidden access, but on the other hand it will allow automation recording without having to bypass or remove any audio inputs assigned on the track.

Which solution do people prefer?

Beta15 is up.

I have finally finished my code review of all the changes in 2.23. I think most of the reported bugs have been fixed in the process, but I’ll go through all the bug reports over the next couple of days. If no big bugs appear, I hope to have a release ready for friday. Many of the good suggestions for improvements that have been posted in this thread will make it into a later release.

New in beta15 are shortcut buttons in the mixer for showing/hiding effect chains, new effect buttons, source and input selectors. The parameter selector on parameter tracks are now aligned to the effect selector in the parent strip that is being automated.

@thcilnnahoj wrote:

@Zynewave wrote:

Sure. Probably coming in 2.24.

Otherwise known as Podium 4.0! =P~

@Zynewave wrote:

– I think the ‘default track color’ setting is ready to be retired. With the default opacity settings, it messes everything up if you select anything but shades of grey.

Can you clarify?

Um, I’ll try, but I can’t guarantee that my explanation will make sense to you! 😆
For reference, example 1 has 2.23’s default color settings: overall color opacity 100%, track background opacity 20%, some random track colors and no default track color assigned.

Before 2.23, you could select a default color and still override it when you set per-track colors, provided you set opacity to 100%.
Now, the strips are always colored, even if you set rack/header/strip opacity to 0. Even on higher opacity levels you don’t override the default track color but can only add various track colors to it instead. So you have a choice between all track backgrounds being pretty much shades of the same color (ex. 2, low opacity) or getting a real color mix (ex. 3, high opacity), like in previous versions, but coloring the whole strip this time. All in all very bright compared to the default settings. (Edit: It can of course be dark as well – I meant to say it’s quite intense.)
Setting the default color to a shade of grey is a little more useful, as you can make tracks appear generally brighter or darker, if moderately applied. (Edit: Sorry, this is of course not correct. It can be achieved by setting a lighter or darker shade of the panel background color! It’s just that I always use grey…) 😉

Thanks for the screenshots. You’re right. I made an experiment in beta11, where the opacity setting would fade into the default track color, instead of the panel color. That resulted in the fully colored track background in your screenshot. I’ve now reverted back to fading into the panel color. That makes the “default track color” still relevant, I think 😉

Btw. I’ve modified the default track coloring slightly in the new beta14, and specified a new default track color. Let me know if the new default colors present problems.