The VST parameter data can be tracked, no problem with that, but it's about the non-parametric VST data.įor example NI Massive's LFO curves are not stored as parameters but as binary data. So far so good in theory.īut practically it's not always possible to know whether a project has changed, especially when using VST plug-ins.īecause there is no simple or documented way the host can know whether a VST plug-in has changed or not. If the project has changed, ask to save, else no reason to ask that. To avoid that question alert there should be an internal mechanism that can track each and every change to your project. Now it's asking me whether I want to save! Why? Q: I just saved my project and chose to close MuLab. to a rack, and so it's easy to further process the mixdown if you want. Of course you can easily change the target module for the mixdowned part e.g. So that's why you didn't see any level meters moving because the mixdowned part didn't go via a rack. This is because a mixdown is expected to contain everything and so MuLab by default assumes it's best to stream it 'dry' to the audio output. Why?īy default, the new part which results from a mixdown is routed straight to the main "Audio Output". The audio part appears in the composer and plays fine but I can't see any meter going up and down in a rack. Q: I did a mixdown with "create new part" checked. If you want to turn a sequenced VSTi into audio, then select the relevant parts and choose File menu -> Mixdown Audio. Q: How can I bounce down MIDI instruments to audio tracks?Ī: If you want to get the sound of your MIDI instrument into MuLab, you have to record the audio output of your MIDI instrument. Once you got your audio part, you can double-click it to edit it in the Audio Lab. You can start the drag from the integrated browser or from outside the app via a MacOS/Windows drag-drop. Drag & drop the audio file(s) onto the track button or onto the composer.if it's connected to a rack/module that has audio input, otherwise you would not hear anything of course. This will only work if the track you're drawing a new part on is suitable for audio parts i.e. Draw a new part in the Composer using the pencil tool, then choose "Audio File", then browse for the file you want to play.Click the track button -> "Add Audio Track".The audio part will start at the position you last clicked on in the composer. There are several ways to insert a new audio part: Solution: Reinstall MuLab so to make sure you have a properly matching MuLab.exe and MuLab.ID.Ī: You can import audio by using Audio File Parts. When the MuLab.ID file does not match the MuLab.exe file you'll hear short beeps and encounter other malfunctions. Q: I sometimes hear short beeps, how come?Ī:The integrity of the MuLab.exe file is protected by the MuLab.ID file against illegal cracking. Blocksize (the smaller the more instant the time between MIDI notes and their sound, but the more CPU intensive).Samplerate (the higher the better sound but the more CPU intensive).Number of CPU cores (the more the better).These are the critical parameters that define the CPU load: That results in clicks in the audio, or in a stuttered sound. So the audio engine has not enough time to generate/process all audio in time. How come?Ī: You've exceeded the power of your CPU. Q: When playing back my composition, sound is bad, music slows down and the CPU meter is in red. Of course this should be done with care, eventually with an extra backup done by you, so that you will not loose this precious backup when the unusable ProjectName.MuProject file is renamed to ProjectName.backup the next time you save ProjectName. If MuLab crashes during writing ProjectName.MuProject file, then the ProjectName.MuProject file will most propably be unusable.īut you can still recover the previous saved version from ProjectName.backup. When saving a MuProject file, MuLab always first renames the original project file to ProjectName.backup. Q: What to do if there was a crash while saving a project? Saving a sequence part preset will result in a MuClip file. Saving a sequence preset will result in a MuSequence file. it defines a target module.Ī sequence part is not a sequence, it uses a sequence. It can also define a loop.Ī sequence part is a composition part that plays a sequence from a certain position until a certain position, and also defines where the events should go to, i.e. Q: What's the difference between a 'sequence' and a 'sequence part' ?Ī: A sequence is a sequence of events.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |