drop in some decent midi support (multiple midi outs/in support, midi
events in/out, midi player)
make it OSX and win ...
(well would get it without midi as well..) and I'm your man.. seems like
it would be everything that's needed.. (maybe ASIO and VST support, or
AU on the mac... hmmm..)
J.
I think you're also missing a very important thing in that beginSprite
handler!!
on beginSprite me
tempVar = timeOut(test).new(500, #doSomething, me)
end beginSprite
You need to set the returned value of that timeout().new() to a variable,
or you get hemorrhoids and excessive eye-booger
I ran into this same problem recently. The limit is 127 characters
including the filename and extension. This is a known bug to Macromedia in
both Director and Authorware. Apparently it has been known internally to
Macromedia for several versions and has not and is not going to be fixed.
Causes
On Wednesday, February 11, 2004, at 10:38 AM, Craig Taylor wrote:
Also, I know there have been threads about this, but the conclusion is
that
there really is no way of protecting video files (MPEG-1) from being
accessed outside of the protected program. Correct?
Protect to what degree? You
Ultimately someone could use a screen capture program or even a video
camera pointed at your monitor if you wanted the video bad enough...No
matter what level of encryption and authentication. All about making it
as irritating as possible without causing end-users grief. IMO, they
shouldn't
On Feb 11, 2004, at 9:38 AM, Craig Taylor wrote:
Also, I know there have been threads about this, but the conclusion is
that
there really is no way of protecting video files (MPEG-1) from being
accessed outside of the protected program. Correct?
Correct, for all practical purposes. Use
I ran into this same problem recently. The limit is 127
characters including the filename and extension. This is a
known bug to Macromedia in both Director and Authorware.
Apparently it has been known internally to Macromedia for
several versions and has not and is not going to be
Which is why the DRM stuff in iTunes and the like is irritating. If
I buy a song on one machine, I should be able to take that song to
any machine I want without being bugged. I mean, if I have a cd, I
can take the media with me to unlimited machines, so long as it
can't be played two places
On Feb 11, 2004, at 10:37 AM, Kerry Thompson wrote:
I don't know of any other way to read a text file in Director.
Try importFileInto. You should also be able to set the member.filename
of a #text member. You might still get the 127-char limit but
baShortFileName can resolve that.
Warren
On Feb 10, 2004, at 5:26 PM, Valentin Schmidt wrote:
It would be much safer to find out the actual Desktop-Folder with some
xtra like Buddy Api: Result = baSysFolder( desktop)
On Feb 10, 2004, at 5:27 PM, Warren Ockrassa wrote:
One way to find out might be to check via Buddy API. Don't know for
Correct, for all practical purposes. Use QuickTime; it supports media
keys that offer some measure of protection.
If the pieces are short enough consider conversion to Flash MX video.
You can import those directly into your cast and keep them internal.
Unfortunately, neither were options.
Colin, you mentioned
renaming the file - simply that just change the extension and make it an
unexpected file name.
Unexpected to whom? Does not MPEGAdvance still play them?
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post
On Wednesday, February 11, 2004, at 12:34 PM, Craig Taylor wrote:
Troy, you mentioned changing the headers - new ground
for me - relatively easy process? Is there somewhere you can direct
me for
more info?
UpdateStage has the BinaryIO xtra. Its documentation has some links
that are useful
There were also some very good posts about this in the past year or two.
A quick trip to the archives may answer a lot of the detailed questions
on procedure and methodology to ripping the heads off video and
reassembling later on-disk.
Since you don't mind writing to disk, hopefully it won't
My vote is for the vList xtra. I am using it in a pretty important project
to do
exactly what you are talking about, and it works great.
Andrew
Having said that, I am not looking to stop a determined party. Just
looking
to make it annoying or, at the very least, unobvious. Colin, you
Also, I know there have been threads about this, but the conclusion is
that
there really is no way of protecting video files (MPEG-1) from being
accessed outside of the protected program. Correct?
Thanks for all the insight,
Craig
Hi Craig,
You can protect/unprotect MPG files on the fly using
baShortFileName works fine with FileIO for pathnames longer than 127.
Though Buddy's open dialogue breaks down for very long path names
(255? at least, it did when increasing the path name by making one
very long folder name). I just tested it on Win XP with a pathname 169
characters
On Wed, 11 Feb 2004 12:34:43 -0500, Craig Taylor
[EMAIL PROTECTED] wrote:
Correct, for all practical purposes. Use QuickTime; it supports media
keys that offer some measure of protection.
If the pieces are short enough consider conversion to Flash MX video.
You can import those directly into
On Wed, 11 Feb 2004 10:49:03 -0500, Troy Rollins [EMAIL PROTECTED]
wrote:
On Wednesday, February 11, 2004, at 10:38 AM, Craig Taylor wrote:
Also, I know there have been threads about this, but the conclusion is
that
there really is no way of protecting video files (MPEG-1) from being
accessed
On Wednesday, February 11, 2004, at 05:22 PM, Deane Venske wrote:
Why not think about using Valentina DB, you could store the MPEG
videos into the database as BLOB and even encrypt this. That way your
video can't be accessed outside your program.
How exactly would you then access them
Unfortunately you can't play mpegs directly out of the database...AFAIK
They have to exist on a hard drive somewhere first, which is bad if you
don't want to be copying big ol' files to someone's hard drive, or take
the time necessary to do so while unencrypting them. It also opens up
the
Thanks to everyone for their thoughts on video file protection. Seems like
either vList or binaryIO Xtras will be the best way to go. I'm now headed
in the right direction and appreciate you all taking the time.
Thanks again,
-_Craig
- Original Message -
From: Bernard.Lang [EMAIL
On Wed, 11 Feb 2004 17:33:55 -0500, Troy Rollins [EMAIL PROTECTED]
wrote:
On Wednesday, February 11, 2004, at 05:22 PM, Deane Venske wrote:
Why not think about using Valentina DB, you could store the MPEG videos
into the database as BLOB and even encrypt this. That way your video
can't be
Does anybody know if there is a compatibility issue with MPEG-4 and Windows
2000?
I authored a Director CD which installs QT 6.4. The movie contains lots of
video. It runs great on Windows 2000 but a tester who tried it on 2000 said
the movies (videos) were all garbled looking but the audio was
24 matches
Mail list logo
