Re: Re: Re: Re: Re: Timeseries/linked files: more than one file
Up one level
Re: Re: Re: Re: Re: Timeseries/linked files: more than one file
Although I'm not sure if this does matter, but if you add the two timeseries files you shouldn't need to associate one with the other. This option is meant to associate a timeseries file with a particular audio or video file (only relevant if you e.g. have more than one video file linked).
What should happen if you have two timeseries files linked and switch to sync. mode, is that you have 1 player for the timeseries files. Underneath there should be the following:
Player2 Offset nn:nn:nn:nnn
file:///path_to_first_ts_file
pulldown box with all linked timeseries files
Apparently you do not have this selection box that allows you to specify which timeseries file you want to synchronize? In principle you should be able to sync the timeseries files one by one via the Player 2. As far as I can see the different offsets are then stored and loaded when opened again?
-Han
Re: Re: Re: Re: Re: Re: Timeseries/linked files: more than one file
Not sure if this has been addressed.. but I often have this same problem. For me, it seems to be more of an issue of how the time offsets are DISPLAYED in ELAN's media synchronization screen. <br><br>Basically when I am in the media synch mode, if I change one timeseries offset, the other one timeseries displays as being changed. For example if I have a file called 1.csv set to 00:00:36.5 and then I set a second file (2.csv) to 00:00:05.5, the 1.csv file displays 00:00:36.5. <br><br>Sometimes I get lucky using the absolute method of synchronizing. Then although the media synchronization mode displays that the CSV ofsets are both the same, the EAF file has the correct time offsets in it (if I open the .eaf file in a text editor), the linked file menu has the correct times, and the plotted CSV data in the annotation mode is also seems correct.<br><br>Is there a way to have the offsets in the media synchronization mode display correctly? Or is there something I should do differently to avoid this problem....<br><br>(I'm running 4.2.0 in Windows 7)<br><br>Happy to email you the error log (its really long for this one...) if that will be a help... just let me know. <br>