4/24/2023 0 Comments Mugen midi volume reset![]() Lads I always start from new template (blank) and add all my instruments as I need them. This is a Cakewalk Bug for sure, as it affects any VSTi so it is particular to Cakewalk (also same with TTS). I can reproduce this on any new project or old projects. Create a new track by re-adding the Plugin VSTi - and paste in the Events - DO NOT RE-EDIT in staff view or the bug will return. (you may need to do this a lot if in staff view) Cut all the events from the track. I do loads of my composition work in Staff View this is why I see this!!!įinish the edit in Staff View as best you can. ![]() Cannot even be sure that is what it is changing - because everything in event list show no changes and all Velocity and volume states are good?īut I can replicate this on any MIDI track now. So i do not know what is giving Cakewalk the idea that there is a volume / velocity change. Right here it is lads, would appreciate if you could have a look and see if it's the same for you - it happens when in Staff View - if you edit notes in staff view in other words add note or move note or delete note - the volume of the track goes high or low or OFF - no settings anywhere in Midi / Audio / Automation of anything else is being touched - you cannot find it to fix it. Again much appreciated!! Will get back to this post asap. Got to spend more time getting this sorted. I wonder would Cakewalk undo history note something? Not likely if a not noticeable from within the track. Thanks guys for the help not a back thing to go over the same information. Not a peep.ĭavid Deneau, that is a interesting observation - so you telling me that you think Omni signal is getting something via virtual controller if not physical and to stop that from happening you remove the channel from processing anything on Channel 1 or omni? (Picking Channel 6 is as far off field as any :)) I'll have a go - I have a Project at the moment with 2 Midi Instrument track exhibiting this issue - I'll have a look and try your suggestion. again automation lanes etc etc nothing there. Midi Level and Velocity still at default no matter what as viewed from Cakewalk. So it affects the plugin (VSTi) And once changed you cannot revert back. So I think it is something I'm doing or something traversing the Virtual Omni - but I missing as it doesn't appear as a Midi Events. but after a few plays and change even the new track has had same happen eventually. It is as I see - either a signal from a Virtual Instrument back out across the Virtual Omni or as you say me knocking something - but this is what gets me when I compare the tracks I can see zero differences in the tracks and settings of the VSTi's - no Midi change requests on Velocity or other / no system messages or anything like that. As it is as if the setting is changing the Velocity. Track for track comparisons show no such the same - setting the MIDI volume at the start of the project track makes no difference. Fact is it is happening to Midi tracks only - Now in saying that perhaps my controller is sending signal that I'm not seeing - but I would expect to pick that up in Midi Events - but not seeing anything there either. I know Cakewalk well have been a user of it since Pro Audio 9 (20+ years ago) so yeah you right those are the obvious suggestions - checked all those and have done a thorough walk through of all the settings and comparisons per track. David Baay, yes much in the way of what I have checked to date.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |