| |
Laxity
Registered: Aug 2005
Posts: 459 |
JCH NewPlayer 21.g4 beta
I febuary/march I decided to code a player for JCH's editor. Mostly because I was feeling like doing some tunes on the 64 again, after attending the X'2004 event. Basically I was annoyed by the tie-note syncronization problem with 20.g4 and just felt up to coding some 64 stuff again. For the past four, five months Drax has been testing the player, and given me some response as to what features to integrate into it and such. If there's any interest in trying out the player I'd release the present beta version with whatever bugs it suffers from. The player has been written from scratch and has some new features, and is roughly the same speed as the old one... So if people still use the JCH editor and find this interesing, please say so! I'd especially be interested in feedback in regards to bugs discovered and suggestions for features etc. |
|
... 54 posts hidden. Click here to view all posts....
|
| |
Laxity
Registered: Aug 2005
Posts: 459 |
Eh.. speed 0 doesn't affect live play, by the way.. I think you're talking about the SHIFT-B thing, where the sequences follow the play cursor.. That one goes crap when speeds are below 2, but the F2 function for previewing sounds etc. doesn't work with 21.b4.. I hope to fix it in the near future though! |
| |
_V_
Account closed
Registered: Jan 2002
Posts: 124 |
Yeah, I'm sorry - I realised the mix-up a few minutes ago and wanted to correct my post, but you beat me to it :). The F2 thing is something which I do use, but I guess you can circumvent it for now by using a test sequence and play those a few times until the it sounds okay, then copy it over to the actual sequence you were planning to use. Or something like that.
And I can understand your newfound motivation through X2004 - I went to X2001 and was really fueled by talking to guys like GRG, Reyn, Graham, WVL, Krill, my groupmates, etc. I so wanted to be at X2004 since the lineup of people was so brilliant (you were one of the "to meet" guys :), but I got stuck between leaving my old job at Germany and moving to university in Belgium. Just didn't have the time - major s*ckage. Oh well, maybe somewhere in the future, huh? :) |
| |
Laxity
Registered: Aug 2005
Posts: 459 |
Status report:
21.g4 final release is about ready, with the F2 sound preview thing working correctly and a few bugs fixed. If there's anybody who have comments or have found bugs that I haven't, this is the time to say the word. Final will be uploaded shortly, if noone replies with bugs or the like. |
| |
dalezy
Registered: Apr 2002
Posts: 476 |
sweet, looking forward to it.
i noticed a random bug (nothing that causes a hazard tho) - sometimes the follow-play option (shift+b) acts a little funky when the tune reached its end and starts all over. one of the tracks seems to lag by a few frames, thus causing a slight phase by playing a little slower than the remaining 2 tracks and sometimes the synch is totally off.
is that similar to what you mentioned in your buglist concering the synchronisation of the speed table?
i'm not sure how this can be reproduced, it mostly happened by random here. =) |
| |
Laxity
Registered: Aug 2005
Posts: 459 |
Hmm.. Wierd.. I think it's a different bug, but related in the sence that it has something to do with the player initialization being executed outside the IRQ, while the player update is inside the IRQ.. This can give syncronization problems, and does so - apparently with the crtl+B thing, and sometimes when you just press.. is it f1(??) to restart the tune in the editor... Anyway, there's a remedy for that, and I'll apply it before releasing the final! Thanks for responding! |
| |
dalezy
Registered: Apr 2002
Posts: 476 |
one thing just popped up here .. whenever i do some changes in the arpeggio-table, like putting more frames in the sound via shift+ins, the last bit of the following instrument in the instrument table changes, causing a mess in almost all the sounds.
could you fix that too? in 20.g4, the instrument table automatically updated whenever any changes in the arp-table have been done =) |
| |
tlr
Registered: Sep 2003
Posts: 1790 |
Pardon me for asking a stupid question, but which version of the JCH Editor should I use the player with?
There are loads of hacked up (or down?) versions. |
| |
Laxity
Registered: Aug 2005
Posts: 459 |
I would say the latest one by JCH.. Get it from http://www.vibrants.dk somewhere! I've not tested it with any hacked versions of the editor! |
| |
dalezy
Registered: Apr 2002
Posts: 476 |
i just found out that np-pack 5.4b comes along with the same bug(?) like the old packer when it comes to superslidekkomandotable-SR-changes.
the following thing ends up being inaudible and almost eaten up by the packer when i have an instrument setting like this:
00 66 80 f3 04 00 00 00
the supercommand for another instance of this instrument goes like this:
90 19
could it be that what the packer gets out is actually the right result and the sr sounds louder than it should in the editor? or does that happen because of the hardrestart or even the filter? i'm sadly technically challenged when it comes to things like that, but i noticed that the same thing occurs in older versions of the packer; i think i only managed to get around this problem with wisdom's packer for 20.g4 tunes, or doing a different instrument with the settings that i put in the supercommands. |
| |
Laxity
Registered: Aug 2005
Posts: 459 |
Quote: one thing just popped up here .. whenever i do some changes in the arpeggio-table, like putting more frames in the sound via shift+ins, the last bit of the following instrument in the instrument table changes, causing a mess in almost all the sounds.
could you fix that too? in 20.g4, the instrument table automatically updated whenever any changes in the arp-table have been done =)
What?.. Never had any problems with that!.. Which editor version are you using? |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 - Next |
