Wireshark · Wireshark-dev: Re: [Wireshark-dev] RTP player - a suggestion

[Erik de Jong <erikdejong@xxxxxxxxx>]

@Peter Budny: If you would be able to write a step by step comparison that would be a great help. I think more use cases/workflows are important input when thinking about a redesign.

Bugzilla has plenty of examples on issues with RTP: https://bugs.wireshark.org/bugzilla/buglist.cgi?quicksearch=rtp&list_id=41643

I have attached a small capture with several RTP streams in one SIP call, I think we could probably use this while discussing this subject further. IMHO the biggest problems compared to GTK are:

- No pause

- Indicator not showing where we are in time when time of day is checked

- Other strange behavior eg when picking 2 random streams from the sample capture and playing sometimes plays the two at the same time when they should be after each other, or only one is played and the indicator starts in the middle of the timeline

- Selecting streams does not work in the player window (ie select a certain stream to play and don't play unselected streams)

And for a better user experience we ought to have the following features added:

- Seeking

- Selecting more than 2 streams from the RTP streams dialog (now only works from the VoIP calls dialog, which means that a supported signalling protocol must be present)

- Exporting audio with playback timing parameters, maybe export audio from the player?

Regards,

Erik

On Mon, Nov 6, 2017 at 10:16 PM, Roland Knall <rknall@xxxxxxxxx> wrote:

Erik and I where having a discussion at Sharkfest about the player today.

I would gladly help you guys solving the issues, the problem is just, that I neither have captures nor detailed explanations.

I do think. Bugzilla may be a good point, but a step-by-step comparison between v1 and v2 would be extremely helpful.

We do not want to reproduce exact behavior though. Improvements still can happen. But at the moment I understand RTP Player is deeply broken and if you guys could provide pointers on where and how it should be fixed, that would be greatly appreciated.

Cheers

> Am 06.11.2017 um 20:53 schrieb Guy Harris <guy@xxxxxxxxxxxx>:
>
>> On Nov 6, 2017, at 12:40 PM, Peter Budny via Wireshark-dev <wireshark-dev@xxxxxxxxxxxxx> wrote:
>>
>> I have plenty of captures handy, but it would probably be best if I record some new ones to illustrate the problems more clearly. I could also write up a “steps to reproduce” showing how I would normally do things in the v1 GUI, and how the v2 GUI makes it harder or impossible to do the same thing.
>>
>> Should I just reply with the files attached (and zipped?), or is there a better way to submit captures?
>
> If you have a problem with the RTP player, the best way to submit captures for them is to either
>
>    1) submit a new bug and attach the captures to the bug (don't bother zipping, just attach the captures directly as separate files, so we don't have to *un*zip them)
>
> or
>
>    2) if there's already a bug for the problem, add more information to that bug as necessary and attach the captures to that bug.
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe

Attachment: sample-call_anon.pcapng.gz
Description: GNU Zip compressed data