Forum Replies Created

Viewing 15 posts - 1 through 15 (of 34 total)
  • Author
    Posts
  • in reply to: Welcome W10, goodbye Breakaway #14189
    powerjam
    Member

    I've had 2 major crashes in the last month since upgrading from Windows 8.1 to Windows 10. Funny, Windows 8.1 worked just fine with BDJ for over a year! Now I'm 99.9% sure my crashes are being caused by Breakaway.

    I hope Breakaway DJ comes out with a Windows 10 compatible update soon. After analyzing my crash report it definitely looks like Breakaway DJ (Audio Enhancer) IS causing the problem. Here's the report:

    n Sat 11/28/2015 5:28:00 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\112715-28203-01.dmp
    This was probably caused by the following module: vaclcskd.sys (vaclcskd+0x5BCC)
    Bugcheck code: 0x139 (0x21, 0xFFFFD00188646520, 0xFFFFD00188646478, 0x0)
    Error: KERNEL_SECURITY_CHECK_FAILURE
    file path: C:\WINDOWS\system32\drivers\vaclcskd.sys
    product: Breakaway Pipeline
    company: Eugene V. Muzychenko
    description: Kernel-mode WDM driver
    Bug check description: The kernel has detected the corruption of a critical data structure.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: vaclcskd.sys (Kernel-mode WDM driver, Eugene V. Muzychenko).
    Google query: Eugene V. Muzychenko KERNEL_SECURITY_CHECK_FAILURE

    in reply to: BSODs caused by Breakaway Audio Enhancer driver on Windows 10 #5630
    powerjam
    Member

    Windows 10 crashed again and locked up, restarted automatically and started doing windows 10 updates during my gig. I was livid. Of course I had a backup ready to go, but it was very embarrassing and frustrating. This is the 2nd time in a month windows 10 locked up on a very high end laptop that ran perfect with all the same software on Windows 8.1 (including Breakaway DJ).

    I am rolling back to Windows 8.1 today.

    in reply to: Welcome W10, goodbye Breakaway #14188
    powerjam
    Member

    My version of this is Goodbye Windows 10, hello Windows7. I have had multiple issues with Windows 10 and not entirely sure any were a Breakaway problem. I am hoping Breakaway (DJ version is what I use) will be updated soon!

    in reply to: BSODs caused by Breakaway Audio Enhancer driver on Windows 10 #5629
    powerjam
    Member

    Good to hear about the new build. Thanks, Milky!

    I actually have figured out why my system crashed in Windows 10…I'll copy and paste from my OtsUsers post in Facebook:

    I am using a Denon MC6000 that is incompatible with OtsAV due to the DAC 24 bit I believe. I use Breakaway DJ to bridge the gap between the MC6000 and OtsAV and it has been rock solid for years doing it that way.

    The actual cause of the crash I do believe I have discovered a workaround…It is related to Breakaway, and it stems from the way I was booting the laptop. IF I booted the laptop before plugging in the MC6000 controller Ots would have no sound usually even if I plugged in the controller after the laptop was booted and before starting Ots. Then all I would do is go into Breakaway and go to I/O configuration and then make sure the controller was selected as the sound device and then go back out of it.

    This was successful previously if this happened and seemed to work in Windows 10 also. BUT after an hour or so, windows would blue screen in Win 10 when I did this.

    Now I've found that if I make sure everything is plugged in, especially the controller, then everything works normally, I can do practically anything I want on the laptop, run my DMX controller, play ED video mode and even surf the internet with 10 tabs open and have my Antivirus turned on. No lags, no delays, no crashes and maybe 10-11% cpu use, most cpu use is caused by Google Chrome tabs, more than what Ots AV video and breakaway use.

    So, even though it says on their website that Breakaway doesn't work with Windows 8 or 10, I've been having great success using it as long as I boot up with the controller/sound card plugged in at boot time.

    in reply to: BSODs caused by Breakaway Audio Enhancer driver on Windows 10 #5627
    powerjam
    Member

    I'm guessing my last BSOD is related to Breakaway DJ, as my system was rock solid prior to the windows 10 upgrade, but this is not proven. But reading the posts that Windows 10 is not compatible with Breakaway products is a pretty good giveaway, I'm just confused at how my BDJ worked for over a year just fine with my same laptop with Windows 8.1.

    in reply to: Windows 10 compatible version… #5638
    powerjam
    Member

    I was using Breakaway DJ with Windows 8.1 for at least a year with no problems, then upgraded the laptop to Windows 10 and now I got one random BSOD in about 2 months of using Windows 10.

    PLEASE give us a compatible version, now I have an unreliable machine. Nothing like your machine crashing and rebooting in the middle of a gig.

    THANK YOU!!!!

    in reply to: Breakaway DJ – Device Does Not Support Requested Format #9738
    powerjam
    Member

    Any luck on 24-bit support? Haven’t heard from you in years! But I’m still recommending your products. Reason I’m wondering is because I still have the Echo Indigo DJx sound card with my newer Win7 laptop and I wanted to use another program alongside my main DJ program, but using Asio, it won’t let me play 2 different applications at once, I tried to use WDM driver and get the same message in BDJ that Device does not support requested format (44100hz, 2 channels, 16 bits.) so I can’t run both apps through BDJ. Thanks, Leif.

    in reply to: Breakaway DJ #9590
    powerjam
    Member

    Just have to say that I have been using Breakaway DJ for gigs for the last couple of months and it has made the sound of my system much better. And basically have had no problems, so that’s excellent for what was a Beta release!

    I had an issue last week where after booting the computer then starting my OtsAv, the Asio driver for BDJ was not recognized so I had to restart OtsAV, then when I did that it saw the Breakaway Asio driver, but everytime I typed in the Ots search bar the audio would slow down and glitch. So I switched to my backup laptop for a song (and wow what a difference in sound – I don’t have BDJ on the other laptop!) – then I had to close down breakaway, unplug my Echo DJx card, plug it back in, then restart BDJ and then finally OtsAV and it was fine after that. There must be some time of initialization that has to be done at startup for it to work properly. I guess I have to be more patient after logging in before starting OtsAV.

    in reply to: Breakaway DJ – Device Does Not Support Requested Format #9737
    powerjam
    Member

    Oh wow – good luck with your moving, Leif. You are a busy guy. If you can do 24-bit support better yet for all! Thanks!

    in reply to: Breakaway 1.30.02 with transparent toolbar for Windows Aero! #5058
    powerjam
    Member

    Darwin, just a quick question, did you increase the buffer/sample size settings at all and test it, sometimes installing new software makes your cpu work harder and requires a higher buffer setting to run with the same quality.

    in reply to: Breakaway DJ #9569
    powerjam
    Member

    For my headphone use, I really like the Zenith setting also – using ATH-m50 cans. I did adjust the bass boost up and the bass shape down though.

    in reply to: Breakaway DJ – Device Does Not Support Requested Format #9735
    powerjam
    Member

    [quote author=”Leif”]I’m starting to realize then need for BDJ PRO, which should support line inputs, four decks, and TCV. Will look into it 🙂.

    ///Leif[/quote]

    If anyone can do it, I know you can. I can’t believe how awesome BDJ already is in terms of low latency for live use with video.

    Maybe you should really consider adding 24-bit support while you’re at it. Although, it is more of a compatibility issue more than a necessity because 16-bit doesn’t sound good enough. The Echo Indigo DJx seems to be a very good audio card and you may be getting more customers wanting the 24-bit support too?

    That said, here is an excerpt from my Indigo DJx owner’s manual regarding 24-bit, what do you think of this?

    Appendix B: An Introduction to Digital Recording
    Converting Sound into Numbers
    In a digital recording system, sound is represented as a series of numbers, with each number representing the voltage, or amplitude, of a sound wave at a particular moment in time. The numbers are generated by an analog-to-digital converter, or ADC, which converts the signal from an analog audio source (such as a guitar or a microphone) connected to its input into numbers. The ADC reads the input signal several thousand times a second, and outputs a number based on the input that is read. This number is called a sample. The number of samples taken per second is called the sample rate.
    On playback, the process happens in reverse: The series of numbers is played back through a digital-to-analog converter, or DAC, which converts the numbers back into an analog signal. This signal can then be sent to an amplifier and speakers for listening.
    In computers, binary numbers are used to store the values that make up the samples. Only two characters, 1 and 0, are used. The value of a character depends on its place in the number, just as in the familiar decimal system. Here are a few binary/decimal equivalents:
    BINARY DECIMAL
    0000000000000000 0
    0000000000000001 1
    0000000000000011 3
    0000000000000111 7
    0000000000001111 15
    0000000000011111 31
    1111111111111111 65,535
    Figure A. Binary numbers and their decimal equivalents
    Each digit in the number is called a bit. The binary numbers expressed in Figure A are sixteen bits long, and have a maximum value of 65,535. The more bits that are used to store the sampled value, the more closely it will represent the source signal. In a 16-bit system, there are 65,535 possible
    31
    combinations of zeroes and ones, so 65,535 different voltages can be digitally represented. (see Figure A above).
    [attachment=0:2sc4xruh]echo24.jpg[/attachment:2sc4xruh]
    Figure B. The more bits there are available, the more accurate the representation of the signal and the greater the dynamic range.
    Your Echo card’s analog inputs use 24-bit ADCs, which means that the incoming signal can be represented by any of over 16 million possible values. The output DACs are also 24-bit; again, over 16 million values are possible. Your Echo card processes signals internally with 24-bit resolution to insure that there is no degradation to the audio signal as it is processed through the system.
    The number of bits available also determines the potential dynamic range of the device. Moving a binary number one space to the left multiplies the value by two, so each additional bit doubles the number of possible values that may be represented. Each doubling of the number of values provides 6dB of additional dynamic range (see decibel section below). So, a 24-bit system can theoretically provide 144dB of dynamic range (6dB times 24 bits = 144dB) versus a 16-bit system with a maximum dynamic range of only 96 dB.
    Also important to the quality of a digital recording is the frequency with which the samples are stored, called the sample rate. In order for a waveform to be faithfully digitized, it must be sampled at a minimum of twice the highest frequency to be stored. Failure to sample frequently enough results in a kind of distortion called aliasing. (If you like technical issues, do some research on The Nyquist Theorem which explains why this
    32
    happens). In addition to aliasing, sampling too slowly will result in reduced high frequency reproduction. Your Echo card allows you to sample sound at up to 96,000 times per second.
    Once the waveform has been transformed into digital bits, it must be stored. When sampling in stereo at 96kHz using a 24-bit word size, the system has to accommodate 4,608,000 bits per second. In the past, storing this vast amount of data was problematic. Today, computer-based digital recording systems record the data directly to the computer’s hard disk. Today’s hard disks are capable of storing large amounts of data, though the performance of hard drives can vary substantially. The speed and size of your hard drive will be a major determining factor in how many tracks of audio you will be able to simultaneously record and playback.

    in reply to: Breakaway DJ – Device Does Not Support Requested Format #9734
    powerjam
    Member

    Are you done yet? 😆

    in reply to: Breakaway DJ – Device Does Not Support Requested Format #9732
    powerjam
    Member

    [quote author=”Leif”]Wouldn’t work very well, as the microphone would then end up mixed with one of the decks. There’s no easy solution to this, which is why I kept mic processing out of Breakaway DJ completely.

    The ultimate solution would be to run Breakaway Live on a separate machine, connected AFTER the mixer. That way, everything would be processed together, including the microphone.

    ///Leif[/quote]

    Leif, all I’m asking for is 1 line input that can be mixed with the signal 🙂 I would like to be able to play a turntable or other input from an external mixer through breakaway along with whatever audio program I’m running on the laptop. It seems excessive to have to have a whole other computer in my setup just to do this, wouldn’t it just be mixing the signal prior to processing it with BDJ? It seems it shouldn’t be that hard, but I am not doing your work! Just run a virtual patch cable from the input to the BDJ interface?

    in reply to: Breakaway DJ – Device Does Not Support Requested Format #9727
    powerjam
    Member

    Awesome, then don’t worry about the 24-bit for the wdm driver, it sounds great in Asio. I just thought it would work with the kernel streaming driver mode also. What about running the stereo mic/line input from the internal soundcard on the laptop through BDJ also while playing OtsAV so I could process the mic input? Can I use the breakaway pipeline configuration? Thanks again.

Viewing 15 posts - 1 through 15 (of 34 total)