MPL Script: mpl_Toggle solo focused FX track.lua Not quite working.

[Sound asleep]

 reaper.Undo_BeginBlock()
  local _, tracknumber = reaper.GetFocusedFX()
  local param = 'I_SOLO'
  if tracknumber >= 0 then 
    local tr =  reaper.CSurf_TrackFromID( tracknumber, false )
    local solo_state = reaper.GetMediaTrackInfo_Value( tr, param )
    reaper.SetMediaTrackInfo_Value( tr, param, math.abs(solo_state-1) )
    reaper.TrackList_AdjustWindows( false )
  end
  reaper.Undo_EndBlock('Toggle solo focused FX track', 0 )

This is the script, it sort of works, but sort of doesn't. It will solo the track, as in the solo button turns on, and everything else mutes, however, audio doesn't pass through. I noticed this in a particular routing situation. So, the track in question is in a folder, and the audio is being sent to the parent just fine, that parent is set not to send to master, but instead to a music buss, and the audio is not making it to that buss.

Unsoloing manually, and then soloing again works as expected.

[nofish]

My hunch is that SetMediaTrackInfo_Value(tr, 'I_SOLO'...) might ignore routing or some such.

May try SetTrackUISolo instead.

[Sound asleep]

Originally Posted by nofish

My hunch is that SetMediaTrackInfo_Value(tr, 'I_SOLO'...) might ignore routing or some such.

May try SetTrackUISolo instead.

Ok, sweet. So, I should replace "SetMediaTrackInfo_Value" with "SetTrackUISolo" I guess?

[nofish]

Yes, that would be my suggestion (without having tested).

[Sound asleep]

Originally Posted by nofish

Yes, that would be my suggestion (without having tested).

Ok, sweet. I'll test it out and report back.

[mpl]

it seems solo value==1 was changed to solo-in-place, so output should be multiplied to 2 or 3.

Please write all issues related to my scripts to dedicated thread at forum (see signature). Otherwise it has low chance to be fixed.

[Sound asleep]

Originally Posted by mpl

it seems solo value==1 was changed to solo-in-place, so output should be multiplied to 2 or 3.

Please write all issues related to my scripts to dedicated thread at forum (see signature). Otherwise it has low chance to be fixed.

Ok, sorry. I didn't realize you had a thread like that. Would be useful if mods stickied that one, I find it is a sticky worthy thread.

I'm not sure I see what you mean. I don't see that in the script. Is that a reaper change? I am using an older version of reaper, 5.99, is it possible that was changed in reaper 6, and your script would function correctly there?

[mpl]

changes solo switch to Solo-in-place (that was Solo (ignore routing) before, as a ==1 default value for SetMediaTrackInfo_Value)

[Sound asleep]

Originally Posted by mpl

changes solo switch to Solo-in-place (that was Solo (ignore routing) before, as a ==1 default value for SetMediaTrackInfo_Value)

Well, unfortunately I'm way too much of a programming plebe to understand exactly what you mean, however, I noticed you updated the script to 1.01 in reapack, and that works great, so thanks a lot!


I also use another of your scripts which disables all non-vsti FX

--[[
   * ReaScript Name:Bypass all FX except instruments on all tracks 
   * Lua script for Cockos REAPER
   * Author: Michael Pilyavskiy (mpl)
   * Author URI: http://forum.cockos.com/member.php?u=70694
   * Licence: GPL v3
   * Version: 1.1
  ]]
  
  -- changelog
  -- 14.01.2014 1.1 fixed wron getinstr id
  
  script_title = "Bypass all FX except instruments on all tracks"
  reaper.Undo_BeginBlock()
  
  counttracks = reaper.CountTracks(0)
  if counttracks  ~= nil then
    for i = 1, counttracks do
      tr = reaper.GetTrack(0,i-1)
      if tr ~= nil then
      
        fxcount = reaper.TrackFX_GetCount(tr)
        if fxcount ~= nil then
          for j = 1, fxcount do
            if j == reaper.TrackFX_GetInstrument(tr)+1 then
              reaper.TrackFX_SetEnabled(tr, j-1, true)
               else
              reaper.TrackFX_SetEnabled(tr, j-1, false)
            end
          end
        end  
              
      end
    end
  end
  
  tr= reaper.GetMasterTrack(0)
  
        fxcount = reaper.TrackFX_GetCount(tr)
        if fxcount ~= nil then
          for j = 1, fxcount do
            if j == reaper.TrackFX_GetInstrument(tr)+1 then
              reaper.TrackFX_SetEnabled(tr, j-1, true)
               else
              reaper.TrackFX_SetEnabled(tr, j-1, false)
            end
          end
        end  
            
  reaper.Undo_EndBlock(script_title, 0)

This works great, however, my ampsims are not considered VSTi.

I was thinking of adding just an "or" statement that might incorporate the name of my ampsim VST, or something like that. This way if it is an instrument it gets enabled state or if it is called guitar rig it gets enable state.

But I don't see how to do that with the J=1 thing. I really know nothing about scripting, unfortunately.

But, if this is too complicated, I get it, it's ok. Thanks for your help.

[mpl]

Originally Posted by Sound asleep

however, my ampsims are not considered VSTi.

fx chain - rightclick plugin - rename FX instance - enable "categorize as instrument"

[Sound asleep]

Originally Posted by mpl

fx chain - rightclick plugin - rename FX instance - enable "categorize as instrument"

Sweet. Thanks! I guess that must be a reaper 6+ thing because I don't see that checkbox. I guess I'm gonna have to upgrade lol.

That's again for all your help, and your sweet scripts.

[mpl]

Originally Posted by Sound asleep

Sweet. Thanks! I guess that must be a reaper 6+ thing because I don't see that checkbox. I guess I'm gonna have to upgrade lol.

That's again for all your help, and your sweet scripts.

Hm, I remember that was possible before.
However, this possible from same menu but from FX browser:
[fx browser - right click - rename]

[Sound asleep]

Originally Posted by mpl

Hm, I remember that was possible before.
However, this possible from same menu but from FX browser:
[fx browser - right click - rename]

No, you were right, I was just confused. I went to do it in FX chain, rather than FX browser. For anyone else wondering, if you do this, it works, however, if you have a track template with guitar rig on it for example, you will need to load up the track template, and then replace guitar rig with the new version that you have now changed to be an instrument, and then save your track template again.