Conquistador's Forum Page

@Zynewave wrote:

Far too much work considering the Wiki is already there. A duplication of efforts really.

That was what I feared would be the case. As far as editing goes, the Wiki is the simplest solution as I see it. Thanks for your efforts.

Sorry about that Frits.
I agree with you 100% here. You were right. The Wiki is more accessible, editable and as a result a more up to date version of the guide anyway.

I guess it was worth a try (at least) to help out with the PDF but the Wiki is wider and deeper in terms of how it brings your efforts as the developer and other Podium user efforts into one easily accesible place for all. 8)

@Zynewave wrote:

[*]”Search For Missing Plugins…” is added to the top menu in the devices panel. This command is available if there are any plugin mappings with invalid file references.

I have been really putting this one to the test as I have many projects somewhat orphaned (FX and Instrument wise) because of a recent reshuffle of my plug ins location and structure.

The ease of use is quite remarkable. One click! It is absolutely flawless. All my orphaned projects can now be brought back online with just one click! 😀

Podium really does offer a very quick workflow. It’s maturing very well. 😉

“Search for missing plugins” is a great time saver. A little – big feature.
Thanks Frits 8)

Just a quick update on my efforts with the Podium Guide Frits, of course the 1.71 thread is closed so I think this thread is the next best one to use for a quick update on the PDF I was working on…creating the PDF was pretty straight forward but editing it was another matter. 😐

Far too much work considering the Wiki is already there. A duplication of efforts really. 🙁

After shuffling between the Podium Wiki and the PDF Guide it really does seem like the Wiki is the only way to go. 8)

With users having access to sharper images (double clicking once to get a larger image, then another double click again to get the original image as you suggested Frits) it seems much better for users to simply access the Wiki version of the Podium guide instead of the PDF.

The PDF has its uses but the Wiki is much more flexible and easier to manage.

I think I will simply focus on a few tutorials I had in mind for Podium and upload those to the Wiki at some point.

The Wiki is a great idea and is way more flexible than the PDF. 😉

@Zynewave wrote:

Experiment with draggable handles on the sound events:

The screenshot shows the fade in handle clicked and being dragged (mouse cursor not shown). The bottom handles will resize the event. This works identically for the select and pencil tools. The handles and fade curves are only shown when the mouse is hovering over an event.

That looks great. You got the idea of the hitpoints for dragging perfectly. 🙂 Strange really as the image looks like it has always been present in Podium. It really fits. 8)

I just want to add a few comments after reading acousmods rather excellent masterclass in clip fades 🙂 …

What seems to be important :
– the top volume line and the fades MUST be linked

Agreed.

– the waveform MUST follow both the fades and the volume values

This would be ideal.

– a visual indication of the fades when the event is not selected is very useful (the Vegas solution is perfect for me), but I understand that it could be a problem if it eats some CPU (which is not the case in Vegas) !

Samplitude does this, it does help.

– what I like with ne “no handle” solution (Reaper, Vegas), is that you don’t need to click precisely on the little squares to change the fades or to resize the event, you can drag the vertical lines or the event edges. It is something extremely irritating in Nuendo…
But of course, you can have both the handles and also allow to drag the lines.

I definitely want those handles. 😉 Optional at least!

Can’t it sometimes be a disadvantage that the waveform is scaled according to the fade curve?

For me it is mainly a visual confirmation of the fades, not for precise editing.
It doesn’t bring a lot of information by itself, but it is rather confusing if the waveform is scaled for the volume but not for the fades.
It is also important for the crossfades.

Yes, yes and yes! 8)

I see no point in showing the fade handles if you have selected e.g. the eraser tool.

But when you have selected the cutter yes !

I would certainly prefer they are visible. Or to make everyone happy why not let the user choose by making it optional at least? 😉

It’s all looking great! 😀 Thanks for the images.

@caco wrote:

Its always facinating finding out how other people work as everybody does it differently 🙂

Indeed. I guess it also shows just how capable Podium is 8)

@Zynewave wrote:

Is the blurred background image a screenshot of Podium?

To be honest, I’m not sure I like this better than the existing splash screen. But I would like to hear more opinions.

I think Podianers effort is pretty good. I am impressed. I still think the current splash screen is better though. I would only really change the current grey colour with a tint of blue or something similar, but that is all.

Very nice effort from Podianer though 8)

@Zynewave wrote:

Would it be sufficient to be able to drag the fade in/out times directly on the event?

Yes this sounds fine. A simple process of dragging a fade at the beginning of a clip or at the end of a clip would be great.

To edit the curve shape you would then need to open the properties dialog (Shift+Enter).

I assume you mean using the options in the image you posted. That sounds good to me as well.

I was also considering extending the fade properties dialog with a listbox where you could create and manage defaults/templates. This list would then be available as a submenu when right-clicking the event, to quickly recall various curve shapes. But maybe that would be overkill?

Brilliant idea and in no way is that overkill! ACID and Sonar have that already. It is a massive time saver.

I would wear that feature out in Podium 😉 it would provide a user with very quick access to curve shapes, an essential optional feature I think. Please add that as well. Overkill? The complete opposite! 😉

How I imagine automatic crossfade would work: When you drag a sound event to overlap another event on the same track, the fade in/out times of the two events will be set to the overlapping interval. The fade out curve of the first event will then be inversed and assigned as fade in curve of the second event. This crossfade will be applied as a separate edit in the undo history. If you don’t want the automatic crossfade you just press undo once. Pressing undo again will undo the event move.

Sounds good and makes sense to me Frits.

The simpler and best way from my point of view :
– drag top edges of the events to made and size the fade (please : ONLY with the mouse, NO modifier key !)

I agree with acousmod here a modifier key to access clip level fades is not something I would be interested in. But of course it can be made optional for those who prefer it.

Some additional suggestions

1. An option to select all clips and fade them all together at the same time. Live 6 and Sonar 6 have this…very handy indeed.

2. I agree with darcy here…

From a fade in / fade out perspective I would change nothing… However, I would like to see automatic crossfades but with the ability to further edit the crossfade curves as you show with the fade controls…

Some way to edit the crossfade type using a similar or possibly the same options as found in your posted image but for crossfades as well.

3. A small square or circular hit point for the drag selection point on any clip. Tracktion has a small white square that makes the selection of a fade point at the edge of a clip that much easier. See Tracktions demo for an example.

So far it all looks great. 😀