Se Connecter:     

Forum: General Discussion

Sujet: the CONSTRUCTIVE thread about BCD2000........ [VDJ 4.1 RELEASED AND WORKS] - Page: 11

Cette partie de ce topic est ancien et peut contenir des informations obselètes ou incorrectes

Thank you for that feedback, and I've read on other dj forums people are narrowing it down to same issues as you... Some faulty chip or incompatibility with motherboard chips.
It even seems that Behringer goes a long way in confirming this as they are working on better driver that will fix "chip issues" (A quote I read at some forum), so there really seem to be some driver issue going on for sure...

And even though you say "you're the first to admitt your wrong", dont worry. The feeling of being right is subjective, and I can totally see that you might have felt that way if the issues came soon in VDJ, and took a while before they surfaced in other apps.

But you seem to be on a good path of some important discovery here.... Hopefully you'll get some luck to what is needed, what chipsets are incompatible, and even some info about new drivers from Behringer (they dont reply to me anymore.. lol).

 
@ Paulheu:
I also used a PCI USB-card & same issue “But” what does help for me is using a USB2 hub strange thing I know, I guess it slows down the traffic a bit whereby the USB ship’s know how to handle the data.
As for the ASIO driver error I’ve found out that ones the performances settings are set to “Best Quality“ it is gone.
 


its a nice little video of bcd working in asio with tcv thanks to julio :)

 
You fail to get back to the original promise Native support. The sound card was not the problem in version 3.4. We don't care about time coded vinyl it does nothing to support the controller. Why have you got off track from the original promise which was native support.
 


Look at the video Digitalmdj!

It works for some already!;)

Now, Dev Team is working on the issues about it not working for all, so its being adressed as we speak
 
I had it working for a few min with the BCD asio drivers, but after changeing some options it fails again, bleh!, this was on a completely new formatted machine. I really think vdj.4.0 is a quantumleap compared to the 3.x series in all aspects, not that the BCD subject are a big matter here, I am getting other-new equipment in a few months. hopefully the bcd issues-support will be adressed in the next release.
I tried to clean out the registry for every possible things that was left by either behringer or Vdj, and do a clean install of the hw-software, but still no luck, any advice ?

 
I had all of those features working in 3.4. The problem is they are not working as designed. I would like to know why it is so hard to creat a input chanel for a mic using the ASIO drivers. You did it for the time coded Vinyl ? I wen't back to my Motu 828 it never fails. It a few years old and works better than what they have on the market now.
 
digitalmdj wrote :
You fail to get back to the original promise Native support. The sound card was not the problem in version 3.4. We don't care about time coded vinyl it does nothing to support the controller. Why have you got off track from the original promise which was native support.

Hey way you do not look the video?
The video shows you that the BCD cans work as a midi controler and an ASIO sound card for TCV using at the same time, is that too difficult to understand?


dj quintana
 
DJ-ALF

Thank you so much

@digitalmdj

Don't speak in plural, many guys are happly enjoying vdj + bcd , it's a shame that it doesn't work for you, but not everthing is because of vdj, xylio drivers are not good enough and some compatiblity with certain chips are the cause why bcd doesn't work correctly.
 
You don't see any of them here do you. It's just a few of us. Behringer sold alot of controllers and ran out of them.Where are they they won't buy something not finished twice. They need a complete solution not a work around.
 


For the LAST time Digitmdj :
- Dev Team is working on this!!!

OK?? hard to understand???

Just wait until Dev Team have looked into why it does not work for all yet
 
Correct, I am in PC industry for a long time and I saw many times hardware parts don't match together! Nothing new, but everything can be solved by a software, but it needs TIME to do it. So again, patience please.
 
Maybe we should make a cute little check box called bcd2000 that way he can complain about how he doesn't like the way its mapped. The main reason we left it midi is so end users can easily change the way its mapped without having to know C++ is that what you want digimdj? To put things in perspective you are 1 in over 5 million users and maybe 1 not happy in severl hundered thousand bcd2000 users here currently enjoying bcd2000 support from vdj. So if native means not beaing able to map the controller unless you know c++ we'll look into if that's what you want. You don't seem to strike me as the computer programmer type so be careful what you wish for.
 


Even video proof is now given that VirtualDJ4 + BCD2000 asio works great for some... ;)

Not saying all, but for some...

And for the unlucky few, Dev Team is working on things..
 
The problem with the current implementation is that it does not allow for the unit to be fully supported. You must have a way to send data back to the BCD in order for the leds to work. This not possible right now. Also, the BCD2000 can be used much more creative if you can apply multi button sequences, like pressing and holding 'buttonX' and moving the jogwheel will move the running loop forwards or backwards or in/decrease the looplenght.

While the current implementation works it's only halfway there IMO. The official word was that the BCD2000 was supported in v4, IMO this is not true as many of it's possibilities remain unavailable and all of this could have been prevented by just reading though the BCD MIDI map which is in the manual which has been available for close to a year now.

What was done is that the MIDI implementation in VDJ was brought to the level where it actually comes close to official MIDI specs and it can understand different MIDI events. This in itself is good and as a side effect allowed for the BCD to be used through a MIDI map.

That's good, but could be better. at least it would be nice to allow sending (multiple) events to a MIDI device when an event comes in. Se when a user presses play you not only start playback, you also turn the 'PLAY' led on and the 'CUE' led off (as an example). Your 'excuse' that C++ would be too hard is just silly. True, it would be for most, but that does not mean the current way it's handled is thought through or even truly tested. I doubt it would have been released if testers came back with the fact there's no way you can turn the leds on or off (which IMO would not be in the 'nice to have' category like the above example with loops is)
 

Well as you said, you have problems with the BCD2000 chip in any programs...

Hopefully that search path will be constructive news for Dev Team, if you can find out why
 
DJ Cyder wrote :
Maybe we should make a cute little check box called bcd2000 that way he can complain about how he doesn't like the way its mapped. The main reason we left it midi is so end users can easily change the way its mapped without having to know C++ is that what you want digimdj? To put things in perspective you are 1 in over 5 million users and maybe 1 not happy in severl hundered thousand bcd2000 users here currently enjoying bcd2000 support from vdj. So if native means not beaing able to map the controller unless you know c++ we'll look into if that's what you want. You don't seem to strike me as the computer programmer type so be careful what you wish for.


C++ is allowing variables to be build in so I don’t see why a kind of mapping with drop-down menus can’t be done when needed?!
 
While I will certainly be trying to figure out why I do not think it is up to me to do so. If the development team choose to support the BCD it is their job to get the needed information. If they don't or choose to not support the BCD because the problems they find that's OK because after all it's their show here..

All the sound issues aside there's still some other things relates to the BCD that should IMO be addressed, one of them being the poor way it is currently implemented as a controller. I have pointed out my issue with this multiple time now so I won't get into that again. That goes for not supporting ASIO on the mic input as well.. If you have ASIO implemented why not on the mic input?!

But I feel the phrase "Either you do or you don't" applies here, right now VDJ does 'sortof' support the BCD2000 ..
 
yes ;)


BUT AGAIN... seems not to be comming through to all....


- Dev team is currently working on why there are problems for some with the BCD2000, and hopefully will come up with a good solution very soon



PLEASE READ THAT! ;)
 
I totally agree and excuse me for saying but I find it a little insulting to the BCD users when the topic’s name suddenly changes to “PROBLEM NOW SOLVED”.
 
57%