Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@bladerunner wrote:
it seems to me that podium is reporting a more accurate cpu reading than other hosts and that podiums engine is based on real time performance (so, equivalent to reapers synchronous mode right? – forgive me if i am repeating stuff that has been mentioned in other related threads) and not the rendering ahead type ability of reapers anticipative mode. when reaper is in synchronous mode i get a similar performance to podium but when in anticipative i get more performance but the trade off is in a delay to real time performance tweaks to plugins etc. (right?!). hope i’m making sense
Exactly. I’ve spent a lot of time optimizing the performance of the engine, so I’m glad to hear that your performance test shows that Podium matches the synchronous mode in Reaper.
ZynewaveKeymaster@bladerunner wrote:
the ongoing cpu spike issue which can be clearly be seen in frits own video here
http://www.youtube.com/watch?v=Jv39dX7NP_Q
its reassuring to know that it happens on the devs own computer as i thought it might be an issue with my own particular set up. it really makes podium almost unusable for me. i haven’t seen behaviour like it in any other host. the spiking seems to be directly linked to the asio buffer size which has to be set at 2048 samples to tame the spikes. in reaper i have no such problem and can run many more softsynths at 512 samples. i have read through all of the cpu related threads in this forum and played around with all of the recommended tweaks etc. but the issue still very much remains.
i have also mentioned timestretching as an issue but i could just rewire reaper for that duty if i needed it so the cpu issue being addressed is my one wish.
i can regularly bounce tracks as a workaround but i think there is an issue that needs addressing here. do others find this is still a problem or are you bouncing tracks to get around it?
Sigh! 😥
If it leaves the impression that Podium suffers from CPU spikes, then I guess I have to redo the video with some tracks bounced. The spikes you see in the video are not random. They occur at places in the song where a lot of notes are playing simultaneously. I shot the video with a buffer size of 2048. As I’ve explained in previous topics, Podiums CPU indicator is deliberately sensitive, to give a clear warning of where there may be problems. Other hosts may use a slower updating CPU indicator, but that does not mean that CPU spikes are more likely to occur in Podium. As you can hear in the video, the spikes does not produce an audible degradation of the audio output.
That you find that Reaper produces lesser CPU spikes at low ASIO buffer sizes can be due to the anticipative mode, which has been discussed here:
http://www.zynewave.com/forum/viewtopic.php?p=13556&highlight=anticipative#13556
ZynewaveKeymaster@thcilnnahoj wrote:
Add a default track color to the default setup color settings. Grey events/notes on grey background are not the prettiest thing to look at, and totally new users might be turned off. The coloring feature could be nicely displayed if all tracks were colored already, and it would also automatically activate the color picker in the inspector, which you can’t miss then on opening your first project ever.
Very easy to do and would help, in my opinion. Even if you set the same gray as the default color it would at least still show the color picker. Otherwise the track coloring options might be a bit too deeply buried in menus for new users to pick up.
The problem with setting a specific color for new tracks, is that it can conflict with the users color scheme. The color could accidentally be the same as the color the user has defined for the background or the selection. When a color is not defined for the track, it will use the “default track color” specified in the color scheme, which should ensure that the color matches the color scheme.
Edit: Hang on, maybe you are just suggesting that the “default track color” option in the colors dialog should be enabled in the default setup? In that case it would not be a problem, and new tracks will have the track color picker enabled by default.
ZynewaveKeymaster@thcilnnahoj wrote:
Got another one: When adding a new track by drag-n-dropping an instrument from the inspector, it’d be good if the track was selected automatically, so auto-assigned MIDI input goes straight to the new instrument! (Saw that in a Studio One video just now :oops:)
Done, but only because Markus wanted it too. :-#
And that’s it for 2.20 =;
I’ll release it tomorrow.
ZynewaveKeymaster@thcilnnahoj wrote:
Found a bug related to window updates:
With the Timeline editor open create a new MIDI event and immediately expand it by keeping the mouse button held and dragging right. The editor will only show the segment that was created before resizing.I’ve now changed it so that once the mouse is released, the embedded editor is updated with the final size of the sequence event.
ZynewaveKeymaster@Conquistador wrote:
1. While the Navigator is very useful it still does not have any handles on either side of it. This is a much needed UI change. It’s not obvious how to move it. Could you please give serious consideration to some sort of indicator or similar to both sides of the Navigator before 2.20 is finished **please**. It *really* needs it. Even a small semi transparent handle on either side would be enough.
It already has a semi transparent handle on both sides. You’ve mentioned this quite a few times now, but you’ll have to create a mockup image so that I can see what you are suggesting.
2. Also the horizontal slider…I really would like to see that back as a default. I use the Navigator but not that much. It’s not ideal for every horizontal task IMO. Why remove the horizontal bar? Puzzling IMO. :-s
I removed the scrollbar to save space. The navigator is essentially a scrollbar, only it shows a miniature of the timeline data in the background. To me it seems pointless to have both a navigator and a scrollbar in the same editor.
ZynewaveKeymaster@LiquidProj3ct wrote:
Hey Frits, this is a bug (I think it’s a bug) present in olders Podium version also, but I didn’t know how replicate it, now I do know. The bug is that sometimes you cannot delete selected clip in arrangement view with SUPR key (DELETE).
Create any clip in any track, and edit it (add notes/audio/…). Then rotate between profiles with F8 until you reach again the original profile. now try to erase the clip with DELETE/SUPR key, you cannot.
Got it!. Fixed. Thanks.
ZynewaveKeymaster@Mike G wrote:
I’ve previously only ever used expanded view so I have a question about “compact” view.
-I add a new track called “Group 1”
-Then set “Use as Group Track” = Yes
-I want to drag an existing track into that group but I can’t
-Only way I can do it is by right-clicking and selecting the menu item “Move Track” “To Group” “Group 1”Strange thing is once I’ve added one track I can drag other tracks on to the group.
Is that the expected behaviour?
At the moment, yes. The reason it doesn’t automatically drop the track into an empty group track, is because it would then not be possible to drag tracks next to or inbetween group tracks. I’ll refine this behaviour in a future update.
ZynewaveKeymaster@Markus wrote:
Cause with pencil tool you cannot select notes.. Or of course you can, JUST USE FUCKING ANOTHER SHORTCUT. Do you even make music yourself? When you make music, you want to get your ideas FAST out.
I cant really see why you cant do that. Now i asking LITTLE thing, and no, you dont want to do it.
Please calm down. You can select notes with the pencil tool without shortcuts, by clicking a note. Are you referring to the marquee selection of multiple notes?
ZynewaveKeymaster@thcilnnahoj wrote:
I don’t exactly remember when this changed but I’d like to see the old behaviour back on this one:
– Double-clicking an event’s volume handle should set focus to gain offset in the properties window, not event name.
Ahh, that happened after I added the “sound event name” text box. The gain input is no longer the first control, so it does not automatically get focus. I’ll fix this.
ZynewaveKeymaster@Markus wrote:
@Zynewave wrote:
@Markus wrote:
..how about possible to strech notes in selection tool.. ? [-o<
That’s possible using the Alt key shortcut. Check out the “note event actions” settings in the piano roll region dialog.
I DO KNOW THAT. I just cant get it why it would be so hard to do. Little thing which makes LOTS OF PPL HAPPY :frustrated:
If you mean it’s a nuisance to have to use the Alt key, then why don’t you use the pencil tool, which allows to resize without key shortcuts?
ZynewaveKeymaster@Markus wrote:
..how about possible to strech notes in selection tool.. ? [-o<
That’s possible using the Alt key shortcut. Check out the “note event actions” settings in the piano roll region dialog.
ZynewaveKeymaster@kyran wrote:
1. The spacebar should always control the transport, regardless of the current focus
Some plugin editors uses the spacebar key for its own purposes, and thus steals the spacebar keypress so that it never reaches the host. Also, all listboxes in the Podium UI is using the same standard key/mouse shortcuts as used by Windows, so in that case the spacebar is used to toggle elements in a listbox selection. Using the numeric 0 and return key to stop/start is more likely to work no matter where the key focus is.
3. Quick create new arrangement: just makes a new arrangement with all the default settings, no popup windows. Make this the default option. Most of the time I only have one arrangement in a project. If I change a setting on them it’s the name. The rest is nice to have, but it just intimidates new users.
Thanks, this is now the default behaviour when you create a new project on the start page. The name you enter for the project will be used for the arrangement name. There is also a “create arrangement” checkbox option on the start page, with popup help that explains this.
ZynewaveKeymaster@ronin wrote:
the global SMR buttons plus the fantastic “add track” and “add child track” button!
http://www.zynewave.com/forum/viewtopic.php?t=1438I have some ideas for a new feature that would include a solution for global SMR, so maybe I’ll work on that for 2.21.