Comments (16)
Hi,
- Did you
Modify scripts/ecn_env.sh
ECN_ENABLED=1
Make sure that MY_GST_INSTALL points to the correct install directory.
2 Please modify sender.sh
killall -9 scream_sender
+which gst-inspect-1.0
+gst-inspect-1.0 gstscream
+gst-inspect-1.0 x264enc
$SCREAM_TARGET_DIR/scream_sender --verbose
3. Run sender.sh.
from scream.
I have executed the modified send.sh script as per your instructions. However, I still encounter an error. The operating system I am currently using is Ubuntu 20.04 with kernel version 5.15.0-88-generic. Do you recommend changing the operating system for testing purposes?
from scream.
from scream.
I'm posting the logs generated by the running 'receiver.sh' and 'sender.sh' scripts.These logs are stored in two separate files.
receiver.log
from scream.
from scream.
Hello, I might not have specified the installation path during setup, and it's possible that the default path was used. The command I executed was 'meson setup builddir'.
Currently, after running 'gst-inspect-1.0', the output on my system is as follows:
Do I need to reinstall? If so, what path should I specify for the installation?
from scream.
from scream.
Hello, I've followed your instructions and successfully reinstalled the program. Now, MY_GST_INSTAL is set to $SCRIPT_DIR/... /... /... /gstreamer/install.
When I executed . /script/receiver.sh, it worked fine and produced the output: "screamrx/imp.rs ecn-enabled."
However, when I run . /script/sender.sh, it still throws an error. Here's the content of the output file for your reference.
send2.log
I also used gst-inspect-1.0 x264enc and successfully located it as follows:
from scream.
from scream.
Hello, I've followed your instructions and added the sender.sh script, which includes the commands gst-inspect-1.0 x264enc and gst-inspect-1.0 avdec_h264.
Below is the output from the sender side.
send4.log
According to the results, avdec_h264 should be present, but x264enc is not.
from scream.
from scream.
Thank you for your guidance. I've checked, and unfortunately, I couldn't find the libgstx264.so file in both the build directory and the install directory. Additionally, upon inspecting the meson-log.txt file in the build/meson-logs directory, it appears that x264enc is disabled.
Is there a specific step or configuration that I might have missed in enabling x264enc during the build process?
In addition, I would like to provide another piece of information. When I disable L4S by setting ECN_ENABLED=0 in ecn_env.sh and run sender.sh, the program output is normal, and I can detect x264enc.
I am wondering if the issue might be related to the version of GStreamer that I installed. I used the following repository: https://gitlab.freedesktop.org/samhurst/gstreamer/-/tree/ecn, specifically the ecn branch.
I did not use the command patch -p1 < <2717.patch. I'm unsure if this might be a problem.
It appears to me that the changes introduced by the patch and the code in the ecn branch are consistent. However, I'm not entirely certain if my understanding is accurate.
I performed the installation using the following commands:
meson setup --prefix=/path/to/install/prefix builddir
meson compile -C builddir
meson install -C builddir
Your insights or suggestions on any potential issues would be greatly appreciated.
from scream.
from scream.
Hello, I successfully ran the sender.sh following your guidance. I greatly appreciate your assistance over these days. Thank you for your patience and support.
from scream.
from scream.
Added more info to README
from scream.
Related Issues (20)
- Same file names in multiple directories with similar content HOT 2
- Memory Leak due to RTCP HOT 1
- Compilation issue HOT 1
- Duplicated source files HOT 2
- Compile error HOT 2
- GStreamer plugins build fails HOT 4
- Example for GStreamer WebRTC HOT 1
- Usage of getTargetBitrate HOT 2
- GStreamer element timestamping issues HOT 16
- Rate adaptation seemingly unstable HOT 53
- Periodic rate drop with CWND control enabled. HOT 4
- Rather large difference between numbers shown
- QUESTION: Real-World Projects HOT 3
- build on Windows HOT 13
- Running SCReAM BW test applications in gstscream not work on Linux HOT 1
- req_url (Embedded_Ace_Get_Task.cgi) -- 403 Forbidden HOT 2
- RtpQueue is full with newCc after 65536 seconds (max uint32_t in ntp domain) HOT 3
- Rust screamtx crash caused by a null buffer passed to rust callback HOT 3
- Rust screamtx crash when RtpQueue was cleared HOT 2
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 scream.