ZynewaveZynewave@thcilnnahoj wrote:
@Zynewave wrote:
@thcilnnahoj wrote:
Quick question: What’s the reason the meter isn’t moved to the bounce track after bouncing? If you disable bounce playback you’ll get a pre-fader reading unless you set it manually.
If the meter is set on an effect track below the bounce track, then the displayed meter will automatically switch to the output of the bounce track when bounce is enabled. Otherwise the meter would be inactive. When you deactivate bounce playback, the meter reverts to show the output of the configured meter track. I think this behaviour is better than actually moving the assigned meter to the bounce track when enabling bounce. Or did I misunderstand what you’re saying?
Perhaps it does make more sense… If you’re only using bouncing to freeze tracks, though, you’ll get a ‘wrong’ reading when you disable bounce playback, as the fader position is moved to the bounce track, but meter position stays pre-fader.
Here’s the scenario:
– You have a track without effects that peaks at -6 dB, track gain is also set to -6 dB. The meter shows -12.
– Bounce the track. The fader position is moved to the bounce track, the meter is now set pre-fader (just not during bounce playback) and shows -12.
– If you disable bounce playback now, the track’s meter shows -6 dB.
Ok, now I see what you mean. Yes, the meter should actually be assigned to the bounce track, like the fader is. Enabling the bounce track should behave just like when adding a new effect. I’ll look at that tomorrow, and then release 2.37. If you have further bug reports, please post those in the 2.37 preview topic, as this topic will be locked when 2.37 is released.
ZynewaveHmm. I haven’t made any fixes on this issue yet. I still have this topic on my todo list.
@thcilnnahoj wrote:
hmm. What would you think about having additional submenus for all effect tracks’ parameters in the track context menu parameter submenu?
This way you’d have access to all parameters in the track effect chain when the individual effect selectors are not visible.
I think that can become a bit overwhelming. But I’ll consider it.
Zynewave@thcilnnahoj wrote:
Frits, have you thought about using some sort of logarithmic scale for mouse-wheel fader adjustments? You can try it on knobs in FabFilter plug-ins – I find it to be super-comfortable!
I could just remove the code I put in to make it snap to full dB steps. I thought it convenient that each wheel click adjusted a fixed dB. Easy to set the fader to -3 or -6 dB for example. Do anyone prefer the wheel to adjust in proportion to the fader range, rather than in dB steps?
Also, shouldn’t scrolling up on a pan control move it left instead of right…? After all, the highest (top) value in pan curve sequences and on pan parameter faders is 100% L.
There are pros and cons of both methods. The reason I chose down to be left, is because it then matches how you adjust horizontal gain and send sliders. I think it would be weird that using the wheel over a pan slider would make the knob move in the opposite direction than gain/send sliders. Perhaps it is the pan parameter that should have L/R swapped :-k
Zynewave@thcilnnahoj wrote:
I noticed a problem with changing time signatures… When you enable snap, the grid shifts, and not like it should! 😮 The weird thing is that it doesn’t happen at any point on the timeline… I haven’t found out what exactly causes it.
Here’s a video with a simple example: http://www.youtube.com/watch?v=NyjVoR6GrMQ (this is after restoring the default setup, I only changed the gridline color)
Thanks. Nice find. Fixed.
ZynewaveSorry to hear you lost your work.
I assume the warning dialog you mention is the one that appears when a plugin has performed an illegal action. The dialog should mention which plugin crashed, and then suggest to use the “save as” command instead of the normal save, in case the plugin has overwritten memory used by Podium.
Was this a new project that you had not saved before the crash? In that case the project subfolder would not have been created yet.
As long as you don’t overwrite an existing file with the “save as” dialog, then the save command should not delete any existing project files.
You say you lost “all of my projects in the directory”. Are you talking about multiple .pod files in the same project subfolder, arrangement subfolders, or .wav files?
Podium only creates crash logs when it’s scanning for plugins.
Zynewave@thcilnnahoj wrote:
I had some fun with real-time bounce recording today… now I remember why I missed it. 🙂 It’s too bad you can’t record any automation on tracks that are bounce enabled, though, even when the effect to be automated comes after the bounce in the signal chain (probably due to the fact that you can’t record enable bounced tracks). It does work with the faders on parameter tracks, so perhaps something can be done? I didn’t try with a MIDI controller, just with VST editors.
Hmm, perhaps record enabling a bounced track should be possible. I’ll experiment with this at some point.
– It seems the highest level you can go to in the browser is a drive’s root directory. Am I missing something or is there no other way to change drives except using the browse dialog (double-click on the folder name bar)?
That’s the highest I can go with the Windows API function I’m using.
– When you drop files that are numbered like 1..20 in an arrangement, they’re not ordered the way you’d expect. 10 comes after 1, 20 after 2, and so on. Even Windows gets this right nowadays. 😉
I’ll have to search for a Windows API function that can help with a more intelligent sorting. I believe sorting behaviour is locale specific.
– If you uncheck “use as group track” for a track that has only one child track, the former group track is suddenly seen as an effect track… Maybe it should be impossible to uncheck this option (also for composite tracks?) when a track has child tracks.
I’ve noticed this too. I’ll fix this at some point.
Zynewave@thcilnnahoj wrote:
Quick question: What’s the reason the meter isn’t moved to the bounce track after bouncing? If you disable bounce playback you’ll get a pre-fader reading unless you set it manually.
If the meter is set on an effect track below the bounce track, then the displayed meter will automatically switch to the output of the bounce track when bounce is enabled. Otherwise the meter would be inactive. When you deactivate bounce playback, the meter reverts to show the output of the configured meter track. I think this behaviour is better than actually moving the assigned meter to the bounce track when enabling bounce. Or did I misunderstand what you’re saying?
Zynewave@thcilnnahoj wrote:
If you delete things from a project, the project browser seems to have a problem displaying this:
Also, I’d prefer if the ‘Move bounced audio to new track’ command in the bounce menu would always create the new track directly below the one that got bounced. Objection, anyone?
Ouch 😯
Fixed. That was a bug that came with the UI changes in 2.36. I’ll probably release 2.37 within a day or two.
Zynewave@LiquidProj3ct wrote:
This hierarchic organization not only defines the visual track layout, but also controls the flow of audio, MIDI, and parameter automation signals. The signal flow arrows at the left edge of track headers and at the top of mixer strips provide a visual confirmation of how tracks are routed.
The basic rule to remember about the track hierarchy is that all audio, MIDI, and parameter automation signals flow upwards from the bottom tracks of the hierarchy until finally reaching the master track at the top. The only exception to this rule are send tracks, which create a branch-off to a bus track from the exact point in the signal chain where the send mapping is placed.
is it me? or these two paragraph seem very redundant with first chapter paragraphs?
http://www.zynewave.com/wiki/doku.php?id=guide:tracks#track_hierarchy
I think they must be fixed
They do seem like two attempts at explaining the same thing. I’ll wait for tchilnnahoj to give his opinion on this, as I believe he collected some of the text from the old chapter, and combined it with his new text.
ZynewaveThanks. Always interesting to hear how people come to know about Podium 🙂
Frits
Zynewave@ninjawarrior wrote:
@Zynewave wrote:
I don’t know why some plugins support mouse wheel only in some hosts. As far as I have tested, I am not doing anything in Podium that should prevent a plugin editor from supporting mouse wheel.
Maybe it is about this shortcut stealing.. Same thing than plugins steal space button. Podium lost keyboard / mouse tracking / support or something. Which is btw so annoying. I send you email about this, but i didn’t get any respond, so i guess you have no intention to fix this.. 👿
I read your email, and I still have it in my inbox. I do intend to do something about the plugin key stealing at some point. Please be patient. There are a lot of things on my todo list.
Zynewave@Trancit wrote:
Normally (if I look at the most hosts), mousewheel alone changes bigger values, with shift or ctrl as modifiers smaller amounts…only one host makes it other way round and I have to say, this works much better:
Imho, if you want to make bigger changes to a fader or knob, it´s far easier to grab it by left clicking and move it…
So, why do we want the mousewheel: especially for smaller changes/fine tuning or slower changes it´s far easier to use the wheel and that´s the reason, why I personally find it much easier to have small increments without modifiers and bigger ones with…
On a volume fader, the mousewheel shouldn´t change the value more than 0.5db, perhaps only 0.33db…take a look at MU.LAB from Mu.Tools…mousewheel on the volume fader changes value in 0.25 increments…works pretty good!
Try the latest 2.37 beta 4. So far I have made mousewheel adjust in 1 dB steps. Shift+wheel adjusts in 0.1 dB steps.
I can see your point about the reversal of the coarse/fine with the shift key, but I think there are arguments to keeping it the way it is. Using Shift for fine adjust is identical to the use of Shift for fine adjust when click+dragging a fader. Also, with the recent support for zooming mixer strips to 20%, it is convenient to use the mouse wheel for coarse adjust of pan and send, since the strip can be zoomed so small that you can’t reliably drag the knob.
Zynewave@Trancit wrote:
I don´t have any knowledge of programming, but could it be, that plugins, that don´t have extra mousewheel support themselves, could benefit from this “hoovering over the dial to set mousewheel focus on that”????
The sentence you quoted, is that an option you have seen in another host?
Btw. I see you are using “hoover” in your posts. The correct spelling is “hover”. Hoover refers to a vacuum cleaner.
And a second question:
Is it a big effort to implement midi controller mapping to Podium elements for hardware controller support???
I don´t think it´s necessary to support special controller directly in first place, but to map a midi CC to a fader or button is quite essential these days with so many brilliant controllers available 8)
I’d estimate it would take me 1-2 weeks to implement. The problem is that there are many items on my todo list with a similar priority. I have to work on one feature at the time.
ZynewavePodium does not yet support general MIDI controllers. Only Mackie Control compatible devices are supported for controlling the Podium mixer.
You can control a plugin with a MIDI controller, if the plugin supports MIDI learn natively.
