|
Muzys' Patch system works like a sampler, so it needs a note on event to trigger the samples.
But you can workaround this by putting Locators in that long Wave and make a Program out of it.
This can be done via the Wave Labo :
=> Create Locators by clicking the Timebar. Locators can be dragged in realtime !
=> Create a Program and Part via the DSP Funx menu.
So now you can play the individual subsections of that Wave and this will make it easier to start somewhere in the middle of that Wave.
If you want to record some tempo changes in realtime via a slider, then Shift+click on the Tempo field in the The Control Panel.
This will popup the Tempo Fader, which can be recorded (hit Record in the Control Panel) just like any other fader.
Alternatively, if you just want to insert individual Tempo events, then just create a long Part/Sequence on track 1 of your Composition. This can be done by Shift+Pencil as this always creates a new Part and a new Sequence at the same time.
Then goto the List Editor, press the [Insert] key, and choose Tempo as event type.
Then you edit the details if that Tempo event.
Note that it's important that a Tempo track - ie. a track that contains Tempo events - is placed on the first track of a Composition, otherwise Muzys won't chase the Tempo events (ie otherwise it won't examine the Tempo events when doing a fast-forward or rewind)
Well lets go step by step :
1) Goto Muzys' System menu (in the Control Panel) and choose "MIDI Hardware".
2) At the left side you can choose the MIDI Input port(s) in your system that you want to use in Muzys. Click the drop down arrow for a full overview of all available MIDI ports. If no ports show up, then you'll have to check your basic system configuration, which is beyond Muzys' scope.
3) Just to keep things as clean as possible it's a good idea to set all port-slots that you don't use to "None". So if you just use one MIDI keyboard, set all MIDI Inputs 2..7 to "None". The same principle for the MIDI outputs.
4) Now close the MIDI Hardware window by clicking OK.
5) Now you should be ready to play your VSTIs. Note that Muzys will always send the events received at MIDI Input to the MIDI In Player, which is defined at the left side in the Control Panel.
Muzys can only *Record* (i.e. via the Record button) small sysex events of maximum 255 bytes long; This is good for recording synth knob tweaks that are sent as sysex packages.
But if you want to recording longer sysex bulk dumps of thousands of bytes, then use the Tools menu : Sysex Dump Manager.
Here you can record large sysex dumps and save them with your Project, or export them as .SYX files.
Last but not least, note that Muzys only listens to sysex received at he port indicated in the System menu : MIDI Hardware dialog.
Well, it's difficult to give a simple answer to that since there are so many cards outside.
As a software developer, we make Muzys compatible with audio card standards like ASIO, MME, DirectSound, SoundManager. Then every such audio card should be compatible. And we don't examine (every new version of) every new soundcard.
Best thing to do is read magazines like Computer Music for their detailed comparison tests between soundcards, and use Google to search the internet on reports of soundcards.
It seems Phatmatic will only work, with Muzys at least, when the file msvcp60.dll is in the windows\system directory.
Windows 98SE does not install this file so you have to acquire it through manual installation or by other software installs. Windows XP has it by default.
A simple Google for "msvcp60.dll" gives various links to download locations.
Indeed, Muzys is not (yet) build for dual monitor systems, since Muzys works in one fixed OS window that is not (very) resizable.
It happens on dual monitors systems that the main OS window Muzys is working in spans both monitors, so that the physical borders are right in between your workspace :-(
And since the main OS window is not really resizable, it seems impossible to get a good graphical setup.
However, there is a workaround for this :-)
Quit Muzys, and goto your Muzys/Data subfolder and start text-editing the "Muzys.Set" file.
Scroll down to the 4 OSWindow_* parameters and set the X-Y-W-H respectively to 8,24,1008,712 (supposed you have a 1024x768 monitor) Then save this file and restart Muzys.
You'll see that Muzys uses these setup parameters to size its main OS window. (Maybe you might want to finetune these parameters towards your system)
We'll improve dual monitor support in the future.
When you want to use Muzys' "Record Audio" on the Mac, you have to use the ASIO driver for your soundcard.
If you're using the built-in soundcard via Sound Manager, then install the ASIO driver for Sound Manager into your "Muzys/ASIO Drivers" subfolder.
This driver is included in any Cubase demo version.
There may be a problem here. It has to do with the MacOS file type/creator stuff.
A proper Vst-Fx-Bank file must have filetype 'AFxB', but when the file comes from Windows / Internet, chance is high MacOS imports them as a 'TEXT' file.
That's why Muzys doesn't show these Fxb/Fxp files from itself, cause the MacOS tells Muzys they are Text files.
Solution is to disable the file type filter in Muzys' File Chooser.
This is done via one of the 8 buttons at the right : right column, 3rd from top : Uncheck "File type filter", and then Muzys' File Chooser will show all files, and you can navigate to the fxb/fxp files. (note however that this file type filter is re-enabled every time you call the File Chooser)
We'll think about a workaround.
By the way, for more info on Muzys' File Chooser, click here.
For example the DS404 :
Now the DS404 is ready for being plugged in in Muzys' SynthRack. And if you do so, you'll get all 16 DS404 Midi Channels listed in the Muzys' Player list !
That's all !
You can do this for any plugin you want to add.
(note that it doesn't make sense to set "Is Multitimbral" for non-multitimbral VSTIs)
Click here for more info on Muzys' Players.
Click here for more info on Muzys' Plugin Manager.
When installing Sampletank LE as a demo, everything seems to work fine.
But when i entered the id & serial, and created, saved & loaded some projects, Sampletank LE starts to crash not only in Muzys, but then also in Fruityloops 3.5.
I have the impression that it has to do with where your instruments root folder is, and also with whether the "SampleTank Settings.txt" in your Sampletank folder contains the "Instruments.LoadSync = yes" parameter.
IF the instruments root folder is too long or containing spaces or something like that (didn't find the very reason yet) AND / OR the "SampleTank Settings.txt" in your Sampletank folder does not contain the "Instruments.LoadSync = yes" parameter, Sampletank LE crashes !!
So you can workaround like this :
After changing and saving the "SampleTank Settings.txt", just plug in a new Sampletank to try the new settings. The problem should have been resolved !
This issue has been reported to IK Multimedia.
Browse to your Muzys folder, open the "Skins" folder, then browse to the appropriate skin folder, and start editing the bitmaps ...
If you want more details, read about Muzys Skins
Since all audio software must precalculate audio fragments before they can be send to the soundcard, and arrive to your ears, there goes some time between the moment some MIDI message is arrived at MIDI input, and the moment that the audio is ready, and is played through the speakers.
Especially on the Windows(r) platform things can be quite serious.
Windows itself, as an operating system, generates latencies (delays) of up to 500ms (half a second !!!) between an incoming MIDI event, and reporting it to the application. And then the audio still has to be calculated and send to the soundcard.
Though, starting from Windows 98, things are improving, and with a good setup and a good soundcard you may achieve latencies of 20ms or less. Especially if you use the ASIO drivers !
Even on faster systems like the Mac (latencies up to 15ms), Linux (up to 10ms) and BeOs (up to 10ms), the problem is there. And even on dedicated hardware machines like samplers and drumboxes, there are measurable delays ! (Roland R8/R70 : 10ms, Yamaha O2R : 20ms, ...)
Sometimes when you miss-click a note in the Grafix Editor and click a blank spot instead, a message pops up, telling that "Lane mask is not unique".
That's because you have used the Pencil Tool while the "AI" = Auto Insert (in the lower left corner) is enabled. Thus when clicking then on an empty spot, Muzys wants to insert a note there. But if the Mask for that lane is not unique enough, Muzys doesn't know what to do, and gives the above message.
So, maybe just disable the "AI" button, so that Muzys won't insert new events.
Oh, and by the way some extra tip : If you want to ramp a group of velocity beams, hold down [Control] while using the Pencil. That will give you the same "line editing" as on curves.
For all details about the Grafix Editor and it's lanes and masks, click here.
|