darcyb62@Zynewave wrote:
If you are trying to add an effect plugin to e.g. an instrument plugin track, the easiest way to do it is to drag the effect mapping onto the first ten pixels of the instrument track header (the part will be highlighted accordingly). This will wrap the instrument track in a new track with the effect plugin.
That’s too cool. I’ve had that happen by accident and I couldn’t relly figure out what I did to make it happen. Now I know and that will save a couple of steps for me every time I add a plugin.
darcyb62Cool…
It looked like Cygnus was loading before JCM900 so I created a subdirectory that would force Cygnus to load after JCM900 loaded and presto… Works like a charm…
darcyb62I created a seperate folder and I moved plugins to this folder 1 at time and tried creating a new project. They all worked until I added Cygnus. I tried Cygnus on its own and it works fine. I then moved everything but the JCM900 and it worked fine. I then added JCM900 and it locks up. Seems to be a problem with JCM900 and Cygnus.
darcyb62@Zynewave wrote:
Btw. I don’t have problems scanning and importing the JCM900 plugin. I don’t have the other plugins in the suite installed, so maybe that is making a difference.
You are correct. It must be one of the others… Let me check this out some more… get back to you soon.
darcyb62😳
Ahhh… never mind… I understand… The JCM plugin is still causing problems but I can work around that not that I realized I’m an idiot… 🙂
darcyb62@Zynewave wrote:
I would not recommend that you put your plugins in the c:Program FilesZynewavePodiumVstplugins folder, as this was intended to be reserved for Podium bundled plugins. This folder is automatically searched by Podium, in addition to the VST folder you specify.
I didn’t put any plugins. All I did was set the plugin folder on the new project setup to that folder in an attempt to bypass the JCM900 plugin. When I did that is scanned 1 level up on the directory tree. This is where the JCM900 plugin sits so the import locked up again. I will try the empty directory suggestion.
darcyb62@Zynewave wrote:
@Zynewave wrote:
When using the new “New Project” setup is it possible to disable the plugin scan when creating the project.
Hmm, not the most beatiful solution; but you could hit the abort button just after the import dialog appears.
Or better yet; set the VST folder temporarily to an empty folder.
That would work but still is a workaround.
darcyb62@Zynewave wrote:
When using the new “New Project” setup is it possible to disable the plugin scan when creating the project.
Hmm, not the most beatiful solution; but you could hit the abort button just after the import dialog appears.
I would think if it was an option that could be set when hit the create button. I would love to just let it run but when you run into some problematic VSTs it would be nice to just bypass the import function.
With Tracktion you have the ability to flag certain vsts to be skipped in a scan pocess. This might be something that would help as well in working through vsts that behave badly with the import.
darcyb62Another issue:
I have tried to bypass the JCM effect by setting the vst folder 1 level deeper by focusing on the Zynewave effects…
I set it as follows:
c:Program FilesZynewavePodiumVstpluginsZynewave Effects
But when I hit create the plugin import dialogue box indicates the following:
c:Program FilesZynewavePodiumVstplugins
It would also be good if you could use multiple folder pointers.
darcyb62When using the new “New Project” setup is it possible to disable the plugin scan when creating the project.
The reason I ask is that the scan freezes when it hits the JCM900 vst. The only way to get out of is to abort then close Podium.
darcyb62@acousmod wrote:
A different zone for Device (audio and MIDI) and Plugins.
I understand that from the engine point of view all of this are mappings, but for the user, the Audio and MIDI devices with there inputs and outputs consitute something different from the plugins.It is the same in the inspector of the arrange view : it seems (to me) to be more logical and faster to use to have a Device category where to choose the output mappings AND the audio and MIDI inputs, and a distinct Plugin category where we find only the plugins…
+1
darcyb62@Zynewave wrote:
Okay… One thing that’s missing. I can’t add a plugin from the new page…
In the intial screen shot you provided there is an icon which I believe would open a menu. It’s not present here.
@Zynewave wrote:
I’ll continue adding some features for the next release, such as:
Menu button at the top of the devices panel with plugin scan and import, as well as some of the other options found in the project wizard.
😉
😳
darcyb62Okay… One thing that’s missing. I can’t add a plugin from the new page…
In the intial screen shot you provided there is an icon which I believe would open a menu. It’s not present here.
Also… shift_ctrl_i does nothing, so to add a plugin I need to back to the old view…
darcyb62This is a great new look. I much prefer it to the previous start page.
The only thing that I could think of as an improvment would be maybe the placement of boxes on the page. It would be great if you could place and size the boxes where and how you want but to make things easier it might be an idea to have a selection of layouts.
For example, I would prefer to have the left most boxes to the right, but them someone else might have different preferences.
When you get right down to it this is pretyy trivial, as everything you need is on that screen. I think the info area at the bottom is great.
Just need those fades and controller support..
darcyb62sexy