Zynewave's Forum Page

@Mike G wrote:

I set up a loop on a composite track and then set record punch-in and punch-out at the same length as loop.
When reaching the end of the first take, podium switched off recording.
It works OK if you just use punch-in and not punch out but I think it would be more intuitive for punch out not to permanently turn off recording when in a loop.
In fact now I come to think about it, why does punch-out turn off the recording button in general (especially when punch-in doesn’t enable record!)

Why do you have punch-out enabled if you don’t want the recording to punch out? The behaviour of punch-out in the scenario you describe seems ok to me. Maybe I would want to record just one loop-pass and then keep the loop running with playback of the take I just recorded.

Was using punch in to get around the fact that I have to cut the start of the loop with the scalpel tool in order to be able to select other takes. As a further suggestion would it be possible to do the scalpel cut at the start of the composite track by default?

I don’t understand this fully. Is it because you have recorded takes that starts beyond the start of the comp event? What do you mean with “the start of the composite track”?

Also would like takes to be named “Take 1”, “Take 2” (Or a,b,c) etc. when picking them in the drop down list on the composite track i would find that easier to remember which take was which as opposed to timestamp. (Maybe have timestamp as well)
If this corresponded with name of track that would be even better.

BTW: Enjoying trying out new comping support, thanks fritz!

The timestamp naming is now optional in beta7. Thanks for the input.

Beta7:

There’s a new “Use timestamp as name for new take events” option in preferences. Disabling this option will then not set the name of the events, but instead use the name of the sound objects. The naming of the sounds on take tracks is now using a more sensible format such as: “Track 1: Take 1”.

Furthermore the following feature is added, which shows my original intention with the timestamped take events:

Setting a take on a composite event will set takes with similar names on all selected composite events. This is mostly useful if the “use timestamp as name for new take events” option is enabled and you are recording from multiple audio inputs. All takes recorded at a given time can thus easily be selected across all composite tracks.

And finally:

Added more detail to the “save changes” message box that appears when loading a new project or exiting Podium.

@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 🙂

@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?

@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.

@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.

Beta3 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.