Topic: Preview: Compact track layout

@Zynewave wrote:

More experiments. This one I would really like your opinion about.

YES! This is wonderful! Love it, although it reminds me (not in a bad way) a little bit of Cubase. 🙂

@Zynewave wrote:

Is the problem only the lack of precision when dragging the pan slider?

Not at all, I’m just very used to it this way from other hosts.
I wanted to suggest for the slider to be equally adjustable on both axis, like your dials behave. I don’t know if it would be awkward to others…
I can live with it if you decide against this. 😉

@Zynewave wrote:

Previously the entire track lane headers have been colorized with the track color <...> Depending on the colors selected for the track, it can be difficult to distinguish lit BSMRX buttons and text. I’ve tried a layout where only the right edge of the track lane is colored, and the main header area is using the normal face color.
<...>
Furthermore you may notice that I have added a spacing between track groups, making a clearer division between groups and parameter tracks.

Very good in both cases!

@Zynewave wrote:

Anyone still prefer the old colorized track headers? Otherwise they are going out.

Let them go.

🙂

/SQ

Frits, i think the tracks losing gain and pan control when you ad an fx is important. i feel it would have been worth an update to correct right away. consider how often we put fx on a track and remove and try again, etc., especially during mixes!

@Zynewave wrote:

On another note, do you have any sort of time frame for a release of 1.95?

It has been more than 8 weeks and AFAICT there are some bug fixes that are in 1.95.

There are no important bug fixes coming in 1.95.

One fix in particular I was referring to was the drag and drop FX bug that removes Gain and Pan dials. Very serious indeed. Guaranteed to waste a huge amount of time in everyday usage. It may be possible that your usage of Podium is understandably more on the back end development side and not the front end everyday project user side that we as your customers reside on.

It’s down to personal preference of course but a fix that might take you a short time to implement or one that is not important to you does not in anyway mean it is not important for other users. I am surprised you thought that particular bug was not “important” it is a major hassle during everyday usage of Podium.

Otherwise I wouldn’t wait this long with the release of 1.95.

So if there were no fixes at all you would wait even longer to release 1.95?

Sounds like we are now moving to a longer development cycle for Podium releases (and of course fixes) in future if that is the case, which is fine if that approach works best for you. Is that a correct assumption?

The available 1.94 demo time expired yesterday, so I am trying to wrap up what I have made so far. Hopefully 1.95 is ready within a week. This means the compact mode unfortunately will not be as completed as I had hoped. I still have to do some work on the track menus.

Thanks for the clarification. But IMO a 2 – 3 month beta for Podium is very long indeed and any changes that could not make it into 1.95 can of course still make it into 1.96 in future anyway.

Thinking aloud…
I just hope we are not looking at 6 releases over a year instead of the usual 12+. But if a longer dev cycle is the only way forward even if it impacts the time frame for fixes, then that is OK but the quicker releases are what separates Podium from many other hosts out there.

@sam c wrote:

Frits, i think the tracks losing gain and pan control when you ad an fx is important. i feel it would have been worth an update to correct right away. consider how often we put fx on a track and remove and try again, etc., especially during mixes!

I could not agree more. While I appreciate we all use Podium differently (especially Frits as a developer) this bug wastes a huge amount time. I am surprised a fix was held back this long (not deliberately of course) but I guess I just thought Frits would see the severity of it and release 1.95 sooner. Anyway hopefully a week from now (as Frits said) 1.95 will be released. 😉

@Igr0 wrote:

@Conquistador wrote:

@Zynewave wrote:

how does the Mixer look now? Are you making these changes there as well or leaving it as is?

I’m not changing the mixer this time around.

Ok cool. 🙂

On another note, do you have any sort of time frame for a release of 1.95?

It has been more than 8 weeks and AFAICT there are some bug fixes that are in 1.95. While I am happy to keep going with the beta’s as it is quite fun to see the evolution of Podium in this way, perhaps if possible it would be better now to return to more regular releases as that means any fixes are released quickly as well and not potentially held up by new features being added over a longer than normal period.

Also new users are unlikely to buy Podium just to beta test it, so the influx of new users has no doubt slowed down as a result of the length of this beta although I can see that the lengthy time frame was most likely totally unavoidable this time as you have always stuck to a structured, consistent and much shorter release schedule over the years.

I am so used to Podium’s nice and steady release schedule of 2 – 4 weeks sometimes even sooner. Never too hurried or too long. Just right.

Of course 1.95 is a very special case indeed and I want you to feel totally happy before releasing it (as others do no doubt), but even if there was any last minute problems you could release a quick fix for that. You have done that before. Therefore, I see no problem with that.

It just means we can access a recent version ready to go (roughly every 2 – 4 weeks as before) with fixes instead of maybe having things stretch for a month or two months, as is the case now. This is a very long time indeed for a Podium release.

It is very odd in a way considering it has never been like this. Of course 1.95’s development process has seen many major changes to say the least, I guess I am just eager to move on now to other more pressing areas in Podium…like auto mapping, time stretching and even Rewire. I know many are waiting for Rewire to compensate for features that Podium does not have yet and ease Podium into their existing set ups.

I know you have given rough time scales for these in the past of course but I am just curious as to when we can return to the usual 2 – 4 weeks release period for Podium 🙂

Conquistador, Why you trying to rush Fritz for 1.95 release? Is it so important?(numbers) I understand if we haven’t this betas. But we have them, and can work farther with projects. Or i missed something? 🙂

Hi Igr0,

What makes you think I am trying to rush Frits based on my comments? Asking for information about the timeframe of 1.95’s release in no way amounts to an attempt to “rush” 1.95’s release. If you read the post you quoted again, you will clearly see (in detail) why I made my comments and the clearly sensible reasons for posting them. 🙂

It would be silly to post my thoughts after it is released as Frits would have wondered why I did not say something as he does of course still encourage user feedback on all aspects of Podium 😉

@Igr0 wrote:

I have strange bug with all 1.95 betas.It happens when i create new arrangement, which have 4 audio tracks and all things by default.So, i have 4 tracks. Then i delete last track(using delete bottom), then next track and so on.But when i delete last track podium crashes. Sorry for my english 😳

I have noticed something similar, but podium does not crash for me.. it simply will not play any audio.

@Zynewave wrote:

Beta 12 furthermore has a new track menu. I’ve joined the right-click track menu and the left-click object popups into one menu. There are new submenus for: “Assign Input”, “Assign Output”, “Assign Effect”, “Assign Source” and “Insert Effect Track”, depending on which track you click on.

The “Assign Source” submenu includes all device mappings that produce sound, i.e. instruments and bus returns.

I’m going to extend this menu with “New Parameter Track” and “Assign Preset” submenus. This should then allow you to do everything on the track headers, without having to use the track inspector.

Excellent, now it’s becoming fun to work with the track headers.
Things I noticed while fiddling arround:

a. When using the command ‘Hide Tracks in Group’ on a bounce track the plugin mapping and the fader of a child track is shown on the bounce track header.

b. After a while of resizing the track headers vertically and closing and opening the mixer there is no way to resize a track header to a smaller size. It looks like a minimum header size setting is active.

c. Moving the first effect track in a track header with the submenu command ‘Move Track’ above the next effect track does not work, moving below works.

One question: Is it possible to deactivate the automatic track header sizing when opening/closing the mixer? Would be great because all the optimized track header sizes are ‘lost’ after opening the mixer view.