H-man.
ronin@Zynewave wrote:
@ronin wrote:
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?
Yes. I’m aware of this option so its not really confusing to me but a new user might stumble accross this.
roninI’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 🙂
The “rotating takes” work really nice!
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 🙂
Mike GHi,
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!)
Background and further suggestions:
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?
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!
Thanks,
Mike G
ZynewaveBeta7:
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.
Zynewave@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.
ConquistadorThe current features recently added are pretty slick. My pick of the bunch would be the ease with which you can cycle through takes with the bar at the bottom of a sound event. Very easy. 🙂
However I think another extremely useful addition to managing and selecting takes is not there yet.
Wave form Peak Display.
In Sound Forge for instance you can set a user defined threshold at which peaks can be detected in an audio file.
When one is cycling through takes it will be much easier to choose a take if you can also see a db marker placed on the file that shows the db value of on audio file at the exact point of a peak.
If I am choosing a take in a recording some might be louder than others or too loud. If I could see where the peaks are (as a marker with a db value) it will make the process of choosing a take much faster and easier without having to bring up the mixer to see the peaks.
Of course such a feature would be extremely useful during the mixing process as well. Podium can show peaks in an audio file (with the mixer)and very useful it most certainly is but when cycling through takes I want full screen real estate which means…no mixer.
Peak information remains very useful and I really think it should be added to any recorded sound event in Podium in the form of markers placed on an audio file. Soundforge, Sonar and I think Samplitude have something similar.
Being able to see a Wave Form Peak display marker also has many corrective uses when editing audio in general. It is not a multi faceted or featured addition to take comping but it will speed up the process of managing takes and the uses for Wave form Peak display markers go far beyond take management.
Only one single marker needs to be displayed on a sound event. That will show the highest peak in the file. As in Soundforge a user defined threshold for detecting peaks could be offerred for more flexibility. The marker could be red when above a user defined threshold and green when below it.
Even without a user threshold setting a default peak detection value that matches the mixer peak values could be used instead.
Zynewave@Conquistador wrote:
Wave form Peak Display.
As I understand it, this is not something that influences how comping should work, so I would prefer we discuss this another time. I’ve got plenty to do just implementing the composite track feature for this release.
Conquistador@Zynewave wrote:
@Conquistador wrote:
Wave form Peak Display.
As I understand it, this is not something that influences how comping should work, so I would prefer we discuss this another time. I’ve got plenty to do just implementing the composite track feature for this release.
Depends how you work IMO. It is more to do with making the process of managing takes easier. But yes no problem…a discussion about it at some other time is fine. 🙂
Mike GWhy do you have punch-out enabled if you don’t want the recording to punch out?
For example you only want to try recording the first part of a loop without overwriting the 2nd part of the loop that you are alrady happy with. (1 bar) but the whole loop lasts 2 bars and you want to get the ryhthm, feel of the loop.
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”?
Try this… Set up a loop start/end. and then arm a new track for recording, starting recording from a few seconds before the start of the loop.
The purpose of this space before the loop is so in the first take you get a chance to count in, get your voice in tune with other notes etc.
The composite track (the bit with the right-click drop down list) and the first take start from the place I placed the play cursor to start recording. It took me a good while before I realised why I couldn’t make use of any of the other takes. The other takes are all shorter in length that the main compsite track length.
Zynewave@Mike G wrote:
Why do you have punch-out enabled if you don’t want the recording to punch out?
For example you only want to try recording the first part of a loop without overwriting the 2nd part of the loop that you are alrady happy with. (1 bar) but the whole loop lasts 2 bars and you want to get the ryhthm, feel of the loop.
After giving this some thought: Now that we have the “deactivate record mode when playback is stopped” option, it is no longer essential that punch-out disables record mode. It will thus be possible to keep loop-recording with punch-out inside the loop. It will also eliminate the confusion you had with why punch-out disables record mode when punch-in does not enable it. Anyone else have arguments against removing the record-disabling feature of punch-out?
Try this… Set up a loop start/end. and then arm a new track for recording, starting recording from a few seconds before the start of the loop.
The purpose of this space before the loop is so in the first take you get a chance to count in, get your voice in tune with other notes etc.
The composite track (the bit with the right-click drop down list) and the first take start from the place I placed the play cursor to start recording. It took me a good while before I realised why I couldn’t make use of any of the other takes. The other takes are all shorter in length that the main compsite track length.
Would it not work as you intended if you set the punch-in at the loop start? That should ensure the comp event is only created at the loop start.
Conquistador@Zynewave wrote:
After giving this some thought: Now that we have the “deactivate record mode when playback is stopped” option, it is no longer essential that punch-out disables record mode. It will thus be possible to keep loop-recording with punch-out inside the loop. It will also eliminate the confusion you had with why punch-out disables record mode when punch-in does not enable it. Anyone else have arguments against removing the record-disabling feature of punch-out?
The added flexibility is very welcome I must say. However Punch out disabling recording is still useful outside of loop recording. I would definitely want to keep it ❗
I think a global option should easily let a user set and forget the feature one way or another.
Zynewave@Conquistador wrote:
@Zynewave wrote:
After giving this some thought: Now that we have the “deactivate record mode when playback is stopped” option, it is no longer essential that punch-out disables record mode. It will thus be possible to keep loop-recording with punch-out inside the loop. It will also eliminate the confusion you had with why punch-out disables record mode when punch-in does not enable it. Anyone else have arguments against removing the record-disabling feature of punch-out?
The added flexibility is very welcome I must say. However Punch out disabling recording is still useful outside of loop recording. I would definitely want to keep it ❗
I think a global option should easily let a user set and forget the feature one way or another.
The punch out still disables recording of MIDI and audio beyond the punch-out position, no matter if looping is enabled or not. The only change is that the record button on the transport toolbar is not deselected once the punch-out position is reached. That is done with the new “deactivate record mode when playback is stopped” option. Please explain why you still want punch-out to deactivate recording?
Conquistador@Zynewave wrote:
The punch out still disables recording of MIDI and audio beyond the punch-out position, no matter if looping is enabled or not.
Ok I thought that behaviour was already / was going to be changed. Thats 100% fine then. 🙂
The only change is that the record button on the transport toolbar is not deselected once the punch-out position is reached. That is done with the new “deactivate record mode when playback is stopped” option.
Strangely enough that all sounds fine. Now that you explained it a bit more…its fine. Totally.
Please explain why you still want punch-out to deactivate recording?
Your last post clarified this for me so effectively punch out…
“still disables recording of MIDI and audio beyond the punch-out position, no matter if looping is enabled or not.”
…so its not a problem.
I will ask though why would one want to keep the record button enabled if punch out has disabled recording of midi and/or audio events…would that not confuse if the record button remains active? If you cannot record midi or audio why keep the button active? ❓ ❓ ❓
Ignore that, I found the answer…
“It will thus be possible to keep loop-recording with punch-out inside the loop.”
Heh… 😛
ZynewaveBeta8:
Using punch-out during recording will no longer deactivate recording mode. This allows punch-out to be used within a loop during multi-take recording.
Fix: The track solo changes introduced in 2.06 had the effect that bouncing the master would not produce sound if Automatic Solo was enabled on the bus returns.
Plus various fixes to the multi-take recording.