ZynewaveThis has been requested before, so today I spent a few hours implementing it. The release note for 2.08 will show:
Added possibility to override the default Podium brushed metal texture. The preferences dialog has a setting for “panel texture image file” and an option for dyeing the image to match the panel color of the current color scheme.
Zynewave@ronin wrote:
I’m sorry but a new bug has crossed my desk 🙂 Maybe you are already aware of this.
The take list (of a comp event) grows with every comp event. This means:
– the first loop had 3 takes -> comp list shows these 3 takes
– the second loop had 5 takes -> comp list shows all 8 takes
…This was pretty confusing because firstly I didn’t saw where these mis-takes are coming from 🙂
I also discovered this bug shortly after I released the beta5. This is now fixed in beta6, which also has this unrelated new feature:
Added possibility to override the default Podium brushed metal texture. The preferences dialog has a setting for “panel texture image file” and an option for dyeing the image to match the panel color of the current color scheme.
The next beta will probably show 2009 in the about box, so until then, happy new year 🙂
Zynewave@Conquistador wrote:
I am sure First has a development schedule (for new features) and wants to focus on that but…this bug is not minor IMO.
This is not a bug. I designed it to work this way, and it has worked this way since the first Podium release. I have acknowledged that the majority of users find this automation behaviour undesirable, and I will look at an alternative solution in a future update to the automation system.
Zynewave@ronin wrote:
I’ve found a small bug in 2.08beta4:
If “deactivate record mode if playback is stopped” is enabled a loop recording (comp track) gets disabled after the first take if the loop is at the end of the arrangement. This problem is independant from the setting “stop playback @ end of arrangement”.
Can someone confirm this?
Thanks. Fixed in beta5.
By the way: I think if there is no arrangement (its empty) playback should never stop with “stop playback @ end of arrangement” enabled. (It would be consistent if it never starts but there is no use case where this could be a desired behaviour 🙂 )
Is the problem that it is confusing that playback won’t start if you try to start an empty arrangement?
Zynewave@ronin wrote:
Hmm this leads to a problem with my use of comp tracks and the “delete oldest take” feature. I’d like to have a track called guitar. this track contains all e.g. clean guitar stuff and I’d like to do a multiple take record for every part of the song. As seen in the screenshot the “delete old take” feature may, while recording the right comp event, delete the first take track which contains a needed part (left side in screenshot) if the take maximum is reached. Is it possible to define this maximum as local maximum? 🙂 If the current loop has only 3 takes (whereas another comp event in the comp track has 5 and maximum is 5) then I should be able to do 2 more takes. Take deletion should then be done loop-based and not track based.
Thanks for the input. I’ve made the loop-recording more intelligent in the new beta5:
You can now start recording beyond your last looped multi-takes, and Podium will reuse the existing take tracks instead of creating new take tracks. The “delete oldest” option will also no longer delete the first track but instead try to rotate the events on the take tracks. Thus you can loop-record with the delete oldest option without affecting takes recorded prior to the loop start.
ZynewaveZynewave@ronin wrote:
1. Is the LAST n takes feature rejected? I think its highly useful.
Nope. See the beta4 release notes.
2. Uncomplete takes are not detected. I gues this has reasons but it could be useful.
Only takes covering the full range of the comp event is included in the comp event take menu. I’ll consider changing this so that take events that stops before the comp event end, are also included.
3. Is it possible to get full multiple comp events per track? Let me explain this with a small example picture.
…
the first event has two takes and the second three takes. After that I can’t record anything. It would be nice to have 5 takes per loop.
A new take track will always be created when recording a new take. If you are running out of space as on your screenshot, you can manually move the second group of take events up on the first take tracks, and then delete the now empty bottom take tracks.
4. Another note for consistency. Personally I think moving(cutting) the comp event should move(cut) the take events. Currently it could easily lead to mistakes. This note leads to the highly appreciated group editing (like fading multiple events) 🙂
I know there are some hosts that implements multi-take this way, but I also read discussion on the net where people complained about this. They argued that they would like to be able to edit the take events as regular events and then promote these edited events to the comp track. I’m going to add some commands for this later on.
Thanks again for your really nice podium! I wish anyone who celebrates it a very nice x-mas 🙂
Thanks. I’m going away for the holidays until the 26th, so merry christmas everyone! 🙂
Zynewave@pavouk100 wrote:
I haven’t chance to try with audio tracks, but I tried compositing track feature on MIDI track and failed like this:
1. Recording on MIDI track with loop activated does not put the track into composite mode.
2. When setting the MIDI track manually into composite mode, recording on it does not create ‘take’ subtracks, instead new recording is merged into already existing single lane (i.e. the same behaviour as pre-2.08 versions).
3. When done, the recorded event has the bar on the bottom (the one used to choose proper part of the takes), although it is useless – there is always only one event to choose.Am I doing something wrong, or is MIDI comping not working yet?
Pavel
MIDI loop recording is not yet implemented. I intend to wait until 2.09 with this. You can still manually add take tracks to a composite MIDI track, but I’ll remove the comment about MIDI comping from the release notes to avoid the confusion.
ZynewaveSome plugins may occasionally perform some heavy computation which is not part of the normal processing (if you e.g. automate parameters which require further recalculations in the DSP algorithm). If this heavy computation has a duration of e.g. 3 milliseconds, then this will cause a spike at ~50% if the ASIO buffer size is 6 milliseconds. The same computation will only cause a spike at ~10% if the buffer size is 30 milliseconds. Etc.
Zynewave@ronin wrote:
I have small wish: could we have an option that enables the comp track to keep the last N takes? Lets say I’d like to keep 5 takes. Currently the recording is “stopped” after 5 takes. Is it possible to change this behaviour so that while recording continues old takes are removed and always the last 5 are kept? this would be very useful for me.
Try the latest beta4, which has these new features:
Reorganized the settings in the preferences dialog into new pages: Projects, Engine, Play/Record, Metronome, Plugins, Application.
Added new settings to the Play/Record page in the preferences dialog:
“Stop playback when end of sound/arrangement is reached”,
“Deactivate record mode when playback is stopped”,
“Convert record enabled tracks to composite/multi-take groups”,
“Delete oldest take when loop-recording maximum is reached”.
Btw. When you say recording is stopped after 5 takes, then this must be because you have set the loop-recording maximum to 5 in the preferences dialog.
ZynewaveThis is best solved with MIDI plugins. I’m even considering removing the two randomize settings once MIDI plugin support is there. If you move these settings to a MIDI plugin, then you get the added bonus of being able to automate the parameters.
ZynewaveBeta3 is available, with a bug-fix, and this change:
New sequence/sound events will be created if recording is started beyond the end of the current events on the track. Previously Podium would extend any existing events on the tracks.
ZynewaveWell, better late than never 😳
As part of the new composite track feature, I’ve finally made the change discussed in this topic. Available in the upcoming 2.08 release.
ZynewaveHi John,
@Rottweiler wrote:
Is the different tools are there to simplify the anyway more complex/fieture rich environment? With xt i dont need to use anything like that, so its a bit unusual for me.
All of the functionality of the different tools can be accessed with just the select tool and by using key shortcuts and popup menus. So if you prefer to work in a “toolless” environment, you can ignore the tools or remove them completely from the toolbar in the editor profile setup dialogs.
Frits
ZynewaveHi,
There is no special upgrade available for users of the CM 1.77 version. If you want to get the full version of Podium (including future updates), you’ll have to buy a license at US$ 90.
Frits