| |
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 |
Quote: 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.
I'll have to test this.. Could you mail me a work tune where this thing shows up? |
| |
Laxity
Registered: Aug 2005
Posts: 459 |
I just tried to test this 90 super command bug, but I can't reproduce it!.. I'm curious as to if you're setting the "kick repeated instruments" option in the pack to "yes" (this is default btw.).. This can be the reason for your problem, as super command 90 remains set until next instrument event. If repeated instruments are kicked, the packed tune will be inconsistant to the unpacked one, as some of them are suddenly missing... Anyway, please send me your workfiles if this is not the case! |
| |
dalezy
Registered: Apr 2002
Posts: 476 |
yeah, i always kick the repeated instruments .. sounds reasonable, i will try re-packing again when i'm home tonight. would be fun if it works, that could have spared me a few grey hairs the previous years too. =) |
| |
Laxity
Registered: Aug 2005
Posts: 459 |
Quote: yeah, i always kick the repeated instruments .. sounds reasonable, i will try re-packing again when i'm home tonight. would be fun if it works, that could have spared me a few grey hairs the previous years too. =)
hehe... It even says so in the docs for 20.g4 somewhere I think;) |
| |
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 =)
Just checked this problem, and I can't seem to reproduce.. All is fine and dandy here... ?? |
| |
Laxity
Registered: Aug 2005
Posts: 459 |
Uploaded the final. Changes since beta:
- Fixed a bug in the vibrato feel, that caused an overflow and made the note go out of tune..
- Fixed the syncroniztion (initialization) bug.
- Super command $Dx $yy set filter/pulse was wrongly documented in Beta text file!.
- Super command $Dx $yy now also accepts a x=2 value where yy will be set as the active
pulse program for the current channel
- F2 preview has been fixed to work. Still has a bug, the last note event will repeast every
two or three seconds if no input was registered by the player. This is a bit annoying, but
the live play feature works, so you can preview your instruments etc. Pressing F2 in the editor
will not clear the sid channels, so it's a good idea to stop the currently playing song (F3) before
pressing F2.
- A bug in the super command $dx has been fixed, that would cause the tempo to change if the $xx value
of the command was set to $f0 or above!
Sorry for the massive delay... work work work |
| |
Bamu®
Account closed
Registered: May 2005
Posts: 1332 |
Does anyone can write a nice (beginner) tutorial for it? |
| |
dalezy
Registered: Apr 2002
Posts: 476 |
laxity, great, gotta check it out on the weekend; having sound-preview enabled via f2 now is really awesome =) |
| |
dalezy
Registered: Apr 2002
Posts: 476 |
Quote: Just checked this problem, and I can't seem to reproduce.. All is fine and dandy here... ??
that problem is still there .. however, it doesn't cause a mess in the actual instrument setup, it's just a tad confusing. =) |
| |
Laxity
Registered: Aug 2005
Posts: 459 |
Which version of the JCH editor are you using?.. All works fine here, and I use 3.04 - as can be downloaded from www.vibrants.dk |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 - Next |
