You probably can c2nim [ffms2](https://github.com/FFMS/ffms2). This is what
avisynth/vapoursynth uses to store a video in a variable like in my script
from vapoursynth import core
video = core.ffms2.Source(source='Rule6.mkv')
And then it provides facility to get specific
Doesn't [!ffmpeg](http://ffmpeg.org/) already support most of this?
Granted that ffmpeg is implemented in C(with some ASM), but it wouldn't be all
that difficult to wrap. Someone crazy enough and who has enough time on their
hands may be even to fully port it to Nim.
I agree with most everyone
This is an odd request
Yes, there are languages that _has support for audio read/write_ \- but the
point is that those languages has that support by means of packages/libraries -
that kind of functionality is never in the core language.
So, if Nim doesn't have it, I guess it's because Nim
I did a lot of video processing in the past.
What you want is a frameserver like
[Avisynth](http://avisynth.nl/index.php/First_script) (Windows-only,
multithreading an afterthought, custom scripting language) or
[Vapoursynth](http://www.vapoursynth.com/doc/gettingstarted.html#example-script)
We have lots of people pitching ideas they can't seem to implement themselves.
Common problem. Other people could implement those ideas, but time and energy
are finite. Also a common problem.
What we need is some sort of NimLancer broker system that would make it easy
for people to hire a
> If you want Nim to become popular in audiovisual computing - Computer Vision
> for self-driving cars or Video Processing for Film & Television for example -
> I strongly suggest that the language comes with basic image/audio/video
> read/write capabilities by default.
Yes, we do. So why
@ jlp765
We video and image processing guys tend to be highly specialized in "pixel
operations" and "image processing operations".
i.e. once we can get at the actual video RGB pixels or audio sample data we
know what to do with them
But we suck at things like setting up video file I/O -
**@videobuddha - what do you currently use (language/libraries/codecs/...)?**
There are a few Nimble packages that wrap external libraries already:
**audio**
* nim-ao
* nim-ogg
* nim-vorbis
* nim-portaudio
* nim-sndfile
* sndhdr
* nshout
* taglib
* sdl2 (for gaming)
ok, since I wrote this, I think the example with the codec developer is just a
bad example. Just because there is a codec in the standard library, doesn't
main you can't develop a better one in that language. But I don't change my
opinion. I think the Nim language is powerfull enough, that it
As @krux02 mentioned, core language should be compact and flexible without
diminishing its usability. Nim syntax already flexible enough so you shouldn't
have any problem implementing the dsl for multimedia applications. While
developing language to fill the niche is nice, it would be more nice
People in Audiovisual Computing need 2 things from a programming language:
1. As fast as possible code execution speed
2. Easy to use, built-in image/audio/video file read/write commands
There is NO programming language right now that does both.
The programming language is either SLOW but
If anyone's interested, I've started integrating webm support into the
[rod](https://github.com/yglukhov/rod) engine. The core libs are
[webm](https://github.com/yglukhov/webm) which is mkv/libvpx wrapper and
[rod_video](https://github.com/yglukhov/rod_video) which is a component for
rod. All
I don't agree. This is an area that is great for you, and would be very
interesting for a lot of other people. But not generally. Just think about
video codec developers. How would a video codec developer feel in a programming
language that has already decided on the builtin video codec. I
Not quite what you are proposing, but there is an `opencv` nimble package (only
a partial wrapper, IIRC).
I wonder how realistic implementing this would be given the Copyright issues
with various codecs.
As someone who does a lot of custom video processing, there is one crucial
functionality I find lacking in almost all programming languages I come across:
1. Loading a video + audiotrack (e.g. Testvid.mkv) with 1 line of code
2. Having FAST read access to both the video frame pixels and
15 matches
Mail list logo
