Conquistador's Forum Page

Hi Brent,

Another RMX user here…I use RMX in Podium on a fairly regular basis and I often drag and drop Midi from RMX to Podiums arranger. Support was added for that a number of versions ago IIRC. I just tried it again (with playback stopped and then again during playback) and no crash.

I assume you are already using the latest version but it is worth asking…are you using RMX 1.8? (1.8.1d) :-k

@aMUSEd wrote:

Also its so confusing that if I save say a copy of “VSTi Project 1” as “VSTi Project 4” it still appears as “VSTi project 1” when I open it in the project menu.

Strange. I don’t think I have come across that problem before. Sounds like a bug. If that is really what is happening then something either by design or bug related is not working as it should.

I wonder if I can reproduce that problem…I’ll have a look.

In general…
Some sort of revision of arrangement saving / management would help. Clips dragged into an arrangement and not being copied into a project folder automatically is something else I would also like to see revised / changed in Podium.

@Zynewave wrote:

:-k Hmm. Fair enough to get all automation ideas on the table while I’m already revising the system.

Thanks for being open minded about it and considering more additions…I can think of a few that will help…

1. Read / Write buttons controls per track. Global Read / Write as well.

2. A central Automation control point within Podium. An Additional Panel maybe or an addition to the Group Panel. Perhaps something that replaces the Group panel when in view. “Show automation control centre” or “Show arrangement automation”.

Nuendo and now Cubase 5 use this…

Watch the first minute or so of the video on this page to see it in action.

You can find out more detail about the central Automation management in Cubase here[/url:ls7n4z2h] Page 190 onwards.

@LiquidProj3ct wrote:

I don’t know about the “big” host as Cubase, Logic… but I can imagine that no, or it would be too complex with too many options, killing my workflow.

That is where a central point for controlling automation in Podium (as in Nuendo and recently Cubase 5) comes in. It really is necessary as it simplifies Automation management making it very easy indeed. Quite a few cubase users wanted the new Automation controls from Nuendo. Initially I could not see why. What is the big deal? I can see why now after reading more about it. It is pretty slick IMO.

If it is a time issue then IMO I think you should feel quite free to take as long as you need Frits to address this problem (hopefully in 2.15). If it is a case of you perhaps wondering if it is *that* important then I think it is.

I have (as many others do of course) a list of features I think would further improve Podium but I would really like to see this particular issue revised above other FR’s personally.

Hopefully addressing it is not too complicated.

Thanks for having another look at the Browser Frits. I initially thought the movement of the info box when the inspector is closed was a bug but it reappeared under the browser. I assume it is as intended. Very nice idea.

@thcilnnahoj wrote:

@Zynewave wrote:

@thcilnnahoj wrote:

– Filters for the Project browser to view only VST/VSTi + parameters; VST presets; Audio/MIDI sequences; Automation sequences. (If possible to seperate all these)

I can see the use for accessing sequences of different types, but why would you want VST filters when you have that directly in the inspector device panel?

Seen as all the devices are available from the browser anyway, I thought you might as well have the ability to access everything in one place, if you wanted.

This is a huge deal IMO. Totally agree one browser should be all that is needed. Why have two Frits? ❓ ❓ ❓

Logic , Sonar, Tracktion, ACID, Ableton Live, Cubase e.t.c use one single browser. Even the new Presonus Studio one uses a single browser. I might add somewhat very similar to the placement in Podium, along with the look and feel. No need for two browsers as that would mean we have to move between the Inspector and the new browser. Slows things down Frits. Complicates workflow. Really.

The browser is an extremely important part of a host as this is how a demo user or existing customer will consistently access all of their projects resources. It’s critical to get it right.

I think we should have access to Presets, Parameters, Track templates, VST’s and VSTi’s and other devices from new browser. Definitely prefer having one browser open instead of two. An option could be added to show a large meter instead of the track panels as devices e.t.c could now be fully accessible in the new browser.

There should be no need to switch back and forth between the browser and the Inspector panels that adds complication to working on Podium…using one browser makes it much easier. A user can of course easily select what they want to see in the new browser.

The inspector shares functionality with the browser which IMO is OK to a point, but I think the two should now be separate (at least optionally) it may have been this way for a long time but I think it is a problem going forward with a need for two browsers to be open for simple tasks.

Logic has a slick browser that allows all the browsing from *one* place with just four tabs. So much easier this way.

1. Loops (Apple Loops)
2. Browser (Instruments)
3. Bin (Audio files)
4. Library (Presets)

Podium could add to the existing Project and File buttons…

1. Project: (Project specific resources like audi and midi)
2. File: (Browse user drive).
3. Presets: ( FXP, Track templates e.t.c)
4. Tempo Synced: If a user should browse in this window the file will tempo sync with the Project tempo. I suppose if Timestretch is implemented it could replace beatslicing.

Some more ideas…

Browser

1. Midi Preview

This would be absolutely great. Surely a consideration for the new browser features as we are almost there.

2. File Management

Anything a user drags from the browser really should be automatically copied to the project folder. This has tripped me up many times leading to a search for the missing file or files.

3. Search box

In Live you can search for a file from within its browser. Really useful feature.

4. File tagging

5. Extend beat slicing to the Browser window (time stretching would be ideal here but without it if any audio file can be beatsliced in the browser then maybe some form of tempo sync can be attained if the project is playing back and a file is being previewed).

I would imagine beat slicing (in the browser) to be something that can be added as an option.

6.Timestretching
Simply ideal for the browser. Of course this is already used this way in many hosts already. It is an somewhat expected feature.

Inspector

1. Large Meter (with realtime db values)

There will be plenty of space for this in the Inspector if Presets, Devices, e.t.c can be managed from the new browser. In any case it can be an optional Panel.

2. Global SMR
It would be great to not have to use keyboard shortcuts to simply solo or un solo a track or multiple tracks. Also it would eliminate the need for a user to zoom out to see where a solo has been added to a track e.t.c or having to use the Mixer to *see* it.

With Global SMR or Arrangement level buttons, three of these buttons could be placed under the File, View and Edit buttons or next to the Group Panel and Colour Picker buttons in the GP.

SMR

If you have a track or more you want to quickly disable or enable solo Mute or record for, you should easily be able to do so by clicking on one of those buttons. The current process we have has had me contantly accessing the current keyboard shortcut to do this as there is no other way currently.

Other…

Plugin Gui docking (looking to have easy Plugin GUI access without any floating windows). If you are working on floating and docking windows please do consider this.

Thanks.