Expose Raw Frame Buffers

[Commander-lol]

Expose Raw Frame Buffers

[blaind]

What about adding a Recorder trait, with some sample recorders (e.g. gif) provided by the library, but customizable easily by end users.

Here's an example of how the API could look:

• adding the recorders in a builder pattern (.add_recorder::<CustomRecorder>())
• inserting MediaCapture as a component for each camera where its needed - this way no need to link the id's. Internally, maybe a few instances could be used but end-user API more bevy-style this way (.insert(MediaCapture::<CustomTracker>::new().set_duration(Duration::from_secs(5)));)

use std::time::Duration;
use bevy::prelude::*;
use bevy_capture_media::{MediaCapture, BevyCapturePlugin};

pub fn spawn_cameras(
    mut commands: Commands,
) {
    let camera_entity = commands
        .spawn_bundle(Camera2dBundle::default())
        .insert(MainCamera)
        .insert(MediaCapture::<CustomTracker>::new().set_duration(Duration::from_secs(5)));       
}

pub fn take_screenshot(
    input: Res<Input<KeyCode>>,
    mut capture: Query<&mut MediaCapture<CustomTracker>, With<MainCamera>>,
) {
    if input.just_released(KeyCode::RShift) {
        capture.single_mut().start();
    }
}

#[derive(Component)]
pub struct MainCamera;

fn main() {
    App::new()
        .add_plugin(DefaultPlugins)
        .add_plugin(bevy_capture_media::BevyCapturePlugin::new().add_recorder::<CustomRecorder>())
        .add_startup_system(spawn_cameras)
        .add_system(take_screenshot)
        .run();
}

pub struct MediaCapture<T: Recorder> {
  recorder: T
}

pub trait Record {
  // some common methods, like receive_frame
}

pub struct CustomRecorder;

impl Recorder for CustomRecorder {
   // ...
}

note: didn't try if possible in practice... (especially the storage of trait, if multiple implementations used)