Re: [xwax-devel] cue points
Brought to you by:
hills
From: Robert-André V. <ra....@ou...> - 2013-02-23 14:15:33
|
Am 23.02.2013 14:48, schrieb The Sighter: > Hey guys. Hi Sascha :) > > Good to see you have brought some ideas together. > > We had implemented Cue-Points in the past in our little xwaxed > modification. Its a shame i cant provide a screenshot of this running > version, since it is completely not on the current code base. > > I only want to let you u know, that i will start the reimplemention of > this stuff soon on the top of the current codebase. At the moment I want > to really stick at the method of storing all the cue-point information > in a .cue file at the same place of the audio file. I used torq for a while. It created a .tqd file for every audio file in the same location. This always resulted in a huge annoying mess :( I'd like it more if those files would be stored for example in a separate cue-folder. > > I will use your list of Information and will provide some in progress > information. > > > One additional Question (especially to Mark maybe): > > Quote:"Yes, you've hit on the lack of xwax storing its own data. At some > point this will need to be addressed" > > > Do you have any Ideas or concepts already, to give xwax a consistent way > for data in- and output? If yes i can make the cue-point-storing feature > fitting this design. > > > Thx for your work and communication guys > > Regards > Sascha Looking forward *thumbsup* > > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > > |