I am using Firewire 6 input and 10 outputs Card.
In Audio Setup>Select Input and select Output is not shownig available Inputs and Outputs in the hardware. I also tried to change ASIO driver to ASIO4ALL.
Earlier MU.LAB Beta A was showing them fine.
MU.LAB Beta B
-
- KVRist
- 263 posts since 24 Oct, 2004 from Delhi, India
Tools are tools, they don't produce anything...
-
- KVRist
- 93 posts since 8 Dec, 2005
Minor suggestion for beta b: when you ask for a new session and you're already playing, then it still keeps playing. I think it would be better to stop playing when a new session is created.
-
- KVRAF
- 37410 posts since 14 Sep, 2002 from In teh net
Yep that's the buggerD-Fusion wrote:Hi Amused
Does it look like this?
Click the picture to get the right size.
I get sound out of it but selecting in and outs does'nt work here.
I am on PC and it worked fine in Beta A.
Oh and don't worry muzycian (this is the only picture i am going to upload since it does'nt show anything special from MuLab)
So i hope it is ok
Getting no sound at all though. On my laptop (KORE system) it won't even play the demo - I click on the play button and nothing. On my Scope PC it does play but no sound though you can see the meters going in Mu-Lab but not in Scope's mixer - that's odd.
-
- KVRian
- 1372 posts since 21 May, 2004 from Serbia
same here, winxp with terratec ews88mt. Playing the demo also doesn't produce any sound though the meters in MuLab are jumping.aMUSEd wrote:Yep that's the buggerD-Fusion wrote:Hi Amused
Does it look like this?
Click the picture to get the right size.
I get sound out of it but selecting in and outs does'nt work here.
I am on PC and it worked fine in Beta A.
Oh and don't worry muzycian (this is the only picture i am going to upload since it does'nt show anything special from MuLab)
So i hope it is ok
Getting no sound at all though. On my laptop (KORE system) it won't even play the demo - I click on the play button and nothing. On my Scope PC it does play but no sound though you can see the meters going in Mu-Lab but not in Scope's mixer - that's odd.
edit:
everything worked fine when I upgraded MuLab to beta b (just copied the new files to the MuLab folder), but after I deleted the old folder and made a fresh install I could not assign audio ins/outs.
-
- KVRist
- 36 posts since 31 Jan, 2006
Hi
I'm using a Windows XP machine, with an Audigy 2ZS soundcard.
On the first run of MU-LAB (I had completely trashed the Beta A installation) I got to the ASIO config screen.
Samplerate was set to 48000Hz in the window.
Could not select inputs or outputs (got the same screen as D-Fusion)
Set Midi I/O Ok, then I get a message
"Couldn't set preferred ASIO samplerate 44100Hz => Current Samplerate = 48000Hz"
Click on OK and MU-LAB comes up with the Sequence and Racks screen, then crashes.
(MULAB.exe has encounteres a problem and needs to close....)
On subsequent runs, MU-LAB will always come up with the samplerate error, then crash.
Hmm... Just noticed that while it had crashed, it had not terminated completely.
I ran the app several times, now looking at the Task Manager, I have multiple instances of MULAB.EXE and DrWtsn32.exe in the processes list. Trying to end the processes does not remove them from the process list. *must* reboot
Just rebooted, then started MU-LAB. Got the same behaviour, and still could not remove MULAB.exe from the process list.
Another reboot required.
Ah well, back to Beta A
Cheers
I'm using a Windows XP machine, with an Audigy 2ZS soundcard.
On the first run of MU-LAB (I had completely trashed the Beta A installation) I got to the ASIO config screen.
Samplerate was set to 48000Hz in the window.
Could not select inputs or outputs (got the same screen as D-Fusion)
Set Midi I/O Ok, then I get a message
"Couldn't set preferred ASIO samplerate 44100Hz => Current Samplerate = 48000Hz"
Click on OK and MU-LAB comes up with the Sequence and Racks screen, then crashes.
(MULAB.exe has encounteres a problem and needs to close....)
On subsequent runs, MU-LAB will always come up with the samplerate error, then crash.
Hmm... Just noticed that while it had crashed, it had not terminated completely.
I ran the app several times, now looking at the Task Manager, I have multiple instances of MULAB.EXE and DrWtsn32.exe in the processes list. Trying to end the processes does not remove them from the process list. *must* reboot
Just rebooted, then started MU-LAB. Got the same behaviour, and still could not remove MULAB.exe from the process list.
Another reboot required.
Ah well, back to Beta A
Cheers
-
- KVRist
- 93 posts since 8 Dec, 2005
Hi Jo,
Here's something I encountered. I tried to open Mu.Lab and do a MIDI recording.
So, 1. I can't seem to set it up so that the MIDI controller is playing through a certain rack without generating a sequence part. If I just click in the upper right where the rack selection is to occur, nothing happens.
Next: If I don't select a rack, then when I hit the record button, the record button lights up and so does the play button.
If I then hit my MIDI keys and then hit the record button again (presumably to stop recording), then it asks for a name for the recorded sequence, but then when I enter one and hit Enter, it just keeps playing and no sequence is persisted.
However, if I start the recording and then hit the play button to stop the playing, it asks for the name and then it persists the sequence.
Note, the second time I hit record to stop the recording, it seems to persist the sequence.
Edit: actually I am not quite sure what the trigger is. When I tried turning on a loop and then recording while it was looping, then I was able to get multiple parts to fail to appear (there was no rack selected but it was playing on the rack that was last used). Strangely, the parts were playing, they just didn't appear in the part view. Then the notes all hung and I had to reset the real-time engines.
Note, I was using CM-101.
Another comment: I think that when you call 'Duplicate Sequence', it should automatically change the name of the sequence (e.g., if the original sequence was "foo", then the name of the duplicated sequence should be changed to "foo(1)" or something like that). Changing the color would be good too. That way it becomes clear that the duplicated sequence has been severed.
I noticed that FL Studio 7 apparently has a way to "select all similar parts" which would, I suppose, automatically highlight all the parts that are copies of a given part (i.e., not duplicated).
Edit 2:
The disambiguation is particularly important when you're using the functionality of the drop-down box below the rack selector to "change" the sequence part that is selected, since if there are multiple sequences with the same name, there is no way to select between them in that drop-down box except trial and error.
Also, it does not seem to be possible to instantiate a sequence part directly from that drop-down box; rather, you have to be operating on an existing sequence part, right?
Further comment: on a short note in the MIDI editor, I can only get the "left" pencil to edit length to the left, rather than also getting the "right" pencil to edit to the right.
Here's something I encountered. I tried to open Mu.Lab and do a MIDI recording.
So, 1. I can't seem to set it up so that the MIDI controller is playing through a certain rack without generating a sequence part. If I just click in the upper right where the rack selection is to occur, nothing happens.
Next: If I don't select a rack, then when I hit the record button, the record button lights up and so does the play button.
If I then hit my MIDI keys and then hit the record button again (presumably to stop recording), then it asks for a name for the recorded sequence, but then when I enter one and hit Enter, it just keeps playing and no sequence is persisted.
However, if I start the recording and then hit the play button to stop the playing, it asks for the name and then it persists the sequence.
Note, the second time I hit record to stop the recording, it seems to persist the sequence.
Edit: actually I am not quite sure what the trigger is. When I tried turning on a loop and then recording while it was looping, then I was able to get multiple parts to fail to appear (there was no rack selected but it was playing on the rack that was last used). Strangely, the parts were playing, they just didn't appear in the part view. Then the notes all hung and I had to reset the real-time engines.
Note, I was using CM-101.
Another comment: I think that when you call 'Duplicate Sequence', it should automatically change the name of the sequence (e.g., if the original sequence was "foo", then the name of the duplicated sequence should be changed to "foo(1)" or something like that). Changing the color would be good too. That way it becomes clear that the duplicated sequence has been severed.
I noticed that FL Studio 7 apparently has a way to "select all similar parts" which would, I suppose, automatically highlight all the parts that are copies of a given part (i.e., not duplicated).
Edit 2:
The disambiguation is particularly important when you're using the functionality of the drop-down box below the rack selector to "change" the sequence part that is selected, since if there are multiple sequences with the same name, there is no way to select between them in that drop-down box except trial and error.
Also, it does not seem to be possible to instantiate a sequence part directly from that drop-down box; rather, you have to be operating on an existing sequence part, right?
Further comment: on a short note in the MIDI editor, I can only get the "left" pencil to edit length to the left, rather than also getting the "right" pencil to edit to the right.
-
- Banned
- 897 posts since 8 Jan, 2005 from Detroit
i was able to open the program this version, had no problems at all. btw, my plugin folder was empty last time. this time too.
however, once i stopped the the demo project, i couldnt start it again. i could do everything but start the sequencer once it was stopped.
however, once i stopped the the demo project, i couldnt start it again. i could do everything but start the sequencer once it was stopped.
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
On windows, there indeed is a bug when you try to select the asio inputs or outputs.
You don't see any ins or outrs to select, and the result is also that no ins and outs are effectively selected and thus that's why there is no sound
This is a new bug caused by the change in the asio setup handling.
A beta B2 patch is on its way to resolve this, arriving later today.
You don't see any ins or outrs to select, and the result is also that no ins and outs are effectively selected and thus that's why there is no sound
This is a new bug caused by the change in the asio setup handling.
A beta B2 patch is on its way to resolve this, arriving later today.
-
- KVRian
- 529 posts since 7 Apr, 2003 from Nashville
I did a clean install of Mu.Lab beta B. I didn't test it very hard, but I got good audio. I noticed when using ASIO4All audio driver I couldn't get the control panel button in the audio setup window to function. FreeAmp 2 loads but if a few notes are played it seems to crash Mu.Lab beta B's audio, just like it did in beta A. As with beta A, beta B couldn't read keFIR v.1, Loopitch, WaveThresh, Synchro, Eclipse, PanGloss, AlienArtifact, or ReValver 2.
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
Johnny, can you please do this:johnny2johnny wrote:Hey Jo, still having an audio problem over here on os x.... and rapture, has no gui, and pluggo plugs can not move dials on gui, and still can not create predator vst, and nomad factory liquid bundle...
1) quit mulab (if it's up)
2) goto mulab/settings folder and open mulab.txt in TextEdit
3) If you see a line "Logging=0", make it "Logging=1". Else add such line "Logging=1"
4) save the text file and restart mulab
5) then quit and email me the newest Log-yyyymmdd-hhmmss.txt that you'll see in your mulab folder
I've added extra logging info in the osx version so we should get more info than the first time we did this.
This should reveal the reason why the audio engine doesn't want to start.
Also emailed you about this.
Thanks.
-
- KVRAF
- 5180 posts since 13 Jul, 2004 from Earth
Hi Jomuzycian wrote:On windows, there indeed is a bug when you try to select the asio inputs or outputs.
You don't see any ins or outrs to select, and the result is also that no ins and outs are effectively selected and thus that's why there is no sound
This is a new bug caused by the change in the asio setup handling.
A beta B2 patch is on its way to resolve this, arriving later today.
I managed to get sound out of it
On page 1 i wrote down 2 bugs i found in Beta B that i hope you can look into
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Also on page 1, I said I'd not got the beta email... 
-
- KVRian
- 1372 posts since 21 May, 2004 from Serbia
I managed to get sound too, by editing the AudioSetup.txt in the Settings folder.
-
- KVRist
- 48 posts since 3 Oct, 2004 from California
i was wondering the same thing, until i noticed that beta b was posted to the same URL that was given in the beta a Email. I hope we're all still in, cuz im bustin my balls lookin for bugspljones wrote:Mmm... is my email not working or is this a very closed group?
and havin fun doin it lol -
- KVRAF
- 25015 posts since 12 Jul, 2003 from West Caprazumia
I don't know if this really is a bug but I can say for sure that it really bugs me:
if the pencil tool is in use, switching from the compossr to the midi-editor or from the midi-editor to the composer, automatically switches to the selection tool.
if the pencil tool is in use, switching from the compossr to the midi-editor or from the midi-editor to the composer, automatically switches to the selection tool.