Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterSorry, I can’t give a time frame for these features. I’ve tried giving long-term time estimates in the past, but they rarely come through, due to the way that Podium development changes course in response to user feedback. So I no longer give time estimates to avoid disappointing users that expect a certain feature to be implemented.
ZynewaveKeymaster@Grenoybel wrote:
Edit: Ok, I’ve done more tests and it’s only happening if I loop in the first bar, and the lost of sync is just in the first beat
Then it’s probably because Nerve ignores negative ppq values (parts per quarter note).
The host provides the plugin with a ppq position at the start of each ASIO buffer. Since Podium may start the loop at bar 1 in the middle of an ASIO buffer, it calculates a negative ppq at the buffer start, so that a ppq value of 0 is synced to the point in the buffer where the loop starts. You may want to contact the Nerve developer about this, if the missing sync remains a problem for you.
ZynewaveKeymaster@thcilnnahoj wrote:
Well, I can’t say I’m overwhelmed by the beautiful lightshow you now get moving the mouse across an arrangement. I could probably enjoy it more if it had a short fade-in/out time, but that’d be too much to ask.
Are you saying that you’d rather not have the highlighting? I made it for consistency with the note event highlighting. I’m planning to add it to the tempo and marker events as well. Further down the line I’ll probably remove the remnant black frame highlighting.
– A problem I’ve occasionally had in the note editor seems to have found its way into the arrangement view now, too. Namely, short events are drawn in a weird way. It’s also very hard to see when they’re selected:

It’s because the new side edges are darkened more than the previous 4-side frame. I’ve now compensated for this by reducing the darkening when the event is less than 4 pixels wide, on both track and note events.
– With a color scheme using bright text on dark backgrounds, notes and event names expand beyond the event borders. Also, the event name box seems offset from the start, resulting in 1px of waveform not being dimmed:

That’s on purpose. The miniature note events have always overlapped the frame. The dimming of the background below the text now has a border of 2 pixels. I found I preferred this look, and it has the benefit that the background is not dimmed when the event is less than 3 pixels wide, as per your previous issue with darkened short events.
– At first glance, I liked the softly colored edges of adjacent events better than the clear-cut almost black lines, although I guess it does make for a better visual separation and I’ll quickly come around to prefer it. It looks weird though sometimes, as the backdrop of the event name, phantom copy and mute symbol seem to overlap the right edge (as mentioned above):

I’ve now shrunk the header area with 1 pixel, so that it does not overlap the right side dark edge. I agree that this provides better separation of joining events.
– There’s a bump at the top on fades and crossfades. Don’t see it? Let’s zoom in. 😛

I’m not seeing anything unusual. What bump are you referring to?
– Events look like they’re shrinking when you hover over them (this actually was the same before, but not as noticable):

Yes. Further down the line, I’ll find an alternative to the black frame highlighting. I left it in, because it is a help when editing crossfades.
Fix: The track event background color is now painted properly when only part of the event is record enabled with punch-in and punch-out.
Nice! But It’s still off with overlapping events:

This is a consequence of the way I layer the painting. Perhaps you can set up a poll asking if people would prefer I redesign this, rather than implement time-stretching 😉
I have a question at the end: Maybe I’m completely crazy, but weren’t there “Undo/Redo Inside” menu entries in the event right-click menu until one or two versions ago!?
They disappared a while ago, in one of the cleanups of the edit menu.
ZynewaveKeymasterI’ve emailed the Poise developer, asking how mousewheel is supported in Poise. I’ll let you know if I figure out why there is a difference in mousewheel support.
ZynewaveKeymaster@Pigini wrote:
@Zynewave wrote:
List your deal-breakers. List the features that when implemented would make you purchase a commercial license.
Why would you call it deal-breaker? The term deal breaker is commonly used for something that ends (breaks) a deal and does not start (make) one.
Or is that meant to be an intentional play with words?What title would you give the competition topic then?
My intent with such a competition would be to find out what missing features are holding people back from purchasing a license.
ZynewaveKeymasterI saw comments about the missing time-stretch support in a Podium Free discussion on another forum, and gave it some thought. I found that I relatively easy could add the stretching to note and curve sequences. That would be the first step. Second step would be resampling of stretched sound events (resulting in pitch shifted sound). Third step would be full time-stretching.
ZynewaveKeymasterI’m using the 4.05 Kontakt Player, without such problems.
Did you update Kontakt to the latest 4.1?
Does it happen in a new arrangement, with only one Kontakt insert mapping assigned?
Does it happen with all the multi-out variants of the dll?
ZynewaveKeymasterI don’t know either. I’m not doing anything to filter out mouse wheel messages before they are sent to the plugin window.
Do you know of any plugins that do support mouse wheel in Podium?
Do you know any other plugins that supports mouse-wheel in Cubase/FL, but not in Podium? Preferrably a plugin that I can download a demo of.
ZynewaveKeymaster@4mica wrote:
Hi all – I have a suggestion, to take or leave. Make midi and envelope clips expandible and compressible, like in EnergyXT.
Spooky 😮
Earlier today I was experimenting with exactly what you suggest. I.e. stretching of note and curve sequence events. First step towards full time-stretch support.
ZynewaveKeymaster@LiquidProj3ct wrote:
Once you start to drag the event and the mouse arrives to A1 the event is lenghten until the next gridline (B1). Once you arrive to B1 the event is shorten to its original value, because Podium takes closest the relative snap point, as you just explained.
My solution would be once you arrive to A1 paint until the next absolute snap point (B1), and once you arrive to B1 paint until the next relative point (A2). Always you arrive a relative point, paint until the next absolute snap point, and viceversa.
You must have read my post before I deleted it. I realised that this was indeed the way to solve it, so that is now done.
Thanks for the blueprint 🙂
ZynewaveKeymasterI’ve added a “Tap Tempo” button to the Tempo Event Properties dialog. Key shortcut for the tap button is Alt+E.
So: You double-click the tempo field in the transport toolbar, or any of the events in the tempo event lane. Once you have tapped at least three times, the calculated tempo is entered in the BPM value field. Each tap will increase the measured time range, and thus result in a more precise bpm value. If you pause for two seconds, the tap history is reset, and you can tap in a new tempo. Press OK, and the tempo is applied.
Will be available in Podium 2.33.
ZynewaveKeymaster@LiquidProj3ct wrote:
I generally agree with those ideas. However i’m pretty busy now, it’s my birthday 🙂 so i’ll post my ideas later, everyone here know them, although
Happy birthday! I have just uploaded the 2.32 release, so you could consider that a birthday present :clown:
ZynewaveKeymaster- Redesigned the graphics of track events.
- Minor bug fixes.
June 28, 2010 at 11:14 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.June 28, 2010 at 09:39 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
