Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterI’ve uploaded the MIDI file tutorial video I mentioned in the post above:
http://www.youtube.com/watch?v=hV1Eg7zToZw
In the video the sound of OmniSynth is compared with the Microsoft GS Synth, and the free sfz+ plugin loaded with the FluidR3 GM soundfont.
ZynewaveKeymaster@ras.s wrote:
I mean how can I make a track to go to a certain output? I’ve only got the master bus that allows me to select a single stereo output at a time. I just can’t figure it out, tried it with sends already and that didn’t work either.
You need to drag the second audio output from the inspector list, and drop it below the last track, to create a new master track. Under this new master track you can then either place the track you want to output to the master, or place a bus return and use the corresponding bus send on the tracks under the first master.
ZynewaveKeymaster@thcilnnahoj wrote:
The recent projects listbox uses a wrong background color, it seems – probably a tiny bug.
It’s transparent. Load a background wallpaper, and you’ll see. I changed it to emphasize that this list does not contain objects in the current project, as the other two lists. I also have some plans for further changes to the recent projects list.
ZynewaveKeymaster@LiquidProj3ct wrote:
– What’s the difference between Update and Rebuild database? i think that update doesn’t scan plugins in database
Update will only scan/import dlls that are not already present in the plugin database.
– How can I customize the global database? I’d like to remove mono plugins and folders
Open the “PluginDatabase.pod” project file from the Podium setup folder, make your customizations, and save back the project. You may want to save a backup, as a “rebuild database” command will rewrite the database from scratch.
ZynewaveKeymasterHi,
@ras.s wrote:
But I acted a bit hastily still. I didn’t make sure it does what I need it to do. I make reggae/dub music, and live mixing is a essential part of that – now that I’ve been more thoroughly demoing and reading this forum as well I figured out I can’t use my (general) midi controller with the program. I mainly need it to ride volume faders, solos&mutes, send amounts, not so much for controlling plugins. That’s a major show stopper for me.. As it’s weekend and my money won’t be going through until early next week, I’m seriously considering canceling my order at Share-it. 😥 Feeling quite frustrated about this… Is this feature how high on the priority list?
Unless your MIDI controller is capable of emulating MCU (Mackie Control) mode, then I’m afraid there are still many months to go before MIDI control changes can be used to operate the Podium mixer.
If this is essential for you, I’d recommend you cancel your share-it order ASAP. I had a look at my share-it control panel, but it doesn’t seem like I can cancel the order for you.
Another one is that I can’t figure out how to set up Podium to use multiple outputs on my soundcard (actually a asio4fall combined two soundcards..). I bet it does that though, I just have to go through the manual a bit more thoroughly.
Podium can only use one ASIO driver. If it’s possible to configure two soundcards in the ASIO4ALL control panel, then that should work. I have not tried this myself.
April 24, 2010 at 01:42 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymaster@ronin wrote:
However I’ve noticed that Bootsie’s epicVerb and DensitymkII crashed Podium while scanning. I think they never crashed it before.
This may not be Podiums fault but I thought I’d mention it (because there is another thread with similiar issues).These plugins have crashed randomly for me with earlier Podium versions. Random crashes are often timing dependant, so the fact that the speed of scanning has changed a bit in 2.28 can explain why they have started to crash for you now.
ZynewaveKeymaster@ronin wrote:
@Frits: There is a tiny mistake in the download-url of beta1. Thank you very much for this beta! I’ll test it right away.
@all: You can still download beta1 by changing the url to “…beta1.zip” instead of “…beta.zip”.Fixed. Thanks.
ZynewaveKeymasterThe upcoming Podium 2.28 will feature a new plugin database system, which will make it easier to avoid VST scanning for each new project, as well as making it easier to update the plugin setup in your older projects:
ZynewaveKeymasterI’ve posted a preview topic for Podium 2.28, which features a new plugin database system. Please comment in that topic:
ZynewaveKeymasterZynewaveKeymasterOk, I downloaded and tested Ferric 1.5. I don’t get the weird GUI behaviour you described. Reading the user comments on the Ferric 1.5 blog page, I see there are new complaints about GUI problems using Cubase:
http://varietyofsound.wordpress.com/2010/04/02/ferrictds-updates-to-1-5/
The problem could be related to the Windows GDIplus.dll you have on your system. Perhaps the new Ferric version requires a more recent GDIplus.dll version.
ZynewaveKeymasterI installed a bunch of Bootsie plugins a couple of months ago, and gradually almost every one of them has crashed at random during plugin scanning. Something scary is going on there. If the problem also exists for Cubase users, I’ll assume the Bootsie developer is aware of the problem and is trying to fix it.
ZynewaveKeymasterJust read in the news on kvr that a new Synth1 1.08 version is released. One of the things mentioned is:
Fix: Correspondence of the malfunction that the MIDI tab of the optional dialogue is replaced by without permission.
Apparently a robot translation from Japanese, but it seems that this is a fix for the MIDI tab problem.
ZynewaveKeymaster@Malcolm Jacobson wrote:
Hi Frits,
@Zynewave wrote:
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.
Why does the plugin database need to be part of the POD file, and therefore part of the template?
Reaper scans for new plugins each time you start it up (by default, but it can be configured to only scan on command) and writes the list of plugins to an ini file in an Application Data folder. You can then create as many Project files (equivalent to Podium projects) as you want without having to rescan the plugin database.
Is there some architectural reason the database can’t be separated from the POD file?
The main reason that the plugin definitions (or database) are included in the project file, is to allow customization of the plugin setups for different projects. You may have different plugin setups that you have organized for mastering, mixing, surround, classical, rock, and so on. Another use could be to have one setup that is organized into folders for plugin vendors, and another into folders for plugin type. You save these different setups in project templates. With the use of the “Load device setup” from the project template menu you can even switch between the plugin setups while working on the project.
I agree that the vast majority of users won’t bother with organizing different plugin setups, and will only ever need one setup. That’s why I’m currently making some changes for 2.28 that will support a global plugin database. The plugin setup is still included in the project, but the management of the plugin setup is now much easier. I hope to have a preview ready later this week.