@jpleong wrote:
Which bug are we referring to, exactly? I’m still using 1.93 (I never upgrade in the middle of a paying project!) and was just about to update…
JP
Frits post…
http://www.zynewave.com/forum/viewtopic.php?t=1459
It disables the audio mixing option on a track if you add an effect by dropping it on the left edge of the track header. You can either manually reenable audio mixing afterwards, or add an effect by creating a group track first, and then assign the effect mapping to the group track.
…has the link to the exact bug I was referring to. Thats the one π
@Zynewave wrote:
So far “expanded” mode is more like “classic” mode, meaning it works like in previous releases. I’m still considering what to do with the expanded mode.
Yes Compact Mode has certainly evolved to a point where Expanded mode is now more of a “classic” mode and as a result probably requires some sort of new focus of sorts. A somewhat unexpected side effect of the refinements in Compact mode.
Perhaps the new compact UI will be used in expanded mode as well, and expanded mode will thus be an extension of compact mode with less restrictions on track management.
Great idea. That seems the most logical progression for the Expanded mode IMO.
Are you sure? The “Instruments” menu (previously named “Source”) contains all mappings that produce audio, meaning bus returns appear in this menu as well.
Good points… that did cross my mind but I can definitely access a GEQ Overtone mapping and a Compressive Pro mapping (both free plugs to download and test) from my Instrument list in B17…
The “Effects” menu contains mappings that take audio as input. Some instruments may accept audio input, and will thus appear in the effects menu as well.
Effects listings are good to go (mappings are correct) in B17, but I am pretty sure I had some instrument mappings showing up in B16 out side of expected mappings like z3ta+ as an FX *and* an instrument. Anyway the mappings in the Effects list are all accurate and correct in B17. Definitely. Instrument listings (with Compressive and the GEQ showing) still seem problematic though.
Apology accepted :P.
π
The line you outlined is not an empty track. It’s the popup line for the lane track. The popup menu is the same as the right click menu on the lane track header. The line serves the dual purpose of displaying what is assigned to the lane track (i.e. instrument and input) as well as a left-click shortcut for displaying the popup menu you also get when right-clicking on the header.
Thanks for the clarification. I think I get it now.
“The line serves the dual purpose of displaying what is assigned to the lane track (i.e. instrument and input)”
That would also explain why there is no “Insert Instrument track” or “Insert Input track” commands I guess.
Cheers. π
B17.
I really like the subtle but stylish circular button in the arrangement view for tracks. I think for new users it is a very good idea. I like it. I will use that instead of right clicking now. Not sure why but in this case I find it more satisfying to click on that button instead of right clicking π
@Igr0 wrote:
@sam c wrote:
we have waited far too long for a bug fix!!!
bye
Why are you shouting here? You see how long to take an update from Steinberg, for example? 3-4 months. And there is a big team. Frits works alone. We all want, that graphical update would be done so, that never come back to this problem anymore. It’s good for us and Frits too. Just wait a little bit more, and you will get what you want. π
Personally while I agree that if we “wait a little bit more” we will get what we want, I don’t see what is wrong with Sam C expressing his views here regarding 1.95’s full release (not as a beta) which I think is what he was talking about.
There was a particular bug which still is IMO a major hassle to deal with, that under normal circumstances would have been addressed within 4 weeks max. It’s almost three months since the last Podium release.
Of course I cannot imagine Frits decided to stretch things out for 3 months on purpose, clearly it was unexpected and unforseen. But…based on the past 100 releases or so that Podium has had so far, (AFAICT all within a 4 -5 week timeframe), one can surely see why some peoples expectations are high for a return to quicker releases. Even more importantly IMO, quicker fixes that are not held up by the addition of more features which are of course welcome.
One simply wants to avoid trading a needed fix for new features. The 4 – 5 week time frame (even much sooner at times), solves that problem.
As for the Steinberg analogy…well they simply choose to work that way. There are many companies that choose an ultra secretive business model for their products, and longer release cycles for patches and fixes but it is a choice not a necessity.
Even Steinberg themselves in the past have released a patch within a 3 week time frame, so even with Steinberg’s huge product portfolio, Cubase 4.02.2217 was released on the 21st of March this year less than three weeks after Cubase 4.02 was released (2nd of March 2007).
Frits, Justin & Christophe (Reaper) are good examples of one or two people consistently developing a product with very short release schedules for features and patches (within 4-5 weeks).
Interestingly, neither Frits nor the Justin and Christophe combo have multiple products to juggle so they can focus on quicker releases which Frits has done about 100 times already since v.0.90. That is why I think it is easy to see why one can be rather eager for the usual quicker releases for Podium. It has always been that way.
Ableton: They have one product but choose to release it on an annual basis. But even they have released patches within a three week period in the past few months. Live.6.09 and Live 6.0.10 had less than three weeks between their releases.
Frits has clarified here and elsewhere on the forum that 1.95 does not represent a permanent change in release schedules for Podium, so I am not worried at all, but I do remain very eager for 1.95’s release as it does have a key fix in it that has been held up (not deliberately) by the addition of new features.
In any case 1.95 is certainly well worth the wait and the release schedule will return to it’s previous state after 1.95 released. π
B16
1. Right click loss:
In Expanded (Advanced) mode you cannot add an effect by right clicking. Is this an oversight or deliberate? I ask because it seems very odd to lose functionality going to Expanded mode from the simpler Compact mode. Expanded mode is of course supposed to provide more flexibility and more features exposed to a user, not less. One can of course add an effect to track by right clicking in Compact mode.
2. Strange plugin issues:
Podium clearly knows the difference between an effect and an instrument mapping but…I can access my Effects (and instruments) from the βInstrumentβ command and my Instruments (and Effects) from the βEffectsβ command. This is puzzling as one would expect to see Instruments in their own list for instance and not a listing for Instruments and Effects when using the Instrument command.
@Zynewave wrote:
In compact mode it is recommended to create dedicated bounce tracks (using the “insert bounce track” menu), instead of manually enabling the bounce mode for an existing track in the track properties dialog.
I agree with the “insert bounce track” suggestion. That way you keep the original pre processed file when attempting to bounce an audio track. What may also help is having the “Use Track for Audio bouncing” option in “Track Properties” grayed out for Effect tracks within a track Panel.
If it is confusing that you have the bounce mode option available in the track properties dialog, then I’ll need to implement different properties dialogs for the different track types.
I think that will definitely help. Thanks.
I’m not sure if I understand you correctly, but there is only one track in the last of your screenshots.
The line that pops up the menu belongs to the lane track, which should be apparent from the coloring with the select color. With the compact mode, it is recommended to keep effect mappings on separate effect tracks because this makes it easier to manage the effect chains.
I totally agree with that.
The “Move track” menus can easily shuffle the effect tracks and the “Replace effect chain” command can replace all effect tracks.
Fine, no problem with that either.
This would not be possible if you assign the effect mapping directly on the lane track. That’s why you only have an “insert effect track” menu on the lane track.
Ok I think I understand what you mean now but why do I need that initial empty lane track? (see image below). You said it would not be possible to use the Move track Menuβs or Replace Effect chain commands without it, but if you right click under the last track in an arrangement for instance you will get the βNew trackβ pop up.
Once it is selected you get the blank lane track. Now one can click on it to insert an effect track which will be placed over it (not on it). But why bother with this lane track when simply right clicking anywhere under the lane track will give you the exact same menu?
Insert as many Effect track as you want from there and the Move track and Replace Effect chain commands will still be accessible. That is what I was trying to say.
3. Another possible Bug…
If I choose to use the blank lane track instead one *can* actually assign an Effect Mapping on it. This is how I did it…if I access my Effects through the βInstrumentβ command I can place that effect on the βAuto trackβ or lane track. But I of course still have the βInsert Effect Trackβ command which will create an extra track. This is confusing.
Just to test this further…when I attempt to access my effects through the Instrument command the effects do not all appear. When I attempt to access my Instruments through the effects command they do not all appear there either. So there are some inconsistencies when using this βlaneβ track.
If you right click on the blank space under any track in a track panel not *on* the track…you get the exact same menu that pops up when right clicking on an empty track in a track panel. So it just seems needless to have this extra “lane track”.
You can insert as many effect tracks as you like, this blank “lane” track or blank mapping holder will still be there. My question is….is it really necessary? Apologies in advance if I have totally misunderstood the obvious here. π
@Zynewave wrote:
Support for auto-save and crash recovery is on the future plan. I’ll need to modify the cache file format so that it stores additional info that can be used to recover the audio streams.
Yes please. Some sort of user specified number of incremental auto saves, that would for instance generate 2 or 3 versions of a project and / or arrangement would be great.
Even a simple auto save at user specified intervals would also be very helpful.
Personally Podium has been the most reliable Host I have ever used. Having said that, your suggestions for Auto save and Crash recovery would take data management up another level as those features would make Podium pretty much impervious to losing data. π
B15…
Hi Frits, a few questions for you…
1.Bounce enabling Effect tracks:
Is there any need for Effect tracks within a track panel to be bounce enabled? It does not appear to “work” this way.
I think perhaps the most logical way in Compact mode to work with bounce tracks is to eliminate the possibility of Effect Tracks being bounce enabled.
The image below has a bounce enabled track header which in Compact mode for simplicity, should probably be the only track with an option to bounce enable it within it’s track properties.
But…I can easily bounce enable the “Sonitus” Effect Track or the “Classic Auto filter” Track, but doing so appears to have no apparent affect. It just looks like something that needs to go unless I am missing something. Of course it is a different matter in Expanded mode where I would not want to lose the current bounce track functionality we have for any track.
In compact mode it is just very confusing IMO to leave the bounce enable feature on for Effect tracks.
2. Extra track created automatically every time:
When creating a new track, a blank track is also created within a track panel in Compact mode. That is a nice way to start off as one can then click on it to choose an effect…well not really because this is what you will see if you right click or left click on that new “auto” blank track…
Now at this point I thought hold on where is the command to let me access my effects? What I see here is the “Insert Effect Track” command. This looks a bit confusing as it says “Insert Effect Track” not “Insert Effect” which should be there.
If I choose the “Insert Effect Track ” option I get another track but this time with the mapping of my choice.
I now have two tracks in the track panel. I only wanted one track.
Unless there is a need for this “other track” can it be removed? Of if you must keep it then possibly allow a user to add an effect to “that” track to avoid having to create another track please.
I also noticed that when I enable bouncing in the track header that “Auto track” suddenly has a B button appear on it. So I guess it’s some sort of representation of the track panel? If that is the case a popup explaining it’s function would really help. If not, why not remove it?
@H-man wrote:
the release of 1.95 (feels like 2.0 don’t you think?)
Personally (I guess you did not direct the question at me π but…) I think 1.95 is many levels above any of the updates for Podium since the first beta (0.90) came out years ago…but…without Rewire, time stretching and other refinements to plugin handling on the project start page, it’s not 2.0 calibre just yet IMO.
There is definitely some ground left to cover before 2.0 and I suspect Frits agrees or 1.95 would be 2.0 by now. Exactly what ground that is (specific features) only he can say for sure, but people expect the three things I mentioned in hosts now, talk less of some time in future.
Podium remains a powerhouse but expectations still remain for key features especially considering how long the competition has had those features for. Years in most cases.
First, can the background to the Volume/Pan faders and the buttons X,R etc. be left in the default background colour. Minor I know but when you’re using my colour scheme …well, there’s alot of orange.
Unless I have missed a colour option that address it…I would agree with your suggestion. Pick the wrong colour and that is the kind of result one would want to avoid. It does not look good. An option to change that or a similar solution would be nice.
And finally, awesome stuff Frits π
Indeed! π
@H-man wrote:
Hey all,
I have tried verison 2 (0.5 or something) and it seems pretty flakey. Menus seem frozen and it crashes out frequently. π₯
So I guess it is a case of stick to version 1.2?
I would think so yes. V.2 is still a beta AFAICT so I did not even download it. I picked up 1.2 instead.
While 1.2 is not going to be perfect (of course no software is) it has had one or two updates since the v.1 release so I think key fixes have already been made. So yes 1.2 IMO would be the one to go for (stability wise) while 2.0 is the risky choice if you just must have the new features. π
B13 thoughts…
Podium is so much easier to navigate and use now. It is a really strange thing but those preset and parameter sub menu’s just make it so easy at track level to work very quickly now. Great idea. It is a joy to work at track level in 1.95. Love it.
z3ta+ presets using the new submenus:
Sonitus Compressor Parameters using the new submenus:
Those little additional graphical touches just give it a very refined, polished, stylish and elegant look.
While it is necessary to give feedback on problems when they occur so that they can be identified and fixed or refined…I think some really positive feedback is due here.
I really have to say Podium using Compact mode in 1.95 is a really nice experience. It really does feel very different to 1.94, it’s much easier to use, with more features and allows for a much quicker work flow. Excellent!
Thanks Frits. π
@Zynewave wrote:
The new beta 13 has further changes to the track menus, including submenus for presets and parameters.
You said “including” so are there other undocumented changes in B13 as well?
@Zynewave wrote:
With a bit of manual work, you can arrange your plugins into favorites folders on the project start page.
Or pre – arrange them on your hard drive to taste, *before* you import them, that way Podium will correctly maintain the folder layout of your plugins after import.
Well well well. That is a surprise. π
I have dabbled with 64 Studio as it takes full advantage of 64 bit processors being a fully 64 bit OS like Vista 64. While Ubuntu is only 32 bit the last time I checked.
But Ubuntu Studio has a broader range of Media apps although one can download all you want into 64 Studio. I think 64 studio is a more Music focused Distro AFAICT and from my experience using both, I found 64 studio much easier than Ubuntu studio to set upbut that is just my preference. π
Anyway… you said…
@polysix wrote:
All seems to run with slow latenc midi with my MK-425c Keyboard works too.
Did you mean “run with low latency” or “runs slow or slowly”?
I ask this because Podium is not a Native Linux app of course and Wine might be introducing a slight delay into the general running of the app but then again if you meant “low latency” then I assume that Wine might be delivering performance levels that are as good as Windows for latency and general operating speed using Podium is that right?
I have neither 64 Studio or Ubuntu Studio installed at the moment so sorry to bother you π
@Zynewave wrote:
I have already replied to this question some time ago in the topic you posted in the VIP lounge:
Yes I remember the discussion but I asked again because judging by a recent comment (on this thread) it appeared you had changed your mind. But that is cleared up now thanks.
The design of the new track layout mode is a major feature. When it is done I’m going back to more regular updates.
Cool. π
@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 π
@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. π
@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 π