VirtualDAW

[EuroHobbes]

I still don't see the appeal, what exactly makes your DAW unique compared towards other DAWs?

[VOODOO U]

Those producers, who only use (vocal) samples and soft synths do not need any of this.

What would be really cool is if you made this a plugin as opposed to a virtual daw.
So focused more as an instrument that could be loaded in any DAW.
As much as possible have it akin to most instrument plugins where all features are on one "page" of the GUI.

[VirtualDAW]

Those producers, who only use (vocal) samples and soft synths do not need any of this.

What would be really cool is if you made this a plugin as opposed to a virtual daw.
So focused more as an instrument that could be loaded in any DAW.
As much as possible have it akin to most instrument plugins where all features are on one "page" of the GUI.

This idea of a DAW-plugin within another DAW is really unique.
While that might be possible, I don't see a real use case, since
my goal is an app, which I really want to use.
I'll implement all those things, which I'm gonna use.
The virtual DAW is for all music producers, who simply
don't use any physical analog devices.
And I can implement more features, if people demand them, that's why I started this topic. My main focus is always on stability, simplicity and resource-saving.

[mesamask]

So focused more as an instrument that could be loaded in any DAW

Go Bitwig. Amazing instrument that also serves as a DAW

More serious:
if VirtualDAW's main goal is to be a lightweight and streamlined DAW, then I'd be interested in using it.
I'm not always keen on firing up a DAW like Bitwig or Studio One when I only want to let's say create patches in a certain Synth. Mostly I'm using hosts like GigPerformer, Element, Cantabile, etc. for that, but I'd probably prefer a slim DAW over those.
Actually there's this little gem "EXT64" which is like a DAW for your pocket, portable .exe with less than 3 MB. But I surely wouldn't mind having an alternative to that.

[whyterabbyt]

Of course it supports audio input: Soft Synths and Audio/Media Files; but no connected physical devices.

Neither of them are the accepted definition of an audio input for a DAW. The accepted definition is those physical devices.

Its exactly equivalent to stating that your DAW has 'audio output' despite it only recording to a file for playback in some other software, and you never being able to listen to what the DAW is doing from inside the DAW.

Please stick to the common accepted usage of terms. Including 'virtual'.

Also; beware of Steinberg asserting trademark over the use of 'Virtual' anything that's DAW/plugin related.

[whyterabbyt]

This idea of a DAW-plugin within another DAW is really unique.

So unique that we already have about 3 of them.

[eclipxe]

I'm sorry, your project will fail and you are wasting your time.

[VirtualDAW]

if VirtualDAW's main goal is to be a lightweight and streamlined DAW, then I'd be interested in using it.

Yes, that's exactly what the goal is. Maybe I should update my description in this way. Thank You!

UPDATE:
I added "Streamlined and lightweight." on my website next to the goal.

[VOODOO U]

my goal is an app, which I really want to use.
I'll implement all those things, which I'm gonna use.

I can implement more features, if people demand them, that's why I started this topic.

Well then based on the former you don't need this "topic" because even if I demand you make it a plugin, you won't if it is something you care less to use. But here I go anyways:
I demand you make it a plugin considering it won't have the ability to record analog sources. This gives it a better opportunity for those producers who *do* record analog sources to utilize your DAW.
I demand you make it, as you say, simple (simplicity) by having all of its features available on one front end of the GUI, no multiple pages. One idea is to make the tracks vertical as opposed to horizontal so the main view is a "mixer" with an in-line vertical piano roll. Voila. Everything one needs ro view on one page.
I demand that you do something extremely convenient and allow instrument tracks where VSTs can be scanned like effect presets. So you load a track and immediately available is a readout with the first instrument plugin name displaying and now with key shortcuts, one can select any vst like an effect preset (or mouse click those adorable little arrow icons with the mousy mouse). Below this instrument preset selection "bar" is that instrument's own preset menu where one can scan and preview. If you go with the vertical tracks there could be some ideas how to do the layout where it's easily readable etc. but that's irrelevant until.
I demand a virtual.keyboard so one can utilize qwerty keys to.trigger notes.

[VOODOO U]

So focused more as an instrument that could be loaded in any DAW

Go Bitwig. Amazing instrument that also serves as a DAW

Yeah that's where Bitwig shines, as an instrument. If it were available as a plugin I'd tattoo the bitwig logo on my shaft. Not really but still.

[VirtualDAW]

Of course it supports audio input: Soft Synths and Audio/Media Files; but no connected physical devices.

Neither of them are the accepted definition of an audio input for a DAW. The accepted definition is those physical devices.

Its exactly equivalent to stating that your DAW has 'audio output' despite it only recording to a file for playback in some other software, and you never being able to listen to what the DAW is doing from inside the DAW.

Please stick to the common accepted usage of terms. Including 'virtual'.

Also; beware of Steinberg asserting trademark over the use of 'Virtual' anything that's DAW/plugin related.

From where do you get those "accepted definitions" ? Which ISO/IEC are you referring to?
I wanted to make clear, that my app can process audio data, and it even may process "audio input" as you describe it, when I support the use of an USB-microphone, which may be implemented at some stage.

I go with this definition of "Virtual Audio Devices" :
[..]Virtual audio devices represent the filter graphs that render and capture audio content. The system audio driver (SysAudio) uses the available hardware and software components to determine the filter graphs to build.[..]
https://learn.microsoft.com/en-us/windo ... io-devices
So these "virtual" devices even could be physical devices, if the system can automatically use them. So if your system configuration supports a physical device as "available" hardware (also known as "Audio Endpoint Devices"), then it may possible to be also used in my DAW, if it produces a supported audio waveform format. But there's no guarantee and so my DAW provides "virtual" sources (like VST3-plugins) only, to not promise more, than expected. This makes it also more affordable.
My DAW will not be a full MIDI-Sequencer; since it will not accept analog MIDI-devices as input. You still can use MIDI Files as input.
So how would you describe the situation differently? The term "virtual" can be used in differnt ways. And a common understanding is, that its not a physical device. And so soft synths and audio/media/MIDI files are no physical input.
Only a USB-microphone would be; And that may be implemented later.

See WASAPI "Audio Endpoint Devices":
[..]The term endpoint device refers to a hardware device that lies at one end of a data path that originates or terminates at an application program. Examples of audio endpoint devices are speakers, headphones, microphones, and CD players.[..]
https://learn.microsoft.com/en-us/windo ... nt-devices

There is no registered trademark "virtualdaw" and no company with that name. And the Steinberg trademark is "VST®", which means "Virtual Studio Technology (VST)". The "Steinberg VST usage guidelines" explain, how to use the trademark in an app and on a website. My app will use VST3 plugins and I have signed the license agreement with them.
From where do you get that information, that they could assert "anything" related to the word "virtual" ? The trademark VST® is not the same as if you use the word "virtual" combined with another word.

[VirtualDAW]

my goal is an app, which I really want to use.
I'll implement all those things, which I'm gonna use.

I can implement more features, if people demand them, that's why I started this topic.

Well then based on the former you don't need this "topic" because even if I demand you make it a plugin, you won't if it is something you care less to use. But here I go anyways:
I demand you make it a plugin considering it won't have the ability to record analog sources. This gives it a better opportunity for those producers who *do* record analog sources to utilize your DAW.
I demand you make it, as you say, simple (simplicity) by having all of its features available on one front end of the GUI, no multiple pages. One idea is to make the tracks vertical as opposed to horizontal so the main view is a "mixer" with an in-line vertical piano roll. Voila. Everything one needs ro view on one page.
I demand that you do something extremely convenient and allow instrument tracks where VSTs can be scanned like effect presets. So you load a track and immediately available is a readout with the first instrument plugin name displaying and now with key shortcuts, one can select any vst like an effect preset (or mouse click those adorable little arrow icons with the mousy mouse). Below this instrument preset selection "bar" is that instrument's own preset menu where one can scan and preview. If you go with the vertical tracks there could be some ideas how to do the layout where it's easily readable etc. but that's irrelevant until.
I demand a virtual.keyboard so one can utilize qwerty keys to.trigger notes.

Please excuse my wording, I did not mean, that I care less about what you suggested. I actually like your idea and I'm considering implementing it. In the first moment, when I read it I was not actually aware what you offered. Thank you!

[VOODOO U]

Oh. Well in that case i demand you forgive me.

[No_Use]

I read over the description, imo some good (albeit not new or unique) concepts there:

- human readable XML(-like) project format
- sandboxed plugins (DAW crash protection)
- (optionally) storing VST state as .vstpreset rather than as Base64 chunk (this one is unique I think)

I think I'll be loosely following further development...

[VirtualDAW]

I still don't see the appeal, what exactly makes your DAW unique compared towards other DAWs?

My DAW accepts "virtual" sources (like VST3-plugins) and Audio/Media files, only. This makes it more affordable. As pointed out by "mesamask" 's post, it will be streamlined and lightweight. And therefore its virtual, since it does not support all physical devices.
It also will not be a full MIDI-Sequencer, although you still can use MIDI files in it. And additionally it can process VST3-Plugins and supported Audio/Media Files. From supported video files it will only use the audio channel.
And there will be features as "No_Use" stated, which will be useful, when being implemented to improve stability, simplicity and to reduce resource usage.