Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterYes, I know, but the Restore option is then greyd so it is not possible to revert the window to its previous size.
Just noticed this. It must be because the window doesn’t have the usual minimize/maximize buttons in the caption bar. However, even though the restore option is greyed out, you can still double click the caption bar to restore.
ZynewaveKeymasterThis must be what went wrong: When you make changes in the plugin editor and then click properties to export the preset, the last changes you made in the plugin editor is not stored in the preset yet. I’ll fix this for the next release. If you use the ‘store current settings…’ command before exporting, the fxp files should be ok.
I think the easiest way for other users to try out these presets would be if you can generate a zip file like the one you emailed me. The users should then use the ‘import library preset from file’ command in the preset panel menu, browse to the folder with the zPEQ fxp files and select all the files in the file dialog (ctrl+a selects all). This will import all presets as program library presets, like you have it in your project file.
ZynewaveKeymasterI thought the project might help. What happens next?
The project helped, and it seems to be ok. The problem is with the fxp files you emailed me. Can you describe how you created them?
ZynewaveKeymasterIt seems as though the fxp files are not saved correctly. They seem random compared to the presets in your project file. Just for clarification, can you describe how you exported the fxp files?
Is it correct that all 51 presets only use one band, and most use a ~3.0 dB gain value?
ZynewaveKeymasterI’m currently looking at it.
ZynewaveKeymasterBut will it be possible too with the floating editor ?
You can maximize it by right-clicking the caption bar and then select the maximize menu command. The caption bar will not disappear though, because otherwise you would not be able to close the window. Only the browser window has the custom minimize, maximize and close buttons when the window is shown in full-screen maximized mode.
ZynewaveKeymasterA little bug : if a secondary monitor is defined to be at the LEFT of the main monitor, the menus of the windows which are in the secondary monitor are shown at the left edge of the first monitor.
Fixed.
September 18, 2006 at 12:53 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterThe space key is used to select the caret object. If you press ctrl+up/down you move the caret without selecting the object. Pressing space will then select the object. Pressing ctrl+space will toggle selection. This is standard Windows behaviour for all listboxes. If you try it in a file explorer you’ll see the same behaviour.
September 17, 2006 at 21:48 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterFrits I need some help here please
I’ll take a look at them tomorrow.
ZynewaveKeymasterAnd a request while you are working on the GUI : a maximise / restore buttons together with the close button of other windows, le the sound editor or a sencond browser would be VERY useful.
Thanks.I have now implemented maximizing browser windows so they appear in full-screen mode like the main window. This is of course only useful if you are using a dual monitor setup.
ZynewaveKeymasterIn addition there could be a subtle texture just to make it look more plastic.
I’m not sure a ‘plastic’ look is what I’m aiming at with Podium. I think brushed metal, marble or glass has a better vibe to it 😉
ZynewaveKeymasterThe space key is overridden when the event listbox on the info page has focus. Just click focus away from the event listbox.
ZynewaveKeymasterSounds great 🙂
Currently zPEQ only supports 1 program, but if people find these presets useful we could consider extending the zPEQ bank to maybe 64 programs, and put these presets in as defaults? This would be the easiest way for new users to ‘stumble upon’ the presets. Otherwise we would need to create a device definition file with the library presets included, but I don’t think many users want to bother with definition files.