TPro freezes with vci-100
Results 1 to 9 of 9
  1. #1
    Tech Convert
    Join Date
    Nov 2008
    Location
    Denmark, outside CPH
    Posts
    15

    Default TPro freezes with vci-100

    Hi guys

    I've got a big problem with my vci TPro setup.
    As long as the vci isn't plugged in everything is fine, wich lead me to belive that the vci might be causing this.
    The freezes are seemingly random, but it feels like it always happens when i'm really jamming out on the knobs and faders.
    The display freezes and the audio goes into a 1/1000 loop, wich isn't a very pleasant sound.
    TPro wil stay in this frozen state until i plug out the vci, at wich point, after a few ekstra seconds of buzzing, it continues playback like nothing has happened.

    I'm using TPro 1.2 ( now 1.2.2 same issue ) and The DJTT mapping with no mods.

    Any idea what is causing this?
    Thanks
    VCI 100, NI Maschine, NanoPad, Audio 8 DJ, HDJ-2000 and 2x KRK R5 PG2's

  2. #2
    Retired DJTT Moderator DvlsAdvct's Avatar
    Join Date
    Mar 2008
    Location
    New Jersey/NYC
    Posts
    4,854

    Default

    Turn off MIDI Out and see if that ends it. You might have a common bug that hasn't been fixed yet.
    It's the FAQ. Read it.

    My Mixes, Mashups and Rants

    Divided we stand
    United we fall

  3. #3
    Tech Convert
    Join Date
    Nov 2008
    Location
    Denmark, outside CPH
    Posts
    15

    Default

    so far no freezes random glitches in a small amount.. but so far it seem to work.
    thanks Dvl
    VCI 100, NI Maschine, NanoPad, Audio 8 DJ, HDJ-2000 and 2x KRK R5 PG2's

  4. #4
    Retired DJTT Moderator DvlsAdvct's Avatar
    Join Date
    Mar 2008
    Location
    New Jersey/NYC
    Posts
    4,854

    Default

    Up your latency a touch and see if the random glitch goes away. I know it's a pain in the ass without the MIDI feedback, but I don't know if there are any other options.
    It's the FAQ. Read it.

    My Mixes, Mashups and Rants

    Divided we stand
    United we fall

  5. #5
    Tech Convert
    Join Date
    Nov 2008
    Location
    Denmark, outside CPH
    Posts
    15

    Default

    yea i miss the feedback already^^
    My Dell Laptop has never realy become friends with my audio 8 so it's running at the standart latency setting with is 5.5ms at 44.1khz.
    anything higher has given major cpu spikes it the past..
    VCI 100, NI Maschine, NanoPad, Audio 8 DJ, HDJ-2000 and 2x KRK R5 PG2's

  6. #6
    Retired DJTT Moderator DvlsAdvct's Avatar
    Join Date
    Mar 2008
    Location
    New Jersey/NYC
    Posts
    4,854

    Default

    I'd up your latency to around 10ms. You won't lose anything in regards to response at all, really. Mine's at 13ms and it's perfectly fine.
    It's the FAQ. Read it.

    My Mixes, Mashups and Rants

    Divided we stand
    United we fall

  7. #7
    Tech Convert
    Join Date
    Nov 2008
    Location
    Denmark, outside CPH
    Posts
    15

    Default

    okay haven't been cue juggeling enough to really need a low latency.. but it's alway fun to push your system to it's limits^^ do you use 44.1 khz or 96.0? by the way
    VCI 100, NI Maschine, NanoPad, Audio 8 DJ, HDJ-2000 and 2x KRK R5 PG2's

  8. #8
    Retired DJTT Moderator DvlsAdvct's Avatar
    Join Date
    Mar 2008
    Location
    New Jersey/NYC
    Posts
    4,854

    Default

    I use 44.1, 96 gives me no added benefit.

    Even if you are cue juggling all the time, you aren't going to need a 5.5ms latency.

    It's fun to push your system until it breaks
    It's the FAQ. Read it.

    My Mixes, Mashups and Rants

    Divided we stand
    United we fall

  9. #9
    Tech Mentor gfocus's Avatar
    Join Date
    Nov 2008
    Location
    Austria
    Posts
    130

    Default

    Man, I was annoyed by that bug (and I did my fair share of bitching around in forums about it). I have ongoing testing to do but I think it's save to say that it doesn't happen on Macs.

    "Beat Phase Output" is one of the surest ways to reproduce this bug. Back on my windows notebook I assigned it to a led on the VCI and turned a few knobs, worked the jog wheels and Traktor froze until I plugged the VCI out (an alternative was to de/re-activate the controller it in the midi settings, but this dialog window died with TPro 1.2).

    To test my current setup, I have beat phase output for Deck A/B mapped to the sync buttons' leds (the vci's leds flicker alot, I wouldnt include this gimmick in a regular mapping) and I turn knobs like a madman.... Nothing! Almost everything works fine, no audio freeze! Just once I managed to freeze the VCI's leds. All controls still worked fine but all leds remained in a fixed state. Eventually I had to plug it out and back in to get accurate feedback about modifier states and such. But that's no problem on a mac. If I would have had an audience, it wouldn't have recognized it.

    On my windows notebook on the other hand, I would've had to restart TPro.
    Everytime you hit SYNC, an old paradigm dies a little.
    Setup: MBP 13", Audio Kontrol 1, VCI 100 1.3, Maschine, Traktor Pro 1.2.2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •