Zynewave@druid wrote:
Is there any reason you thought a group should become a bus return group if a bus return track was inside?
The group track will only be marked (internally) as a bus return group/section, if it is the only group that has bus return tracks child tracks. Podium uses this to include the group track in the docked bus return section in the mixer, if you have enabled the docked bus option in the mixer region properties.
Zynewave@batman42ca wrote:
On the Podium page that shows “Contents – Arrangements, Sounds ” and “Devices – I/O Busses, Plugins” menu bars, I used to have a menu option under “Devices – I/O Busses, Plugins” for “Import Plugin“.
What could I possibly have done to make that menu option disappear?
I’m using Podium Free – version 2.37.
Weird. Please provide more details of what commands you do see in the menu.
Zynewave@levendis wrote:
Say you have a set of tracks (possibly of different groups) soloed. The Global Solo button will light up and when clicked will un-solo those tracks.
What I’d like is to then be able to click the Global Solo button again and have the previous track solo states invoked.
Auditioning recent edits could then be A/B’d between the output of all tracks (bar those muted) and a selected sub-group.
I think you can achieve what you want, by using the undo/redo commands to A/B the solo mode changes.
Zynewave@4mica wrote:
So, Frits, you have a new computer now? Congratulations if you do…
I don’t have a new computer yet. Still no ETA of a 64-bit Podium build.
Zynewave@druid wrote:
Frits, is this intentional, or an oversight? I don’t really want midi going to my group track for analysis, just want audio to run through it, almost for it to be invisble.
Input selectors are removed from all tracks in the bus return section. When you move a bus return track into a group track, this group track becomes the bus return section (which can be shown docked in the mixer). This was done as I thought it would be confusing to be able to assign inputs in the bus return section. So it is intentional, but I’ll consider removing the auto-hide of the input selector.
Zynewave@ronin wrote:
There was a problem a few versions ago which prevented fast shutdown of Podium. Security tools like virus scanners caused a massive delay while writing the configuration file. This has been fixed a few versions ago and that fix should already be in Podium free too.
This was fixed in 2.38, so it will appear in the next Podium Free release.
ZynewaveI’ve removed the spam links from the post, and locked the account.
Zynewave@throbert wrote:
good to hear of the possibility, Zyne. Do you have an ideal if there will be an xp64 bit version or is way too early to tell
It should work on XP64, but I will only be testing it on W7 64.
Zynewave@MelodyMan wrote:
Bump for this problem. It’s still one of the things that annoys me the most in Podium. In Tracktion for instance, disabling the plugins is enough to not make them cause a delay anymore. In Podium i have to remove them from the track entirely, which is a pain.
The effect bypass button is “softer” than a plugin disable button. One purpose of the bypass button is to A/B the dry signal with the wet signal. For that purpose it is necessary to delay the dry bypassed signal with the same latency as the plugin, or else the dry/wet audio would shift in time.
Also why can’t one save an effect-chain on the Master-track?
I may add support for this later on. I haven’t implemented it yet, because I need to add code that filters out the audio output from the chain.
ZynewaveHi,
I’m currently changing my VAT registration, so I unfortunately have to take the shop offline for the time being.
Frits
ZynewaveThere’s no enough memory to load the selected sound font
That message is not generated by Podium. It must be sfz+ that displays it. Perhaps you could try to clear and then reselect the soundfont, after sfz+ has displayed the error message.
ZynewaveHi Mike,
Very nice. I’m going to add those as favorites on my YouTube channel.
About tutorial 1:
The ~5 second delay you experience before the plugin scan dialog appears, after clicking the “create project” button, was caused by the old method I used to write the Podium.ini file. This was changed in Podium 2.38, so the next Podium Free release should no longer show this delay.
About tutorial 3:
Instead of 1/create track, 2/drag instrument from list onto track, you can have the track automatically created by dragging the instrument onto the blank area below the last track.
Zynewave@thcilnnahoj wrote:
@Zynewave wrote:
@LiquidProj3ct wrote:
Making the groove templates assignable to sequence events rather than tracks, makes it possible to assign different grooves along the timeline.
Could be possible have a track groove overwritted in real time with by secuences groove?
I’ll consider that. If a groove template is assigned to a sequence event, it would override any groove template assigned to the track.
I suppose a groove assigned to a track should be inherited by child tracks, agreed? This means that any parameter tracks will also be affected by the groove template on the parent track. This may not always be desirable, if you for example are using level automation to gate the audio synced to other tracks. So, perhaps the groove selector on the track should include the options “None”, “Use groove from parent track”, followed by the list of defined groove template sequences.
This sounds like a very good plan to me! 8)
I think this solution would make it redundant, or at least reduce the need for a dedicated “destructive” input quantization. You would just assign a straight 16th note groove to a drum sequence you are recording, and your recorded notes will automatically play quantized on the next loop. Once you are done with the layering of drum notes, you could apply the quantize edit command, to tidy up the sequence.
Comments, suggestions?
Wouldn’t that mean that you have to create a sequence before recording, or pause inputting notes after the first loop to set up a groove template for the sequence to have it auto-quantized? I don’t know how you do it, but I personally don’t create any sequences by hand when recording.
I guess this wouldn’t be an issue if there was a track-wide groove template as well, as suggested above.
It would require a pre-created sequence event before a groove template can be assigned to it, so that is one reason why being able to assign groove templates to tracks is a good idea.
Zynewave@LiquidProj3ct wrote:
Making the groove templates assignable to sequence events rather than tracks, makes it possible to assign different grooves along the timeline.
Could be possible have a track groove overwritted in real time with by secuences groove?
I’ll consider that. If a groove template is assigned to a sequence event, it would override any groove template assigned to the track.
I suppose a groove assigned to a track should be inherited by child tracks, agreed? This means that any parameter tracks will also be affected by the groove template on the parent track. This may not always be desirable, if you for example are using level automation to gate the audio synced to other tracks. So, perhaps the groove selector on the track should include the options “None”, “Use groove from parent track”, followed by the list of defined groove template sequences.
ZynewaveI’ve grabbed the link, for later research. Thanks.