On 2015-04-29 14:51:21 +0000, Charles Lindbergh said:
> On Wed, 29 Apr 2015 08:50:26 -0500, BRIAN P EHNI <bpehni@gmail.com> wrote:
>
>> On 2015-04-28 21:07:33 +0000, Charles Lindbergh said:
>>
>>> On Tue, 28 Apr 2015 10:06:39 -0500, john szalay <john.szalayatatt.net> wrote:
>>>
>>>> BRIAN P EHNI <bpehni@gmail.com> wrote in
>>>> n
>>>>>>
>>>>>> Thay are working mp4 and 3gp video files with very peculiar file
>>>>>> names.
>>>>>
>>>>> If his aim is to have them seen, it ain't working here.
>>>>>
>>>>> Brian Ehni
>>>>>
>>>>>
>>>>
>>>> Same here, unless I access them with the Windows 10 test OS
>>>> I,m running on a spare computer (test machine) (build 10061)
>>>>
>>>>
>>>
>>> You might consider installing VLC, a very robust, free, all-in-one
>>> media player,
>>> which far outstrips the capabilities of virtually any other media player
>>> available, be it Windows, MAC OS X, Android or iOS.
>>>
>>> See: http://www.videolan.org/
>>
>> You must have missed my first post. THE FILES ARE INSIVIBLE, EVEN WHEN
>> DOWNLOADED.
>>
>> Brian Ehni
>
> There is no reason to be snarky nor do you have any justification for shouting
> at me using all caps. I read your posts but my response was directed to John
> Szalay.
>
> As you were able to see and open the video I posted, it would seem your
> Newsreader, Unison, might have a problem with Bykers file naming protocol.
>
> My newsreader, Forte Agent, has no problem with his posts. I will repost
> another of his videos, using his naming convention, that way you can determine
> if it is the file naming or post encoding.
>
> It never pays for a dog to bark and growl at the person who is trying to feed
> him.
Sorry; I was having a bad day, and I took it out on you. I got the
second file, though the file name came thru as "______________ ______
-______-. _________.mp4"
Brian Ehni
|
| Follow-ups: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 |
|