COCKOS
CONFEDERATED FORUMS
Cockos : REAPER : NINJAM : Forums
Forum Home : Register : FAQ : Members List : Search :
Old 09-20-2006, 07:19 PM   #1
misterC
Human being with feelings
 
Join Date: Jan 2006
Posts: 41
Default clipsort log errors

Didnt get any response in the user forum so figured I'd try here...



I'm running the linux 'jackified' ninjam client on my FC5 box..

Once I'm done jamming, I get on my XP box and when I try to either 1) open the clipsort.log in REAPER or 2) use cliplogcvt.exe to build each users track, on 9 out of 10 jams I just get one of these errors:

Error parsing log line
user line has wrong number of tokens
local line has wrong number of tokens
unknown token in logfile

Any ideas?

Also, when I use the options -savelocalwavs and -writewav all I get is an output.wav but can't get anything to open it, what format of wav does it save in?
misterC is offline   Reply With Quote
Old 08-02-2019, 04:07 AM   #2
Torben Scharling
Human being with feelings
 
Join Date: Jan 2009
Posts: 43
Default

Old topic but I now have the same problem with one of my jams I wanna open, other jams of mine just before and after, open fine, but one gives me the same error, so I cant get the merged wavs.....
Torben Scharling is offline   Reply With Quote
Old 08-02-2019, 01:39 PM   #3
pljones
Human being with feelings
 
pljones's Avatar
 
Join Date: Aug 2007
Location: London, UK
Posts: 598
Default

It would help to see the file, really.
__________________
Quote:
Originally Posted by Tony Williams
...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world.
pljones is online now   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 01:35 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.