I don't think so, an application has no way of kowing how to resolve e.g.
0 FILE main.ldr
1 <params> a.dat
1 <params> imported.dat
0 FILE a.dat
1 <params> 3001.dat
0 FILE imported.dat
1 <params> a.dat
0 FILE a.dat
1 <params> 3001.dat
where the second a.dat is nested from wherever imported came from.
It could be solved by something like:
0 FILE main.ldr
1 <params> a.dat
1 <params> imported.dat
0 FILE a.dat
1 <params> 3001.dat
0 NOFILE
0 !MPDLEVEL ++
0 FILE imported.dat
1 <params> a.dat
0 FILE a.dat
1 <params> 3001.dat
0 NOFILE
0 !MPDLEVEL --
By putting the mpdlevel meta inbetween valid mpd content it should be backwards compatible without polluting extracted dat's, though incorrectly resolved, in non supporting apps
This is just a quick draft though, It might be solved in different / better ways.
Edited 1 time(s). Last edit at 2012-11-10 01:23PM by Roland Melkert.
