String Bud! Wot the Fook

itsthejayj's picture

Having one of those excellent QC nights and then this! Am i going crazy here!

This weird string result was produced as a result of a bunch of string scanning patches, string components and kinemes read from file patch. Here composition is reduced down, retaining the produced strings!

Any idea what is going on here! Nutz

PreviewAttachmentSize
WotTheFook.qtz10.66 KB

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

itsthejayj's picture
Re: String Bud! Wot the Fook

Ok it has something to do with the Serato history file i'm trying to read using Kineme String with file. Strange anyway. Not sure if this is a kineme bug or some cleverness on behalf of Serato. Anyway i'm attached the NSFileTypeRegular file and comp

PreviewAttachmentSize
kineme string with file.zip3.3 KB

cybero's picture
Re: String Bud! Wot the Fook

OK, I ran the composition, I got the wiggy result. I replaced the paths with identical paths, result, all works aok.

Find attached.

I don't think the problem is specifically to do with the Seratto file.

I think you're barking up the wrong tree.

The File Info | String from File comp ran as I would expect it to do.

No complications.

PreviewAttachmentSize
WotTheFook tester.qtz10.57 KB
WotTheFook tester.png
WotTheFook tester.png29.76 KB

itsthejayj's picture
Re: String Bud! Wot the Fook

I'm pretty sure it the sera to file using some weird binary format.

Your see my problem if you look in the original composition i posted, then edit the first 'movie location' input, go to the end of the string and move the cursor back character by character. You see what i mean ;?) ... it just stuck ever other character.

No matter i'll tackle things in objective c and see what the results are there. Cheers any way Peter

cybero's picture
Re: String Bud! Wot the Fook

Tried that, didn't get the problem you've posted about, although the snapshot comp you posted did evidence that kind of problem on first opening, upon even repasting the file path you used, the numbers tallied correctly.