You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
doing it a similar way (and including the ffmpeg library) would allow animated png or gif (which is what most people have asked for). I am not a lawyer, and don't want to talk to them about this - so we should stay away from things fraught with danger, like H264, and other potentially patented video codecs in the binaries that we distribute.
The text was updated successfully, but these errors were encountered:
We can currently save a buffer as a CSV file. What about saving multiple buffers to the csv file and replaying them in a similar fashion to the reference waveform? (this would also be useful for demo mode). This way we would have access to the actual data, as well as use Scopy as a rendering platform instead of relying on video encoding libraries (which shouldn't really be a dependency for our application).
The user specifies number of buffers/seconds to capture. Multiple channels can be saved at once as well, and people can use different scaling/zooming to view the waveforms.
If people want to make .gifs/.mp4s out of the waveforms, they can always use 3rd party software.
There are ways to export png in the instruments, but sometimes - it's the time variation that is more important for documentation/labs.
In this case - export to animation would be required.
Some pointers can be found : http://www.ifnamemain.com/posts/2014/Jul/11/screen_capture_1/
doing it a similar way (and including the ffmpeg library) would allow animated png or gif (which is what most people have asked for). I am not a lawyer, and don't want to talk to them about this - so we should stay away from things fraught with danger, like H264, and other potentially patented video codecs in the binaries that we distribute.
The text was updated successfully, but these errors were encountered: