Home Forums Breakaway Audio Enhancer Breakaway 1.02 RC4 – OtsAv problem fixed?

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #103
    Leif
    Keymaster

    http://www.claessonedwards.com/rc/breakaway_setup_1.02_rc4.exe

    Please give it a go and let me know what you find.

    Thanks 🙂

    ///Leif

    #4401
    pekkaar
    Member

    Hi Leif,

    I downloaded the RC4, using it for around 30 mins and it started to pop the "License issue" dialog, and puts itself into Bypass every 30 min or so — however I already purchased v1.01. The license worked fine in 1.01, and 1.02 RC2 that I also DLd and used for a few days before the RC4.

    When I try to re-register using the code I got from you for v1.01, I get an ‘Invalid License key’ message in a tooltip bubble.

    FYI, I did not change any HW component of this computer (a laptop).

    Regards,
    Peter

    #4402
    Leif
    Keymaster

    Hi Pekkaar!

    I’m sorry to hear that. My apologies — we’ve upgraded to a newer version of the licensing software we’re using — there may be an incompatibility. Please e-mail your new hardware ID to the support department – windows_system at claessonedwards dot com, and we will happily generate a new key for you. I apologize for any inconvenience.

    ///Leif

    #4403
    Anonymous
    Guest

    [quote author=”pekkaar”]Hi Leif,

    I downloaded the RC4, using it for around 30 mins and it started to pop the "License issue" dialog, and puts itself into Bypass every 30 min [/quote]

    Same here. 30 days trial is over for me.
    Sorry can’t test this version with OtsAV in case of the 30 min bypass.

    #4404
    Darwin
    Member

    I shutdown Breakway 1.02 RC2 and installed RC4. Everything went without a hitch and the About screen shows me as registered. Hope this is true 30 mintues from now! At any rate, will start testing it now.

    XP Pro Sp-3

    #4405
    Anonymous
    Guest

    What’s new in "RC4"?

    #4406
    Anonymous
    Guest

    Hi Leif!

    I run a fast (7:55h) test using KS in / KS out. It’s Ok, no dropouts.

    YES, Breakaway 1.02 RC4 – OtsAv problem FIXED.

    I’m a hobbyist DJ, playing my music in friend’s dance parties. I don’t use my system 24h/7d, but when using it, I need at least 7 h of uninterrupted sound. In the last party, yesterday, I could use it, and was successfully. My sound was great (using OTSAV DJ and Breakaway).

    The next party is only september 6. Thus, I have 2 weeks to test more settings using OTSAV and Breakaway.

    If I get any new problem, I will let you know.

    Many thanks.

    Carlos

    #4407
    Darwin
    Member

    Just to note – I *swear* this version sounds better! Anyway, swearing aside, everything has been working flawlessly so far and I haven’t encountered the de-registratrion problem 🙂

    #4408
    Anonymous
    Guest

    Hi Leif!

    My long time partial tests using Breakaway with OtsAV DJ Pro-Classic+ version 1.85.064:

    KS Input:
    KS Output – 25:00h – No dropouts
    DS Output – 22:40h – No dropouts
    Wave Output – 24:50h – No dropouts

    DS Input: This option is now available, but when selected, Breakaway don’t get sound.

    Wave Input:
    KS Output – 23:50h – No dropouts
    DS Output – Next week
    Wave Output – Next week

    Carlos

    #4409
    Anonymous
    Guest

    Hi Leif!

    Now, the lasts tests:

    Wave Input:
    DS Output – 20:20h – No dropouts
    Wave Output – 22:50h – No dropouts

    Carlos.

    #4410

    Hey Leif

    I want to test this on OtsAV. Is this version a final or a beta version though?

    Thanks

    #4411

    By George I think you’ve cracked it!

    OtsAV DJ on play for 10 hours yesterday and today and not so much as wobble let alone a 2 second cut out.

    Yes, I think the problem has been fixed! Thanks Leif.

    #4412
    Leif
    Keymaster

    Excellent!

    Finally. 🙂

    The fix will be in Breakaway 1.2, which should hopefully be released in a few days.

    We had a few licensing-related problems with 1.02, so we’ve decided to do away with the hardware-id locking once and for all. Thus, 1.02 Release Candidate went back to the drawing board, and became 1.2. 🙂

    ///Leif

Viewing 13 posts - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.