Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@thcilnnahoj wrote:
Regarding tags…
Seeing as the “Tracks” tag is meant to provide a view of all tracks, don’t you think new tracks should always receive this tag, along with any and all tags that are selected at the time of track creation?
Bus tracks are now nicely tagged automatically unless you go the old-fashioned way of creating them, in which case it would make no difference which tags they get, as you’ll have to change it anyway (unless you select only the busses tag).I would even go as far as to suggest the master, busses and tracks tags should be non-removable, but maybe that’d take away a little too much freedom…
The default “tracks” tag was intended as a suggestion, to have at least one tag that when selected will hide the master and bus tracks. Personally, if I want to divide audio tracks into categories, I would rename/remove the “tracks” tag.
ZynewaveKeymaster@Malcolm Jacobson wrote:
@Zynewave wrote:
The template file seems ok to me. It imports like shown in the screenshot of your previous post. Can you give me more details about what is not working?
The VSTi does not load as part of the template. All of the tracks do, but no device. Isn’t the device definition meant to be saved as part of the template?
The device definition in your template file appears to be ok. Please describe how you experience that the VSTi does not load. Are the icons for the device mappings red? If so then the plugin dll file could not be located within the VST folders you have specified in the preferences. Your template refers to:
C:Program FilesVstpluginsGarritanARIA Player Multi VST_x86.dll
Is that still the location where you have installed the plugin?
ZynewaveKeymasterBeta 8 is up.
The timing adjustments are now saved in the project file. Also fixed a plugin import bug with some synths supporting surround output.
If no bugs are found in this, I’ll release 2.27 tomorrow.
ZynewaveKeymaster@thcilnnahoj wrote:
Hey, I’m still up (yawn), and have just uploaded a new video, complementary to Frits’ side-chain video: http://www.youtube.com/watch?v=7F2B0_VwnJM (HD not ready yet at time of writing)
Favorited 🙂
If you keep this up, I may end up learning something about Podium that I didn’t know already 😆
ZynewaveKeymasterIt could be an issue with your soundcard driver. Try to disable your MIDI/audio interfaces in the Interfaces dialog before exiting Podium. If it still hangs when you try to exit, then the problem could perhaps be related to antivirus tools.
There have been reports about slow closing times caused by antivirus tools:
March 27, 2010 at 00:40 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterHi Carl,
Use the Podium browser, or any Windows file explorer, and drag your loop files onto the tracks timeline area. To place them at a specific point (such as 30 seconds into the song), zoom in on that point first.
Frits
ZynewaveKeymaster@kingtubby wrote:
I watched the side-chaining video and was able to follow it ok, but I think newer users would definitely benefit from some annotated guidance. Maybe you should pause the video at key steps with a text description of what you’re demonstrating.
I’ve added annotations to the video. In the future video tutorials I make, I will try to pause the mouse actions in the places where annotations should pop up, so that the viewer has time to read it before the action continues.
March 26, 2010 at 15:09 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterI’ve uploaded a 2.5 minute video that demonstrates how to use sidechain compression:
http://www.youtube.com/ZynewaveDotCom
I experimented with the YouTube annotation feature, which I find is rather nice. It allows me to add speech bubbles to the video after it is uploaded. Would this kind of video benefit from having speech bubbles explaining the mouse actions, or is the video simple enough to understand what’s going on?
March 25, 2010 at 11:25 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.March 25, 2010 at 03:12 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.March 24, 2010 at 02:03 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.March 23, 2010 at 23:38 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymaster@ronin wrote:
I’ve tried beta4 yesterday and wanted to share some thoughts:
Honestly, I have to admit that I don’t really understand what the controls are doing. I had to read through this thread to get an idea. After that I knew that it wouldn’t be very useful to me but I can imagine that other users might have a good use for it.If you have time to read over the help page I uploaded to the wiki (link provided in an earlier post), and you still have questions about the controls, please let me know what needs to be clarified further.
1. I don’t like modal dialogs at all. Sometimes I wish to inspect another part of the arrangement while tweaking. Maybe the new dialog can be non-modal and just stay on top?
That will require a bit of work, so maybe something I will do in the distant future.
2. There is “Adjust timing” in the piano roll editor and in the arrangement editor. I couldn’t figure out how “Adjust timing” works in the arrangement. I’ve selected events etc. but nothing happend during tweaking the knobs ( “preview” was activated). Only the timings editor in the piano roll did change something.
When you use it in the arrangement editor, the quantization is applied to the sequence/sound events, and not the events within the selected sequences. In the arrangement editor the adjust command is thus mostly useful if you for example want to adjust the timing of the slices of a beat-sliced loop.
3. A double-left-click action resetting the knobs to their initial value would be great.
Ctrl+click will do this. This shortcut applies to all controls in the Podium UI. Double-click is used for opening stuff. I’d rather not mix up those conventions, even though this is in a dialog.
4. How about something like “randomize velocity/volume”? That would be useful to me in conjunction with the other timing commands to humanize drum parts.
Coming in a later release.