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:)
thcilnnahojNice! Thanks for the detailed recap. 🙂
If you want to do a little extra work, you could try Podium’s beat slicing on the (non-distorted) rhythm guitar, and then the new quantize function to correct the timing just a little.
May be worth a try, and it might work if the guitar signal has a fast enough attack.
thcilnnahojThat’s really nice – great job! I bet you didn’t think it would turn out this well the first time. 😉
My observations are: there’re short clicks sometimes (noticable at 1:42-1:50 – probably too short crossfades), the rhythm guitarist should work on his rhythm (as should I :P), and I really like how the bass sounds!
Would you mind telling us a little about what equipment you used in the end?
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.
thcilnnahojthcilnnahojthcilnnahojI 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.
thcilnnahoj@Malcolm Jacobson wrote:
[*]The MIDI Learn function in Camel Space does not work in Podium.
[/list]
At least MIDI learn works fine here. Are you sure you assigned your MIDI input to the effect track, and not only to the instrument track (see http://www.zynewave.com/forum/viewtopic.php?t=2132)?
The automation tracks are automatically created for other effects’ parameters I’m trying to record, so it might be a possible cause.
Besides that, I can confirm all the other problems with Camel Space (demo).
It also takes away keyboard focus (spacebar, numpad 0/enter) from Podium. But I don’t use any of their plug-ins, so I don’t think I’ll bug Camel Audio about it.
thcilnnahojthcilnnahojthcilnnahojThere’s a super-minor thing I noticed in beta 7, which might very well be intentional. I just don’t think it’s very pretty. 😉
I’m talking about the text color on empty/transparent selector buttons – when you bypass them, the text is dyed as well, making it unreadable with the default color theme.
thcilnnahojthcilnnahojThe “+” and selector buttons in track chain panels are translucent when no devices are assigned.
Wow. When you think it can’t get any better, it just does like that. 🙂
The way you show the separate bus inputs in that video is a real eye-opener!
thcilnnahojthcilnnahojI can only confirm that the newest version of Drumatic (3.0.2 – http://www.kvraudio.com/news/12577.html) doesn’t import at all in 2.27 beta 6, and an incorrect mapping is created for it in 2.26. The old version I use (3.0.1) still works fine in both.