Feature Requests

[ciro1983811]

Maybe not… the container could adapt to the length of the sped up or slowed down video, but it’s just a visual thing …

[fkalmus]

@ciro1983811

is it possible to add a speed of reproduction for video events on the top bar ?

@musicullum

Basically yes, but it would require that the events follow speed change…or maybe not?

Just for an idea. In Reaper it is solved the same way as in VLC: “playback-speed-multiplyer”.

Meanwhile @ciro1983811 I can’t emagine how difficult it gets if system needs to re-calculate this with PART trigger timestamps, where exactly the re-calculated frames were in case of e.g. flexloop (that e.g. VLC doesn’t need to “keep in mind”)

[ciro1983811]

Yup!! I would simply link the playback rate to the event container … so if the file is 30fps with the multiplier would play @30,05 or 29,95 fps etc etc

Independently from parts etc etc

[musicullum]

@ciro1983811

I would simply link the playback rate to the event container

Have fun with that
It is not simple at all.

However, my video editor features to size an event with alt or ctrl, then it adjusts video speed accordingly. While that still requires for us to find all places in the code where the length of media files and sections are now “wrong”, it would be more doable than the other way around, or “ignore” it, meaning visual length of track event not matching what you see.

[Spork]

@fkalmus

Basically wanted to post here, yes, but not 100% sure, but as @Spork is credited in C14, probably will have answer or some thoughts about

… someone called my name?

@fkalmus

But seems VL won’t see C14’s drummer track content regardless it is “converted” to midi clips within the Drummer track. Tested with

Nah, it’s a Cubase 14 feature only. It’s a valid point to think DAWproject could handle it. But it’s an internal Track-Type. Other DAW would need to have the same output of those tracks. Here, a drum machine. And what about Samler Track, the same.
That’s why it could not be added to DAWproject.

@fkalmus

when clip is converted to “MIDI events”

MIDI Tracks without any output are not part of the DAWproject format. Only Instrument Tracks.

See you,
Michael.

[SDerMan]

Once again… Any chance of this?

[musicullum]

This is post No. 686, guys. And you are refering to a much earlier post, so we need to look it up and that takes time. Pls start a new topic. Even though this thread is about wishes and suggestions, not all of those should be in one giant thread, it reduces the chance that we can keep track of all of it, thanks.

And yes, we will provide options for text and background color for Lyrics, step by step.

[Folelser]

in my opinion, a very interesting and necessary feature for a live tool.

would be about the Signature Track,

• Have the option of importing it solo, or selecting it in a project’s import so that you can just update the existing one.
  (At present, it’s impossible to copy/paste a signature track and the import overwrites the project).

• To be able to act as a track like Cubase, this would enable entire sections to be copied and pasted rather than marker by marker.

• Fix the bug where a new signature marker tends not to be inserted in numerical order, e.g. if I write on 45, it tends to be inserted after 50 rather than before 46.

Importing midi tracks for automations would also be a plus, rather than having to reprogram in VST LIVE, which is less readable in this respect.

[jrose]

@nowiamone

“Looping within the Sequencer” function, why not also think about a revolutionary feature (Audio and Midi Loops within a Loopstation-Section with nice visual feedback, controllable via touch/assignable hardware.)
btw: if someone thinks ‘why dont you just use Ableton for that’ = The Looper Plugin in Ableton has severe disadvantages, e.g.: You’re unable to see an overview of all loopers going on, as each is “Hidden” in the specific track - and the audio-engine is bad-> Tempochange equals pitch-change. With Steinbergs knowledge of Audio-Engines, it should be possible to create a Looper-Loopstation which also automatically recognizes transients, being able to automatically slice/cut silence at the beginning of the audio-loop, or even auto-quantize audio.

Connecting some “independent Looping” to VST-Live is a really good idea. I would really like to integrate Maschine 2 or 3 as Software-VST into VST-Live. But for now - this is not possible because of the missing VST-plugin-Input feature, which prevents recording audio in Maschine.
There is already a feature request for VST input handling, I started early this year!
And a good thing is Maschine don’t have most of those limitations mentioned above and could be used as a multi looper similar to other hardware, but it is already integrated in the song /project structure and auto load functionality for VSTs!

[steve_pin]

Tempo Follow
Would be great if the tempo follow feature would be included. In other words, a live drummer or turntable would have the lead in tempo. VST Live would follow. One can find this feature in Ableton Live https://blog.abletondrummer.com/ableton-tempo-follow/

[marcopan]

Telling you that my needs are in the context of music for prose theatre, I must confess that still I cannot abandon Cantabile, which flexibility I cannot renounce. TYhe only apparent advantage of VST Live on Cantabile (I’m considering only Pro versions of both applications) is a more user firendly DMX integration.

As an example of something I never succeded to implement in VST Live is n event based cross fade. I don’t know at what level it could be possible, within the architectural choices on which the product is based. I mean sending an event from a MIDI controller, starting a track a zero volume while another track is till playing. With sliders on the same controller (or authomation) both tracks can be cross faded.

Is it my limitation, not to be aable to implement this in VST Live? DO you think some feature can be added in future to VST Live to implement this?

[musicullum]

Actions and Shortcuts (which can be automated) feature an “inverse” setting. Programming two actions, one for fade out, one for fade in (set to reverse) should do the trick. Actions can be automated with either an Automation Track, or a MIDI track sending the MIDI messages as programmed.

There is no specific fade option though; you would have to program each step (which you can, in the automation editor, using the line tool). We may add a fade (up/down, from/to) feature later.

[marcopan]

thank you for your comment, but fading is not my issue, I know how to do.
What I need need is:

1. track A is playing
2. I send a signal from a controller which
3. make track B starting, without stopping track A
   The rest managing volume, authomating somthing etc. is a further step and I have ideas

[musicullum]

@marcopan

make track B starting

“Tracks” is a linear sequencer, tracks can not be started individually.

But you can move events on the track to start where they are supposed to.

Or, if you want to do that dynamically, enable FlexLoops (at the top of the setlist), and assign start times to each part (locate in the timeline, and simply click the rightmost Part item). Then, when you select a Part, it will locate Tracks to the Part start time, quantized to beats or whatever you set for FlexLoops.

[Stephane_Michaud]

Maybe you can get rid of this “layer” and “stack” non sense? Very counter intuivite. Why not something like “midi instrument” or “analog instrument” or something more evident and clear like that ?

[fkalmus]

E.g. because LAYER’s can be layered or even used wo any instruments

[birdmug]

I’d really like to be able to normalise audio events. I have been using the volume adjustment on audio events, but it seems limited to a 6db increase. I’d like to not be constrained by that limit and ideally be able to normalise as I would in Cubase.

[CliveJ]

You could insert a compressor and turn up the output

[fkalmus]

or even push ch fader up, etc

[CliveJ]

…or normalise outside of VSTL.