@4mica wrote:
Sounds good now…is the midi quantize feature still going to be implemented?
The midi grooves, as discussed in the 2.41 preview topic, has not been implemented yet. It still is my intention to implement it at some point. I got sidetracked with other non-Zynewave stuff the last couple of months, and only recently started to work on Podium again. The first few releases will be about minor features and bug-fixes.
@thcilnnahoj wrote:
Something problematic I noticed:
When you move a sequence (just keep it ‘floating’ a second or two by not releasing the mouse button) in the arrangement editor while recording/real-time bounce recording something, playback is interrupted until you drop the sequence or cancel moving it. 🙁
Thanks. Fixed.
@thcilnnahoj wrote:
@Zynewave wrote:
Btw. there is no concept of an “active” zoom snapshot. The zoom snapshot buttons will light up (appear selected) if the current zoom settings matches those stored for the snapshot. So, if a snapshot is set to only affect track height zooming, then it will light up if that matches, ignoring the status of the other three zoom settings. That way there can be multiple snapshot buttons that appear selected.
Yeah, you’re right on that. What I meant was that you couldn’t, for example, activate a snapshot that zooms in on bars 26-30, and then use another snapshot to zoom in vertically. These would have to be combined into one snapshot currently – not that this is a problem!
Correct, you can’t do that currently. But you will be able to do just that, with the changes I suggested in this topic. This is a simple thing to implement, doable within a days work. So is it worth the effort to implement this?
@thcilnnahoj wrote:
I don’t think two options are enough, though, if Trancit wants to only store the zoom level without song position. Likewise, I’d probably make a snapshot for editing that zoomed in vertically, but without binding it to a specific track (would this reset the view to the top, by the way?).
Ok, I’ll add an option for each of the four settings then.
A snapshot that only changes the track height zoom will not change the top offset. If you want it to reset to the top, you could create the snapshot when it was at the top, and then enable both the track offset and track zoom options on the snapshot.
The other suggestion, I think it was made by CQSD originally, was to make another feature for vertical zoom level recall (like “track height presets” in Studio One). This way you could combine separate your self-made zoom presets for the X and Y axis. Since you can only have one active snapshot, this isn’t possible at the moment. Honestly, though, I don’t know if this would be useful or just make it more confusing.
I don’t like the idea of introducing another type of zoom preset dedicated to track offset/height. It can be handled just as well by the current snapshot feature. Btw. there is no concept of an “active” zoom snapshot. The zoom snapshot buttons will light up (appear selected) if the current zoom settings matches those stored for the snapshot. So, if a snapshot is set to only affect track height zooming, then it will light up if that matches, ignoring the status of the other three zoom settings. That way there can be multiple snapshot buttons that appear selected.
Thanks for the feedback.
Edit: It probably is a good idea to add a fifth “First snapshot in a group” option on each snapshot. This will enable you to separate the snapshots into separate groups for e.g. timeline and track zooming. Sort of like it is done with the grouping of track tags.
The last competition did not result in many responses, so I’m thinking that people perhaps are not interested in this type of competition.
Do you have a suggestion for a new competition topic?
The shop is now online again. All users with an expiring upgrade period should have received an email today, with a discounted offer for extension.
@Trancit wrote:
Would it be possible to include such an option in a rightclick context menu??
Rightclick a snapshot button to bring it up???
That is what I suggested. There already is a right-click menu for the snapshot buttons. The new options should just be added to this menu. Or are you talking about a different menu?
Difficult to please both of you, without implementing this as some sort of option 😉
There are four settings stored for each snapshot: Timeline start, timeline size, track top offset and track height zoom percentage.
I could add options for these four settings in the snapshot button right-click menu. So each snapshot can be configured differently, meaning you could use some snapshots to position the timeline, and others to adjust zoom range, etc.
By default all four options would be enabled for new snapshots, so you would need to adjust the options for each snapshot, if you want them to affect only part of the zoom settings.
Is that the way to go? Should all four settings be available as individual options in the menu, or should it be reduced to two options, labeled “Horizontal timeline range” and “Vertical track range”?
@throbert wrote:
Zyne, How goes it on the 64 bit front. Have you been able to aquire a 64bit pc yet, any further dvelopment or fixes to speake of.
throbert
Sorry, no news on the 64-bit front. I’m still using my old Vista 32-bit PC.
@chase wrote:
I take it you are are the Programmer – Developer of Podium?
Yes. I am the only person behind Zynewave.
What would you like to see happen with Podium?
Were do you see Podium in say 5yrs?Do you think you’l be taking it to a higher or the next level?
– staffing more people to handle the business side of things.
or help with programing etc etcDo you see Podium growing as a company business and software is what I’m asking i guess.
or will Podium slowly stagnate or turn into more of a programmers hobby kinda thing?
Podium has always been a hobby of mine. The last 5 years I’ve been fortunate to be able to work full-time on Podium. I’m not making enough money from Podium sales to continue with it full-time though. In the future I will need to find a more dependable source of income, which inevitably means I will get less hours per week for Podium development. That means returning to the way I developed Podium for the first 15 years of its existance. So I see myself continuing with Podium development in-definitely.
I gather from the different questions you’ve been asking, in other topics as well, that you are requiring a lot of specific features within surround-sound processing, etc. You should perhaps be looking at products such as Nuendo, or some of the other big players that has a wider range of features than Podium currently offers.
1/ You can set up a bus return mapping that extracts a single mono channel from a bus that is being fed with a surround bus send mapping.
2/ You can’t. You’ll need to find a surround tool plugin that can handle individual channel gain, pan, mute and solo. I’m not familiar with the available surround plugins. I’ll probably develop such a plugin in a distant future.
3/ Panning is only available on tracks that are feeding into a parent stereo track.
4/ You can’t. If you undock the master section in the mixer region properties, the master track will zoom like regular tracks.
5/ Yes. Same principle as mentioned in question 1.
6/ You’ll need to set the gain fader to after the send mapping. Turning the gain down will then not affect the send level.
The feature limitations in Podium Free are only those that are mentioned on the download page. In other words, the features covered in your questions 2..5 are not restricted in Podium Free.
1/ Yes, wav & aif.
2/ Yes.
3/ Very.
4/ It cannot be adjusted.
5/ Unlimited.
About the Reason/rewire question: I am not particularly familiar with Reason, so perhaps other users that are using Reason will chime in with some comments on that.
@thcilnnahoj wrote:
Say I have a limiter plug-in that has a dither algorithm built in, and I want to make use of it directly inside Podium. Please help me see through this confusing stuff! 😉
Let’s say I set this very last plug-in in the chain to output 16-bit (dithered). Podium will still render a 32-bit file (or even 64) from this, right? Does this simply leave the other bits unused, or what happens here?
The float values should ideally be value-quantized by the dithering plugin so that a later conversion to 16 bit integer values (by Podium) just removes/truncates unused bits. It’s important to not apply any processing or gain-scaling after the dithering plugin.
If I would then use the export file dialog to create a 16-bit file from the master bounce render, won’t this essentially do the bit conversion twice – the second time just by truncating…?
You can open the sound properties for the master bounce file, and change it from floating point to 16-bit integer. That way it is not needed to do the bit conversion when you later export the arrangement as a wav file. But it is ok to just leave the master bounce as a float file.
Is there even a way to do this right currently?
Once Podium supports dithering natively, it will be an option in the export dialog. It will probably also be a global option for the audio interface, so that dithering is automatically applied each time Podium outputs audio to the audio interface, ensuring that realtime monitoring also is dithered. Of course, if you are using a dither plugin as the final step in the master chain, you should then not enable the native Podium dithering.
Just to be sure: When you say the visuals are late compared to the audio output, do you mean the position of the play cursor as it moves across the waveforms on the tracks?
Is it a constant delay, or does the delay increase as playback progresses?
Please check that the samplerate in the arrangement properties dialog is set to 48000. Changing the default samplerate in the interfaces dialog will not affect the samplerate setting in arrangements that are already created.