Bitwig + Arturia Pigments different versions = Mess.

Discussion in 'BitWig' started by clipper, Mar 3, 2026.

  1. clipper

    clipper Producer

    Joined:
    Aug 1, 2019
    Messages:
    201
    Likes Received:
    114
    Location:
    Málaga.
    Hi there,
    I got to come back to my desktop PC to try and finish all the projects I left behind, kind of, abandoned.

    I open a project and I find all the instances of Pigments are sounding weird, just like a sinewave. Doesn't seem to me to have used that kind of sound for what I was working on, but hey, I check all instances and I see they're all loading the preset "Welcome". So, I open with notepad++ the .bwproject file to see if there's any information about a preset I used or whatsoever. No luck. All I see is I was using VST3 and no more info, just the path where the .vst3 file is. And the version of the plugin.

    Is there any way to fix this, or, at least, anybody knows what's happening here?

    I checked that plugin version and I see that the version used was 2.0.0.747
    I check what plugin version is installed and, voilà: 5.0.2.4658
    I know pulsewave is going to scold me, but I have to say I updated this loooongggg time ago, so I wasn't aware of "different versions, different story so stay with the ones you already use".

    By the way, I have no clue of if this is happening because of bitwig or because of pigments, but I guess this is my fault because of the updating... silly me. :(
     
  2.  
  3. Melodic Reality

    Melodic Reality Audiosexual

    Joined:
    Feb 18, 2023
    Messages:
    876
    Likes Received:
    577
    Guess only fix is to install that version of Pigments elsewhere (in other folder within the same directory), so it doesn't replace newer one if they share the same name and Bitwig will hide it in redundant versions, but will probably load it just fine, if it doesn't, just move out newer version, let it scan the old one, save presets inside of old Pigments and then you can probably load those just fine in newer version later on.
     
  4. clipper

    clipper Producer

    Joined:
    Aug 1, 2019
    Messages:
    201
    Likes Received:
    114
    Location:
    Málaga.
    Thanks for the answer, Melodic Reality.:like: That's a good suggestion and I found also somebody somewhere else who had the same problem and his solution was to install version needed, load project, save presets, get rid of old version, install latest, and load saved presets into the newer version. I'm just leaving this here in case somebody else might need this info, because right now I have so many stuff to fix that I'm overwhelmed. As soon as I fix this, I'll come back to this thread to give feedback on how could I solve it.
     
Loading...
Loading...