Hi guys. I
'd really like to do more string manipulation while entirely svoiding vvvv which is always slow with text despite having a good set of easy to use nodes.
I guess this would mean loading or streaming files in vl and vl running asynchronously.
Any suggestions on how? Or when? Guest
we don’t have a file-loader in VL yet. definitely high up on the list though. so for now your best bet is still to use the loader in vvvv and pipe the string into VL to do the rest…
Reader (Raw) should be the fastest, it just passes the bytes over without converting to string or anything…
Right, trying to use getItem I can’t put the array in a loop because it isn’t immutable and therefore I can’t get the individual chars to form strings.
It seems like a very limited set of options for arrays at the moment. Is this going to be expanded upon during the update, perhaps a coverter to immutable arrays?
what you are trying to to is a job for a specific encoding, since there are many ways to store a string in a byte array. the VL library has imported the following tools from the .NET framework for it:
Forget it. Had to Trim the empties.
FileReader seems to be broken in the current alpha
that one was leaked prematurely…we’ll announce when it is ready.
latest alphas now have FileReader [IO] and FileWriter [IO]. both in byte and string versions. blogpost with more information pending…
Thanks, I tried it a little earlier today and I found that “FileName (Join)” crashes VL and vvvv :
To reproduce, start and Empty VL class. Try to set the “FileName (join)” node.
Problem Event Name: CLR20r3
Problem Signature 01: vvvv.exe
Problem Signature 02: 34.106.1986.0
Problem Signature 03: 5835ab78
Problem Signature 04: VL.CoreLib
Problem Signature 05: 0.43.19.61678
Problem Signature 06: 5835ace3
Problem Signature 07: 1d7
Problem Signature 08: 0
Problem Signature 09: System.StackOverflowException
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 2057
Additional Information 1: 4500
Additional Information 2: 45007255a30f5f72f9c39f09ad658d0a
Additional Information 3: 35b1
Additional Information 4: 35b145f427242b9eefbd723b6135564a"
There were some other slight issues with it, but I’ll have a deeper look
Confirmed, thanks. Will be fixed asap.
thx for report,
fixed in upcoming alpha