Improve initial template Welcome message text
Description
Improvement
Let's improve the Welcome message text on the initial template.
- Add info that Cardinal Native automatically detects the default OS sound output device.
- Add info that user can click TRIG button in ADSR to quickly hear sound output to test.
Welcome to Cardinal!
This is the Native Audio/MIDI variant.
It has 2 audio outputs, enabled by default.
This Native Audio variant automatically
detects your default OS sound device,
shown in the top right corner before the
performance meter values.
Use Engine menu to enable input and/or MIDI.
To test your sound output now
you can click the TRIG button
in the ADSR module shown.
A basic VCO + ADSR + VCA is the default patch
Context ( from IRC chat discussion )
oslovebug understood, but would greatly help...especially since it's non-obvious if sound is available or not...since the initial template Welcome doesn't say. (On Windows, the Standalone version will lock onto Windows default output. You can click the Latch and Momentary buttons to hear the sound from the VCO/ADSR... if it's not working, then you might have the wrong default audio device setting in Windows. 17:18 oslovebug That would be a huge improvement... Just simple MORE TEXT on that initial templates' Welcome message note !
17:19 dreamer sure, the welcome message can have some more explanation 17:19 dreamer I still have no idea what you are talking about though :) 17:19 dreamer something about latch and momentary buttons? 17:20 dreamer seems highly specific to what you are trying and not something general for users
17:20 falktx the default template includes the ADSR module where there is a momentary button to open the gate 17:20 falktx can be used for quick testing of sound
17:20 dreamer oh, sorry I'm on the standalone which is different -_- 17:20 dreamer ah, CardinalNative opens a different template
17:21 falktx but indeed, this is too general. the templates are different per variant
17:24 oslovebug Wow... there's a damn trigger button already on the ADSR !!!! THAT should be in the Welcome message! NICE 17:24 oslovebug (totally missed it) 17:25 oslovebug That is indeed the missing sauce in the Welcome message !
17:26 dreamer this welcome patch is normally used in the plugins where passing midi is usually easier 17:27 dreamer but for a quick test being aware of the trigger button is probably good anyway
17:27 oslovebug would have saved me hours... I am not kidding... messing with installing JACK on Windows, looking at my device drivers... etc.etc... trying to figure out why/where Cardinal isn't finding my devices...or where to set the device output... (1. it's an automatic thing. Didn't know that! 2. Hit trigger button in ADSR to test the sound output for the default device) 17:28 oslovebug I'll open the issue for this improvement (especially for Standalone) 17:28 oslovebug Thanks! You solved a simple mystery that can now be put into 2 lines of Welcome message text to help others in the future! 17:29 oslovebug Do you think Host Audio might enumerate and show the default device scanned/picked up ? 17:29 oslovebug or too hard? 17:30 oslovebug hmmm, can change at anytime... and hard to get that feedback loop...now that I think more about it. OK skip it. bad idea generally.
17:31 dreamer it's not the Host Audio module that does this. maybe it could be displayed in the menu bar? left of the fps 17:31 oslovebug Awesome! 17:31 dreamer it only makes sense for CardinalNative though, which again: is not the primary usecase of the project 17:32 oslovebug understood, but great improvement and saving me hours (and future users)