Zynewave.
acousmodHi Frits,
I didn’t know where to post this topic…
I’ve made some changes in the SpatPod 5.1 and other plugs, and will gradually make the files for my other plugins, so could you update your database and/or give this link for the files ? http://acousmodules.free.fr/mappings.htm
Also, the download link for the SpatPod 5.1 has changed (rar file now) : http://acousmodules.free.fr/fichiers/SpatPod.rar
I’ve also began a series of tutorials for them.
When you will have a little time, could you look at this one http://acousmodules.free.fr/tutorial2a.htm , and tell me if I’m wrong in some parts (not yet finished) ?
Thanks !
ZynewaveHi Jean-Marc,
I’ve updated some of the info in the device definition forum: AcousModules
It would be nice if you could create a page on your site, which acts as a sort of portal for Podium related stuff. It could be your current mappings.htm added with download links for the plugins. Then I can just link to this page in the device definition forum, and skip showing download links for the plugins. You seem to update your plugins quicker than I update the links 😮
ZynewaveComments to your tutorial:
Very impressive. And this is now the second user-created tutorial that is appearing. I appreciate your efforts, as it hopefully will be a help for other users.
In the tutorial you describe how a user can use the ‘Import file’ menu to import device definitions. This will work in most cases, but the recommended way is to use the ‘import device definition’ command in the project wizard, because; The wizard will automatically search for the plugins in the VST root folder specified by the user, in case the plugins are not found at the default location indicated in the definition file. The wizard will also handle cases where you import a definition for a global plugin that already is imported, and will then assign a new instance number to the second import and reuse the old device definition object from the first import.
Your explanation of how to import a wave file onto a track could be done in fewer steps. You describe that you must go back in the browser to import the file and then back to the arrangement to open a list window to drag the imported object onto the track. Why not just open the list window in the arrangement, locate the file with the embedded file browser in the right hand side of the list window, and drag the file onto the track. This will then automatically import the file into the project.
acousmodThis will work in most cases, but the recommended way is to use the ‘import device definition’ command in the project wizard,
Yes, I knew this way, but I have choosen for this first step the manual way in order to explain the relationship between the Definition file and the plugin file.
With the Wizard, one has not idea about what is involved the first times. Anyway it was the case for me… perhaps because I’m french and don’t understand all the words !
The wizard will also handle cases where you import a definition for a global plugin that already is imported, and will then assign a new instance number to the second import and reuse the old device definition object from the first import.
Hmm, I’m not sure that I understand this.
Global plugins can work in a multichannel way ?
Why not just open the list window in the arrangement, locate the file with the embedded file browser in the right hand side of the list window, and drag the file onto the track. This will then automatically import the file into the project.
ahhh.
I agree with you and this is what I do myself, but for the same reason, I thought (perhaps am I wrong) that this way, since much longer, was for a first approach more clear for people that discover also Podium.
Perhaps that the result is the contrary : I will try to correct this.
But also, to be honest, I am a little bit confused with the Object/File List, which is at the same time a kind of duplication of the Track Browser, but not really the same, and a sort of file explorer which doesn’t acts really like one.
For example, a simple button to go up in the path like in a regular file explorer will generally avoid to open the new Windows explorer for finding a file (less clic, better way !).
This is not a criticism. Just a personal feeling.
I know also that people (and I !) like that a software can be intuitive to handle, especially when it is so original like yours, and it seems to me that there is something around that is a bit “cumbersome”.
It’s why I asked you in an other post for a Sound Category in the track Inspector for easy visualization of the pool and direct drag and drop of files, or a direct shortcut (Ctrl + I !) and/or right clic option for direct import.
Sure, these things are little details and may differ from users, but as I teach for years I see what is functionning and what drives people to say : “yes, very powerfull, but finally I prefer this one”. And for every day work, this finishes to have a great importance.
On the other way, Podium has a lot of great tricks, and it’s a real pleasure to see how some things are handled, like the way to change the hierarchical position of a track or to add a new automation track : there is no other software to do this so easily and efficiently !
So excuse me for a so long post…
acousmodIt would be nice if you could create a page on your site, which acts as a sort of portal for Podium related stuff. It could be your current mappings.htm added with download links for the plugins. Then I can just link to this page in the device definition forum, and skip showing download links for the plugins.
It’s what I will do !
Thanks !
ZynewaveHmm, I’m not sure that I understand this.
Global plugins can work in a multichannel way ?
Global plugins differ from insert plugins, in that there are several mappings that all refer to the same plugin instance. This is needed when you have multitimbral or multi-output plugins. You need the different mappings to be able to route separate MIDI channels and audio channels in the Podium mixer. The mappings are linked to the specific plugin instance with the ‘global instance’ number in the mapping properties dialog. With the project wizard you can import a definition file for a global plugin several times, and each time Podium will then duplicate the mappings but allocate a new global instance number, so that you can work with multiple instances of a global plugin.