Zynewave.
ninjawarriorWohoo! thanks for fixing insert 🙂 Now we have proper duplicate command! Next all in one pianoroll tool 😉
thcilnnahoj@Zynewave wrote:
There is and “end of track” marker, but I don’t know how reliable that is. Do you have a couple of example MIDI beat files that you can email me? Some that has pauses at the end, and that will import with the pauses in other hosts. And of course, the MIDI files should not have been saved with Podium.
Will do.
The downside to how you implemented it now is, of course, that it’ll extend events created by importing MIDI files if your snap setting is larger than their original length.
@Zynewave wrote:
I see you kept the old “== Title ==” headers.
…
I also replaced your // line termination with true paragraph spacing. I find it easier to read. Any reason you use the // forced line feed?
I did those things because I didn’t know better! Didn’t look at the formatting close enough. 🙂
LiquidProj3ctFrits, I’ve problems with master bouncing. I wanted to do an small intro for a track, so I used Ctrl+A in arrangement view to select all clips and I moved them 8 bars towards right, then I did the intro.
However when I was bouncing it the intro always was silenced in the final audio. I finally solved it, and maybe you could consider it a bug, the problem was that the first tempo event was displaced too, and bounce don’t render anything that is before the first tempo marker.
edit: btw some changes that you do in english versions, as the “scheme” word, are irrelevant in the spanish translation, so you can consider them updated 🙂
thcilnnahojMy good deed for today: http://www.zynewave.com/wiki/doku.php?id=guide:tracks 😉
Please review it… a few things are marked with “fixme”, and the dialog screenshots need to be updated as well.
The hierarchy section could be much better, but I can’t think of anything to add at the moment. I’ll think about adding additional screenshots tomorrow.
Questions about terms & formatting:
– Should we use **Input** and **Source** selector or input and source selector? I see you also used “plugin selector” in the getting started chapter…?
– I wasn’t sure if you actually use the term “group panel” anymore, so I didn’t use it either in the tracks chapter.
About track templates (I don’t use any, so this is a first):
– Why do track templates show up in effect track template menus, and effect chains show up in track template menus? If that’s a known limitation, I hereby request improvement! 🙂
– Personally, I would also swap the positions of the Replace Effect Chain and Insert Effect Chain commands on the templates menu.
thcilnnahojContinuing from the e-mail (don’t know if you’ve read the post above already!?):
With the conclusion you’ve reached, does that mean auto-extending sequences on import is the best you can do, as many MIDI files don’t seem to have an end point set after all, or will Podium use this end point if it is set? As for the sequence names, I hope you noticed that at least the AD MIDI file actually has a name defined in some or the other data field. I’ll look forward to 2.35 to test it!
Edit: Or maybe the sequences could at least be extended up to the next beat. If you drop a MIDI file while using smaller snap values like 1/16 snap, it just doesn’t work for me. 😕
About the guide, I can’t promise to get anything done over the weekend, but I think I’d like to tackle either the big Track Inspector or Mixing chapters next. Are you still on the new Editor Menus chapter?
A keepsake from the old tracks chapter:
In fact, as far as routing is concerned, a track in Podium is similar to a piece of track in a railroad model. Imagine a train station to the left and a train yard to right. Most of the track pieces that enter the train yard on the right side are simple and straight but some of them look like forks and allow two or more tracks to combine into one. The ‘trains’ in Podium carry audio, MIDI or parameter automation signals. The ‘train station’ in Podium is small and only has one platform and all the tracks are eventually combined into one single track: the Master Output track.
That train station analogy is so cute you just want to hug it! 😳
LiquidProj3ctRecording chapter, 10th or 11th paragraph:
Loop mode can be activated by clicking the loop button on the transport bar, or by pressing L. Set the loop range by moving the loop locators, or using the options on the loop region context menu.
When recording with loop mode activated, sound events will be overwritten on each subsequent pass through the loop range. Conversely, any new MIDI data recorded will be added to the existing note sequence when recording in loop mode, enabling you, for example, to layer drum notes during each pass.
That’s not true, isn’t it? When loop mode Podium automatically creates new takes
LiquidProj3ctAlso, a little above that paragraph:
Recording will commence on all record enabled tracks whenever playback is started with record mode activated, beginning at the position playback was started
You can activate record mode after playback had started and Podium will record
thcilnnahojBoth should be fixed now, thanks.
I also removed the \ new lines. I did use them on purpose to separate things a little more, but it’s fine with me if Frits prefers it the other way.
LiquidProj3ctYeah, thanks, I was about to ask about those \, I was searching in wiki docs although
Zynewave@LiquidProj3ct wrote:
Frits, I’ve problems with master bouncing. I wanted to do an small intro for a track, so I used Ctrl+A in arrangement view to select all clips and I moved them 8 bars towards right, then I did the intro.
However when I was bouncing it the intro always was silenced in the final audio. I finally solved it, and maybe you could consider it a bug, the problem was that the first tempo event was displaced too, and bounce don’t render anything that is before the first tempo marker.
I don’t think it was the tempo event that was the problem. When you use the Select All command, it currently selects all events, including the hidden bounce events. When you then drag the selection, the bounce event will be moved too. I think that is what happens. I’ll do some tests. I think I’ll change the Select All (Ctrl+A) command so that it does not select hidden bounce events.
Question: Should Select All be changed so that only selects events that are available in the editor? For example, in the arrangement editor it would not select events that are on tracks hidden by a collapsed group, or a disabled track tag.
LiquidProj3ctMaybe it’s a good idea, but I’d like that my mates write their opinions about that.
Zynewave@thcilnnahoj wrote:
My good deed for today: http://www.zynewave.com/wiki/doku.php?id=guide:tracks 😉
Please review it… a few things are marked with “fixme”, and the dialog screenshots need to be updated as well.
The hierarchy section could be much better, but I can’t think of anything to add at the moment. I’ll think about adding additional screenshots tomorrow.
Many thanks. I’ve reviewed it, updated the links in the index, and also uploaded new dialog screenshots. I’m done revising it, so it’s all yours again, if you had planned to make further changes.
Questions about terms & formatting:
– Should we use **Input** and **Source** selector or input and source selector? I see you also used “plugin selector” in the getting started chapter…?
Hmm, I would say without ** **, but I’ll leave it up to you. I used “plugin selector” because I thought that would make sense.
– I wasn’t sure if you actually use the term “group panel” anymore, so I didn’t use it either in the tracks chapter.
Group panel, RIP.
About track templates (I don’t use any, so this is a first):
– Why do track templates show up in effect track template menus, and effect chains show up in track template menus? If that’s a known limitation, I hereby request improvement! 🙂
I’m not sure I understand you completely. All track templates are managed in one list. Podium does not know whether a track template contains effect tracks or source tracks before it loads the template. If the template contains only an effect track, you can still use it to create a new source track. If a template contains a full source track with effects, you can still load just the effect chain from the template.
Zynewave@thcilnnahoj wrote:
Continuing from the e-mail (don’t know if you’ve read the post above already!?):
With the conclusion you’ve reached, does that mean auto-extending sequences on import is the best you can do, as many MIDI files don’t seem to have an end point set after all, or will Podium use this end point if it is set? As for the sequence names, I hope you noticed that at least the AD MIDI file actually has a name defined in some or the other data field. I’ll look forward to 2.35 to test it!
Edit: Or maybe the sequences could at least be extended up to the next beat. If you drop a MIDI file while using smaller snap values like 1/16 snap, it just doesn’t work for me. 😕
As it seems to be rare that a MIDI file contains a pause at the end, I decided to skip that in this round of MIDI file improvements. At least the names are now working properly.
About the guide, I can’t promise to get anything done over the weekend, but I think I’d like to tackle either the big Track Inspector or Mixing chapters next. Are you still on the new Editor Menus chapter?
Yes, I’m still working on the Editors chapter, and will be there for quite a while. You are free to mess around with Tracks and all the remaining chapters. The “Arranging” chapter is a bit of a junk-yard currently. Perhaps it would be better to name it “Editing & Mixing” and move the “Edit Actions” page there.
A keepsake from the old tracks chapter:
In fact, as far as routing is concerned, a track in Podium is similar to a piece of track in a railroad model. Imagine a train station to the left and a train yard to right. Most of the track pieces that enter the train yard on the right side are simple and straight but some of them look like forks and allow two or more tracks to combine into one. The ‘trains’ in Podium carry audio, MIDI or parameter automation signals. The ‘train station’ in Podium is small and only has one platform and all the tracks are eventually combined into one single track: the Master Output track.
That train station analogy is so cute you just want to hug it! 😳
That, and much of the old Tracks chapter, was written by Piltdown Man.
thcilnnahoj@Zynewave wrote:
Questions about terms & formatting:
– Should we use **Input** and **Source** selector or input and source selector? I see you also used “plugin selector” in the getting started chapter…?Hmm, I would say without ** **, but I’ll leave it up to you. I used “plugin selector” because I thought that would make sense.
I’m not sure because the conventions page says ‘named’ UI elements should be in bold type. The selectors do have a name written dimmed on them, but it’s not the same as for toolbar menu buttons, so I don’t know if it qualifies. I’ll keep it as is just so they stand out more.
About track templates (I don’t use any, so this is a first):
– Why do track templates show up in effect track template menus, and effect chains show up in track template menus? If that’s a known limitation, I hereby request improvement! 🙂
I’m not sure I understand you completely. All track templates are managed in one list. Podium does not know whether a track template contains effect tracks or source tracks before it loads the template. If the template contains only an effect track, you can still use it to create a new source track. If a template contains a full source track with effects, you can still load just the effect chain from the template.[/quote]
Well, I just think that I probably would never need to load an effect chain from ‘normal’ track templates (I’d use them to save instrument and input setups), and likewise wouldn’t create a new track from an effect track template… It seems strange to me that they’re all the same, but maybe it’s just me.
Zynewave@thcilnnahoj wrote:
there’s something weird going on with bouncing, pre- & post-fader stuff:
– Set a track’s level to -6 dB and render an offline bounce. Rendering ignores the level setting but not the pan setting (I don’t know why, but it’s always been like this, I think). So far, so good.
– Now delete the bounce track, then enable real-time bouncing, record a bit, and play it back – same as before.
– Delete the bounce track again, add an effect that doesn’t change anything on its own (like zPEQ), and offline bounce again – works fine.
– Get rid of the effect/bounce track, add the effect again, and do a real-time bounce. The recording level is half of what it should be. Switch to bounce playback, and it is again half as loud!Unfortunately, I can’t do extensive testing right now… maybe I’ll have time later on, if Sherlock Nielsen doesn’t catch the villain first!
Alright, I think this is another side of the problem we discussed some time ago in this topic:
http://www.zynewave.com/forum/viewtopic.php?p=16942#16942
Maybe the time has come to finally fix this bug 😳
One solution would be to create an effect track exclusively for bouncing, as you also mentioned in that other topic. On that “bounce” track you would then not be able to assign an effect. That simplifies the technical difficulties with the bounce/effect routing in my code. It also means that the bounce point can remain at the post-effects position, even when you add effects to the chain. The question is: Should this bounce track be made invisible for the user, or should it appear in the chain panel like it does today?
If it is to be visible in the chain panel, I could make it a proper “bounce selector”, which when clicked will show a menu with the bounce options (same as the current track > bounce submenu). You’ll also be able to drag the bounce track up and down in the chain panel to position the bounce extraction point. I think I’m in favour of the bounce selector. Opinions?