ModPlug Central

OpenMPT Development (Archive) => Bug Reports => Bug Report Archive => Topic started by: l8 on May 17, 2006, 18:36:00

Title: (support) RC2 tracker quit with error
Post by: l8 on May 17, 2006, 18:36:00
situation:

os: win xpsp2
audio: behringer bca2000
driver setup: asio

i just create new song and then load some samples, when i try to play them on keyboard, or staring song tracker quits. problem solves by selecting dx driver.
Title: (support) RC2 tracker quit with error
Post by: rewbs on May 17, 2006, 20:01:54
Can you try with the asio4all drivers?
Title: (support) RC2 tracker quit with error
Post by: LPChip on May 17, 2006, 21:47:21
Looks like your not choosing the right buffersize or wrong frequency. Try altering the settings to be like your asio card.

To help you, what soundcard do you have? brand and type preffered.

And what version of the tracker are you using? MPT 1.16? RC2? latest beta?
Title: (support) RC2 tracker quit with error
Post by: l8 on May 18, 2006, 03:42:03
Quote from: "LPChip"Looks like your not choosing the right buffersize or wrong frequency. Try altering the settings to be like your asio card.

To help you, what soundcard do you have? brand and type preffered.

And what version of the tracker are you using? MPT 1.16? RC2? latest beta?

audio interface - BEHRINGER BCA2000.

version of tracker - latest RC2.
Title: (support) RC2 tracker quit with error
Post by: rewbs on May 18, 2006, 08:46:21
Can you try with the asio4all drivers?

That way we can determine if it's some incompatibility with your ASIO driver.
http://www.asio4all.com/
Title: (support) RC2 tracker quit with error
Post by: LPChip on May 18, 2006, 10:23:25
You also might wanna try to download the latest beta and install it over your RC2 (Its required for beta to first install RC2 anyway)

I've looked into the Specs (http://www.zzounds.com/item--BEHBCA2000) and couldn't really make up how well ASIO is nativelly supported. It looks like it is, but without real specifications.

It speaks about sampling frequencies of 44.1k, 48k and 96k. I also read that transferring midi data over 48k won't work. I therefor suggest to set the bitrate setting to either 44.100 or 48.000 with 16 bits stereo sound.

I wouldn't install ASIO4ALL just yet, cus your device nativelly supports this. Also check your control panel, and set ASIO Monitoring to digital.
Title: (support) RC2 tracker quit with error
Post by: l8 on May 18, 2006, 10:35:17
Quote from: "rewbs"Can you try with the asio4all drivers?

That way we can determine if it's some incompatibility with your ASIO driver.
http://www.asio4all.com/

suggested driver works fine. but it loads my cpu 70-80% on simple 4ch oldchool mod. when i use native asio driver -  cpu load 40-50%. i know that such high cpu load depends on usb2.0 bus of my audio interface.

native driver click and pops, espesially when new pattern begins.
also strange things happen in control pannel. native panel showing 8 ms latency, and modplug window 10ms. sometimes 100ms, never the less then native control panel settings locked at 8 ms.
Title: (support) RC2 tracker quit with error
Post by: l8 on May 18, 2006, 10:42:04
Quote from: "LPChip"
I wouldn't install ASIO4ALL just yet, cus your device nativelly supports this. Also check your control panel, and set ASIO Monitoring to digital.

asio monitoring set to digital helped me! THANKS ALOT!
96khz, 32bit, 5 ms latency 20% load on classic mod. with no cliks..
but never the less, modplug  shows 10ms delay (control panel - 5ms), i think that tracker has wrong detection of latency.
Title: (support) RC2 tracker quit with error
Post by: LPChip on May 18, 2006, 11:00:59
Quote from: "l8"
Quote from: "LPChip"
I wouldn't install ASIO4ALL just yet, cus your device nativelly supports this. Also check your control panel, and set ASIO Monitoring to digital.

asio monitoring set to digital helped me! THANKS ALOT!
96khz, 32bit, 5 ms latency 20% load on classic mod. with no cliks..
but never the less, modplug  shows 10ms delay (control panel - 5ms), i think that tracker has wrong detection of latency.

Not really. 10ms is just <48 samples which in Dx produces 10ms. This screen was never altered. Its more of an indication. New people don't know what 48 samples mean. So they usually set it to max which gets a huge delay etc.

EDIT: since this not a bug, but a support issue, closing the status (on top)