ZynewaveBut don’t you think that tools icons looks a little blurred now?
The tool icons are now smaller and anti-aliased. To me this looks better. I’ve always been unhappy with the sharp pixelized look of the old icons, which was a direct copy of the tool mouse cursor images.
I have just replied to the post you referred to. I moved the topic from the VIP lounge to the support forum, so others can read the topic.
ZynewaveHi Max,
I’ve debugged the daHornet plugin to see what’s going on. The VST spec defines a feature called ‘sizeWindow’ which is a way for a plugin to ask the host to resize the plugin window. Podium replies to the plugin that it supports sizeWindow. Strangely, if I disable this feature, then the daHornet plugin will resize the window by itself, which will work both with hiding and showing the keyboard. When Podium reports that sizeWindow is supported, the daHornet for some reason don’t call this function when pressing the button to show the keyboard. This appears to me as a bug in the plugin. If I disable the sizeWindow support, then there are other resizable plugins that won’t work, so I’m afraid we will have to live with this daHornet bug.
Frits
ZynewaveZynewaveIs the massive advertising campaign on the plan for 2006?
No specific plans yet, but I probably will be doing more advertising.
So… Will you start developing the feature you and I talked about way back now?
Eventually, yes.
ZynewaveAny chance for the offline bounce feature in November ?
Offline bounce is one of those features I hope to start on in January. There is a better chance that I may be able to speed-optimize disk streaming in November. Would that make it possible to work with your project?
ZynewaveZynewaveZynewaveThat sounds like a simple bug. I’ll get it fixed for the next release.
ZynewaveZynewaveZynewaveI’ll think about the stereo to mono track option. If you want to hear the final output in mono (to test your song for mono compatibility), you can temporarily select the master mono mapping on the master track. This will mix stereo tracks to mono.
ZynewaveI tried your project, and followed your instructions about moving the mouse fast over the waveform icons while it is playing, but I still can’t get it to crash. I tried it both on my W2K/800 MHz PC and my new dual core 2.8 GHz PC.
I assume you are using the latest Augur.dll, released in July?
What exactly is the message that is displayed when the crash occurs?
ZynewaveIt seems if you accidentally record, with a track record-enabled it destructively over-writes it. Is there a reason this cannot be non-destructive?
The undo history is currently reset for the sounds and sequences that is recorded. An item on the future plan is to support undo of recorded material. If you happen to record over a sound, it is only stored in temporary files. The actual sound file is unaffected until you select to save the sound.
ZynewaveI tried Augur, and I couldn’t get it to crash. I tried adjusting all parameters and even automated waveform selection. It’s possible that the crash is related to the Augur preset you are using. If you can email me a simple project with an Augur preset that causes the crash, I will have a look at it again.
ZynewaveI think the best way to support this would be with a key shortcut customization dialog. There are just not enough keys to support shortcuts for all menus and buttons etc. Everyone has different preferences. I almost never use the scroll option, so I would prefer to use ctrl+F for something else.