Tobias Megies

> I suspect that this is due to the fact that trace list is regenerated every time the the merge method is invoked Yeah, we started this as simple as...

> some work to be done before my suggested solution is decent/general enough, Great, just let us know when you have something! > and I also have to read up...


Uhm.. I think that image was created from the attached code..

Oh, right, command line parameters.. sorry, too long ago, no idea. You'll just have to try some values.

I think this would really only be useful to debug certain electrical problems when setting up a station (e.g. getting rid of 50Hz hum, ...), i.e. when you have some...

Yes. We could still try to make multiple threads connecting to different servers. Maybe that is less of a problem (than it was connecting in multiple threads to the same...

Is that already with verbose flag `-v`? Full output? Can you get data from that very same seedlink server with other means OK (e.g. with [this](http://docs.obspy.org/master/packages/autogen/obspy.clients.seedlink.basic_client.Client.get_waveforms.html#obspy.clients.seedlink.basic_client.Client.get_waveforms))

Please try to fetch a specific short time piece using above basic seedlink client. I doubt this is seedlink-plotter specific..

> However, easyseedlink does bring data chunks. Hmm.. strange. I thought maybe the seedlink server was configured to not allow same commands. But this might not be the case if...