ZynewaveWhere in the manual is the screenshot you are referring to?
You can’t move the browser that is embedded in the left side of the main window, but you can use the “new browser window” command in the Window menu. That gives you freedom to rearrange the main window and the separate browser window any way you like.
Zynewave@carl wrote:
does that mean when i load a loop ican just use the alt key and drag copies of the loop like in reaper?
I’m not sure what Reaper does. From your question I gather that when you alt+drag in reaper, it will insert multiple copies of the loop if you drag beyond the length of one loop? That’s the old style that I think the Acid application first made popular. It doesn’t quite work like that in Podium. The fastest way to insert multiple phantom copies of a loop, is to select the sequence/sound event and then press the Insert key for each repetition. When dragging in Podium you either move the event or hold a key to copy the event (alt for phantom copy and ctrl for unique copy).
Doesn’t Reaper support clone/ghost/phantom copies of sounds/sequences? If it does, then how do you drag normal copies versus ghost copies?
ZynewaveIf you don’t intend to edit the individual clips that you want to duplicate, then I recommend you use phantom copies. In the case of sound clips it will save a lot of memory and file space, since you only have one instance of the memory/file that is shared among all phantom copies.
The difficulties with the dual functionality for Alt+Drag has come up before. I think I’ll change it so that Alt+Click+Drag does not start a resize action in the arrangement editor. You’ll then have to click the small square box at the bottom right of an event to resize it. By removing this feature, Alt+Click will now start a phantom copy drag no matter if the alt key is pressed before or after the click. This will make it behave similar to the Ctrl+Click dragging for unique copies. Does anyone object to that change?
Zynewave@thcilnnahoj wrote:
Hmm, what about people who work with multiple templates… maybe the “import database” button could become a sort of dropdown menu to select a template.
Sure, you can use the ‘old’ way to create a project from a template, but it’d be nice to have them all available like this.
If you have saved your own project templates, then there will be a dropdown menu button. I think most users will never use the project template feature, so I’m trying to figure out a transparent way to handle a global plugin database, without worrying the user about templates.
– How does it work for plug-ins that have since been removed – does the “update database” function clean them out automatically?
Yes, I think they should be cleaned out.
– Does the update function go by filename only, or will it create additional mappings for plug-ins that are already present, but the user may have created custom mappings for?
No, it will skip any plugin whose dll is already referenced in a mapping in the database. Otherwise it would need to rescan all plugins anyway, and then there won’t be much time saved with the update option.
– If the option for importing surround mappings is removed, you’ll have to delete them from the very first plug-in database yourself, no? I hope they won’t reappear, should you use the “update database” function.
Though I guess there’s no need for concern since this change in 2.27: “Using any of the import plugin commands will only create surround mappings for the plugin if there already are other surround mappings in the project.”?
I’m considering moving the stereo and surround options up on the page as general options, and not just plugin related. The options also decide if surround mappings should be created for audio ins/outs and busses.
– Is this going to change anything concerning audio and MIDI device setups, or will the database somehow only story plug-in (and external instrument/effect) mappings?
No, the project template menu will work as always. It’s only the auto-generated “plugin database” template which will be used to extract VST plugin definitions only.
Zynewave@ronin wrote:
Sounds reasonable. Does it solve the problem I had with the initial scan? Maybe there is an easy way to trace the plugins that had already been scanned and omit them in subsequent scans (in case of a crash).
Scanning of each plugin produces the various device mapping, device definition, preset and parameter objects. To be able to skip rescanning plugins in case of a crash, then it’s necessary to save the project template file after each scanned plugin. I’m afraid that is going to slow down the scanning process noticeably.
I’m curious: How many crashing plugins do you encounter during a scan of your complete plugin collection?
Once a plugin has crashed, Podium will put it on the quarantine list. Future complete scans will then skip these crashing plugins. So the problem should only exist the first time you scan all your plugins, unless you manually remove the crashing plugins from the quarantine list.
ZynewaveHere’s how I’m planning to change the Create New Project page:
These options will be removed:
“Scan and import mono/stereo VST plugins”
“Scan and import surround VST plugins”
“Save the created project as a project template”
Instead, for the first project you create you will see this option:
“Create plugin database”
When you create the project with this option enabled, it will scan for plugins as in previous versions, but once scanning is complete Podium will automatically save a project template named “Plugin database” without prompting the user for a template name.
The following projects you create will then show these options:
“Import plugin database (updated: xx-xx-2010)”
“Recreate plugin database”
“Update plugin database”
If you only check the “import plugin database” option, Podium will import the plugin definitions from the “Plugin database” template file, and there will be no scanning.
The “update plugin database” option will import the plugin database, but scan for any new installed plugins that are not already in the database.
Any suggestions for ways to make this easier?
Zynewave@nomnomnom wrote:
Swing, if you apply swing, and then move your notes, it’s automaticly snap it. So you lost your swing. Kinda bad thing. Ye, i can always turn snap off, but turning it off and on repeatedly takes lot’s of time.. Moving swing notes on snap on, snap should be ignored.
A “relative snap” option is on the todo list. This will allow you to move events in steps of the grid size, but without snapping the start of the events to the grid lines.
Zynewave@Lion wrote:
Would it be possible to have MCU emulation in it?
Please clarify. MCU emulation in the Podium UI?
ZynewaveClicking on the timeline should create a new curve sequence. Click+drag to create and resize. Once you have the curve sequence event, you can draw in the actual curve in the curve editor. Either double-click the event to open the curve editor window, or select the embedded editor profile.
ZynewaveFor simple fade-in/out, gain and pan, you can drag the handles in the upper left/right corners of each sound event. For precise adjustments, right-click an event and select “sound event properties”.
If you want more advanced curve automation of level and pan, then use the track right-click menu and select “automate parameter > level/pan”. After that you can use the pencil tool (or double click with the select tool) to draw curve sequences and use the curve editor, or you can use the parameter faders in the mixer to create the curve sequences.
Zynewave@druid wrote:
When just the files are listed right in the project arrangement view like in XT, I can choose which I want and as long as I’ve maintained the VST folders, and load it. If I’ve recently updated it, or added more, they are just listed automatically after the file is there, I don’t need to maintain any database within the host as well.
If the plugin dlls are not scanned, then it won’t be possible for the host to know whether a plugin is an instrument or an effect. That wouldn’t work well in Podium where the list of plugins are filtered depending on whether you click on an effect or a source selector.
ZynewaveHi lalo,
In one of the next releases I’ll improve the MCU-compatible control surface support. That should at least be a step in the right direction. I can’t give you a deadline for when I’ll implement generic support for MIDI-learn in the Podium UI. It’s on the todo list, but there are a lot of essential features on that todo list 😉
Zynewave@andreariderelli wrote:
if it will be possible in the near future to have a global plugin cache/db and only then the possibility to choose the customized plugins setup for each new project.
i mean: to avoid to scan vst directory every time you start a new project, but “having multiple plugin setups for your different types of projects”
Yes, if I understand you correctly. The plugin cache/db you talk about will be stored in a project template file. I’m going to revise the way that you access this project template (i.e. plugin database) on the Create New Project page. If you only work with one plugin setup, then the result should be that you don’t need to scan for plugins every time, unless you have installed new plugins and want to update the plugin database.
Zynewave@eincande wrote:
Can i provide you with info (log file ?) that would make you track down the tranzport issue ? maybe record a midi track with midi message correspondig to start/stop/Etc ?
the control is MCU compatible but i don’t know if it is 100%. but start stop should work at least 😉
I’ve looked at my source code for the MCU support, and I think I’m going to revise it very soon. The problem is that it currently requires the MCU device to respond to MIDI SysEx messages to identify the device. I think that is why it won’t work with a lot of the so-called “MCU-compatible” devices. I’ve received reports that Kore2 and Zoom R16 doesn’t work either. These devices probably only support the non-sysex messages that are used for button presses and fader movements etc. The SysEx messages are primarily for updating the MCU LCD display etc. With a bit of luck, I’ll have this working for Podium 2.28 or 2.29.
– about x64 : does podium user multicore ? i need to handle large project if a close future and i would like to get rid of cubase + i need to adress more ram (samples banks, like always :).
Podium supports multicore. To make use of RAM beyond the 3GB limit (which is the limit for 32bit applications), you can use the jBridge converter. I haven’t yet tried jBridge myself, but from what I’ve read then EACH plugin wrapped in the converter can use up to 3GB.
– Can you export all tracks to indiviual wav file ? (sending all session to protools) with or without effects ?
You can by using the bounce feature. If you have bounced all the individual tracks, then there already are bounced wave files in the project folder. You also have an export option in the bonce menu. In the bounce menu you can also specify whether it should bounce before or after effects.
ZynewaveHi Andrea,
Thanks for your feedback. It emphasizes the need to make the project template system more accessible on the create new project page, as discussed in the topic thcilnnahoj linked to.
you are telling me that it is better to save a project as a new template after i complete a vst scan and then start any new project with this template, aren’t you?
That is correct. The reason that the plugin setup is included in the project, and not in a single global database, is that it allows for having multiple plugin setups for your different types of projects. You may want to create custom plugin setups for working with surround sound, mastering, classical composition, etc.
I’m going to make some improvements to the project template system for the coming 2.28 release.