Start a new topic

[Rebex] better handling of ANSI Recording files


i miss two things in the Dashboard View "ANSI Recording".

1.) It would be nice if i can export more than one ANSI File at a time. This is a very important feature for us (we've a lot of short rebex sessions every day) . 


2.) In addition to that a "multi-logfile-textsearch" would be perfect!



1 person likes this idea

hi, export is not necessary because you can copy file from folder. but integrated search will be nice feature. Filip  

When i open *.ans-files direct in notepad++ i see a lot of escape sequences and "Convert to UTF8" doesnt change anything. I'm not an encoding please feel free to give me some tipps for a better readability of ANSI Files with an external editor.

Hi Sven,

the ansi files used in Royal TS are in a special format used to "play back" the session. When you select an ansi file in the dashboard you will see by default the text representation (without the escape characters) in the lower part of the dashboard:


This is a conversion done by Royal TS. You can select all the text and copy it to your favorite editor or you can use the Export button to export it as text file.

I hope this helps.


Thank you stefan, i know that. 

But as i wrote in my first post...we've a lot of short rebex sessions every day and sometimes (days later) we search for a specific event on a specific day. In the past we opened simultaneous 20 or more putty text logs in notepad++ and searched for a string in all one step. 

At the moment we cant reproduce this quick workflow with ANSI Logfiles (1:1). The only way i see is to export every single ANSI-Log...on by one. :-/ Thatswhy i wrote this thread.


Apropos "play back". Very nice feature but i miss a "skip forward/skip backward" quickly jump to the next (or last) keyboard input. Sometimes interruptions without keyboard input are just too long for the previously implemented "fast forward"-feature.

I'm not sure if the skip feature is possible but I will look into it.

For the ansi log files, I can think of two solutions:

  1. Automatically create a .txt file with the content of the stripped ansi file as shown in the dashboard by default. This would be created automatically upon disconnection but could take some time, depending on the log size.
  2. A button in the toolbar or export menu entry which allows you to create those text files on demand (even for multiple files)
The second solution wouldn't be that much of effort to get in... Would that work for you?


Login or Signup to post a comment