Reply To: Preview 2.34: Minor consistency updates

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. 😕

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! 😳