how to disable default auto-tempo when i drag audio clip from browser to track

[person1]

its annoying

[pough]

It wasn't too hard to find.
Settings -> General -> Editing -> Detect tempo of imported audio files

[Maarid]

It wasn't too hard to find.

it is a pity that this does not affect the automatic checkboxes of autotune and autotemp of the sample that has just been rendered to a new track

[pough]

it is a pity that this does not affect the automatic checkboxes of autotune and autotemp of the sample that has just been rendered to a new track

Can you be more specific about what you're doing? I just tried a few different ways to render and none of them resulted an audio clip with the auto-pitch or auto-tempo checked.

I rendered audio from a MIDI clip. I rendered audio from an audio clip. I rendered a track to a new track.

Even after turning the setting back on again I'm not getting an audio clip with either of those settings checked.

[Maarid]

Even after turning the setting back on again I'm not getting an audio clip with either of those settings checked.

I am sincerely happy for your good luck, it is extremely annoying and slows me down

version 12.5.5

[dysjoint]

Yeah, I spent a good couple hours trying different settings and render options, but I cant find any way to render a track to a new track without having the new audio file defaulting to auto pitch/tempo. The best work around for midi was to extend the midi clip out as far as needed to catch reverb and delays, and then render the clip {not the track}
The new wav file will appear on top of the midi clip and you can drag it to a new track manually. However if you drag that exact same file into the project from the browser, it will have auto pitch/tempo enabled again.
This is with everything I can find in settings to do with auto:... or detection... turned off.
It must be possible, I just haven't found it yet.

[Maarid]

but I cant find any way to render a track to a new track without having the new audio file defaulting to auto pitch/tempo.

there's actually some kind of cocktail of glitches. not only does the tempo definition work 60\40, where 60% of samples without tags try to invent a tempo and always with an error, because I have it specified in the name of the sample. The forced inclusion of the function in the workflow [render to a new track] might not be noticed if the function did not work as slowly as possible, as slowly as I have never seen anywhere, in any of the DAWs. Up to the point that with any slightest manipulation of the sample, the pace of which is completely equal to the pace of the project, the program is not very clear what it starts rendering every time, noticeably wasting time.
Once again, I am clearly convinced that Waveform is built in such a way that it is impossible to start working, composing or arranging in it. We have a very high-quality music editor for post-processing of already invented compositions, for honing sound and high-frequency rendering of synthesizers. When trying to compose a composition, you will be constantly stopped by ambiguous glitches, knocking down inspiration and mood at almost every stage of composition construction.
I do not know how to shout about it to be heard.

Waveform users, answer me, do you really like the constant opening/closing of a separate midi editor window as soon as you touch the open plugin window? Or is it that I personally have a taste problem?

[dysjoint]

Yeah, for me I got used to using clip stretching as a fine tuning/pitching mechanism. And I also like to adjust the timing of things by dragging the waveform inside the clip slightly off the grid as needed. With autotempo/auto pitch on the waveform disappears as soon as you try moving it and then Waveform redraws it. With long clips it's a nightmare.
I know what pitch I want and I know what timing I want. I don't want the Daw trying to interfere and slowing the whole thing down.
I am more talking about sound design and electronic style bass mangling, drum sampling. Not recorded multitracks. Maybe it's a different experience for others.

[pough]

I am sincerely happy for your good luck, it is extremely annoying and slows me down

I just find that developers are more likely to track down a bug if you provide them with a clear set of steps that can replicate the issue consistently. I'd do some more testing, but I'm currently on vacation and not near my music computer. Hopefully this can be fixed.

[Maarid]

I just find that developers are more likely to track down a bug if you provide them with a clear set of steps that can replicate the issue consistently.

A very strong impression that nothing will change. I'm not saying this, all the forum topics on KVR in the Traction section say this, if you thoughtfully read older topics.
I recently read on my forums that the development of the user interface, including its relevance of use and method of application, stopped in version Tracktion 6! For myself, out of curiosity, I found and downloaded this version with some difficulty, you won't believe it, the trial version met me absolutely identical to 12.5.5, without new features, do you understand? An absolutely identical version of the program, where only innovations are missing. Including all the glitches and all the inconveniences of use, which migrated from version to version up to the latest.
If you know how to contact the developer directly in order to minimally remove at least inconveniences, I would be very grateful to you for warning of such an opportunity, because judging by the only local forum, it seems that developers ignore the opinion of users regarding the usability of the program.