sampler DISCOVERY

[gakto2009]

couldn't find any consumption specs for the u46mkii or the western digital passport drive. I found the specs for the padkontrol and the vci-100

each one is about 150mA
if we assume that the u46mkii is 150mA
and the passport is 150mA

add all those up and we have 600mA
100mA more than the 500mA output of the USB bus.

Power Specifications
- Power consumption: 2.5W (Typical)
- USB Bus powered (500mA Maximum) and DC +9V/500mA Adapter support

[taboo]

hmmm.. i think i need to add a point here... i use the firewire to my soundcard w/o power adaptor and have also connected the mpd24 via usb that generates the power from the laptop as well... could this be the reason for me as well? well i will most certainly test it out tomorrow. with power adapter that is.

BUT..

ive noticed that the sampler "over-all" have latency. but the latency i have in my occassion is when i send a small sample from a channel to the sampler in order to make an effect. u guys speaking of glitches and drop-outs... well in my case it basically freezez for say 1 sec. major in my opinion...

any1 have an idea?

[gakto2009]

I don’t think power is the issue here; none of my MIDI devices run from usb, apart from the M-Audio MIDI interfaces its self. My Edirol FA-101 is powered by the mains (mainly because the laptop won’t power it via 4 pin firewire) and used as a MIDI interface also.

The problem gets worse for me the greater the latency is...

Anyone interested in doing some proper tests and following through with some feedback?

[Macgyver]

okay so more testing yet again.

been using the kernel driver to control the soundcard in mxvibes.
have experienced 2 crashes 1 each night where mixvibes just stops.. no sound... and then a window comes up saying mixvibes encountered error or something like that. i suspect it has something to do with me using the kernel as the soundcard driver, i don't know though.. but thats really the only variable that was changed but i really dont know what the cause of it is plus i never really experienced crashes with mxivibes like that.. rare occasions but none where the sound completely stopped like that.

interesting... any thoughts???



but on to what i really came in to talk about.
after putting the driver back to the u46 driver in mixvibes. i opened up the media base ive been using for the last few days to do my testing. i'm hitting the cue button repeatedly on the Vestax... cpu use goes up drastically..i found it strange since it was the 1st song and mixvibes was being started fresh.

well it seems that if i open a media base and load in a song into the player that is not within that media base then mixvibes becomes sluggish and cpu usage increases a lot. while pulling any song from the media base so far... there is no real increase in cpu usage...everything stays under about 30%.

sounds like this may be a bug in mixvibes???.

used songs from the media base and the korg padkontrol.. and usage still didn't get higher than 30% really.

[Macgyver]

last weekend i gave everything a LIVE run. (i was crossing my fingers, praying, & hoping) I had a few backup measures in place in case anything went wrong. Luckily I didn't have to resort to any of them.

Using my "super light setup" as described earlier in this thread.

Everything worked as desired.

There was only one time where there was a slight problem. That was when I searched for a song outside of mixvibes. Although the actual song was scanned into the media base, the fact that i loaded it into the player from outside of mixvibes (i dragged the file from a windows explorer folder). At this point Producer began getting bogged down. so now from within Producer i loaded the same song into the player and all was fine. Defnitely a bug in Producer

Korg padkontrol worked well. There were some instances where multiple rapid MIDI commands from both the vci and the padkontrol caused some delays or a command not being completed.

I opted not to use the kernel as the driver and I had no crashes as I had been having earlier in the week when i did testing using the kernel. I used the u46mkii driver for this performance.