H-man.
Mike G@UncleAge wrote:
@Mike G wrote:
However when selecting a track in the mixer it doesn’t slide the track into view in the arrangement…
Wouldn’t this mean that if I was working on a bass track and decided I need to adjust the drum fader in the mixer then the bass track would lose focus?
Good point, I didn’t think of it like that!
My thought process was I’m adjusting the level of this track, but I need to navigate to the part of the track this audio starts at…
The daw should read our mind to figure out which we wanted …… oops! Frits is good but not that good!!
Maybe there should be a way of selecting the track from the mixer if you wanted it to, like double click the track mixer header or something like that…
thcilnnahojThankfully adjusting faders does not set change which track has focus! 8)
Neither does clicking on SMR or bypass buttons or opening plug-in editors.
H-man@Zynewave wrote:
@H-man wrote:
The state of the track headers no longer changes with the tabs (I liked this behavior a lot).
What state? With “tabs”, do you mean the tabulator key or the page headers at the top of the project window?
No sorry I was referring to the Editor Profile Bar buttons. Previously, I believe that you had a default state where track headers were expanded in the Tracks view and minimised on the Mixer view (tab, Profile Bar button).
This made sense to me, especially as there is no ‘Minimise all tracks’ button.
@Zynewave wrote:
@H-man wrote:
As mentioned I’d like the state of the inspector and browser to be stored/recalled across tabs as well.
Please clarify.
A feature request really. At present the Inspector/Browser is independent of the Editor Profiles. I just though that if one was working on the Editor page with the Browser open, switching to the Mixer might have it hidden and on the Tracks page (profile) it could be shown but the inspector (for presets) rather than the browser.
@Zynewave wrote:
@H-man wrote:
Clicking on a track in the rack doesn’t highlight the corresponding track in the mixer or track headers (ie. Group track).
If the track is shown in the rack, then it is already the focus track, and so should already be highlighted in the tracks and mixer regions?
I guess all I was saying was that clicking on a track in the rack, group, parameter or otherwise doesn’t update the focus on the Mixer or Track Header. If that’s the desired behavior then …okay.
@Zynewave wrote:
@H-man wrote:
Adding output gain and output panning to and effect in the rack sets the fader at two locations on the mixer strip (two active squares) and shows additional Pan & Fade controls in the mixer
I belieave that’s how it always have worked, or do you mean you have found a new bug?
Nah, I think I just got confused because there was a send on the track.
@Zynewave wrote:
@H-man wrote:
Would it be possible for the new track menu to stay rolled out and change focus as you click on different tracks in the mixer? As it is now I still prefer to right-click the track. Clicking anywhere else would close it of course.
But you can already do that by right-clicking on the track header or mixer strips? Or are you referring to something else?
I was just trying to think of a way to change the behavior, I just don’t see how I would add this Track menu tab to my workflow (as opposed to the right-click we mentioned).
Maybe it’s a hot-key thing :shrug:
Hope this helps clarify my points. One final thing, is intended that “Insert new effect track” is now gone from the Track Menu?
H-man@thcilnnahoj wrote:
Thankfully adjusting faders does not set change which track has focus! 8)
Neither does clicking on SMR or bypass buttons or opening plug-in editors.
Sure, but the focus track could still follow on the track header as it does in the mixer as per Mike G’s comment.
The behaviour above suggests that this would be feasible without the track header zooming all over the place when muting tracks etc.
Worth consideration. I personally find scrolling and resizing track headers slows the workflow.
With all due respect to the Dev, it’s a little like Kama FX. That synth is amazing but there is a tenancy to waste time click-drag-ing things around.
thcilnnahojYeah, I support that request! My post was more of an answer to what UncleAge suspected could happen, which would indeed be quite annoying.
@UncleAge wrote:
@Mike G wrote:
However when selecting a track in the mixer it doesn’t slide the track into view in the arrangement…
Wouldn’t this mean that if I was working on a bass track and decided I need to adjust the drum fader in the mixer then the bass track would lose focus?
H-manYeah my bad, kinda mis-read the tone 😳 (-1 Internets to me)
I’m finding 2.23 to be a huge update with some really sensible improvements. I fear that users who have not been following the betas will wonder if they’re looking actually at Podium when they install the update 😉
Mike G@thcilnnahoj wrote:
@Mike G wrote:
Just had a crash when bouncing master track and now I can’t open that arrangement without podium crashing.
Same on 2.22 and 2.23 betas (Hmm maybe this is a support post not a 2.23, feel free to move…
By the way this is quite an old track from previous v of podium reloaded and with newly created device setup importedOuch! Did it crash during bouncing or after it finished? If it’s the latter, you could try removing the bounced sound from the project before opening the arrangement.
Maybe make a backup copy first, in case Frits wants to take a look at the crashing project.
Good call, deleting the bounce files did the trick!!
… Or was it unplugging my audio device… not sure now!!
But I’m still finding that clicking bounce again on the master track causes a crash, any ideas as to how I find out what’s causing it?
ahh ha… dsk b3x organ was the culprit, should have realised. it was a very recent addition but worked fine in playback.
pavouk100Automation recording bug(?); have track with some recorded audio, add some effect and try to record automation like this:
– unassign track input
– arm track for recording
– press ‘record’ and then ‘play’ button on the toolbar.
If you fiddle with any effect control on the armed track, automation lanes are properly created and recorded, but there is no sound coming out of the track at all. Or is it my misunderstanding how automation should work now?
Tested is on beta14.
sam cWill I be able to reduce the size of the BSMR buttons?
thcilnnahojAddition to the beta 14 buglist:
– Hide a track (with the H key) while hovering the mouse cursor over the new gain/pan sliders so you see the value popup. After that, there’s a crash when you try to unhide it again, by keyboard or minimize button on the header.
ZynewaveBeta15 is up.
I have finally finished my code review of all the changes in 2.23. I think most of the reported bugs have been fixed in the process, but I’ll go through all the bug reports over the next couple of days. If no big bugs appear, I hope to have a release ready for friday. Many of the good suggestions for improvements that have been posted in this thread will make it into a later release.
New in beta15 are shortcut buttons in the mixer for showing/hiding effect chains, new effect buttons, source and input selectors. The parameter selector on parameter tracks are now aligned to the effect selector in the parent strip that is being automated.
Zynewave@sam c wrote:
Will I be able to reduce the size of the BSMR buttons?
No. The buttons are now the same size as most other buttons in the Podium UI. Can you give me your reason for why you would like them to be smaller?
sam c@Zynewave wrote:
@sam c wrote:
Will I be able to reduce the size of the BSMR buttons?
No. The buttons are now the same size as most other buttons in the Podium UI. Can you give me your reason for why you would like them to be smaller?
Fritz, I just think they are a little over sized for the track menu. Particularly if I have the track minimized…too much button graphics. However, it is a personal quirk!
Zynewave@thcilnnahoj wrote:
Addition to the beta 14 buglist:
– Hide a track (with the H key) while hovering the mouse cursor over the new gain/pan sliders so you see the value popup. After that, there’s a crash when you try to unhide it again, by keyboard or minimize button on the header.
I think this bug and all other value popup issues are fixed in beta15, but let me know if you still find problems.
Zynewave@pavouk100 wrote:
Automation recording bug(?); have track with some recorded audio, add some effect and try to record automation like this:
– unassign track input
– arm track for recording
– press ‘record’ and then ‘play’ button on the toolbar.If you fiddle with any effect control on the armed track, automation lanes are properly created and recorded, but there is no sound coming out of the track at all. Or is it my misunderstanding how automation should work now?
Tested is on beta14.
Well, this is because I so far haven’t done enough testing 😳
The track is silent, because Podium currently mutes record enabled tracks.
As I see it, there are two ways I can fix this issue:
1/ Enable playback of a record enabled track, if there is no input assigned or if the input is bypassed.
2/ Add a new “Automation Record” track option. This will be placed below the “Record” option in the track menu. I would like to avoid having to add another button for this, so perhaps Ctrl+R key shortcut or Ctrl+clicking the R button could toggle this track option. This solution adds the complexity of having another track option with a somewhat hidden access, but on the other hand it will allow automation recording without having to bypass or remove any audio inputs assigned on the track.
Which solution do people prefer?