kami wrote:When attempting to start ComSkipper.app OSX wants to run it in classic mode. Is this correct\normal?
kami wrote:Bit afraid to go there at the moment as I have a lot of recordings scheduled in the next while. Should I be?
Also ... FYI I'm attemting to run this on an iMAC G5 "PPC" NOT Intel.
kami wrote:So far FileWatcher.app appeared to open (momentary flash of a window opening) without any error window. I looked in the activity monitor but could not find it there. Is it actually running? If so what would it be called in activity monitor?
kami wrote:All the recordings in my EyeTV Archive folder are named *.eyetv NOT *.mpg Is this wrong? Filewatcher.app did not generate any .plist file that I can find.
nyamatongwe wrote:RC3 fixed the message box issue in ComSkipper for me.
One very large file failed within comskip with CPU sticking at around 30% rather than the normal 95%+ until it produced an incomplete .plist and said it had only found 7 frames. Worked OK after editing to remove some extra content at start and end. May be an idea to update the included version of comskip as the upstream site shows current version is 14 revisions later.
nyamatongwe wrote:The EyeTV limitation where it overwrites the .eyetvr file is a bit unpleasant. I wonder if there is some way to tell it "hey I changed this file behind your back, read it in again". The "all" option to FileWatcher is good - I had started working on a script to do that myself.
simo wrote:Can this be used to create markers to the recording so it'd be possible to permanently remove commercials using "Compact" in EyeTV's editor?
Lycestra wrote:The config.h is kinda annoying in how its staticly configured to the host machine, rather than allowing the compiler to aid in target-specific stuff. But I think Mac OS X is the only platform with universal binaries, which is why its so annoying. The config.h had to be modified so that x86-specific options are enabled on non-ppc, and ppc-specific options are enabled on ppc. Kludgey, but it compiles
Lycestra wrote:By the way, is there some way to maybe make this as a Recording Plugin (rather than a Live plugin) so it works like Edit features (like export and compress do)?
Cheers.
Lycestra wrote:ACCEL_DETECT broke some compile thing on PPC (jump code), but i forgot to make it a ppc-only config thing. There was a warning breaking the compile regarding some of that code for altivec. It probably should be enabled for x86 considering how many accel options there probably are for x86 cpus. (not sure how much it varies for intel-mac) ppc is pretty much altivec and thats it. maybe.
cc -c -pipe -Wall -W -Os -fasm-blocks -Wno-unused -DHAVE_CONFIG_H -arch i386 -arch ppc -I/Developer/qt/mkspecs/default -I. -Ilibmpeg2 -IAC3Dec -Iargtable2-7/src -o cpu_state.o libmpeg2/cpu_state.c
{standard input}:17:stvx vector instruction is optional for the PowerPC (not allowed without -force_cpusubtype_ALL option)
cc -c -pipe -Wall -W -Os -fasm-blocks -Wno-unused -DHAVE_CONFIG_H -arch i386 -arch ppc -force_cpusubtype_ALL -I/Developer/qt/mkspecs/default -I. -Ilibmpeg2 -IAC3Dec -Iargtable2-7/src -o idct_altivec.o libmpeg2/idct_altivec.c
In file included from libmpeg2/idct_altivec.c:29:
/usr/lib/gcc/powerpc-apple-darwin8/4.0.1/include/altivec.h:36:2: error: #error Use the "-maltivec" flag to enable PowerPC AltiVec support
Lycestra wrote:Let me know if you want any help. I plan on testing what I have tonight. I've got a history of trying to make things work (for me) when the source is available, so really, it was more fun than anything to try getting this compiling. Making it work on ppc is another issue, but hopefully not too much of a slog.
#define SaturateRound(x) (x < -32768) ? -32768 : ((x > 32767) ? 32767 : ((short)x));
j-christ wrote:It might be better to move development discussion to sourceforge, though.
Lycestra wrote:probably is a little better. I didn't actually look at it to consider what it does.
I'm on Leopard, so my GCC probably is a little newer. Are you using XCode 2.5? (leopard has 3, but 2.5 is the update for 10.4 that came out after leopard) Not quite sure how to use -maltivec at a command line that does both archs. If the compile was split into 2 gcc commands, the resulting objects would have to be merged using 'lipo' (takes thin binaries and combines them. the name appears to be a joke on the old 68k/PPC "Fat" binaries.) That would mean modifying makefile rules to have arch-specific objects (whatever.ppc.o and whatever.x86.o) and then the final object (whatever.o) be a lipo command that depends on the other two. never done that myself. blah. Maybe switch to XCode.
gcc --version
i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5367)
I just regged with sourceforce. Prolly about time I did. amazingly still got the same name as here. This is /my/ nick.I'll look at that tonight. for now, I should get to work.
Oh yeah. i was wondering whats with the QT make directives? thats just.. weird.
qmake -projectj-christ wrote:
I'm using XCode 2.4.1, but really everything I do is from the command line (I'm really a linux geek, not a Mac OS X one), so it's
- Code: Select all
gcc --version
i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5367)
i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5370)
Copyright (C) 2005 Free Software Foundation, Inc.
I'm experiencing this too. I'm on an Intel Mac (MacBook Pro).kami wrote:So far FileWatcher.app appeared to open (momentary flash of a window opening) without any error window. I looked in the activity monitor but could not find it there.
rackerby wrote:I'm experiencing this too. I'm on an Intel Mac (MacBook Pro).kami wrote:So far FileWatcher.app appeared to open (momentary flash of a window opening) without any error window. I looked in the activity monitor but could not find it there.
_
Lycestra wrote:rackerby wrote:I'm experiencing this too. I'm on an Intel Mac (MacBook Pro).kami wrote:So far FileWatcher.app appeared to open (momentary flash of a window opening) without any error window. I looked in the activity monitor but could not find it there.
_
Easiest way to see the error is to run it in Terminal. basically, in the terminal, type "/path/to/wherever/FileWatcher.app/Contents/MacOS/FileWatcher" (replacing /path/to/wherever with wherever you keep it) and see what happens. Maybe a segfault, or a linker error.
if (argc>1) { bool do_all=false;
for (int i=0; i< argc; ++i)
{
if (strncmp(argv[i],"all",3)==0) {
do_all=true;
break;
}
}
if (do_all)
{
Also, update on my progress with the universal binary test. Keeping it simple to test the comskip functionality, I tried running MarkCommercials.sh on the mpg file in an existing file. EyeTV wasn't running while doing that, and then I started up EyeTV when it was done. It didn't seem to do anything. Tho i forgot to change the saturatedround function.
Might be that bug, a miscalibration, or I'm just not using it right. I was expecting that if EyeTV isn't running while the MarkCommercials.sh script is running, it would tweak the file so commercials are marked, and EyeTV started after that would see it as such. I figured that MarkCommercials.sh was a good starting point to test just that functionality. What should I expect if I run MarkCommercials.sh while EyeTV isn't running?
./comskip -v 6 file.mpgj-christ wrote:Let's move this discussion to the ETVComskip forum at:
http://sourceforge.net/forum/forum.php?forum_id=766457