Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

export time variation (animations) #445

Open
rgetz opened this issue Jun 8, 2018 · 1 comment
Open

export time variation (animations) #445

rgetz opened this issue Jun 8, 2018 · 1 comment

Comments

@rgetz
Copy link

rgetz commented Jun 8, 2018

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.

@rgetz rgetz added this to the phase2 milestone Jun 8, 2018
@adisuciu
Copy link
Contributor

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.

@adisuciu adisuciu modified the milestones: phase2, backlog Aug 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants