H-man.
pavouk100@Zynewave wrote:
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.
Works fine now. Thanks!
ZynewaveBeta9 is up. This is hopefully the final beta. I would appreciate if some of you could try it out and report if everything is ok.
Among a few bug-fixes to the multi-take feature, there is this additional bug-fix:
Fix: Bypassing a mono device chained after a stereo device would only produce output in the left channel.
H-manHi all,
I just thought that I would chime in and report that I am very happy with the 2.08 new features and fixes.
Better that anything is that testing the Comping features has got me to back playing my Guitars and not just twiddling dials and piling effects 😆 .
Most important for me is that 2.08 has got to the point where there is quite a lot of flexibilty in how one can set up the recording (auto comp activate etc.) and the resulting changes to the Punch-in/out make perfect sense IMHO.
Note that whilst possibly a little antiquated, I think that the existing Punch-in/out is a feature worth retaining in its current state.
One thing that I like (pre-existing feature I think) in Podium is the way gain, stretch and now track-swiching controls on the events become active on ‘mouse over’ which makes the Comping process all that much easier and faster.
The only aspect of the new features that I had found a little confusing (Thx for raising Mike) was that the Comp Track event (first one) would commence from the cursor position and not the first loop marker, requiring the user to have to slice the Comp track at the first loop marker to get access to the other (sub) tracks.
Maybe the Comp track event could be set to auto-slice at this point? I get it that this can be remedied using the punch-in marker however I feel that new users will find this confusing and ‘eat’ the half-hour or so that I did until I figured it out.
Just a thought. Other that that I am really pleased with the addtions.
Brilliant as always Frits!
Ben
PS: Possible bug? I found at one stage that I lost the ability to delete events on a track with the ‘delete’ key when there were a large number (40+) of copied or cloned events. Right click – delete would still work tho.
Zynewave@H-man wrote:
Better that anything is that testing the Comping features has got me to back playing my Guitars and not just twiddling dials and piling effects 😆 .
Fantastic 🙂
The only aspect of the new features that I had found a little confusing (Thx for raising Mike) was that the Comp Track event (first one) would commence from the cursor position and not the first loop marker, requiring the user to have to slice the Comp track at the first loop marker to get access to the other (sub) tracks.
Maybe the Comp track event could be set to auto-slice at this point? I get it that this can be remedied using the punch-in marker however I feel that new users will find this confusing and ‘eat’ the half-hour or so that I did until I figured it out.
I’ve changed it so that the comp event will be split at the loop start, not during the first take, but when the recording loops back.
PS: Possible bug? I found at one stage that I lost the ability to delete events on a track with the ‘delete’ key when there were a large number (40+) of copied or cloned events. Right click – delete would still work tho.
Hmm, the number of events should not matter. Are you sure that the tracks region had keyboard focus?
H-man@Zynewave wrote:
PS: Possible bug? I found at one stage that I lost the ability to delete events on a track with the ‘delete’ key when there were a large number (40+) of copied or cloned events. Right click – delete would still work tho.
Hmm, the number of events should not matter. Are you sure that the tracks region had keyboard focus?
Possibly not. I will try to see in the next day or so whether I can recreate the problem and if so, provide the specific environment in which it happens.
Mike GIdea for slight mod in future:
Could it be possible to right click the take track and select it as the active take (might be more intuitive for beginners) that clicking in the main compiste track’s bar (Which is Invisible till you hover over it with mouse!)
I know it might be ambiguous which part of the take you wanted to use so not sure about this.
Thanks,
Mike G
Mike GBug report for multitake.
Used 2.08 and 2.09 beta7 both have this issue:
NOTE: For newly created project it works fine. This only doesn’t work for projects created from my project template. I have reloaded default setup and still doesn’t work for any project I create from my template.
Set preferences to:
max takes =3
delete oldest takes=True
Use timestamp as name=False
1 – When record a comp track for 1st time it will not auto delete the 1st recorded take, just keeps overwriting the 2nd and 3rd takes.
2 – When start again recording (when have all 3 takes already filled up),
will then delete 1st take but will only create 1 new take after that.
3 – Not sure if this is a bug or “feature”… When have existing takes recorded and then start to record a new take, the new take is not auto selected as the active take in the main comp track. Is this just so you don’t overwrite any existing “comping” cross fades that you’ve been doing etc. I can get it to make new takes the active ones by deletiung the audio file in the main track.
NOTE: Sometimes seems to delete old take but works better in newly creted from scratch projects than in those from templates!
Shall I email my project template file?
Thanks,
Mike G
Mike GWhen editing a loop would be useful to have an incision (i.e a split made with the scalpel tool) that is “movable” also would be good if it had an editable crossover value (i.e. 0 – 0.5 secs)
When comping it would be good if I could set a short loop running and move the “incision” location back and forth until it sounds good.
Could be implemented as a temporary “incision” (i.e. Can move “incision” point only until let go of mouse button) or could be a permanent “splitter” widget.
For my purposes either would be fine. In some ways temp splitter might be more flexible allowing you to tweak crossfades etc. afterwards.
pj geerlings@Mike G wrote:
When comping it would be good if I could set a short loop running and move the “incision” location back and forth until it sounds good.
+1
That sounds like a fantastic idea !