Fantom-G

SVQ file information??

SVQ file information??

19 Apr 2012, 19:12
does anybody have any inside info on the svq file format? it seems like it would take very little work to put together a simple program that copies songs + all associated phrases to another project. the same could be done for other song data but phrases would be a good start. i say it'd be 'easy' but that's assuming some knowledge as to how the svq files are formatted.

if i knew what the guys at Roland know it'd probably only take me a few days to make some sort of working solution. a few weeks to make it pretty & user friendly. but I'm just one guy..

the idea is simple:

- read all bytes of the file into a buffer. (IN)
    - make a new buffer(OUT)

    - begin reading IN byte by byte. Any bytes that don't represent 'which' phrase/sample is being used can be copied directly to the OUT buffer.

    - when you get to a chuck of data that represents 'which' phrase/sample is being used, add the value to a multidimensional array or equivalent & add a path to the associated file. you could also add a reference as to whether it is a sample or phrase.

    - here's the only tricky part but it's simple too.
    you will need to know the destination project folder. using that, we can look at the project for the first available phrase/sample in the corresponding folders. at that point we can determine our 'new' phrase/sample index. once we know that number we can translate it into whatever bytes the fantom actually uses internally. we will save this value in our array along with the rest of the data.

    - at this point instead of 'copying' the original value of which phrase/sample was used, we will use our 'new' value.

    each individual phrase/sample only needs to be added once. each time we find one. first check to see whether we've found it already. if so, just use the 'new' phrase/sample value & proceed..


    the above is a detailed description of how I'd actually go about doing it but the process is so simple it could be described as follows:

    - continue reading IN byte for byte and:

    - 'copy' ANY bytes that do not represent 'which' phrase/sample was used directly from IN to OUT.

    - 'replace' ALL bytes that do represent which phrase/sample was used by substituting the 'new' value.

    there are so few necessary changes to the original data, I'd be confident that my resulting svq file would not be corrupt.

    but if i have to try to crack unknown encryption, then reverse engineer everything to figure it out, it would take more time than i have to give.. :(
    Last edited by parker.bobby on 20 Apr 2012, 00:51, edited 1 time in total.

    Re: SVQ file information??

    19 Apr 2012, 20:13
    i was thinking about something earlier. it really doesn't require another thread since it's kind of on topic..

    with so many user requests related to 'integration' with other gear & a lack of file handling capabilities & processing power on workstations in general... im not gonna argue that 'better' file handing is possible with these machines is possible but, moving 2000 files totalling over 4 gigs has never been easier than it is with your quad core laptop :)..

    that said.. i wish Roland would patch the G's file handling situation with some simple tools. again, im not gonna argue with the people that want 'real' os updates.. but, i'd rather have 13 'simple' software programs that i could use externally. rather than nothing at all. not an elegant solution either, it'd be nicer to have a single comprehensive file management program but bigger projects take longer.. & longer, & longer, until they arrive unfinished or late, or never at all..

    the reason I'm leaning towards the pc/mac solution is because i know development would be easier on them. for many reasons, the most important is the fact that the programs are, 'unimportant', relatively speaking. an os update cannot have 'new' bugs or imagine the complaints then? it happens, we know it.. so, you gotta put in lots of testing time when you make a change to a large system. especially when it may make the machine less usable than before.. software doesn't have this problem. if file manager v2 has bugs, don't use it. but you can keep using your fantom..

    i was reading the facebook fantom g page & it seems like a lot of folks or enjoying using ipads with their workstations. many made requests that there be ipad apps & the like for future fantoms.. with that kind of feedback it's a wonder why you'd stay away from solutions like that. they could be less costly than trying to work with a powerful but difficult os of the latest generation of gear.

    my reasons for wanting a workstation are likely different from theirs. i have no desire to use my workstation in combination with an ipad or laptop. i thought that's what controllers were for. It seems like you'd have the best of both worlds. all the power of a true DAW with all the headache of a MIDI setup.. of course, if manufacturers do make their gear interface freindly then setup is simple & there are no headaches. but they don't all conform..

    like i said, my reasons may differ from yours. i bought a workstation because it is a single item that has many useful tools for audio production all in one box. keys, controllers, sounds, sampling, fx & mixing.. on the g these things work well in both live & studio situations. i use it for 'studio in a box'. i often set it on my coffee table or at the end of my big chair & have at it.. i used to do the same with my laptop & little edirol mini controller too. this took up less space, had more power, & barely any cables to hook up so it was 'neat'. but still, my workstation has more keys & cool pads that serve as 'super controllers' if you use them right..

    man, i get to rambling... long story short, i think most folks are more prone to hook their workstation up to a computer than i am & even I'm willing to move the USB drive to the pc when necessary. that said, i can't imagine anyone that'd refuse to use an app that helps with file handling..

    peace.

    ← Back to Fantom-G