2014-01-09 21:04:25 -08:00
|
|
|
#include <math.h>
|
Revamp API and start using doxygen
The API used to be designed in such a way to where it would expect
exports for each individual source/output/encoder/etc. You would export
functions for each and it would automatically load those functions based
on a specific naming scheme from the module.
The idea behind this was that I wanted to limit the usage of structures
in the API so only functions could be used. It was an interesting idea
in theory, but this idea turned out to be flawed in a number of ways:
1.) Requiring exports to create sources/outputs/encoders/etc meant that
you could not create them by any other means, which meant that
things like faruton's .net plugin would become difficult.
2.) Export function declarations could not be checked, therefore if you
created a function with the wrong parameters and parameter types,
the compiler wouldn't know how to check for that.
3.) Required overly complex load functions in libobs just to handle it.
It makes much more sense to just have a load function that you call
manually. Complexity is the bane of all good programs.
4.) It required that you have functions of specific names, which looked
and felt somewhat unsightly.
So, to fix these issues, I replaced it with a more commonly used API
scheme, seen commonly in places like kernels and typical C libraries
with abstraction. You simply create a structure that contains the
callback definitions, and you pass it to a function to register that
definition (such as obs_register_source), which you call in the
obs_module_load of the module.
It will also automatically check the structure size and ensure that it
only loads the required values if the structure happened to add new
values in an API change.
The "main" source file for each module must include obs-module.h, and
must use OBS_DECLARE_MODULE() within that source file.
Also, started writing some doxygen documentation in to the main library
headers. Will add more detailed documentation as I go.
2014-02-12 07:04:50 -08:00
|
|
|
#include <util/bmem.h>
|
|
|
|
|
#include <util/threading.h>
|
|
|
|
|
#include <util/platform.h>
|
|
|
|
|
#include <obs.h>
|
|
|
|
|
|
|
|
|
|
struct sinewave_data {
|
|
|
|
|
bool initialized_thread;
|
|
|
|
|
pthread_t thread;
|
2014-03-10 19:04:00 -07:00
|
|
|
os_event_t event;
|
Revamp API and start using doxygen
The API used to be designed in such a way to where it would expect
exports for each individual source/output/encoder/etc. You would export
functions for each and it would automatically load those functions based
on a specific naming scheme from the module.
The idea behind this was that I wanted to limit the usage of structures
in the API so only functions could be used. It was an interesting idea
in theory, but this idea turned out to be flawed in a number of ways:
1.) Requiring exports to create sources/outputs/encoders/etc meant that
you could not create them by any other means, which meant that
things like faruton's .net plugin would become difficult.
2.) Export function declarations could not be checked, therefore if you
created a function with the wrong parameters and parameter types,
the compiler wouldn't know how to check for that.
3.) Required overly complex load functions in libobs just to handle it.
It makes much more sense to just have a load function that you call
manually. Complexity is the bane of all good programs.
4.) It required that you have functions of specific names, which looked
and felt somewhat unsightly.
So, to fix these issues, I replaced it with a more commonly used API
scheme, seen commonly in places like kernels and typical C libraries
with abstraction. You simply create a structure that contains the
callback definitions, and you pass it to a function to register that
definition (such as obs_register_source), which you call in the
obs_module_load of the module.
It will also automatically check the structure size and ensure that it
only loads the required values if the structure happened to add new
values in an API change.
The "main" source file for each module must include obs-module.h, and
must use OBS_DECLARE_MODULE() within that source file.
Also, started writing some doxygen documentation in to the main library
headers. Will add more detailed documentation as I go.
2014-02-12 07:04:50 -08:00
|
|
|
obs_source_t source;
|
|
|
|
|
};
|
2014-01-09 21:04:25 -08:00
|
|
|
|
2014-02-09 04:51:06 -08:00
|
|
|
/* middle C */
|
Revamp API and start using doxygen
The API used to be designed in such a way to where it would expect
exports for each individual source/output/encoder/etc. You would export
functions for each and it would automatically load those functions based
on a specific naming scheme from the module.
The idea behind this was that I wanted to limit the usage of structures
in the API so only functions could be used. It was an interesting idea
in theory, but this idea turned out to be flawed in a number of ways:
1.) Requiring exports to create sources/outputs/encoders/etc meant that
you could not create them by any other means, which meant that
things like faruton's .net plugin would become difficult.
2.) Export function declarations could not be checked, therefore if you
created a function with the wrong parameters and parameter types,
the compiler wouldn't know how to check for that.
3.) Required overly complex load functions in libobs just to handle it.
It makes much more sense to just have a load function that you call
manually. Complexity is the bane of all good programs.
4.) It required that you have functions of specific names, which looked
and felt somewhat unsightly.
So, to fix these issues, I replaced it with a more commonly used API
scheme, seen commonly in places like kernels and typical C libraries
with abstraction. You simply create a structure that contains the
callback definitions, and you pass it to a function to register that
definition (such as obs_register_source), which you call in the
obs_module_load of the module.
It will also automatically check the structure size and ensure that it
only loads the required values if the structure happened to add new
values in an API change.
The "main" source file for each module must include obs-module.h, and
must use OBS_DECLARE_MODULE() within that source file.
Also, started writing some doxygen documentation in to the main library
headers. Will add more detailed documentation as I go.
2014-02-12 07:04:50 -08:00
|
|
|
static const double rate = 261.63/48000.0;
|
2014-01-09 21:04:25 -08:00
|
|
|
|
2014-02-14 14:13:36 -08:00
|
|
|
#ifndef M_PI
|
2014-01-09 21:04:25 -08:00
|
|
|
#define M_PI 3.1415926535897932384626433832795
|
2014-02-14 14:13:36 -08:00
|
|
|
#endif
|
|
|
|
|
|
2014-02-09 04:51:06 -08:00
|
|
|
#define M_PI_X2 M_PI*2
|
2014-01-09 21:04:25 -08:00
|
|
|
|
|
|
|
|
static void *sinewave_thread(void *pdata)
|
|
|
|
|
{
|
|
|
|
|
struct sinewave_data *swd = pdata;
|
|
|
|
|
uint64_t last_time = os_gettime_ns();
|
|
|
|
|
uint64_t ts = 0;
|
2014-02-09 04:51:06 -08:00
|
|
|
double cos_val = 0.0;
|
2014-01-09 21:04:25 -08:00
|
|
|
uint8_t bytes[480];
|
|
|
|
|
|
2014-03-10 19:04:00 -07:00
|
|
|
while (os_event_try(swd->event) == EAGAIN) {
|
2014-02-09 04:51:06 -08:00
|
|
|
if (!os_sleepto_ns(last_time += 10000000))
|
|
|
|
|
last_time = os_gettime_ns();
|
2014-01-09 21:04:25 -08:00
|
|
|
|
|
|
|
|
for (size_t i = 0; i < 480; i++) {
|
2014-02-09 04:51:06 -08:00
|
|
|
cos_val += rate * M_PI_X2;
|
|
|
|
|
if (cos_val > M_PI_X2)
|
|
|
|
|
cos_val -= M_PI_X2;
|
2014-01-09 21:04:25 -08:00
|
|
|
|
2014-02-23 15:27:19 -08:00
|
|
|
double wave = cos(cos_val) * 0.5;
|
2014-02-09 04:51:06 -08:00
|
|
|
bytes[i] = (uint8_t)((wave+1.0)*0.5 * 255.0);
|
2014-01-09 21:04:25 -08:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
struct source_audio data;
|
2014-02-07 02:03:54 -08:00
|
|
|
data.data[0] = bytes;
|
2014-01-09 21:04:25 -08:00
|
|
|
data.frames = 480;
|
|
|
|
|
data.speakers = SPEAKERS_MONO;
|
|
|
|
|
data.samples_per_sec = 48000;
|
|
|
|
|
data.timestamp = ts;
|
|
|
|
|
data.format = AUDIO_FORMAT_U8BIT;
|
|
|
|
|
obs_source_output_audio(swd->source, &data);
|
|
|
|
|
|
|
|
|
|
ts += 10000000;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return NULL;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* ------------------------------------------------------------------------- */
|
|
|
|
|
|
2014-06-25 00:13:00 -07:00
|
|
|
static const char *sinewave_getname(void)
|
2014-01-09 21:04:25 -08:00
|
|
|
{
|
|
|
|
|
return "Sinewave Sound Source (Test)";
|
|
|
|
|
}
|
|
|
|
|
|
2014-02-14 14:13:36 -08:00
|
|
|
static void sinewave_destroy(void *data)
|
Revamp API and start using doxygen
The API used to be designed in such a way to where it would expect
exports for each individual source/output/encoder/etc. You would export
functions for each and it would automatically load those functions based
on a specific naming scheme from the module.
The idea behind this was that I wanted to limit the usage of structures
in the API so only functions could be used. It was an interesting idea
in theory, but this idea turned out to be flawed in a number of ways:
1.) Requiring exports to create sources/outputs/encoders/etc meant that
you could not create them by any other means, which meant that
things like faruton's .net plugin would become difficult.
2.) Export function declarations could not be checked, therefore if you
created a function with the wrong parameters and parameter types,
the compiler wouldn't know how to check for that.
3.) Required overly complex load functions in libobs just to handle it.
It makes much more sense to just have a load function that you call
manually. Complexity is the bane of all good programs.
4.) It required that you have functions of specific names, which looked
and felt somewhat unsightly.
So, to fix these issues, I replaced it with a more commonly used API
scheme, seen commonly in places like kernels and typical C libraries
with abstraction. You simply create a structure that contains the
callback definitions, and you pass it to a function to register that
definition (such as obs_register_source), which you call in the
obs_module_load of the module.
It will also automatically check the structure size and ensure that it
only loads the required values if the structure happened to add new
values in an API change.
The "main" source file for each module must include obs-module.h, and
must use OBS_DECLARE_MODULE() within that source file.
Also, started writing some doxygen documentation in to the main library
headers. Will add more detailed documentation as I go.
2014-02-12 07:04:50 -08:00
|
|
|
{
|
2014-02-14 14:13:36 -08:00
|
|
|
struct sinewave_data *swd = data;
|
|
|
|
|
|
Revamp API and start using doxygen
The API used to be designed in such a way to where it would expect
exports for each individual source/output/encoder/etc. You would export
functions for each and it would automatically load those functions based
on a specific naming scheme from the module.
The idea behind this was that I wanted to limit the usage of structures
in the API so only functions could be used. It was an interesting idea
in theory, but this idea turned out to be flawed in a number of ways:
1.) Requiring exports to create sources/outputs/encoders/etc meant that
you could not create them by any other means, which meant that
things like faruton's .net plugin would become difficult.
2.) Export function declarations could not be checked, therefore if you
created a function with the wrong parameters and parameter types,
the compiler wouldn't know how to check for that.
3.) Required overly complex load functions in libobs just to handle it.
It makes much more sense to just have a load function that you call
manually. Complexity is the bane of all good programs.
4.) It required that you have functions of specific names, which looked
and felt somewhat unsightly.
So, to fix these issues, I replaced it with a more commonly used API
scheme, seen commonly in places like kernels and typical C libraries
with abstraction. You simply create a structure that contains the
callback definitions, and you pass it to a function to register that
definition (such as obs_register_source), which you call in the
obs_module_load of the module.
It will also automatically check the structure size and ensure that it
only loads the required values if the structure happened to add new
values in an API change.
The "main" source file for each module must include obs-module.h, and
must use OBS_DECLARE_MODULE() within that source file.
Also, started writing some doxygen documentation in to the main library
headers. Will add more detailed documentation as I go.
2014-02-12 07:04:50 -08:00
|
|
|
if (swd) {
|
|
|
|
|
if (swd->initialized_thread) {
|
|
|
|
|
void *ret;
|
2014-03-10 19:04:00 -07:00
|
|
|
os_event_signal(swd->event);
|
Revamp API and start using doxygen
The API used to be designed in such a way to where it would expect
exports for each individual source/output/encoder/etc. You would export
functions for each and it would automatically load those functions based
on a specific naming scheme from the module.
The idea behind this was that I wanted to limit the usage of structures
in the API so only functions could be used. It was an interesting idea
in theory, but this idea turned out to be flawed in a number of ways:
1.) Requiring exports to create sources/outputs/encoders/etc meant that
you could not create them by any other means, which meant that
things like faruton's .net plugin would become difficult.
2.) Export function declarations could not be checked, therefore if you
created a function with the wrong parameters and parameter types,
the compiler wouldn't know how to check for that.
3.) Required overly complex load functions in libobs just to handle it.
It makes much more sense to just have a load function that you call
manually. Complexity is the bane of all good programs.
4.) It required that you have functions of specific names, which looked
and felt somewhat unsightly.
So, to fix these issues, I replaced it with a more commonly used API
scheme, seen commonly in places like kernels and typical C libraries
with abstraction. You simply create a structure that contains the
callback definitions, and you pass it to a function to register that
definition (such as obs_register_source), which you call in the
obs_module_load of the module.
It will also automatically check the structure size and ensure that it
only loads the required values if the structure happened to add new
values in an API change.
The "main" source file for each module must include obs-module.h, and
must use OBS_DECLARE_MODULE() within that source file.
Also, started writing some doxygen documentation in to the main library
headers. Will add more detailed documentation as I go.
2014-02-12 07:04:50 -08:00
|
|
|
pthread_join(swd->thread, &ret);
|
|
|
|
|
}
|
|
|
|
|
|
2014-03-10 19:04:00 -07:00
|
|
|
os_event_destroy(swd->event);
|
Revamp API and start using doxygen
The API used to be designed in such a way to where it would expect
exports for each individual source/output/encoder/etc. You would export
functions for each and it would automatically load those functions based
on a specific naming scheme from the module.
The idea behind this was that I wanted to limit the usage of structures
in the API so only functions could be used. It was an interesting idea
in theory, but this idea turned out to be flawed in a number of ways:
1.) Requiring exports to create sources/outputs/encoders/etc meant that
you could not create them by any other means, which meant that
things like faruton's .net plugin would become difficult.
2.) Export function declarations could not be checked, therefore if you
created a function with the wrong parameters and parameter types,
the compiler wouldn't know how to check for that.
3.) Required overly complex load functions in libobs just to handle it.
It makes much more sense to just have a load function that you call
manually. Complexity is the bane of all good programs.
4.) It required that you have functions of specific names, which looked
and felt somewhat unsightly.
So, to fix these issues, I replaced it with a more commonly used API
scheme, seen commonly in places like kernels and typical C libraries
with abstraction. You simply create a structure that contains the
callback definitions, and you pass it to a function to register that
definition (such as obs_register_source), which you call in the
obs_module_load of the module.
It will also automatically check the structure size and ensure that it
only loads the required values if the structure happened to add new
values in an API change.
The "main" source file for each module must include obs-module.h, and
must use OBS_DECLARE_MODULE() within that source file.
Also, started writing some doxygen documentation in to the main library
headers. Will add more detailed documentation as I go.
2014-02-12 07:04:50 -08:00
|
|
|
bfree(swd);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2014-02-14 14:13:36 -08:00
|
|
|
static void *sinewave_create(obs_data_t settings,
|
Revamp API and start using doxygen
The API used to be designed in such a way to where it would expect
exports for each individual source/output/encoder/etc. You would export
functions for each and it would automatically load those functions based
on a specific naming scheme from the module.
The idea behind this was that I wanted to limit the usage of structures
in the API so only functions could be used. It was an interesting idea
in theory, but this idea turned out to be flawed in a number of ways:
1.) Requiring exports to create sources/outputs/encoders/etc meant that
you could not create them by any other means, which meant that
things like faruton's .net plugin would become difficult.
2.) Export function declarations could not be checked, therefore if you
created a function with the wrong parameters and parameter types,
the compiler wouldn't know how to check for that.
3.) Required overly complex load functions in libobs just to handle it.
It makes much more sense to just have a load function that you call
manually. Complexity is the bane of all good programs.
4.) It required that you have functions of specific names, which looked
and felt somewhat unsightly.
So, to fix these issues, I replaced it with a more commonly used API
scheme, seen commonly in places like kernels and typical C libraries
with abstraction. You simply create a structure that contains the
callback definitions, and you pass it to a function to register that
definition (such as obs_register_source), which you call in the
obs_module_load of the module.
It will also automatically check the structure size and ensure that it
only loads the required values if the structure happened to add new
values in an API change.
The "main" source file for each module must include obs-module.h, and
must use OBS_DECLARE_MODULE() within that source file.
Also, started writing some doxygen documentation in to the main library
headers. Will add more detailed documentation as I go.
2014-02-12 07:04:50 -08:00
|
|
|
obs_source_t source)
|
2014-01-09 21:04:25 -08:00
|
|
|
{
|
2014-02-09 11:34:07 -08:00
|
|
|
struct sinewave_data *swd = bzalloc(sizeof(struct sinewave_data));
|
2014-01-09 21:04:25 -08:00
|
|
|
swd->source = source;
|
|
|
|
|
|
2014-03-10 19:04:00 -07:00
|
|
|
if (os_event_init(&swd->event, OS_EVENT_TYPE_MANUAL) != 0)
|
2014-01-09 21:04:25 -08:00
|
|
|
goto fail;
|
|
|
|
|
if (pthread_create(&swd->thread, NULL, sinewave_thread, swd) != 0)
|
|
|
|
|
goto fail;
|
|
|
|
|
|
|
|
|
|
swd->initialized_thread = true;
|
2014-02-14 14:13:36 -08:00
|
|
|
|
|
|
|
|
UNUSED_PARAMETER(settings);
|
2014-01-09 21:04:25 -08:00
|
|
|
return swd;
|
|
|
|
|
|
|
|
|
|
fail:
|
|
|
|
|
sinewave_destroy(swd);
|
|
|
|
|
return NULL;
|
|
|
|
|
}
|
|
|
|
|
|
Revamp API and start using doxygen
The API used to be designed in such a way to where it would expect
exports for each individual source/output/encoder/etc. You would export
functions for each and it would automatically load those functions based
on a specific naming scheme from the module.
The idea behind this was that I wanted to limit the usage of structures
in the API so only functions could be used. It was an interesting idea
in theory, but this idea turned out to be flawed in a number of ways:
1.) Requiring exports to create sources/outputs/encoders/etc meant that
you could not create them by any other means, which meant that
things like faruton's .net plugin would become difficult.
2.) Export function declarations could not be checked, therefore if you
created a function with the wrong parameters and parameter types,
the compiler wouldn't know how to check for that.
3.) Required overly complex load functions in libobs just to handle it.
It makes much more sense to just have a load function that you call
manually. Complexity is the bane of all good programs.
4.) It required that you have functions of specific names, which looked
and felt somewhat unsightly.
So, to fix these issues, I replaced it with a more commonly used API
scheme, seen commonly in places like kernels and typical C libraries
with abstraction. You simply create a structure that contains the
callback definitions, and you pass it to a function to register that
definition (such as obs_register_source), which you call in the
obs_module_load of the module.
It will also automatically check the structure size and ensure that it
only loads the required values if the structure happened to add new
values in an API change.
The "main" source file for each module must include obs-module.h, and
must use OBS_DECLARE_MODULE() within that source file.
Also, started writing some doxygen documentation in to the main library
headers. Will add more detailed documentation as I go.
2014-02-12 07:04:50 -08:00
|
|
|
struct obs_source_info test_sinewave = {
|
|
|
|
|
.id = "test_sinewave",
|
|
|
|
|
.type = OBS_SOURCE_TYPE_INPUT,
|
|
|
|
|
.output_flags = OBS_SOURCE_AUDIO,
|
|
|
|
|
.getname = sinewave_getname,
|
|
|
|
|
.create = sinewave_create,
|
|
|
|
|
.destroy = sinewave_destroy,
|
|
|
|
|
};
|