Re: [gentoo-user] mpeg4ip - replacement

2014-10-25 Thread Samuli Suominen

On 25/10/14 02:40, Joseph wrote:
 Which application replaced mpeg4ip ?

 I'm trying to streem mpeg4 video and in the past I was using mpeg4ip
 but I can not find it.

 -- 
 Joseph


media-video/gpac has extended mpeg4 support
media-libs/libmp4v2 with USE=utils has command lines utilities
media-video/atomicparsley or media-video/atomicparsley-wez

and of course, ffmpeg, libav, mplayer, ...

when mpeg4ip was removed in favour of the new (read: maintained)
libmp4v2 googlecode project,
these were the replacements, and users were able to accomplish whatever
mpeg4ip did with them

thanks,
samuli



Re: [gentoo-user] mpeg4ip - replacement

2014-10-25 Thread Neil Bothwick
On Fri, 24 Oct 2014 20:29:17 -0600, Joseph wrote:

 looking for access module matching rtsp: 18 candidates main debug: no
 access modules matched main error: open of
 `rtsp://66.18.xxx.xxx:554/mpeg4/media.amp' failed main debug: finished

Is VLC istalled with the rtsp USE flag?


-- 
Neil Bothwick

Time is the best teacher., unfortunately it kills all the students


signature.asc
Description: PGP signature


Re: [gentoo-user] Re: ceph on btrfs

2014-10-25 Thread Andrew Savchenko
On Fri, 24 Oct 2014 16:20:36 + (UTC) James wrote:
 Andrew Savchenko bircoph at gmail.com writes:
  We are using openrc too, no related issues. (systemd is banned on
  all our setups: masked and its dirs are in INSTALL_MASK, so we don't
  have its stuff floating around.)
 
 замечательно

Рад помочь :)

Best regards,
Andrew Savchenko


pgpRxUflonr6N.pgp
Description: PGP signature


Re: [gentoo-user] Moving the portage tree to /var

2014-10-25 Thread Tanstaafl
On 10/7/2014 6:03 PM, Mick michaelkintz...@gmail.com wrote:
 On Tuesday 07 Oct 2014 22:56:28 Mike Gilbert wrote:
 Quite the opposite. Ideally, you should remove the PORTDIR setting
 from make.conf. repos.conf is the newer, more flexible way to
 configure it.

 Unfortunately, that will break some of the third-party portage tools
 which parse make.conf directly.

 Scratches head ... so are we supposed to guess this, wait for a news 
 article 
 somewhere, or will it show up in an emerge log somewhere?

So... would appreciate a response from someone who knows.

I really dislike making systemic changes like this without really solid
guidance on how (and hopefully the why too)...



Re: [gentoo-user] mpeg4ip - replacement

2014-10-25 Thread Joseph

On 10/25/14 09:04, Neil Bothwick wrote:

On Fri, 24 Oct 2014 20:29:17 -0600, Joseph wrote:


looking for access module matching rtsp: 18 candidates main debug: no
access modules matched main error: open of
`rtsp://66.18.xxx.xxx:554/mpeg4/media.amp' failed main debug: finished


Is VLC istalled with the rtsp USE flag?


--
Neil Bothwick


I just add the rtsp use flag and re-compile the vlc but I still getting an 
error:


main debug: processing request item: rtsp://66.18.xxx.xxx:554/mpeg4/media.amp, 
node: Playlist, skip: 0
main debug: resyncing on rtsp://66.18.xxx.xxx:554/mpeg4/media.amp
main debug: rtsp://66.18.xxx.xxx:554/mpeg4/media.amp is at 0
main debug: starting playback of the new playlist item
main debug: resyncing on rtsp://66.18.xxx.xxx:554/mpeg4/media.amp
main debug: rtsp://66.18.xxx.xxx:554/mpeg4/media.amp is at 0
main debug: creating new input thread
main debug: Creating an input for 'rtsp://66.18.xxx.xxx:554/mpeg4/media.amp'
main debug: using timeshift granularity of 50 MiB, in path '/tmp'
main debug: `rtsp://66.18.xxx.xxx:554/mpeg4/media.amp' gives access `rtsp' 
demux `' path `66.18.xxx.xxx:554/mpeg4/media.amp'
main debug: creating demux: access='rtsp' demux='' 
location='66.18.xxx.xxx:554/mpeg4/media.amp' file='(null)'
main debug: looking for access_demux module matching rtsp: 10 candidates
main debug: no access_demux modules matched
main debug: creating access 'rtsp' 
location='66.18.xxx.xxx:554/mpeg4/media.amp', path='(null)'
main debug: looking for access module matching rtsp: 19 candidates
main debug: net: connecting to 66.18.xxx.xxx port 554
qt4 debug: IM: Setting an input
main warning: connection timed out
access_realrtsp error: cannot connect to 66.18.xxx.xxx:554
access_realrtsp debug: could not connect to: 66.18.xxx.xxx:554/mpeg4/media.amp
main debug: no access modules matched
main error: open of `rtsp://66.18.xxx.xxx:554/mpeg4/media.amp' failed
main debug: dead input
main debug: changing item without a request (current 0/1)
main debug: nothing to play
qt4 debug: IM: Deleting the input

It seems like there is no demux module matching rtsp

--
Joseph



Re: [gentoo-user] mpeg4ip - replacement

2014-10-25 Thread Joseph

On 10/25/14 01:54, Walter Dnes wrote:

On Fri, Oct 24, 2014 at 07:40:12PM -0600, Joseph wrote


I can stream mpeg-4 from camera locally using both: vlc and mplayer
but when I log-in from  remote computer not of them work.


 Does the remote computer have mplayer built with the same flags/codecs
as on your local computer?  Ignore the CPU-specific stuff.

 Can I assume that you're actually streaming from both computers?  Or
are you playing back a recorded file locally, as opposed to streaming
live from the remote?

--
Walter Dnes waltd...@waltdnes.org
I don't run desktop environments; I run useful applications


Well, the remote camera is Axis 207 so it has its own server. There is no 
mplayer on it.
When I access camera from the network computer the same as camera is on both 
vlc and mplayer work.
But when I try to stream over the internet (from different) it doesn't work.  


Can mpalyer stream the mpeg 4 video file over rtsp; I think only vlc can do it.

--
Joseph



Re: [gentoo-user] mpeg4ip - replacement

2014-10-25 Thread Joseph

On 10/25/14 09:35, Joseph wrote:

On 10/25/14 09:04, Neil Bothwick wrote:

On Fri, 24 Oct 2014 20:29:17 -0600, Joseph wrote:


looking for access module matching rtsp: 18 candidates main debug: no
access modules matched main error: open of
`rtsp://66.18.xxx.xxx:554/mpeg4/media.amp' failed main debug: finished


Is VLC istalled with the rtsp USE flag?


--
Neil Bothwick


I just add the rtsp use flag and re-compile the vlc but I still getting an 
error:


main debug: processing request item: rtsp://66.18.xxx.xxx:554/mpeg4/media.amp, 
node: Playlist, skip: 0
main debug: resyncing on rtsp://66.18.xxx.xxx:554/mpeg4/media.amp
main debug: rtsp://66.18.xxx.xxx:554/mpeg4/media.amp is at 0
main debug: starting playback of the new playlist item
main debug: resyncing on rtsp://66.18.xxx.xxx:554/mpeg4/media.amp
main debug: rtsp://66.18.xxx.xxx:554/mpeg4/media.amp is at 0
main debug: creating new input thread
main debug: Creating an input for 'rtsp://66.18.xxx.xxx:554/mpeg4/media.amp'
main debug: using timeshift granularity of 50 MiB, in path '/tmp'
main debug: `rtsp://66.18.xxx.xxx:554/mpeg4/media.amp' gives access `rtsp' 
demux `' path `66.18.xxx.xxx:554/mpeg4/media.amp'
main debug: creating demux: access='rtsp' demux='' 
location='66.18.xxx.xxx:554/mpeg4/media.amp' file='(null)'
main debug: looking for access_demux module matching rtsp: 10 candidates
main debug: no access_demux modules matched
main debug: creating access 'rtsp' 
location='66.18.xxx.xxx:554/mpeg4/media.amp', path='(null)'
main debug: looking for access module matching rtsp: 19 candidates
main debug: net: connecting to 66.18.xxx.xxx port 554
qt4 debug: IM: Setting an input
main warning: connection timed out
access_realrtsp error: cannot connect to 66.18.xxx.xxx:554
access_realrtsp debug: could not connect to: 66.18.xxx.xxx:554/mpeg4/media.amp
main debug: no access modules matched
main error: open of `rtsp://66.18.xxx.xxx:554/mpeg4/media.amp' failed
main debug: dead input
main debug: changing item without a request (current 0/1)
main debug: nothing to play
qt4 debug: IM: Deleting the input

It seems like there is no demux module matching rtsp

--
Joseph


On one of the forums someone suggested tat VLC does not support Apple's 
proprietary rtsp over http protocol.
(piece of crap Axis proprietary cameras)

--
Joseph



Re: [gentoo-user] Moving the portage tree to /var

2014-10-25 Thread Michael Orlitzky
On 10/25/2014 09:57 AM, Tanstaafl wrote:
 On 10/7/2014 6:03 PM, Mick michaelkintz...@gmail.com wrote:
 On Tuesday 07 Oct 2014 22:56:28 Mike Gilbert wrote:
 Quite the opposite. Ideally, you should remove the PORTDIR setting
 from make.conf. repos.conf is the newer, more flexible way to
 configure it.

 Unfortunately, that will break some of the third-party portage tools
 which parse make.conf directly.
 
 Scratches head ... so are we supposed to guess this, wait for a news 
 article 
 somewhere, or will it show up in an emerge log somewhere?
 
 So... would appreciate a response from someone who knows.
 
 I really dislike making systemic changes like this without really solid
 guidance on how (and hopefully the why too)...
 

I'm only guessing, but I don't think PORTDIR is going away for a while.
Eventually, portage will probably begin to warn you if you have PORTDIR
set in your make.conf, and will tell you to move your settings to
repos.conf (with a pointer to the man page or wiki). That'll stick
around for another while. Then, you'll get a news item telling you that
PORTDIR is going away in a month or so.

Finally, your shit will stop working and that's your final warning =)

More realistically, the portage upgrade might die or ewarn loudly if you
still have PORTDIR set.




Re: [gentoo-user] Moving the portage tree to /var

2014-10-25 Thread Mick
On Saturday 25 Oct 2014 17:45:05 Michael Orlitzky wrote:
 On 10/25/2014 09:57 AM, Tanstaafl wrote:
  On 10/7/2014 6:03 PM, Mick michaelkintz...@gmail.com wrote:
  On Tuesday 07 Oct 2014 22:56:28 Mike Gilbert wrote:
  Quite the opposite. Ideally, you should remove the PORTDIR setting
  from make.conf. repos.conf is the newer, more flexible way to
  configure it.
  
  Unfortunately, that will break some of the third-party portage tools
  which parse make.conf directly.
  
  Scratches head ... so are we supposed to guess this, wait for a news
  article somewhere, or will it show up in an emerge log somewhere?
  
  So... would appreciate a response from someone who knows.
  
  I really dislike making systemic changes like this without really solid
  guidance on how (and hopefully the why too)...
 
 I'm only guessing, but I don't think PORTDIR is going away for a while.
 Eventually, portage will probably begin to warn you if you have PORTDIR
 set in your make.conf, and will tell you to move your settings to
 repos.conf (with a pointer to the man page or wiki). That'll stick
 around for another while. Then, you'll get a news item telling you that
 PORTDIR is going away in a month or so.
 
 Finally, your shit will stop working and that's your final warning =)
 
 More realistically, the portage upgrade might die or ewarn loudly if you
 still have PORTDIR set.

I haven't touched this on my systems yet.  As a matter of fact, I totally 
forgot about it!

(Old age creeps up on you)  :-p

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] mpeg4ip - replacement

2014-10-25 Thread Walter Dnes
On Sat, Oct 25, 2014 at 09:41:20AM -0600, Joseph wrote

 Well, the remote camera is Axis 207 so it has its own server. There
 is no mplayer on it.  When I access camera from the network computer
 the same as camera is on both vlc and mplayer work.  But when I try
 to stream over the internet (from different) it doesn't work.
 
 Can mpalyer stream the mpeg 4 video file over rtsp; I think only
 vlc can do it.

  You mentioned in a previous message that mplayer and vlc work on one
computer, but not on the other.  So we know they both work.  I think the
problem is somewhere in the remote access.  How are you accessing the
rtsp stream?  Is it like so (example name and numbers)...

mplayer rtsp://10.1.2.3/stream_name

  Things to check...

* if you're using a domain name rather than an IP address, is it defined
  in the remote machine's /etc/hosts ?

* is the remote machine's firewall blocking the camera's IP address ?

* is the camera set to only stream to a specific IP address (range) ?

-- 
Walter Dnes waltd...@waltdnes.org
I don't run desktop environments; I run useful applications



Re: [gentoo-user] Moving the portage tree to /var

2014-10-25 Thread Michael Orlitzky
On 10/25/2014 01:49 PM, Mick wrote:
 
 I haven't touched this on my systems yet.  As a matter of fact, I totally 
 forgot about it!
 
 (Old age creeps up on you)  :-p
 

I haven't bothered with it either, I really like being able to do:

  PORTDIR=$REPOS/gentoo-x86 PORTDIR_OVERLAY= emerge -1 whatever




Re: [gentoo-user] mpeg4ip - replacement

2014-10-25 Thread Joseph

On 10/25/14 13:51, Walter Dnes wrote:

On Sat, Oct 25, 2014 at 09:41:20AM -0600, Joseph wrote


Well, the remote camera is Axis 207 so it has its own server. There
is no mplayer on it.  When I access camera from the network computer
the same as camera is on both vlc and mplayer work.  But when I try
to stream over the internet (from different) it doesn't work.

Can mpalyer stream the mpeg 4 video file over rtsp; I think only
vlc can do it.


 You mentioned in a previous message that mplayer and vlc work on one
computer, but not on the other.  So we know they both work.  I think the
problem is somewhere in the remote access.  How are you accessing the
rtsp stream?  Is it like so (example name and numbers)...

mplayer rtsp://10.1.2.3/stream_name

 Things to check...

* if you're using a domain name rather than an IP address, is it defined
 in the remote machine's /etc/hosts ?

* is the remote machine's firewall blocking the camera's IP address ?

* is the camera set to only stream to a specific IP address (range) ?

--
Walter Dnes waltd...@waltdnes.org
I don't run desktop environments; I run useful applications


I can login and access the camera setting over the Internet, the only part that 
is not working is streaming over rtsp.
MotionJPEG works but that takes a lot of bandwidth. 


I think you are correct it might have something to do with firewall.

I've open port range: 5 to 50999 and forward it to 10.10.0.127 (this is 
camera IP address on the other network).

When I try vlc:
Connection failed:
VLC could not connect to 66.18.xxx.xxx:554.
Your input can't be opened:
VLC is unable to open the MRL 'rtsp://66.18.xxx.xxx:554/mpeg4/media.amp'. Check 
the log for details.

I open port 9090 (tcp/udp) on the remote firewall and forward it to 10.10.0.127:80  
But I'm puzzled why is it trying to connect to: 66.18.xxx.xxx:554 
Maybe this is the problem. 


rtsp port 554 is enabled on the camera.

--
Joseph



Re: [gentoo-user] mpeg4ip - replacement

2014-10-25 Thread Joseph

On 10/25/14 13:51, Walter Dnes wrote:

On Sat, Oct 25, 2014 at 09:41:20AM -0600, Joseph wrote


Well, the remote camera is Axis 207 so it has its own server. There
is no mplayer on it.  When I access camera from the network computer
the same as camera is on both vlc and mplayer work.  But when I try
to stream over the internet (from different) it doesn't work.

Can mpalyer stream the mpeg 4 video file over rtsp; I think only
vlc can do it.


 You mentioned in a previous message that mplayer and vlc work on one
computer, but not on the other.  So we know they both work.  I think the
problem is somewhere in the remote access.  How are you accessing the
rtsp stream?  Is it like so (example name and numbers)...

mplayer rtsp://10.1.2.3/stream_name

 Things to check...

* if you're using a domain name rather than an IP address, is it defined
 in the remote machine's /etc/hosts ?

* is the remote machine's firewall blocking the camera's IP address ?

* is the camera set to only stream to a specific IP address (range) ?

--
Walter Dnes waltd...@waltdnes.org
I don't run desktop environments; I run useful applications


* I'm using only IP addresses no domain name.
* on the remote computer camera is on 10.10.0.127 IP address
so I open port 9090 and forwarded to IP  10.10.0.127:80 on the remote firewall

When I tried mplayer, I get:

mplayer rtsp://66.18.xxx.xxx:9090/mpeg4/media.amp
MPlayer SVN-r36370 (Gentoo)-4.7.3 (C) 2000-2013 MPlayer Team
MMX2 supported but disabled

Playing rtsp://66.18.xxx.xxx:9090/mpeg4/media.amp.
Resolving 66.18.xxx.xxx for AF_INET6...

Couldn't resolve name for AF_INET6: 66.18.xxx.xxx
Connecting to server 66.18.xxx.xxx[66.18.xxx.xxx]: 9090...

librtsp: server responds: 'HTTP/1.0 501 Not Implemented'
STREAM_LIVE555, URL: rtsp://66.18.xxx.xxx:9090/mpeg4/media.amp
Stream not seekable!
file format detected.
Failed to get a SDP description from URL 
rtsp://66.18.210.217:9090/mpeg4/media.amp: 501 Not Implemented


--
Joseph



Re: [gentoo-user] mpeg4ip - replacement

2014-10-25 Thread Walter Dnes
On Sat, Oct 25, 2014 at 01:18:27PM -0600, Joseph wrote

 Playing rtsp://66.18.xxx.xxx:9090/mpeg4/media.amp.
 Resolving 66.18.xxx.xxx for AF_INET6...
 
 Couldn't resolve name for AF_INET6: 66.18.xxx.xxx

  Why is the machine doing anything IPV6-related for an IPV4 address?

 Failed to get a SDP description from URL

  Some bad news... you just published the entire URL, including the full
IPV4 address.  Take it offline *NOW*.

  Possibly some good news... you say that you can't access it remotely.
Does your ISP block servers on your account?  That may save you.

-- 
Walter Dnes waltd...@waltdnes.org
I don't run desktop environments; I run useful applications



Re: [gentoo-user] mpeg4ip - replacement

2014-10-25 Thread Joseph

On 10/25/14 22:31, Walter Dnes wrote:

On Sat, Oct 25, 2014 at 01:18:27PM -0600, Joseph wrote


Playing rtsp://66.18.xxx.xxx:9090/mpeg4/media.amp.
Resolving 66.18.xxx.xxx for AF_INET6...

Couldn't resolve name for AF_INET6: 66.18.xxx.xxx


 Why is the machine doing anything IPV6-related for an IPV4 address?


Failed to get a SDP description from URL


 Some bad news... you just published the entire URL, including the full
IPV4 address.  Take it offline *NOW*.


OH well, experiment over for now :-)  I'll obtain different IP from my provider.



 Possibly some good news... you say that you can't access it remotely.
Does your ISP block servers on your account?  That may save you.


No, they don't block anything.  Googling around, I'm not the only one with this problem. 


--
Joseph