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?
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.
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@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.
Zynewave@LiquidProj3ct wrote:
@Zynewave wrote:
In a future update I may add a handle at the center of the events, so that’s why they are currently aligned to the bottom.
Another handle? Imagine an audio event with four handles in each side, too much I think. Why don’t you fusion handles? I mean, you can join in only one dot timestretch&resize handle and using a key shortcut to alternate between them, usually before click ALT for timestretch. It’s the standart way, even in Video editors, as I can see while I’m learning Sony Vegas HD 9 demo, because Camtasia demo expired already (I won’t do more videos with it :P)
edit: when people test demos they don’t read manuals until they think that the program can satisfy their needs (lots of times they never do it!). If you integrate easy, fast, consisntet and standart methods Podium had a bigger chance to show its power and advantages.
The reason I added stretch as a separate handle, was to make it more obvious that you can time-stretch the events. If you needed to Alt+click the handle to stretch, most people would never know about this feature, unless they read the manual.
Zynewave@LiquidProj3ct wrote:
Due to an error I’ve stretched a curve event and I discovered it after carefully editing the clip. It’s pretty easy make an error resizing it because the dots of resize and timestretch are pretty close. Could you please separate them a bit?
In a future update I may add a handle at the center of the events, so that’s why they are currently aligned to the bottom.
Zynewave@thcilnnahoj wrote:
Must…resist…nnngrrh… No, the urge is too strong! 😈
If you moved that new button one pixel to the right, the arrows would line up again.
Thanks a LOT for fixing real-time bouncing, but please don’t forget about the stuff in the 2.34 preview thread.
Don’t think I haven’t been tormented by this also 😛
The problem is that aligning the arrows violates one of my other principles, which is that the space between buttons and panel edges are 5 pixels. Furthermore, if the user sets a different scrollbar size in Preferences, then the arrows are misaligned anyway.
I’ll get back to the 2.34 preview topic, once I’ve gathered some strength 😉
Zynewave@LiquidProj3ct wrote:
I found some problems and I think they’re related.
I’m aware of these issues. Currently the separate editor timeline does not update if you move/resize the sequence event that was used to open the editor. One day I’ll improve this behaviour.
Zynewave@LiquidProj3ct wrote:
Using a custom colour?
I think it would be overkill to add another color to the setup just for this. For each new setting that is added to the color setup, it becomes more and more complicated to create a color setup that does not conflict with custom track colors.
ZynewaveI have uploaded a video that demonstrates MIDI file audition and dragging MIDI files onto the note editor:
ZynewaveZynewaveZynewave@LiquidProj3ct wrote:
1. In arrangement view I’ve selected one single clip. I barely can remeber where the others phantom clips are, so I could screw it up (and I did it several times). Please, highlight (no active selection highlight) all phantom copies when you select one.
Anyone have suggestions to how phantom events of a selected event should be highlighted?
Nice color setup, btw. 🙂
ZynewaveIt depends on how many plugins you have in your arrangement. A plugin chain on a single track can only use one cpu-core, because each plugin depends on the finished output of the previous plugin. So if you only have plugins on your master track, then only one core can be used. That’s the same in realtime and offline rendering. If the offline render is slower than realtime, then I would think a plugin is to blame. Some plugins may not be capable of doing faster than realtime, and thus may block the offline render. Try switching out the plugins to see if one of them is to blame.
Zynewave
