Quick Sign In:  

Forum: Old versions

Topic: vdj 5.0.6 pitch bug with bcd 2000 Mapper 3.2 [SOLVED]

This topic is old and might contain outdated or incorrect information.

I found a bug with vdj 5 rev 6 and BCD mapper:

If you let the pitch range to 33% and have the right config (BCD 2000 as sound card in sound config) it's oK. If you change the pitch range in the Options Settings to any other (new) value, the pitch fader doesn't move properly when you move the pitch fader on the BCD. I suspect a mapper problem because when you change the pitch with the mouse it works fine.

My configuration:
- IBM Thinkpad T60 Core Duo 1.8 Ghz - 2Go RAM - 100 Go Dasd
- Window XP sp2
- VDJ 5 Rev 6
- BCD Moramax Mapper 3.2
- BCD 2000 in ASIO Mode 4ms Latency (As Moramax recommend)
- BCD Mapper 1.0.0.6 Firmware 1.3 , USB Driver 1.1.1.0 , ASIO Driver 1

My Sound Settings :


My Remote Ctrl Settinbgs:


My Option Settings - Here it works fine. Problem occurs when the pitch range is changed to another value than 34% :


My Performance Settings:
http://fred.barre33.free.fr/Vdj%205%20Rev6%20bcd%20Mapper%2032/Cfig%20Perf%20Cfig%20Bug%20Pitch%20Fader%20vdj%20V5%20rev6.JPG" border="0">

The BCD mapper Configuration:


Note that the problem occurs for each pitch range value when the sound cards is set as ASIO in place of BCD. In this case, even with 34% pitch range the Fader doesn't change when you move the bcd pitch fader. This setting is like:


This problem looks solid, I suppose it could be reproduced easily (with a BCD 2K of course).
 

Posted Wed 05 Dec 07 @ 7:40 pm
moramaxPRO InfinitySenior staffMember since 2005
yes i know the problem...i'm working on to fix it.
the update will be available soon.
 

Posted Thu 06 Dec 07 @ 12:56 am
moramax wrote :
yes i know the problem...i'm working on to fix it.
the update will be available soon.


Thx Moramax for your quick answer. I hope it would not be too much complex.
 

Posted Thu 06 Dec 07 @ 2:55 am

I just downloaded the 3.3 Mapper. The pitch problem looks fixed (I tested 6%, 8%, 33%). I did some non regression tests which are ok.
I consider this issue as closed and the problem fixed.
 

Posted Fri 14 Dec 07 @ 8:33 am


(Old topics and forums are automatically closed)