VST instrument suddenly not sounding

[quintessential]

Hi Helio Community,

Please be patient as I learn the basic navigations of Helio. Thank you. Started a new project days ago that included two VST tracks, a Sonatina Violin (by bigcat) and City Piano (by bigcat). All worked fine until today. I loaded the project clicked 'play" and the piano is not sounding. Spent time searching and read the "Getting Started Guide" but did not find a solution. I was thinking perhaps I accidentally 'muted" the piano track but not sure where a 'mute setting' is located. Any help would be much appreciated.

Thank you very much.

[peterrudenko]

Yes, you have probably muted the track, you can toggle mute with the 'M' hotkey or the "Mute/Unmute" commands in the pattern roll's track menu. Muted tracks are displayed as dimmed with a 'M' indicator in the pattern roll, but there is no indication for it in the piano roll yet; I'll need to fix that.

Also if something goes wrong with how Helio works with VST plugins, you may check the development build, it includes many VST/VST3 fixes from the latest JUCE version.

[quintessential]

Yes, you have probably muted the track, you can toggle mute with the 'M' hotkey or the "Mute/Unmute" commands in the pattern roll's track menu. Muted tracks are displayed as dimmed with a 'M' indicator in the pattern roll, but there is no indication for it in the piano roll yet; I'll need to fix that.

Yes, that was the issue. I do see the 'M' indicator in the pattern roll for that specific 'muted' track. I guess I accidentally hit 'M' at some point. Fixed! looking forward to the fix in the piano roll since that is where I spend most of my time (for now, as I learn the application). Thanks Peter!

Also if something goes wrong with how Helio works with VST plugins, you may check the development build, it includes many VST/VST3 fixes from the latest JUCE version.

Glad you addressed that. For a couple of days I was having an issue with a
VST violin track (Sonatina Violin x64- by bigcat). When I clicked play, the violin sounded like a whistle. To fix the issue, I would either close Helio and reopen it, delete the instrument from the Orchestra Pit and reinstall it or just ignore it and it would fix itself (I do not remember in what order) as this happened a few times. Thus far, the violin vst has been working with no issues. However, I downloaded the dev-buildx64 (that you kindly linked) and I will utilize that instead of the original version I downloaded (ver. 3.10 x64). Thank you!

Question #1 please:
Interesting observation ... after opening the portable dev-build x64 for windows, I noticed it had the same projects that I already created. How did the dev-build find my projects that were originally created in the portable ver. 3.10 x64 that I downloaded last week?

Question #2 please:
How can I identify what version (or dev-build) of Helio I am using inside the application?

Thank you

[peterrudenko]

All builds store their settings in the same configuration file regardless of version, so they all work with the same projects, instruments etc.

You can see the app version number in the header in the top right corner of the window (when not using the native title bar), on Windows the version number is also available in the file properties. There's no indication as to whether it is a stable or development build, the latest dev build will just appear as the next version, 3.11.

[quintessential]

All builds store their settings in the same configuration file regardless of version, so they all work with the same projects, instruments etc.

Ok, thank you. I understand

You can see the app version number in the header in the top right corner of the window (when not using the native title bar), on Windows the version number is also available in the file properties. There's no indication as to whether it is a stable or development build, the latest dev build will just appear as the next version, 3.11.

I understand thank you. I unselected 'native title bar' in settings and now see the version number in the top right corner.