Forum Replies Created

Viewing 15 posts - 76 through 90 (of 247 total)
  • Author
    Posts
  • MrKlorox
    Participant

    Okay, after some playing around with other virtual soundcards (Voicemeeter), I landed on one with a buffer combination that works (Voicemeeter VAIO). BAE ignores VAC-based virtual cards like Breakaway Pipeline, which is what made me think it was not intended to do this. So download Voicemeeter Banana to get the driver.

    Input: KS, “Breakaway Pipeline 1” (duh) 480, 4, 48000, 2.
    Output: KS, “VoiceMeter vaio”, 240, 4, 48000, 2.
    Audio Realtime Priority and Adaptive SRC enabled.

    I did not open a DAW and try to record from it, but I’m able to listen to it by using “Listen to this device” and it doesn’t have any noticeable latency. There’s the occasional pop, so the buffers don’t seem perfect yet.

    MrKlorox
    Participant

    I spent a while trying to get BAE to record processed audio some years back, and it seems explicitly programmed to disallow this. What you want is a feature of BreakawayOne.

    in reply to: Windows 11: BAE Keeps Closing #16886
    MrKlorox
    Participant

    Yeah, the Downloads page has the latest links. However the Home-Audio page that hosts all the BAE info contains links to the older version.


    @Milky
    , could you let Leif know this so he can update that link and reduce the number of accidental 1.40 downloads?

    in reply to: Windows 11: BAE Keeps Closing #16882
    MrKlorox
    Participant

    Nice! Also, the latest version of BAE is 1.42. This may or may not have an impact on the reliability of the virtual soundcard driver. Glad you got it sorted.

    in reply to: Windows 11: BAE Keeps Closing #16876
    MrKlorox
    Participant

    Which version do you have installed? Have you tried uninstalling and reinstalling? I just loaded it up on my Win11 laptop and it seems fine so far…

    in reply to: MPX and stereo out of phase #16873
    MrKlorox
    Participant

    This truly IS a pathetic excuse for forum software, and it makes interaction much more difficult than it needs to be without editing or DMing. It’s just not conducive to a community or any kind of deep/direct support. I agree there should be more (any) interaction from Leif.

    I say if you got a line in with Leif, and he’s responding, take that and run with it. We just request you post your solutions here once you have figured them out. Sorry this place wasn’t effective for you.

    in reply to: 3.19.43 crashing on Win 11 22H2 #16865
    MrKlorox
    Participant

    Interesting. Are you able to get into the configurator and change devices?

    You might be able to check the logs here and see if there are any clues: %localappdata%\BreakawayOne\log (C:\Users\[USERNAME]\AppData\Local\BreakawayOne\log)

    • This reply was modified 3 years, 6 months ago by MrKlorox.
    in reply to: 3.19.43 crashing on Win 11 22H2 #16863
    MrKlorox
    Participant

    Updated to 22H2 and it seems to be behaving normally after running all night. I can’t replicate this.

    Edition Windows 10 Pro
    Version 22H2
    Installed on ‎2020-‎09-‎10
    OS build 19045.2130
    Experience Windows Feature Experience Pack 120.2212.4180.0

    in reply to: 3.19.43 crashing on Win 11 22H2 #16862
    MrKlorox
    Participant

    My bad. I could have sworn I updated to 22H2 earlier in the week… I’ll look deeper on another system.

    in reply to: 3.19.43 crashing on Win 11 22H2 #16859
    MrKlorox
    Participant

    This isn’t happening here.

    Edition Windows 10 Pro
    Version 21H2
    Installed on ‎2020-‎09-‎10
    OS build 19044.2130
    Experience Windows Feature Experience Pack 120.2212.4180.0

    I remember about a year ago there was an update that messed up virtual soundcards like Breakaway Pipeline. But this is the only update I know of that affected BA1.

    Are you using the management package by chance? Mine never recovers if I manually crash it.

    in reply to: Adding Codec #16850
    MrKlorox
    Participant

    Hi. There should be a thread in this forum with links to the correct AAC codec. Let me do a quick look…

    Here’s the thread: https://ceaforum.net/?topic=stream-encoders

    There is a link on page one and page two to the same AAC codec.

    in reply to: BAE stop working suddenly #16840
    MrKlorox
    Participant

    [code]Driver Provider: Eugene Muzychenko
    Driver Date: 9/13/2020
    Driver Version: 4.64.0.11318

    I did not notice if the driver was uninstalled upon the uninstall of the broken BAE so I was wondering if somehow there was a background update to the Pipeline since it’s not version 4.31 as Milky stated above.[/code]

    If I recall correctly, there was a windows 10 update a couple of years ago that broke Ray’s Virtual Audio Cable, on which BreakawayPipeline is based. The Pipeline version included in 1.42 is the updated version (which I believe is 4.64 of VAC). I think since they’re not technically the same product, Pipeline and VAC will be using different version numbers, but I don’t know.

    All I know is I currently use BA1 with the official VAC and haven’t had this issue yet. I’ll play around with BAE and see if I can’t replicate this issue.

    • This reply was modified 3 years, 8 months ago by MrKlorox.
    in reply to: Save and restore Backup configuration #16830
    MrKlorox
    Participant

    There’s a configuration backup as well. Common> System> System Information> Bottom right.

    I believe you also need to save your presets, speaker setup (if configured), as well as your license information. As long as you’re using the same motherboard (MAC address), it should accept your license without needing to email support.

    It couldn’t hurt to backup your %localappdata%\BreakawayOne folder, but I don’t know if it’s necessary.

    in reply to: RDS – fm1/misc/rds_ps #16819
    MrKlorox
    Participant

    Nice! Leif to the rescue! Good to know that when we can’t help, Leif has our backs on some of the more obscure broadcast technicalities.

    in reply to: Brekaway One Crash #16798
    MrKlorox
    Participant

    Is Silence Sense turned on?

    Check Core> Miscellaneous> I/O> Main Input> Silence Sense

    If you have a second core configured, you can pass it through to the primary core when it detects silence. There might be a misconfiguration somehow.

    Check Core> Miscellaneous> I/O> Input 2> Input 2 Source and see if it’s trying to use a core that isn’t there or something.

    Outside of this setting, I’m not sure what else it could be off the top of my head.

Viewing 15 posts - 76 through 90 (of 247 total)