Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterWill the fix be in the next update?
Yes. Going up in a day or two.
ZynewaveKeymasterI’ve changed the scan & import function so that the actual plugin loading is done by the UI thread. This fixes the RealGuitar2 hang. I figured there may be other plugins that gets confused if they are not loaded from the UI thread. There was a recent report about a conflict between Cygnus and JCM900 which may be related. The downside is that the scanning is a tiny bit slower now and the progress dialog is a little less responsive to user input, but I think it is worth the sacrifice to get a more stable plugin load.
ZynewaveKeymaster@Improv wrote:
@Zynewave wrote:
Could you try to create a new project using the project wizard in 1.66 and see if this causes it to hang?
I did that just now and specified first the RealGuitar2 folder and then my whole vstplugin folder, both worked, no problem-quick import, no hanging.
I have tried the RealGuitar2 demo, and I get the hanging too. I don’t think it has anything to do with the new project start page. I get hanging too when using the ‘quick setup’ or ‘scan & import’ commands in the project wizard. This also happens in release 1.65. I can use the ‘import plugin’ commands to import the RealGuitar2 plugin without problems. The problem only occurs with the scanning procedure. The difference is that the plugin scanning occurs in a background thread to allow the user to abort the scanning with the abort button in the progress dialog. This appears to cause problems with RealGuitar, as if it assumes that the plugin construction occurs in the UI thread. I’ll do some more testing.
ZynewaveKeymasterProbably a good time to update the Podium demo
The latest 1.66 release is available as a demo. I’ll probably release another demo at the end of the month when the start page is more complete.
ZynewaveKeymasterThey say you give updates 3 times a year.
That’s probably lost in translation. I wrote in my interview that I release updates “2-3 times every month”.
What were the other sequencers tested in the article?
ZynewaveKeymasterSounds interesting. Don’t you mean 9/2006 for September? Or maybe their numbering don’t follow the months.
I got an email on the 9th of August from one of the Beat editors, asking if I would do a short interview as part of an article about independent audio software developers. I assume the same interview questions were asked to other host developers. Is this what you have seen in the mag? Share more details please 🙂
ZynewaveKeymaster@P. Rene wrote:
cool, so does this mean per song we have a folder and subdirectory saying audio, fades and so forth and so on.
You have one project file which contains all arrangements and sequences in the project. Only the sound files are saved as separate wav files, and they will be saved in separate folders for each arrangement.
ZynewaveKeymasterSo far I’ve implemented a ‘new projects folder’ setting in the preferences dialog. This will default to the ‘Zynewave Podium Projects’ folder that the installer creates, but you can change this. When you save a new project that hasn’t been saved yet, it will automatically be saved as a sub-folder in the ‘new projects’ folder. The sub-folder will be named after the project. You can override the sub-folder creation by using the ‘save as’ menu. Each new sound you create in the project will be saved in a sub-folder structure similar to the folder placement within the project. Sounds created in arrangements will thus be placed in sub-folders of the project folder, named after the arrangement. Again you can override this by saving the sounds manually with ‘save as’.
ZynewaveKeymasterI’ll see what I can do. I’m currently working on creating file folders for new projects and sub-folders for arrangements. Deleting orphan sound files are more safe when the project is contained in its own folder.
ZynewaveKeymaster@Podianer wrote:
I cannot delete them via the file browser.. 🙁
No. I haven’t had the ‘guts’ to implement a file delete command yet. It’s on the plan. You’ll need to use the Windows explorer.
ZynewaveKeymaster@Podianer wrote:
ah, ok, thanks.. I will delete the “unpinned” 🙂
Just make sure they don’t belong to another project.
ZynewaveKeymasterThe sound files are not deleted. You can see what sound files are actually used by the project in the list window file panel. Sound files that are linked to sound objects in the current project are indicated with a pin head.
ZynewaveKeymasterJust turn a knob on the device, and podium would automatically learn
what controller it is (even NRPN) and then the user would just have to give a name to this controller and continue for every knob of the deviceA ‘MIDI learn’ functionality in the track inspector parameter panel is on the plan.
ZynewaveKeymasterIdeally you would find a nova definition file in the Podium library:
http://www.zynewave.com/wiki/doku.php?id=definitions:index
But there is no definition file for the nova in the library yet. The next best thing is to find a cubase patch script for the nova. Googling for “novation nova patch script” I found a script file on this site:
http://www.deepsound.net/pc/supernova/supernova.html
Importing the script file will give you a correct preset list for your nova, but the script file does not contain parameter definitions. Podium will however create a set of default control change parameters, which is more extensive than the set of controllers you got when importing the GM definiton file. I’m guessing that most of the Nova parameters can be controlled with single control change messages, so that should get you started. Setting up NRPN parameters can be quite tedious and requires some knowledge of how MIDI works.
ZynewaveKeymasterHi,
A few days ago, I got it recording controllers (pan, volume, etc)
from my evolution uc33e. This was really exciting. But I can’ t do that anymoreDo you have the problem with the exact same project and instrument track that was working before? Are you controlling a plugin instrument or a hardware synth? Does the control changes you send from your controller actually change the sound in the instrument, in other words; is the problem only recording the automation?
To be able to record parameters, the device you are controlling with your MIDI controller must be configured with the proper parameters. If you select your instrument track and open the parameter panel in the track inspector, you should find the list of supported parameters here. If you are controlling a plugin, then some plugins handle the conversion from MIDI CC to VST parameters internally, in which case the MIDI parameters don’t have to be present in the Podium parameter list.
If you cannot find the problem, you could email me your project file.