[Gstreamer-bugs] [Bug 143473] - newline in property value in gst-launch string breaks parsing

bugzilla-daemon at bugzilla.gnome.org bugzilla-daemon at bugzilla.gnome.org
Tue Jun 1 18:09:35 PDT 2004


http://bugzilla.gnome.org/show_bug.cgi?id=143473
GStreamer | gstreamer (core) | Ver: 0.8.1





------- Additional Comments From jyasskin at mail.utexas.edu  2004-06-01 21:09 -------
I'm really trying to write the element in bug #141686. I want to include a
newline in the format string, which is specified as a property. But gst-launch
doesn't seem to be able to parse property values containing newlines, hence this
bug. I figured it'd be easier to give you a test case involving filesrc since
you actually have that element installed.

I see the -e problem: zsh (what I'm running) doesn't need -e to process escapes,
os x never processes them, and bash and gnu need -e. printf doesn't have these
problems, so my problematic gst-launch command should be:
gst-launch filesrc location="`printf "blah\nblah"`"

I'd like you to interpret this bug as "please show me a way to, from a shell
prompt, include a newline character in a element's property value. If, as I
suspect, there's no way to do it, please fix that." 

I think the symptom of this bug is these two lines in the error message:
WARNING: erroneous pipeline: no element "blah"
         Trying to run anyway.
because I'm never asking for a "blah" element.
Do none of you get this part of the error message? I am running on os x, so it's
possible that's causing the problem, but it would be a very strange os dependency.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.




More information about the Gstreamer-bugs mailing list