Output Portal, how to fix Pan

Discussion in 'Software' started by Hareesh S, Mar 27, 2021.

Tags:
  1. clone

    clone Audiosexual

    Joined:
    Feb 5, 2021
    Messages:
    6,971
    Likes Received:
    3,046
    I would doubt there is any difference in behavior with the paid version.
     
  2. justwannadownload

    justwannadownload Audiosexual

    Joined:
    Jan 13, 2019
    Messages:
    1,298
    Likes Received:
    836
    Location:
    Central Asia
    I found the solution.
    Go into C:\ProgramData\Output\Portal\Presets
    Browse the preset packs folders. "001 STRETCH & SMEAR", for example. See anything suspicious yet? Yeah, this is not a coincidence, I assure you.
    Delete the "originals". Rename "****.xml.back" to "****.xml". Might backup the whole folder somewhere else prior to that, just in case.
    Do this with all folders.
     
    • Winner Winner x 2
    • Like Like x 1
    • Love it! Love it! x 1
    • Useful Useful x 1
    • List
  3. uladzislau

    uladzislau Producer

    Joined:
    Sep 29, 2018
    Messages:
    176
    Likes Received:
    109
    Wow, you're a legend! It fucking works! @Hareesh S mark his comment as best answer. This bug is now SOLVED. :chilling:

     
    Last edited: Jul 13, 2021
  4. Hareesh S

    Hareesh S Producer

    Joined:
    Dec 26, 2019
    Messages:
    236
    Likes Received:
    87
    Ohh shit! Thanks a lot man!
     
  5. DoubleTake

    DoubleTake Audiosexual

    Joined:
    Jul 16, 2017
    Messages:
    2,245
    Likes Received:
    1,213
    Typical sloppy work - LOL
     
  6. emdebee

    emdebee Member

    Joined:
    Nov 27, 2021
    Messages:
    11
    Likes Received:
    10
    Best Answer
    For the Windows v1.0.1 release with the messed up presets... I have a much easier solution (I spent way too much time trying to weed out the dodgy presets and duplicates - what a mess) :winker:

    Grab the latest Mac - Output Portal release v1.0.4

    Open the included pkg file with 7-Zip then navigate as below... You'll find virgin, unadulterated factory presets at the end of the rabbit hole.

    Portal_OSX_1.0.4R1537.pkg\Output.pkg\Payload\Payload~\.\Application Support\Output\Portal\

    Delete all folders in C:\ProgramData\Output\Portal (Documentation, Presets and SubPresets) then replace with the ones from above - may as well delete local.db as well - this gets regenerated. Don't forget to backup any added preset banks before deleting the folders - then add them back afterwards once the clean preset folders from the OSX install have been put in place.

    Sorts out ALL of the issues with dodgy presets and the endless duplicates etc... Easy peasy :wink:
     
    Last edited: Feb 23, 2022
    • Winner Winner x 2
    • Love it! Love it! x 1
    • List
  7. Dildo Baggins

    Dildo Baggins Kapellmeister

    Joined:
    Nov 22, 2019
    Messages:
    114
    Likes Received:
    50
    Never mind panning, I can't get the preset packs to show up in Portal.
     
  8. justwannadownload

    justwannadownload Audiosexual

    Joined:
    Jan 13, 2019
    Messages:
    1,298
    Likes Received:
    836
    Location:
    Central Asia
    Thank you very much! I tried to clean it up manually but gave up when I noticed that some of the differently named presets are actually the same. Unortunately the built-in distortion FX still crackles like hell in FL Studio regardless of the settings. I didn't actually expect it to change tho.

    Are you sure they are in the right folder and it has read permissions? It should be C:\ProgramData\Output\Portal\Presets
     
  9. Dildo Baggins

    Dildo Baggins Kapellmeister

    Joined:
    Nov 22, 2019
    Messages:
    114
    Likes Received:
    50
     
  10. paracosm

    paracosm Newbie

    Joined:
    Jul 13, 2023
    Messages:
    1
    Likes Received:
    0
    I found the problem in the .xml files of the affected presets (located in C:\ProgramData\Output\Portal\Presets\), if you search for "<Connections>", you should find a line that says exactly that right below a line that says "
    </Node_Properties>". Now below the <connections> line, the first two connections should normally route each stereo channel to the respective output, but in the affected files this is not the case, instead, the first Connection in the affected files says
    HTML:
    <Connection SourceNode="MKUOutputBus_MainOutput" SourceChannel="AudioOut1" DestinationNode="AudioOutputNode" DestinationChannel="1"/>
    .

    If you change this line to
    HTML:
    <Connection SourceNode="AudioInputNode" SourceChannel="0" DestinationNode="MKUInputBus_MainInput" DestinationChannel="AudioIn0"/>
    , it should work perfectly again.
     
Loading...
Loading...