thcilnnahojBug report! 😉
The color picker doesn’t resize correctly when you increase button size. It only does once you resize the inspector afterwards.
thcilnnahojI also need to apologize for the increasing delay on the bounce chapter I said I would write. I must admit I’ve made very little progress so far, as it would appear that I have a job now. 😉 That, and a few personal decisions have left me with much less time to spend on Podium-related stuff. I’ll still try to pop in for beta-testing (you know I love it! :mrgreen:) now and then.
Oh, and I will definitely try to slip you a little something from my first paycheck. 😉
thcilnnahoj@Zynewave wrote:
Using the Insert key to add copies of selected events will be pushed forward on the timeline until reaching a position where there are no overlap with existing events.
😀 Very nice Engrish description there! I just hope it once again works like it previously did. Thank you, thank you, thank you.
Fix: Fade-in/out curves with a duration of 1 sample could result in level overload.
Also great news. Unfortunately I can’t give it a test, but I’ll make sure to let you know if it still happens sometime.
From the 2.37 thread:
– Mono and multichannel side-chain mappings (or multi-mappings in general) seem to share instance numbers. Ex.: If there are both a mono SC #1 and a stereo SC #1, creating a new instance of stereo SC #1 names it stereo SC #3. Of course this only applies if the mappings were created from the same DLL.
The mappings belonging to a single plugin instance are linked by the combination of the plugin file name and the instance number. Are you suggesting that the mapping names should read “#2”, even though the instance number in the properties is 3?
I guess so – it would make more sense to me that they’d be treated like separate plug-ins in this regard. It’s true that there’s a discrepancy with the configuration in the device mapping properties… Then again, I haven’t encountered a situation in which I needed to manually assign instance numbers.
You know I just report this and other things as I notice them, and most are minor issues that can be saved for a rainy day, if you even think they merit some more attention. 😉
@levendis wrote:
When you move a fader and set it back to the original value in one action (not by right-click cancelling), it still creates an undo point, which is kind of a waste…?
I like this behaviour.
I can ‘enter current value’ at the edit position. Then, as any edit, have the option to undo.
Thank-you thcilnnahoj for being observant.
Oh yes, it’s indeed useful for parameter faders. I was thinking of the usual gain, pan, or send level faders – as always, a super-minor thing.
thcilnnahojThey look great overall, and I especially like how they look on dark backgrounds. 8)
The spacing on the left and right sides on icons in lists is a little off, though, I’d say. I also preferred the notes and waves to the new Ableton- or Propellerhead-ish arrangement/sound icons, but hey. 😉
When you click anywhere to the left of a list item name and icon, its info is shown in the box below, but the item doesn’t actually get selected. This doesn’t seem new, but I only noticed it now… don’t know if it’s intentional.
Also, when you switch to the other display mode on the project page (I don’t even know what it’s called), the icons are not colored correctly when you select things.
I use white as color for ‘plugin editor’, but it seems the color is painted on top of the icons instead of the other way around, which means the icons on open plug-ins’ selector buttons disappear again when using a dark color scheme. I guess it may not be worth the effort to muck around with it any more just for a minor issue like this, though.
thcilnnahojthcilnnahojEnable automatic solo (Alt+S) on the MIDI track!
Also see this video, it might help. The only difference when using Poise should be that you assign which pad goes to which output yourself, so you can skip renaming the output mappings, like at the start of the video. The shortcut for automatic solo has been changed recently, so forget about Shift+Alt+S, please.
thcilnnahojOh no, no… I need to restrain myself a little to not try and influence your artistic vision.
…Honestly, though, those are very nice gradients. 
@Zynewave wrote:
Please refresh my mind with an example. The new icons I’m designing are all colorized with the text or selection text color.
Hmm, are you sure it’s working correctly, then? The icons do not get colored over here:
(Active selection text color = red)
You removed the icons from most places outside of lists, so the remaining ones that can become hard to see are the tool icons and device type icons used in lists.
Also, the + icon on phantom copies still uses the active selection text color where it should use the one for inactive selection.
thcilnnahoj@outsiderinvention wrote:
1. why does it ask me if i want to save everytime i close the program when i always save prior to clicking on the X? i just saved my project so don’t ask me again.
I’ve only experienced this with some Native Instruments plug-ins so far. Maybe if you could try to find out which plug-in is responsible, it’ll make it easier to ‘fix’ the problem.
Here’s a quote from Frits regarding this (from an older topic):
@Zynewave wrote:
When exiting, Podium requests the preset data from plugins, and if the data is different from the last saved data, it asks to save. Some plugins return different data every time it is requested. That can be because they put a time stamp in the data, or som other forms of counters/randomness related to copy protection.
3. why can’t the project window be extended to show some empty space in the timeline automatically. why do i have to resize things manually or be grabbing at the edge of the screen to insert or duplicate clips?
Not sure I understand correctly… :-k You can always zoom out as far as you’d like to show empty room on the timeline, but maybe this is what you mean by resizing things manually.
thcilnnahojFor now I think I’ll stay with the smallest button size on the desktop PC. I’ll check it out more thoroughly once I get to my laptop…
– It seems Podium only really uses the font name (like it says) from the standard font selection dialog that opens… It would be nice if at least the minimum size to use could be specified as well, especially if the user sets font scaling to 0%.
– The +/- icon replacement looks out of place to me, and even more so in combination with the “tree” lines and slightly oldschool folder icons. But I don’t know what else you might have planned to change. 😉
– It seems you slightly decreased the size of the S on solo buttons, and the letters on small selectors (BEX) while redrawing them…? Makes the E in particular a little fuzzy, compared to previous versions.
– Love the new pin icon, tabs, inspector panel and editor/mixer headers. I could list a few more places that would look nice with a soft gradient like that. 😉
Also, as you know from my constant complaining about this (:blush:), most icons become invisible if you use both bright text and bright selection colors (or both dark). As you’re working on them now, maybe it’s the right time to take care of this.
thcilnnahojI also need to bump this:
Hey, I just noticed that duplicating stuff with the Insert key now stops adding new copies as soon as you hit an already existing event.
It previously continued to insert notes/sequences past already existing ones, and even filled in gaps between events, even it that meant the inserted one was cut short. I really, really liked the way this worked…
The removal of this function has slowed me down quite a bit during working with quantized material… I can see it could cause problems now, when you duplicate many events at once, but it was always so useful for single ones. Pretty please? O:)
thcilnnahojThings I noticed in the last few days:
– Mono and multichannel side-chain mappings (or multi-mappings in general) seem to share instance numbers. Ex.: If there are both a mono SC #1 and a stereo SC #1, creating a new instance of stereo SC #1 names it stereo SC #3. Of course this only applies if the mappings were created from the same DLL.
– Making a selection by Shift+clicking in the curve and sound editor doesn’t override snap like expected (by me, at least :wink:). If you hold Shift and then click somewhere, it still snaps the start/end of the selection to the grid. This works differently in the arrangement and note editors, where the selection begins exactly at the clicked position instead of snapping.
– Shouldn’t the new project page/panel be able to have key focus? I was stumped after hitting enter to confirm the project name, the ‘create’ button pulsated and invited me to press it, but hitting enter again tried to open a project from the recent projects list instead.
– When you move a fader and set it back to the original value in one action (not by right-click cancelling), it still creates an undo point, which is kind of a waste…?
– I’ve had the f&%#ing (excuse me) overload problem happen again – with just one fade!!! And it seems it was dependent on the fade shape this time… Not only does this block the entire project sound, it also makes your computer slow to a crawl, and you can only hope you’re still able to deactivate arrangement power before something blows up… 🙁
thcilnnahojHello and welcome!
@Infinitoar wrote:
-Have and option to where pics used in the project window and track background can be “centered”, “stretched”, and/or “tiled”.
Sounds good. Though I only rarely use images, I’d also appreciate it if we could set one per arrangement, as opposed to one per project.
-Export to MP3 option. With of course more options such as Bitrate and others**Paid version only**
Hmm, I don’t think this is something that should warrant an “upgrade” to the full version, as the tools to convert to mp3 are all available for free. Because of this, it should also be relatively easy to implement a front-end for the LAME encoder in Podium. But as Frits recently said, there are oh-so-many small and easy things on the to-do list… 😉
The same unfortunately goes for a backup save option, among other things. They’ll show up with time… we’ll just have to be patient (or millionaires who can sponsor Zynewave).
You’ve probably already noticed the videos that were made by fellow Podium users LiquidProject and myself. Do you perhaps have an idea of what you’d like to see a video about?
As for problems with CPU use – it’d be nice if you could say which type of soundcard/audio interface you’re using, which sort of drivers, and roughly how many VST plug-ins – there’s only so much a PC can take. 😉
Also, even if you get noises during playback, they will not be in the final render (use Export to Sound File from the File menu). If the noise is still present when you play the rendered file, please let us know, and we’ll try to investigate further!
thcilnnahojI agree, it would be nice to resize the editors separately, though that would probably require some tedious rewriting. 🙁
It would also be a problem when you use the “shared timeline” profile for an editor (you can find it in the view menu). That certainly has its uses still.
Regarding the numbers… I haven’t seen the show, unfortunately (shame), but how about this as an answer: “The owls are not what they seem.” 😉
thcilnnahojWhoops… it’s been nearly two weeks now, sorry!
I read it again and actually think there’s no need for the sentence.
It’s hard to describe the hierarchy in simple words without starting to explain about group tracks and stuff, which this section already does anyway. 😉
So I’ve updated the tracks chapter without it. Of course you can add a new opening sentence if you like, but as I say, it’s not really needed, and your time is surely better spent on other things!
thcilnnahojHmm, are you using it as a mono or stereo mapping? It seems the mono mapping is created by Podium unknowingly, since it doesn’t behave as expected… I don’t see a problem with the stereo mapping so far.