Waveform 13.5.2 Public Beta Available

[cjayconrod]

Were people honestly expecting huge feature drops in a .5 release? I'm happy with a ton of bugfixes and greater stability. The release notes show a lot has been going on behind the scenes and under the hood. Thank you.

[dysjoint]

It's always going to be hit and miss as to whether updates matter for you personally. Clip launcher was a great addition in a paid update that I will probably never use. Automation Clips, in a point release, makes much more sense to me. It's just the way it is. Check the response to the latest Studio One update for example.

[Maarid]

I can replicate this

the tape start\stop effect on the sample adds the effect directly to the beginning and end of the sample itself, that is, if we have a long sample stacked in the middle, then applying the tape effect we will not see the faders either at the beginning or at the end, we need to increase the selected sample to its original size and only then the faders will be visible. as I understand it, the tape effect does not take into account the selected sample length.
If I'm not mistaken, this error has been present since version 11

[dysjoint]

When the eye is selected to show the automation I can't zoom or scroll vertically in the midi editor. I can still zoom and scroll horizontally.

Merging midi clips wipes automation curves and assignments. May be a logical reason for this but it's a bit annoying.

The shaded visualisation in the editor, either side of the focus area, that goes up and down to illustrate the automation position seems to only follow the absolute curve, even if relative and scale edits have been added. The actual automation functions correctly. Not a show stopper.

Copy and paste only works for the curve in focus? So needs to be repeated 3 times to copy Absolute/Relative/Scale and get the same summed curve?

All of these might be by design, just noting them in case.

Requests:

When clicking on the dashes next to the eye, where you select parameters to automate, it would be nice if currently active curves were diplayed above the plugin list. Or some other way of quickly flicking between active curves like you can on tracks.
Edit: Something like Kirchoff EQ presents hundreds of parameters, even Serum presents loads, so this request would be super useful

Any chance of being able to save user curves?

Sounds negative but not intended, loving the feature.

[dRowAudio]

I’ll get back to the other questions in this thread but just a quick note that we’ve address the early reported bugs in 13.5.3 which is now available from the PUBLIC BETA downloads section.

[dysjoint]

Random bug: Add an audio sample to a track. Proxy file off, no pitch/time/stretch. Shorten the audio clip from the ((beginning)) using the outer 'hollow' triangle (creating an internal loop inside the source file, correctly displayed in Loop Properties). Turn on loop in the clip header and drag the end point out so the shortened clip is looped a number of times. Press A to set the in/out markers, Loop on in the transport section. Position the playhead ((before)) the clip, press play. The first play through ignores the clips' internal loop window and plays from the start of the source file and then starts looping internally. Shift the clip in the timeline, press A, position the playhead again, same result. First playthrough is incorrect. Subsequent playthroughs appear correct. Render Clip option appears to render the bug. Merge clips renders the bug. Render Track sometimes renders the bug, unless the clip is positioned to begin at the start of bar 1, then it appears to always render the bug.

Turning on 'Use Proxy File' removes the issue.

[Maarid]

I’ll get back to the other questions in this thread but

I sincerely understand that such requests are not directly related to the new trend .5 updates, but I poked around and figured out what to do with the poor grip between the tracks on the left, I increased the magnifying glass interface many times, made the mouse speed as low as possible and made sure that the stretching arrow between the tracks is activated only on two white pixels between the black stripes of the edges of the tracks themselves, with a good mouse speed, two pixels hit it becomes difficult, above and below the two black interface bars are also two pixels each., If you increase the arrow's appearance to 6 pixels, including the interface bars, this will no longer be a problem for any mouse speed.

[dayvyg]

automation can be done not generally, but tied directly to the audio clip itself, it's cool, but doubtful, nothing has changed for me, to move the automation location, select all the points, copy, then delete, select a new location and paste, instead of just moving or repeating a separate clip containing automation on the second track.

I have to agree. I think it would be best to decouple automation from the midi/audio clip itself. I think many were thinking/hoping that an automation clip would be a separate clip that contained automation information only.

[Maarid]

automation can be done not generally, but tied directly to the audio clip itself, it's cool, but doubtful, nothing has changed for me, to move the automation location, select all the points, copy, then delete, select a new location and paste, instead of just moving or repeating a separate clip containing automation on the second track.

I have to agree. I think it would be best to decouple automation from the midi/audio clip itself. I think many were thinking/hoping that an automation clip would be a separate clip that contained automation information only.

difficulties of the English language, "automation clip" - sounds the same for "a separate block with automation content" as for "automation within the clips themselves"

Formulate your wishes correctly, As you wish

[dayvyg]

Hi Maarid,

I'm not sure if I'm misunderstanding you, you're misunderstanding me, or both. Anyway, when I heard clip automation, I assumed it would be an automation clip separate from the midi/audio clip. This is how it is done in some other DAWs and seems more flexible to me. Example attached from Mulab.

[Maarid]

good mood, you're absolutely right, that's exactly what I thought when I saw the phrase "automation clip", which is what I wrote about. Don't pay attention to the interpretation error, I'm trying to joke so clumsily.

[dayvyg]

[pough]

You can create a clip that only includes automation. It would have to be on the same track, though, so a bit complicated to move around. That's what I've done for one audio clip where I wanted the automation to start before the audio clip start and end after the audio clip ends. Just add a MIDI clip over the audio clip and use it for nothing but automation. You should be able to do that same with MIDI clip on MIDI clip, which I haven't gotten around to testing.

However, I would vote for automation clips to be able to exist in a separate track for easier management. Also, a vote for being able to vertically stack clips in a track. Or maybe that can already be done and I just don't know how?...

[Maarid]

Also, a vote for being able to vertically stack clips in a track. Or maybe that can already be done and I just don't know how?...

as far as I know, there is no accidental copying when dragging several clips can literally lead to the loss of short segments under large ones with complete confusion on the cutting board. If they began to take from the classics *Synapse Orion*, then it would be possible to take a delicious thing from it, namely the direct duplication of the track outputs to the second track for mixing. I understand the idea that any plug-in or chain in the rack can be ignored, which is very convenient, but personally I have difficulty rendering individual tracks with sidechain or normal parallel compression, I have to physically duplicate samplers or synthesizers completely with the entire track, which causes considerable discomfort.
But again, these are my personal difficulties, sometimes I find a way out, sometimes not.

yes, yes, the rendering of a separate track, the effects of which use a sidechain, if I want to render a track separately, then the second track from where the sidechain comes from must BE AUDIBLE, correspondingly, if my bass track affects several tracks, I can only render them together to take into account the sidechain, these are the problems I have Strange difficulties

[dayvyg]

You can create a clip that only includes automation. It would have to be on the same track, though, so a bit complicated to move around. That's what I've done for one audio clip where I wanted the automation to start before the audio clip start and end after the audio clip ends. Just add a MIDI clip over the audio clip and use it for nothing but automation. You should be able to do that same with MIDI clip on MIDI clip, which I haven't gotten around to testing.

However, I would vote for automation clips to be able to exist in a separate track for easier management. Also, a vote for being able to vertically stack clips in a track. Or maybe that can already be done and I just don't know how?...

Be nice if you could stick them in an automation lane. I don't like the idea of stacking them on top of each other. Pretty hard to see at a glance. Not so bad in a small project but it'd be a bit of a nightmare in a larger one.