Comments (4)
So I made the changes to job.js for those who want to know how to do concat.
prepare:
if (job.parsedOpts()['source_file'] == 'concat'){
callback("hasInput");
}else{
fs.stat(job.parsedOpts()['source_file'], function(err, stats) {
if (err) {
job.exitHandler(-1, "unable to read input file (" + job.parsedOpts()['source_file'] + ").");
} else {
if (stats.isFile()) { job.filesize = stats.size || Number.NaN };
callback("hasInput");
}
});
and spawn:
if (job.parsedOpts()['source_file'] != 'concat'){
args.push('-i', this.parsedOpts()['source_file']);
}
send the string "concat" as the input file, then in your "encoder_options" format your options as specified in the ffmpeg documentation for concat.
simple usage: -f concat -i yourfileslist.txt -c copy
from codem-transcode.
Hi Scott, glad you got it working with the concat filter. I'm going to refer to what I just wrote at #31 as well (check it out if you will): Codem was initially built with the one file in, one file out philosophy. That doesn't seem always viable anymore, so we are considering other options, but we don't have any short-term plans to implement these features. We need to rewrite a considerable amount of code to support these features properly.
from codem-transcode.
Thanks for responding, after looking at your code I would agree that in conjunction with the scheduler it would indeed take a lot of code refactoring. The standard tee is a much different animal than the HLS outputs mentioned in issue #31. Since the transcoder js code alone could be easily refactored to allow for multiple predictable outputs by simply implementing an output array+loop in a few places, I am going to work on it a little bit. The scheduler however... ruby is new to me. like since last week.. To get around it I will implement a similar 'hack' if you will, in the filters or directly with json for the output in the jobs table until my project settles down and I will start to learn ruby properly. Nice work btw. even with the tweaks, this project is saving me from re-inventing the wheel.
from codem-transcode.
I agree. We were going to build out an internal solution from scratch. This
is great work.
Julian Bankston
(615) 669-3057
Founder
Britevid
Mave Media LLC
On Thu, Jul 24, 2014 at 9:34 AM, Scott Freeman [email protected]
wrote:
Thanks for responding, after looking at your code I would agree that in
conjunction with the scheduler it would indeed take a lot of code
refactoring. The standard tee is a much different animal than the HLS
outputs mentioned in issue #31
#31. Since the
transcoder js code alone could be easily refactored to allow for multiple
predictable outputs by simply implementing an output array+loop in a few
places, I am going to work on it a little bit. The scheduler however...
ruby is new to me. like since last week.. To get around it I will implement
a similar 'hack' if you will, in the filters or directly with json for the
output in the jobs table until my project settles down and I will start to
learn ruby properly. Nice work btw. even with the tweaks, this project is
saving me from re-inventing the wheel.—
Reply to this email directly or view it on GitHub
#30 (comment)
.
from codem-transcode.
Related Issues (20)
- Is it possible to generate multiple bit-rate as well as corresponding master m3u8 in a single job? HOT 8
- Idea: Incorporate provision for AWS Lambda HOT 2
- node-sqlite3 is throwing error, does it affect Transcodem? HOT 1
- Database configuration using port isn't working HOT 2
- /jobs/:id is MUCH slower than /jobs HOT 5
- Transcoder sometimes doesn't clear jobs from memory correctly
- Transcoding file streams HOT 1
- External mysql2 connection HOT 4
- Init script with codem-transcode and CentOS 7 not working HOT 7
- How to add file input name in the email report
- changing sqlite3 to mysql HOT 1
- Install depends on old packages and non-existing too HOT 3
- PID file
- -ss and or -t should be before -i HOT 2
- ffmpeg stderr buffer size HOT 1
- Generate SPRITE image for thumbnail HOT 7
- Object storage integration HOT 6
- v.1.0-alpha: job failed processing with bunyan usage error HOT 4
- cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
- hướng dẫn tạo video lên top google
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from codem-transcode.