Zynewave.
Zynewave@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.
Malcolm Jacobson@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?
Cheers,
Malcolm.
thcilnnahojI noticed something that could use a little thought:
Imagine you create a new group track and add a few child tracks to it. They of course all get tagged with, say the standard “Tracks” tag. This results in the child tracks not minimizing when you try to collapse the group, as not only the group track, but also the child tracks themselves are tagged, and thus always appear “expanded.”
I guess you can’t simply tell Podium not to tag child tracks, as we know all tracks except the master(s) are child tracks… :-k
And something else that’s unrelated: Since the disabling of the sound name/filename naming capability in the sound properties dialog, all my projects end up being comprised of audio events with very undescriptive names (meaning “Track 1, 2, 3…”), as I tend to name the tracks at a later time.
With the ‘sound event name’ box, it seems you can only name each event separately, even if they’re all phantom copies. š
Edit: Ah, what the heck. One more!
Would it theoretically be possible for a zoom snapshot to know it spans the whole length of the arrangement, and update accordingly? I always set up the first snapshot slot for this purpose, but as the arrangement grows, I regularly have to resize the zoomed area by hand. Just a small matter, of course.
ronin@Zynewave wrote:
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.
I’ll try to read/test it in detail tonight. Since there seem to be no other complains about that I think it is okay as it is + you usually put a lot of thoughts into new features. I’ll report back when there are problems.
ZynewaveI’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?
kingtubby@Zynewave wrote:
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?
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.
Mart.
Zynewave@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.
thcilnnahojHey, 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)
It has a more relaxed pace than the last one, and I hope everyone will be able to follow along this time.
Once again, it’s probably more of a demonstration than a tutorial, as I don’t show exactly how to set everything up from zero. As such, it’s also not really aimed at absolute beginners…
Well, I hope you can “take something home” from it! š
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.
I must admit I like it better without annotations, because it seems a little frantic (probably how my video looked like to others :lol:). Maybe it’s just because I already understand what it is you’re doing in it, as a Podium user.
Zynewave@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 š
ZynewaveBeta 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.
Zynewave@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?
Zynewave@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.
Zynewave@thcilnnahoj wrote:
I noticed something that could use a little thought:
Imagine you create a new group track and add a few child tracks to it. They of course all get tagged with, say the standard “Tracks” tag. This results in the child tracks not minimizing when you try to collapse the group, as not only the group track, but also the child tracks themselves are tagged, and thus always appear “expanded.”
I guess you can’t simply tell Podium not to tag child tracks, as we know all tracks except the master(s) are child tracks… :-k
New child tracks are assigned the same tags as the group track, so that when deleting the group track it won’t leave the child tracks without tags (i.e. invisible). I implemented that after you made this remark in the 2.26 preview topic:
Hmm, I experienced a moment of confusion yesterday, when I deleted a group track, and all child tracks disappeared along with it! Of course they were just invisible because only the group track had the selected tag.
So assuming the child tracks should still remain tagged, one solution is to allow tagged child tracks to be collapsed, if the parent group track is visible. Would that solve it? :-k
And something else that’s unrelated: Since the disabling of the sound name/filename naming capability in the sound properties dialog, all my projects end up being comprised of audio events with very undescriptive names (meaning “Track 1, 2, 3…”), as I tend to name the tracks at a later time.
With the ‘sound event name’ box, it seems you can only name each event separately, even if they’re all phantom copies. š
The name of new sounds can be edited in the sound properties dialog until the first save of the project/sound file. Do you miss a possibility to rename the sound file, or to apply a name to all selected sound events?
Edit: Ah, what the heck. One more!
Would it theoretically be possible for a zoom snapshot to know it spans the whole length of the arrangement, and update accordingly? I always set up the first snapshot slot for this purpose, but as the arrangement grows, I regularly have to resize the zoomed area by hand. Just a small matter, of course.
Yes it’s possible. I’ll keep it in mind for a future update.
thcilnnahoj@Zynewave wrote:
New child tracks are assigned the same tags as the group track, so that when deleting the group track it won’t leave the child tracks without tags (i.e. invisible). I implemented that after you made this remark in the 2.26 preview topic:
Hmm, I experienced a moment of confusion yesterday, when I deleted a group track, and all child tracks disappeared along with it! Of course they were just invisible because only the group track had the selected tag.
So assuming the child tracks should still remain tagged, one solution is to allow tagged child tracks to be collapsed, if the parent group track is visible. Would that solve it? :-k
That sounds like a very good solution. At least, I can’t see any problems with it right now.
The name of new sounds can be edited in the sound properties dialog until the first save of the project/sound file. Do you miss a possibility to rename the sound file, or to apply a name to all selected sound events?
A-ha! Didn’t know that yet.
Being able to rename the audio file itself again is not so important to me, personally, though I guess it would be for others. I see the appeal of naming sound events stemming from the same audio file separately, but I would appreciate a way to rename multiple events at once. Without applying the volume, pan and fade settings in the sound event properties dialog, though – that would also be nice, but a different matter altogether. O:)
Zynewave@Malcolm Jacobson wrote:
Unfortunately the Multi version of Garritan Personal Orchestra 4 still imports with only 2 outputs. I made a Track Template a while ago that included the 16 MIDI inputs and 16 stereo outputs, but it doesn’t work in 2.27b5, or 2.26 for that matter. Do I have to create a new template, or is there some way to get the import to recognise that the plugin has 16 stereo outputs?
I purchased my GPO4 upgrade tonight, and I have found out why the GPO4 multi-out doesn’t import correctly. Expect a fix in 2.28.