Version: unknown (using KDE 3.3.90 (alpha1, CVS >= 20041206), compiled sources) Compiler: gcc version 3.3.4 OS: Linux (i686) release 2.6.10 Which is the correct way for recording a streaming? I cannot record from http://musica.virgilio.it/multimedia/goldrake_video/adsl/index.html It's an ASX. I never used the record with KMplayer, so I click on the record button than I click on "Start recording" button. I selected Xine for playing and ffmpeg for record. I've got them installed correctly on the system.
CVS commit by vriezen: Also read text/plain mimes and make mplayer handle http://musica.virgilio.it/multimedia/goldrake_video/adsl/index.html too. CCBUG: 95956 M +1 -0 kmplayerpartbase.cpp 1.131 --- kdeextragear-2/kmplayer/src/kmplayerpartbase.cpp #1.130:1.131 @@ -1035,4 +1035,5 @@ static bool isPlayListMime (const QStrin !strcmp (mimestr ,"application/smil") || !strcmp (mimestr ,"text/xml") || + !strcmp (mimestr ,"text/plain") || !strcmp (mimestr ,"application/x-mplayer2")); }
This asx contains the url mms://media.tin.it/users/matrix/nettv/caraturo/goldrake_adsl.wmv which was properly found with Xine (I fixed it, so MPlayer should handle this too). When you start recording, it jumps to the first playable url in the ASX, that's the mms://...wmv url. Most likely in your config is ffmpeg as recorder. You better choose either mencoder or 'mplayer -dumpstream', because ffmpeg is limited wrt. its input (and I think mms:// is not supported by ffmpeg). Does this help, can you record now?
Oh, yes. With ffmpeg I can't get it, but with MEncoder I get it. Is it difficult to get a response with KMplayer? For example, if I get an error with ffmpeg because it cannot record that kind of stream can't KMplayer try for MPlayer or MEncoder or tell user: "Sorry, I can't record this stream because you has not the right program installed" or something like this? Could be usefull. Thank you. Good work. When I can see KMplayer into kdemultimedia? For KDE 4?
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.