MPL Import Session Data (parsing and taking data from RPP file)

[mpl]

Originally Posted by nofish

Hi mpl,
when trying to use your script (for the first time actually) I get an error:


Just synchronized ReaPack so it should be up to date.
Could it be because I'm trying to import from a quite old project (from 2013)?
Could send you the .rpp via PM if it helps.
Thanks.

Hi, yes, seems something changed in structure, send rpp please.

[arjunned]

Hi, mpl!

Wondering if it's possible to implement the below features for this script? It would be a huge time-saver (atleast, for me! ).

1. Import Track Layout as per the source, when importing new tracks. Right now, new tracks are imported with the Global Layout as default. Can there be option to have Mixer and Track Panel Layout retained/copied from the source?

2. Import tracks respecting folder structure from the source. Right now, importing as new tracks breaks parent/child structure of the tracks in the source.

Thanks!

[mpl]

Originally Posted by arjunned

1. Import Track Layout as per the source, when importing new tracks. Right now, new tracks are imported with the Global Layout as default. Can there be option to have Mixer and Track Panel Layout retained/copied from the source?

Added for 2.06

2. Import tracks respecting folder structure from the source. Right now, importing as new tracks breaks parent/child structure of the tracks in the source.
Thanks!

By default when you importing track, it is important to reset its structure position (so you can import some track to the wrong level of folder structure). But you can ignore this and import track with their source level position as is - when you click at destination, select 'New track at the end of tracklist, obey structure'.

[arjunned]

Originally Posted by mpl

Added for 2.06

Awesome, thanks!

Originally Posted by mpl

By default when you importing track, it is important to reset its structure position (so you can import some track to the wrong level of folder structure). But you can ignore this and import track with their source level position as is - when you click at destination, select 'New track at the end of tracklist, obey structure'.

Ah, got it! I completely missed the "obey structure" option.

Would it be possible to have an option to also import assigned 'group flags' from source tracks?

Thanks!

[mpl]

Originally Posted by arjunned

Would it be possible to have an option to also import assigned 'group flags' from source tracks?

added for 2.07,
also added option to import project track group names

[arjunned]

Originally Posted by mpl

added for 2.07,
also added option to import project track group names

Thanks, mpl!

[arjunned]

Hey, mpl!

Do the sends and recieves not get copied over anymore in v2.0+? It used to work fine in v1.28. Now, imported tracks don't seem to have sends/recieves as per source.

Source:
>> https://i.imgur.com/KB0VIlM.png


Destination:
>> https://i.imgur.com/NXpjHZq.png

Any chance we can get a "copy source send/receive routing" as well? Unless this option is already there and I've missed it completely!

-Arjun.

[arjunned]

Originally Posted by arjunned

Hey, mpl!

Do the sends and recieves not get copied over anymore in v2.0+? It used to work fine in v1.28. Now, imported tracks don't seem to have sends/recieves as per source.

Source:
>> https://i.imgur.com/KB0VIlM.png


Destination:
>> https://i.imgur.com/NXpjHZq.png

Any chance we can get a "copy source send/receive routing" as well? Unless this option is already there and I've missed it completely!

-Arjun.

Just checking in on this, in case a solution is possible.

[mpl]

Originally Posted by arjunned

Hey, mpl!

Do the sends and recieves not get copied over anymore in v2.0+? It used to work fine in v1.28. Now, imported tracks don't seem to have sends/recieves as per source.

It was very poor designed so I removed it for v3. Internally I did a code to collect this data for future, noone mentioned it so I didn`t anything with that yet.

What you suggest to do (and how to design, I mean UI) with following scenarios:
1) multiple imported tracks have same send track, this track is not imported
2) multiple imported tracks have same send track, this track is imported as well
3) send track is "already" in the project (like you have "Vocal Hall" in the source project and track with partially matched or same in destination project)
4) you need to saparately add each send track per imported track
5)... maybe other things I don`t see?

I maybe had this previously (too much data int the head, so I probably forgot), but since I will build it from the scratch, it would be probably nice to firstly ask users how they see this should be implemented.

[arjunned]

Originally Posted by mpl

It was very poor designed so I removed it for v3. Internally I did a code to collect this data for future, noone mentioned it so I didn`t anything with that yet.

What you suggest to do (and how to design, I mean UI) with following scenarios:
1) multiple imported tracks have same send track, this track is not imported
2) multiple imported tracks have same send track, this track is imported as well
3) send track is "already" in the project (like you have "Vocal Hall" in the source project and track with partially matched or same in destination project)
4) you need to saparately add each send track per imported track
5)... maybe other things I don`t see?

I maybe had this previously (too much data int the head, so I probably forgot), but since I will build it from the scratch, it would be probably nice to firstly ask users how they see this should be implemented.

I can see why this is such a rabbit hole.

For what it's worth, very basic send/receive logic was retained when using the below two options from v1.28:



I have mostly only ever used the "Link sources imported as new tracks" function. And that used to work well when you import a set of tracks and want their send/receive logic as per the source tracks.

[mpl]

Originally Posted by arjunned

I can see why this is such a rabbit hole.

For what it's worth, very basic send/receive logic was retained when using the below two options from v1.28:



I have mostly only ever used the "Link sources imported as new tracks" function. And that used to work well when you import a set of tracks and want their send/receive logic as per the source tracks.

See destination menu for 2.08

[jessesbakery]

I'm trying to use this script for the first time and am getting this error when the action is called:

mpl_ImportSessionData.lua:1615: attempt to call a nil value (global 'ReaPack_BrowsePackages')

Has anyone seen this before and know a way around it?

Thanks!
Jesse

[mpl]

Originally Posted by jessesbakery

I'm trying to use this script for the first time and am getting this error when the action is called:

mpl_ImportSessionData.lua:1615: attempt to call a nil value (global 'ReaPack_BrowsePackages')

Has anyone seen this before and know a way around it?

Thanks!
Jesse

Make sure you have installed:
- latest ReaPack
- VariousFunctions package (howtoinstall)

(I have just updated ImportSessionData to prevent this error)

[Triode]

For anyone importing tracks that have sends at the same time as tracks with corresponding receives, the method is to select "Import Sends" in the destination selector (as well as their destination) for both the tracks with sends and the tracks with receives.

MPL, I'd suggest for clarity to make the UI specify "Import Sends and Receives" (without changing any functionality).

I initially tried selecting import sends for just the tracks with the sends (not the tracks with their receives). This seemed to cause the import of any FX chains to fail as well as not importing the sends.

[mpl]

Originally Posted by Triode

For anyone importing tracks that have sends at the same time as tracks with corresponding receives, the method is to select "Import Sends" in the destination selector (as well as their destination) for both the tracks with sends and the tracks with receives.

MPL, I'd suggest for clarity to make the UI specify "Import Sends and Receives" (without changing any functionality).

I initially tried selecting import sends for just the tracks with the sends (not the tracks with their receives). This seemed to cause the import of any FX chains to fail as well as not importing the sends.

Technically RPP has only information about receives.
Depending on needs, you can:
1) import tracks as is
2) import with sends, in that case you have to click "handle sends", sends will be imported as new tracks
3) import with sends, in that case you have to click "handle sends", BUT if you have receive channels set enable for import with a "remap" check, send will created for imported tracks.

So how exactly I should modify UI? (sorry, Im not a native english speaker)

[Reflected]

Dear Michael

Can you make this work on track templates too?

[mpl]

Originally Posted by Reflected

Dear Michael

Can you make this work on track templates too?

added support RtrackTemplates for 2.11

[Reflected]

Originally Posted by mpl

added support RtrackTemplates for 2.11

Awesome!
Thank you!!

[arjunned]

Hi, MPL.

Looks like the sends don't import correctly in 2.11.

Source:


Destination:

[Triode]

Originally Posted by arjunned

Hi, MPL.

Looks like the sends don't import correctly in 2.11.

Source:


Destination:

If you're importing the sends at the same time as the receive tracks it only seems to work if you have "import sends" selected on the receive tracks too. Did you see my post a few posts above.
I can't get it to work at all unless I do it this way.

[arjunned]

Originally Posted by Triode

If you're importing the sends at the same time as the receive tracks it only seems to work if you have "import sends" selected on the receive tracks too. Did you see my post a few posts above.
I can't get it to work at all unless I do it this way.

Hmm. I have "import sends" selected on the receive tracks. But it still doesn't seem to import send correctly. v2.10 works correctly.

Also, I noticed that it imports the correct "amount" of sends, but all the sends are to the first track that's been imported.

Example 1:


Example 2:

[Triode]

Originally Posted by arjunned

Hmm. I have "import sends" selected on the receive tracks. But it still doesn't seem to import send correctly. v2.10 works correctly.

Also, I noticed that it imports the correct "amount" of sends, but all the sends are to the first track that's been imported.

Example 1:


Example 2:

Definitely something odd with v2.11. I also couldn't get sends to import correctly.
I've rolled back to v2.10 and importing sends works again if I import the receive track at the same time and mark all the tracks (including the receive tracks I'm importing) with "import sends".

I've never managed to import sends when the receive track is already in the session. This script needs a manual!

[mpl]

Originally Posted by Triode

Definitely something odd with v2.11. I also couldn't get sends to import correctly.
I've rolled back to v2.10 and importing sends works again if I import the receive track at the same time and mark all the tracks (including the receive tracks I'm importing) with "import sends".

I've never managed to import sends when the receive track is already in the session. This script needs a manual!

Sorry for late reply.
Looking at this. There is no difference with importing sends section between 2.10 and 2.11. Importing sends is a huge pain in REAPER, since all the links are ID-based. When you import anything from another project all the tracks are messed up, it is near impossible to handle verything correctly.

I need a more detailed steps to reproduce and source+destination project examples. Everything goes fine if:
- mark source tracks to "new track at the end of tracklist"
- mark "import sends" (which probably means "import send links if the send/receive is imported to this session", sorry for incovenience, I`m not english speaker).

when the receive track is already in the session

Ok so I importing, let say, drums, with room aux bus already presented in the project. If you import this room track as well, the links will be be added from drum tracks to this receive track. Otherwise how the script should know where to send these drum tracks if the receive track is already in the project?

[Triode]

Originally Posted by mpl

I need a more detailed steps to reproduce and source+destination project examples.

Hi MPL

Most of the time when using your import script I'm transferring plugin settings to a project with pre-existing tracks, so this would be the detailed scenario:

- Start your script
- Select the project to import from
- Select the tracks I want to import and do Match for them
- Refine any tracks that missed the right settings from the match algorithm
- Select all the tracks I'm importing by click-selecting and either command or shift-select including any receive tracks
- Select "import sends" for all these tracks
- Click Import

This works in version 2.10 if the track with receives is imported at the same time. It does not work in 2.11

It may be that a receive track is already in the session I am importing to, in which case I would hope that the script would check for receive tracks in the session that have a matching name to the sends on the tracks in the session I am importing from to resolve these.

In your script there is also a "Do not import, only mark for sends remap" - I've never understood how to use this or if it's relevant to the above workflow.

Many thanks

[Gass n Klang]

All tracks are being imported as parent tracks. Am I missing something?

[mpl]

Originally Posted by Gass n Klang

All tracks are being imported as parent tracks. Am I missing something?

If matched by name, yes. If new track at end of track list, there is "obey structure" flag in that menu.

[Gass n Klang]

perfect i missed that one!

[The Bunker]

Hi, firstly thanks for the awesome script. Its really helped me speed up some of my process. Was just wondering, do you have any idea why when it imports things like group names from one project to another, it puts those names in quotation marks? Its not a huge deal but seems odd and I was wondering if I was doing something incorrectly or if it is intended behaviour.

[mpl]

Originally Posted by The Bunker

Hi, firstly thanks for the awesome script. Its really helped me speed up some of my process. Was just wondering, do you have any idea why when it imports things like group names from one project to another, it puts those names in quotation marks? Its not a huge deal but seems odd and I was wondering if I was doing something incorrectly or if it is intended behaviour.

fixed for 2.12

[Triode]

Hi MPL

Through use I've noticed a couple of things with this script that are not obvious (and may have changed in recent versions) I'm using version 2.11 now:

When you click "Import" the only tracks that will be imported are the ones that are selected on the left. I initially thought there was a bug that was causing the script to only work sometimes. I think you should either change the import button to "Import Tracks Selected Here" or make the track selection not matter and import every track according to the instructions in the middle column.

Here's a picture to illustrate. The only track that will be imported is the "Kick" track (number 4). I think most users will think the track selection is a way to organise your preferences to populate the middle column and not a limiter on which tracks are then imported.

Thanks again for the script which has been useful even though there are these quirks.

[Triode]

I've also worked out how to use the "Do not import, only mark for sends remap" option.

In the following picture I've selected the two receive tracks with the option "Do not import, only mark for sends remap" but it doesn't populate the middle column immediately. I need to have selected "Match by name" for the remap option to do anything.



Since these two functions are linked I think just selecting remap should be enough to get this result in the middle column (if there are viable matches in the session)



Thank you for reading this

[Triode]

One final thing:

In the above example when you:

1. Match track by name
2. Select "Do not import, only mark for sends remap"
3. Then try to unselect "Do not import, only mark for sends remap" you can't. Once this option has been selected for some tracks you can't turn it off and you have to restart the script (it sticks even if you try selecting "None" or any other destination option.

Thanks

[gfndkimo]

Hello~
I am wondering...after I import session data..
the track item will be the offline....
it seems only patch the destine folder ...didn't copy the source file..
so it won't on line...
I must close the project and reopen it..then search file folder ...
is that normal?
o what should I set?

[mpl]

Originally Posted by Triode

One final thing:

In the above example when you:

1. Match track by name
2. Select "Do not import, only mark for sends remap"
3. Then try to unselect "Do not import, only mark for sends remap" you can't. Once this option has been selected for some tracks you can't turn it off and you have to restart the script (it sticks even if you try selecting "None" or any other destination option.

Thanks

Made an internal cleanup - menu, flags inside. It should more consistent now.

Originally Posted by Triode

I think most users will think the track selection is a way to organise your preferences to populate the middle column and not a limiter on which tracks are then imported.

Obeying selection is also disabled by default with ability to turn it off.

Originally Posted by gfndkimo

Hello~
I am wondering...after I import session data..
the track item will be the offline....
it seems only patch the destine folder ...didn't copy the source file..
so it won't on line...
I must close the project and reopen it..then search file folder ...
is that normal?
o what should I set?

Yes, thats the issue that coming from relative path set with source project. Latest version has experimental options to 1) fix relative paths and make them absolute, 2)import media as well

[Triode]

Thanks for those changes MPL. I'll check them out when I'm back in the studio.

[Triode]

Hi MPL

2.13 is the best version so far. Thank you

On this version when I select some tracks in the left column only the destination match mode I'm mousing is selected (not the other tracks). Licecap:



Also I've never managed to import any track groups for media/razor edits (even when selecting Group Flags and Track Group Names).

[The Bunker]

Originally Posted by mpl

fixed for 2.12

Great thank you.

[mpl]

Originally Posted by Triode

On this version when I select some tracks in the left column only the destination match mode I'm mousing is selected (not the other tracks).

should works fine for 2.14

Also I've never managed to import any track groups for media/razor edits (even when selecting Group Flags and Track Group Names).

I never used razor edits so I don`t understand how track group is related to it. Any RPP example + gif?

[Triode]

Originally Posted by mpl

should works fine for 2.14


I never used razor edits so I don`t understand how track group is related to it. Any RPP example + gif?

Thanks!

The track edit groups have been in reaper for a while. It's this kind of grouping (with the checkmarks at the top):



Edit groups don't get imported with your script.

Cheers

[mpl]

Originally Posted by Triode

Thanks!

The track edit groups have been in reaper for a while. It's this kind of grouping (with the checkmarks at the top):



Edit groups don't get imported with your script.

Cheers

Ah I see, these 2 top checks are v6.73+ API additions and weren`t in the docs when I built that part. Added to 2.15.