thcilnnahoj's Forum Page

No bug, just a little weirdness: When you delete an event that you’ve got ready in the embedded editor (whichever type), you normally end up with an “empty” embedded editor. If you delete the whole track the event is on, however, the editor will stay and still reference the no longer existing event (provided there are no phantom copies of it left elsewhere).

This happens to the non-embedded editor also when you delete the event that’s currently opened in it, but in this case, I think there’s not much else to show other than an empty sequence window…

Smile! 🙂
When you change the play/power color, the play cursor head still keeps the old one:

Heh, got another one for you. 😛

There’s a strange behaviour when Alt-clicking “overlapping” ghost notes: GIF animation (250 KB).

I don’t know about you, but I think it should always switch over to the note that’s visible as a ghost (brown one in the example), even if it means other notes occupying the same tonal space become unavailable as clickable ghost notes.

I’m sure there’s a valid reason for this: Why does the hue still change when I try to get a color gradient simply fading to black or white?

@Zynewave wrote:

– Is there a reason for the velocity buttons in note editor, point type buttons in curve editor and channel select buttons in sound editor to be aligned to the left instead of to the right?

If they were right-aligned, they would cover the value markings. I don’t think it would look good if they were aligned in the middle just left of the value markings.

I always think those buttons look a little lost in the embedded editors compared to the windowed ones. Of course the buttons shouldn’t overlap the values numbers. It’s only a suggestion… I can never know if it’d turn out to be a success! 😉

@Zynewave wrote:

@thcilnnahoj wrote:

“Sir Bugalot” has another fiendish bug’s head on his lance to serve as trophy on the walls of King Fixalot’s castle! 😆

There’s a selection/key focus problem concerning tempo and marker events.
In this example GIF (245 KB) I try to select and delete a tempo event with the DEL key on the keyboard whilst different editors have focus.

– First with focus on the arrangement editor – works fine.
– Then with focus on an “empty” embedded editor – here the tempo/marker event doesn’t become the active selection but still gets deleted, probably since there’s nothing else selected in the empty E.E..
– Focus on the embedded editor – works fine as well.
– And lastly, focus on the mixer. The event is not set as the active selection here either, and so it actually deletes the focus track in the mixer instead! :o)

It is on purpose that pressing delete with focus on the mixer will delete the track, even if there is an event selection. What do you recommend should be done: Should delete in the mixer delete any event selection, even though you may be on a mixer profile without a timeline and tracks region? Should clicking in the tempo/marker lanes force focus to the tracks region, removing focus from the mixer/embedded region?

Not sure I understand… Selecting any event (audio, MIDI, automation) while the mixer has focus will always set focus to the arrangement and make the event the active selection, like the embedded editor does in the GIF. It does this even if there’s an active selection in the embedded editor – this will become inactive until the editor has focus again. The actively selected mixer region only does not set tempo or marker events as active selection unlike it does with other events.
So as long as the mixer region has focus, it should of course delete the focus track. But selecting any kind of event outside the mixer (be it only on the timeline or marker regions) should set active selection to the event.

Are you this far through the bug reports already! 😀

@Zynewave wrote:

How else would you want it to look? I’ve tried cutting the text off with the same border on the right side, but it does not look good when the text is abruptly cut in mid-air.

Yeah, this one – I think it’s only natural that the padding space would be on either side. But maybe it doesn’t look good if a letter’s cut in half indeed, when there’s still space to the right…

Well, it’s your call whether you want to keep the fader frame! 😀
I wouldn’t have a problem with it, apart from that it can potentially clash with the dB markings and I don’t think it’s really needed to find out about the fader’s hitbox size (besides, it looks like the last few pixels on each side of the frame are not inside the fader hitbox area).

@Zynewave wrote:

@thcilnnahoj wrote:

– It seems the “live” color selection on the color picker constantly writes to the hard disk (podium.ini?) – I can even hear it scratching away! 😯
Maybe the color selections could stay in memory and could only be written to file when you leave the UI color selection, by switching back to track color selection.

That must be because you have a track background image in the project properties? The original image is reloaded to apply the panel dye coloring. To avoid this Podium would need to keep two copies of the image in memory, which I think is a waste.

Forget about it… It’s a known problem with the graphics card I had to put in yesterday because the old one died (that’s the third one for ATi for me). Nothing to do with hard disks! 🙂
What remains is that using the color picker for this purpose produces massive CPU use.
I didn’t use a background image before, but I gave it a try just now. It updates images dyed with the timeline fill color with a little delay – since you said it has to reload the image, that’s probably depending on the image dimensions or file size, right?

I’ve got a suggestion for the mixer zoom slider: Since it zooms in little steps, like the other zoom sliders too, it’d be nice to be able to use it with the scroll-wheel in the same way.