@moikkelis wrote:
Hey, i have notice that when i have some VSTi OPEN and i tune knobs while song is playing, the space function wont work. Its pretty damn shit to tweak sound and then push to space to return maker and it wont work.
So far what do this is
Novation V-Station
NI Battery 3
Podium will react to the space bar key if the plugin does not intercept the key. Some plugin editors have been coded to use their own key shortcuts, and route unused keys to the host. I’m guessing that the plugins you mention uses the space bar key for something.
@moikkelis wrote:
So, you claim podium can do easy sidechain? Post me directions, or maybe track template? I dont understand that which is in wiki. 😳
If we refer to this tutorial:
Could you please describe which parts you don’t understand? Maybe I can use that info to make the wiki guide more understandable.
@moikkelis wrote:
To me, first run was totally crash one. I need to restart my computer. Dunno what happen 🙄 But on second run everything works fine.
Without more clues, it’s difficult for me to guess what could have caused that. In all my tests here, I have not experienced crash at startup.
Edit, i play my song and while PLAYING i push power off button and podium crash. Here is what it give me.
AppName: podium.exe AppVer: 2.19.0.0 ModName: battery 3.dll
ModVer: 3.0.4.1 Offset: 0044671e
I have tried the Battery3 demo, and I get no crash with that. Does the crash happen every time you switch off power?
Dear Frits. Is it possible to get option to shortcut TAB button to open and close mixer? Similar in ableton?
At some point in the future, I’ll implement user customization of key shortcuts. At that point it would be possible to add support for this. In the standard configuration however, the tab key is used to rotate key focus between the available editor panels. The F7 key can be used to open/close the mixer.
@kingtubby wrote:
@Zynewave wrote:
For the users that have reported problems with plugins in the 2.18 release: To test if the changes to the UAC build options in this beta has fixed the problems, you need to copy the beta exe to the program files/zynewave folder, and run it from there.
Well done Frits, my Guru problems are now fixed 🙂 =D>
Regarding the file location, do you mean “program files/zynewave” as opposed to “program files/zynewave/podium”? I tried it in both locations and it worked either way.
Doesn’t matter where, only it should be in the Program Files folder tree to make UAC kick in.
@swindus wrote:
I have tested it with Drumazon and Nepheton from D16. They support MIDI out since the latest version. Any chance for implementing this?
http://www.zynewave.com/forum/viewtopic.php?t=1874
Because the new versions can also sends pattern and instrument names to the host.
I prefer to wait with this, until I start on a update of the drum map editor.
Are you using ASIO drivers for the onboard interface? If not, try the generic ASIO4ALL driver.
2.19 beta1 is now available. Please post your test results in the 2.19 preview topic in the future forum.
@moikkelis wrote:
Take a look at ableton live sidechain feature. That is easy way.
http://cdn1.ableton.com/movies/compression_and_sidechaining.mov
Thanks. That’s a nice tutorial. I wish I had time and resources to do video tutorials like that for Podium.
The main difference between Podiums and Lives sidechain support, as I see it:
In Live you choose the sidechain input source track in the plugin editor on the compressed track. In Podium you insert the sidechain input on the source track. Two different approaches, each with their own pros and cons. It may be easier to do a simple side-chain setup with Live. With the Podium approach it is possible to set up multiple input tracks for the sidechain input (if for example you have multiple bass drum tracks). You can also add the sidechain input anywhere in the source track chain, and not just pre/post effects.
@swindus wrote:
It is not possible to add a device via drag and drop to an empty folder in the device list on the project page. It is possible if the folder holds at least one item. This makes the reorganization of loaded plugins/devices more complicated as it could be.
Is there a reason for this? Or is it a bug?
The reason is that it would not be possible to insert a dragged object between two folder objects (i.e. under the same parent as the folders) if it should always add it as a child to the folder.
If you hold the control key when you drop an object, it will be added as a child object of the object you drop on. This works for all object types and not just folder objects.
You can’t “scrub” in the sense that you will hear what you drag over, but if you enable the “link edit cursor to play cursor” option in the view menu, then playback will jump to where you release the dragged edit cursor.
If you are using Podium 2.18 and Vista, then it may be a problem with the UAC feature that is enabled by default in the new compiler tool I’m using. This was discussed in this topic:
http://www.zynewave.com/forum/viewtopic.php?t=2025
Until 2.19 is released, you may want to revert to 2.17.
Click with middle mouse button anywhere in the timeline regions.
Click and drag the top triangle of the edit/play cursor.
If you want a larger single-click area for dragging the cursor, you can modify the timeline ruler region:
Open the “editor profile properties” from the view menu. Open properties for the “timeline ruler – cursor” region. Disable the “left-click to slide timeline” option.
@thcilnnahoj wrote:
One more:
Font anti-aliasing for the time/beat counter on the transport bar has become pretty bad compared to 2.17 and before, at least on my system.
(Comparison image with Big Transport setup)
Thanks. I’m fixing this now.
Btw. Be sure to check Synth1 again in the next Podium release. As mentioned earlier today in another support topic, I’ve changed some build settings in the new compiler tool so that UAC is no longer enforced. I think it’s likely this fixes the Synth1 problem.
I will be disabling the UAC option in future builds of Podium. I found that when I rescanned my plugins with Podium 2.18, the Drumatic 3 plugin popped up module creation errors. Drumatic 3 is a SynthEdit plugin, and it will save some .sem module files in the plugin folder when it is being initialized. I don’t why SynthEdit is designed this way, but a lot of SynthEdit plugins do this.
I tried disabling the UAC option in the linker, and Drumatic 3 no longer shows errors when scanned. Hopefully this is the same issue as reported for Synth1 and Guru.