Muzys "weird stop"
-
- KVRer
- 3 posts since 25 Nov, 2011
Dear Sirs,
I'm using the sequencer Muzys v1.5 & v3.0, with the interface Tascam US 144, in Windows XP (32 bits) Profesional 2002 SP2, in a Pentium 4, clock 2.8 Ghz, RAM 1 Gb, USB 2.0 port, and the US 144 driver v2.00 and the firmware v1.12, and I have the following problem:
When it's reproducing a MIDI sequence, stops every 20 minutes approximately and when starts again launch sequence with a super fast tempo gradually lowering to the original value. What can be happening?
I have tried the 5 options of Latency in the Audio Performance settings and the 5 options of audiostream buffersize in the Muzys audio hardware settings, with no success.
Then, I tried to do some test and I realized that the problem is the sequencer Muzys v1.5 and v3.0, because the Fruity Loops v7 don't do that weird "stop". I search the Computer Muzys official website without luck... Do you have any clue about that issue? Why a sequencer stops that way and the other doesn't?
Your help will be really appreciated.
Thank you very much in advance.
Kind regards,
Renzo[/b]
I'm using the sequencer Muzys v1.5 & v3.0, with the interface Tascam US 144, in Windows XP (32 bits) Profesional 2002 SP2, in a Pentium 4, clock 2.8 Ghz, RAM 1 Gb, USB 2.0 port, and the US 144 driver v2.00 and the firmware v1.12, and I have the following problem:
When it's reproducing a MIDI sequence, stops every 20 minutes approximately and when starts again launch sequence with a super fast tempo gradually lowering to the original value. What can be happening?
I have tried the 5 options of Latency in the Audio Performance settings and the 5 options of audiostream buffersize in the Muzys audio hardware settings, with no success.
Then, I tried to do some test and I realized that the problem is the sequencer Muzys v1.5 and v3.0, because the Fruity Loops v7 don't do that weird "stop". I search the Computer Muzys official website without luck... Do you have any clue about that issue? Why a sequencer stops that way and the other doesn't?
Your help will be really appreciated.
Thank you very much in advance.
Kind regards,
Renzo[/b]
-
- KVRAF
- 2323 posts since 4 Mar, 2004 from Portugal (Lagos)
Had no idea that there was someone still using Muzys
after its saga. Anyway, I don't use it for 8 years or something; by that time I was using a Terratec DMX 6 Fire on an Athlon XP, 2 gb, and never ever had a glitch using midi. Probably it gets short of Ram.
Eventually something intelligent will appear written here. Watch this space.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
I also can't remember any such issue. So far i can remember, Muzys was/is very stable. Unfortunately, Muzys is not under my control anymore, and so i can't give further support on it. Maybe try MuLab, which is the completely rebuild reincarnation of Muzys. It's not the same, but very alike, and MuLab can do a lot more than Muzys. More info on http://www.mutools.com
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
To ECHO Jo.... Try MuLab. Give yourself a gift for ChristmasRenzo wrote:thanks for your help and time, folks! anyone have another suggestions? regards, R
ABEFLGMOPPRRST 
-
- Banned
- 897 posts since 8 Jan, 2005 from Detroit
are you able to monitor cpu/ram usage while it happens? it sounds like a buffer is filling up then purging/catching up to current point in sequence, since all midi is dispatched on a time line.
if you want support, definitely use something current like mu.lab. theres still advantages to muzys if you ask me. but in different areas than mu.lab. mu.lab doesnt have any arrangement tools yet.
if you want support, definitely use something current like mu.lab. theres still advantages to muzys if you ask me. but in different areas than mu.lab. mu.lab doesnt have any arrangement tools yet.
